Tuesday May 10, 2011

Part 19: EBS Customizations – Estimate to the best of your Knowledge

CEMLI estimation is a task which is required from time to time during the project. You, as team lead, shall be able to determine development effort quickly, but always in a standardized and repeatable way. Such an easy calculation sheet helps you a lot!

It is suggested to store the estimation results and related assumptions together with the CEMLI documentation itself.

[Read More]

Friday Apr 29, 2011

Part 18: EBS Customizations – From AIM to OUM

Oracle Unified Method has taken over all legacy methods, therefore also the CEMLI tasks and documents had to be adapted slightly. Use Cases, one of the key additions to OUM, will from now on be used to define the expected CEMLI functionality.[Read More]

Thursday Apr 21, 2011

Part 16: EBS Customizations – Just package everything!

There isn't a single solution for packaging, it mainly depends on the project phase and the way how you manage releases and bug fixes. The only advise here is: discuss with your release / deployment manager which one is the best to fulfil your individual project needs. It has not to be always the well known option 1. If you like to try out option 2 or 3, keep in mind that you have to implement a good change control in your deployment tree; there are some prerequisites to fulfil.[Read More]

Friday Apr 15, 2011

Part 15: Packaging EBS Customizations - What shall be part of?

Our installation packages usually contain only the minimum. But additional scripts for validation, deactivation and registration steps could improve the customization quality and finally save a lot of time. If you like to adapt one of these suggestions please define a good procedure how to handle exactly.[Read More]

Tuesday Apr 12, 2011

Part 14: EBS Customizations - Multi Language, Messages, Help Files and Training Guide

There are a number of surrounding customization activities to improve the usability. Additionally, this will allow first and/or second level support faster reaction. Invest in a clear project procedure to address such additional 'material' like message structures, solution databases, help files and UPK topics.

Although it is a customization (what we discuss in this blog series), it should be handled in the same way than any other (project) application standard.

[Read More]

Wednesday Apr 06, 2011

Part 13: Versioning EBS Customizations

Versioning is a must in software development projects. Make sure that you enable tag replacement to update the file individual version automatically in the header. The directory structure shall support individual CEMLI folders, but also packaging.

Put also the deployment packages under release (version) control, define an additional folder and place all CEMLI packages there.

[Read More]

Tuesday Mar 29, 2011

Part 12: Link EBS Customizations and Business Processes

Although customizations are often developed independently, a visual link to the related business process activity shall be maintained. This information is then distributed across the whole implementation team, to get reviewed and improved when needed.[Read More]

Friday Mar 25, 2011

Part 11: EBS Customizations - The Documentation Phase

A lot of common documentation can be generated by utilizing BI Publisher reports. Instead of updating a documentation again and again, such a cumbersome step can take advantage of generated information. Needless to say, that additional text has to be written separately to complete the common MD.070 document.[Read More]

Tuesday Mar 22, 2011

Part 10: The EBS Development Part – Just some Hints

Although custom development is rather seen as “just an addition to the EBS standard”, don’t underestimate the activities and prepare the environment accordingly.[Read More]

Saturday Mar 19, 2011

Part 9: EBS Customizations, how to track

Building the bridge from Gap analyse to the development has to be done in a controlled way. Usually the information is provided differently, but it is suggested to collect all requirements centrally. Oracle APEX is a great solution to enter and maintain such information in a structured, but flexible way. APEX helped me a lot to work with distributed development teams during the complete development cycle.[Read More]

Friday Mar 18, 2011

Part 8: How to name EBS Customizations

Technical and functional customized objects should always follow a naming convention. This naming convention should be project wide, and only one place shall be used to maintain (like in a Wiki). If the name is for the end user, rather put a customization identifier at the end; if it is an internal name, start with XX...[Read More]

Wednesday Mar 16, 2011

Part 7: EBS Modifications and Flagged Files in R12

Flagged Files is a very helpful EBS R12 technique when analysing patches. Implement a procedure within your development process to maintain such flags. Let the DBA run the patch analysis in an environment with a similar patch and customization level as your current production.[Read More]

Saturday Mar 12, 2011

Part 6: EBS Extensions vs. Modifications

Extensions and Modifications have to be handled differently during their lifecycle. Modifications implicate a much higher risk and should therefore be reviewed more frequently. Good cross references allow you to give clear advise for the testing activities.[Read More]

Thursday Mar 10, 2011

Part 5: Choose the right Tool - or - why

Oracle EBS offers plenty of alternatives to implement customizations. Create and maintain a decision tree to support the design process. Do not leave the decision just on developer side. Limit the number of alternative solutions as best as possible; choose one which is the most appropriate also from future maintenance perspective.[Read More]

This blog is all about Best Practice and suggested procedures when managing customizations within an EBS project or implementation.


« July 2016