9.
Version Control Have Code, Patches
& Setups
synchronized
across all
environments?
• Why this code works in one environment and not in other?
• Is this the right version of code for this environment?
• Who/when migrated this code?
• Who approved?
9 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

10.
Global teams Have Code, Patches
& Setups
synchronized
across all
environments?
• Who changed the code? Why?
• Who provided business requirement?
• Who owns the code?
• How the team will communicate?
• How to track changes?
10 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

11.
Documentation Have Code, Patches
& Setups
synchronized
across all
environments?
• Where and how to document?
• Who owns the documentation?
• How does it get updated?
• How do these updates get migrated across?
11 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

29.
Code Deployment
• Developer specifies Code pack version to be migrated
• Code pack gets checked out by automated process
Checkout • Here on every action in this process gets logged for audit purposes
Code Pack
• Check out specified version of code unit
• Copy to destination folder
• Deploy to specified schema
For every line
in Code Pack • Perform migration options as defined in code pack for that code unit
• At the end of this deployment, a notification email is sent to all stakeholders
• Deployment logs are maintained for the life of the environment
Communicate
29 Oracle OpenWorld 2010 Managing Oracle EBS Customizations