SCMU is an in-house alternative to Oracle's Application Change Management Pack (ACM) developed by Santos, an Australian oil and gas company, to manage customizations across their Oracle E-Business Suite environment. SCMU uses shell scripts to create, migrate, and back out changes through a menu-driven interface, providing version control and automation benefits similar to ACM but without the cost and complexity of Oracle Enterprise Manager. The presentation demonstrated SCMU's functionality and discussed plans to review customizations ahead of an upcoming Oracle EBS R12 migration.

1. SCMU: our alternative to Application
Change Management Pack
Tony Scholefield
Santos
17 August 2010
The most comprehensive Oracle applications & technology content under one roof

2. Agenda
• About Santos
• Application Change Management Pack
• Why SCMU?
• What is SCMU?
• Demonstration / Screen dumps
• The future
• Questions

3. About Santos
• We are:
– Oil & Gas Exploration & Production
– An Australian company providing energy for Australia
and Asia
• Offices (using Oracle) in Adelaide, Brisbane, Perth, Jakarta,
Gladstone and Roma
• Field sites in Cooper Basin, Southern Queensland, offshore WA,
offshore Victoria and in Indonesia
– Approximately 2,000 employees, numerous contractors

4. About Santos
• We run:
– Oracle E-Business Suite Release 11i.10.2 (+)
– Financials – GL, PA, FA, AR, AP, CM, i-Expenses, Treasury
– Supply – PO, IN, OM, i-Procurement, Sourcing, Intelligence
– Human Resources – HR, Payroll, OTL, OLM, Self Service,
iRecruitment
– Numerous customisations
– Typically migrate 30 – 40 changes to production each month

5. Audience survey
• Have you seen my customisations
presentatation?
• What version of EBS are you running?
• What is your role?
• Do you use OEM?
• Do you use ACM?

6. Application Change Management Pack
• Oracle Application Change Management Pack (ACP) is an add-on
component to Application Management Pack (AMP) and Oracle
Enterprise Manager Grid Control (OEMGC) that manages and
monitors customizations for Oracle E-business suite applications.
OEMGC
Customization
AMP Manager
ACP Patch Manager
Setup Manager

7. How ACM works
• Check in customization into file version control system
(SVN).
• In Customization Manager, use check in code within
SVN to create a package (patch).
• In Patch Manager, deploy patch created to target
instances.
• In Setup Manager, migrate any additional functional
setups to target instances.

8. Why SCMU?
• We do not have OEM and therefore ACM
– Cost?
– DBAs resistant to change?
– Bad initial impression / experience?
• We do many changes most months
• Improve migration process
– Efficient for DBAs
– Reduce errors

9. What is SCMU?
• Tool developed in-house
• Unix shell scripts
• Installed on DEV/TEST and PROD servers
• Provides ability to
– Apply patches
– Dependencies
– Back out
– Automated

10. Main menu
+======================================+
| Santos Change Management Utility |
+======================================+
1) Create New Change
2) Create Tar File
3) Apply a Change
4) Create New Release
5) Copy a Change from Remote Server
6) Copy a Release from Remote Server
7) Implement a Release
8) Archive a Release
9) View a Release
Q) Quit

11. Demonstration
• Demonstrate the SCMU functionality
(fingers crossed)
• I have included some screen dumps for
the post-conference version

12. Create a change

13. Template files

14. Create a TAR file

15. The future
• R12 April (Easter) or August 2011
• Review / reduce the number of
customisations
• Develop a Java interface (?)

16. Questions

17. Tell us what you think…
• http://feedback.insync10.com.au
• Tony.Scholefield@Santos.com