Managing Oracle EBS Customizations



Driving the Efficient Enterprise




                     Samir Deshpande   - Oracle...
Agenda

    •    Why manage customizations?

    •    Typical customizations for E-Business Suite

    •    Challenges man...
Why manage customizations?
    •    Improve operational Efficiency

    •    Reduce operating expenses

    •    Process a...
Typical Customizations
•     Reports
       •      Customer facing outputs
       •      Management reports
       •      ...
IT Challenges
•       Environment Strategy
         •      Dev/SIT/FIT/Perf Test etc.

•       System Dynamics

•       In...
Environment Strategy                                                     Have Code, Patches
                              ...
System Dynamics                                                          Have Code, Patches
                              ...
Interdependencies                                             Have Code, Patches
                                         ...
Version Control                                                  Have Code, Patches
                                      ...
Global teams                                              Have Code, Patches
                                             ...
Documentation                                                Have Code, Patches
                                          ...
Tracking, migrating, testing                                    Have Code, Patches
                                       ...
How to manage EBS customizations?




13   Oracle OpenWorld 2010       Managing Oracle EBS Customizations
Strategy
                             Communicate



                              Automate



                           ...
Strategy - Simplify

•    People
        •     Environment ownership
        •     Code ownership
        •     Roles and ...
Strategy - Standardize

•    People
        •     Role based

•    Processes
        •     Environment management
        ...
Strategy - Automate

•    Processes
        •     Standard process flows
        •     Environment management


•    Techn...
Strategy - Communicate

•    People
        •     Stakeholder list and communication plan

•    Process
        •     Envi...
Key Success Factors
      •     Strong support from Management

      •     Willingness to change

      •     Agreed docu...
Implementing the strategy to address IT
Challenges
•        Environment Strategy                          Significant impa...
Environment Strategy                                                     Have Code, Patches
                              ...
Environment Strategy               Periodic refresh from Production Clone Stage
                                          ...
Environment Strategy – 7 Steps

                                    Defined environment purpose


                  Establ...
Environment Strategy – 7 Steps defined
•        Defined environment purpose
•        Establish Release management process ...
Environment Ownership
                                                 Env            Role                           Owner...
Benefits of Environment Management
•        OPEX reduction
         •  Resource optimization [hardware/people]
         • ...
Code migration

•        Pre Requisites

         •    Finalize version control repository for code and documentation

   ...
Code Packaging
           Code Pack                 •   Code Pack is identified by a unique
                              ...
Code Deployment

                   • Developer specifies Code pack version to be migrated
                   • Code pack ...
Code Migration
      Dev Environment                                        FIT Environment



                           ...
Code migration
•        SCM Team defines and manages migration process

•        Developer responsible for code developmen...
Benefits
•        Process standardization and simplification across releases

•        Installing sense of ownership and a...
Patch and setup migration




         These processes should be similar to Code migration process




33   Oracle OpenWor...
34   Oracle OpenWorld 2010   Managing Oracle EBS Customizations
THANK YOU!

Authors
         •    Samir Deshpande
                 •     Samir_Deshpande@dell.com
                 •     C...
To learn more about how Dell can help you
drive an Efficient Enterprise visit:

• Dell’s onsite TSR for a
  free quote

• ...
Upcoming SlideShare
Loading in...5
×

Managing Oracle EBC Customizations

2,318

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,318
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
106
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Managing Oracle EBC Customizations

  1. 1. Managing Oracle EBS Customizations Driving the Efficient Enterprise Samir Deshpande - Oracle EBS Technical Architect & Program Manager Vrishab Kakade – Oracle EBS Apps DBA
  2. 2. Agenda • Why manage customizations? • Typical customizations for E-Business Suite • Challenges managing customizations • Four step strategy to manage customizations • Implementing the strategy • Q&A 2 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  3. 3. Why manage customizations? • Improve operational Efficiency • Reduce operating expenses • Process automation • Improved production uptime • Installing sense of ownership • Reduced inconsistencies and risks • Brings clarity and transparency to business • Better Audit Controls @Dell (from just - 2 global EBS systems) • Over 1500 customizations • Over 35 non prod environments • Over 200 servers 3 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  4. 4. Typical Customizations • Reports • Customer facing outputs • Management reports • Transactional reports • Reconciliation reports • Forms • Custom functionality • Interfaces • Integration with various external systems • Conversions • Legacy environments data conversion • Data warehousing • Enhancements/Extensions • Addition of new functionality • Personalization • Forms personalization @Dell (from just - 2 global EBS systems) • 500 RICE components 4 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  5. 5. IT Challenges • Environment Strategy • Dev/SIT/FIT/Perf Test etc. • System Dynamics • Interdependencies › Patch/Code/Setups • Version control • Global Teams • Documentation • Tracking, migrating, testing and certifying Significant impact of customizations on major upgrades such as 11i to R12 5 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  6. 6. Environment Strategy Have Code, Patches & Setups synchronized across all environments? Env 1 Dev env for production support and project 2 Env 2 FIT Env for project 1 and Dev for project 3 Env 3 SIT production support then CRP3 for project 2 DR Production Env 4 UAT for project 1 and 2 Env 5 Dev env for project 1 Env 6 Perf Test for project 1 Env 7 SIT production support then CRP3 for project 2 Env n Training needs 6 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  7. 7. System Dynamics Have Code, Patches & Setups synchronized across all environments? Business Change Request •New functionality •Enhancements Production Oracle Patches Defects •PSU •Functionality issues •Upgrades •Up/downstream system needs Project Defects •Std functionality issues •Coding issues 7 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  8. 8. Interdependencies Have Code, Patches & Setups synchronized across all environments? Code, Patch, CR, Defects they could be interdependent – how to identify and manage these dependencies? 8 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  9. 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. 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. 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
  12. 12. Tracking, migrating, testing Have Code, Patches & Setups and certifying synchronized across all environments? • How to track dependencies? • What to migrate? When? • Who migrates? How? • How to test and certify the change migration? 12 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  13. 13. How to manage EBS customizations? 13 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  14. 14. Strategy Communicate Automate Standardize Simplify 14 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  15. 15. Strategy - Simplify • People • Environment ownership • Code ownership • Roles and responsibilities • Processes • Environment management • Code build and deploy • Patches/setups migration and tracking • Cloning • On Boarding/off boarding • Technology • Servers/environments • Code and documentation repository 15 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  16. 16. Strategy - Standardize • People • Role based • Processes • Environment management • Code build and deploy • Patches/setups migration and tracking • Cloning • On Boarding/off boarding • Audits • Technology • Servers/environments • Code and documentation repository 16 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  17. 17. Strategy - Automate • Processes • Standard process flows • Environment management • Technology • Cloning • Code/Patch/Setup deployment 17 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  18. 18. Strategy - Communicate • People • Stakeholder list and communication plan • Process • Environment strategy • Environment management • Code/Document repository and Management processes • Software configuration management processes • Audit controls • Technology • Portal – single point of entry 18 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  19. 19. Key Success Factors • Strong support from Management • Willingness to change • Agreed documentation methodology • Adequate communication • Periodic reviews and alignment with strategy 19 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  20. 20. Implementing the strategy to address IT Challenges • Environment Strategy Significant impact of customizations on • Dev/SIT/FIT/Perf Test etc. major upgrades such as 11i to R12 • System Dynamics • Interdependencies › Patch/Code/Setups • Version control • Global Teams • Documentation • Tracking, migrating, testing and certifying 20 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  21. 21. Environment Strategy Have Code, Patches & Setups synchronized across all environments? Env 1 Dev env for production support and project 2 Env 2 FIT Env for project 1 and Dev for project 3 Env 3 SIT production support then CRP3 for project 2 DR Production Env 4 UAT for project 1 and 2 Env 5 Dev env for project 1 Env 6 Perf Test for project 1 Env 7 SIT production support then CRP3 for project 2 Env n Training needs 21 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  22. 22. Environment Strategy Periodic refresh from Production Clone Stage Prod Clone Support (PCS) Production Support Perf Prod Dev FIT SIT UAT Production Test Staging DR Release 1 Test Prod Dev FIT SIT @Dell Other • 300+ interfaces to Release 2 Environments external systems • End to end testing? Dev FIT SIT Training @Dell • Several simultaneous in- SandBox flight projects Release ‘n’ Conversion Each release may have one or more Dev FIT SIT Patch projects/CRs/Patches @Dell DEVELOPMENT • Virtualization 22 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  23. 23. Environment Strategy – 7 Steps Defined environment purpose Establish Release management process to manage all CR/patching etc Develop Environment refresh strategy Define environment refresh cycles Establish environment sync up plan Environment recycling plan Audit Controls 23 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  24. 24. Environment Strategy – 7 Steps defined • Defined environment purpose • Establish Release management process to manage all CR/patching etc • Develop Environment refresh strategy • Automate cloning from Prod to Production Clone Support(PCS) • Perform all critical activities such as scrambling data, password changes, disable production outbound notifications, database links, cleanup etc. on PCS • All the environments refresh/cloning to be performed from PCS environment backup • Define environment refresh cycles • Production staging – refresh weekly - source production • PCS – refresh periodically – source production • Release environments – refresh initially/on demand – source PCS • Support environments – refresh periodically – source PCS • Training – prior to training start – source UAT • All TEST environments – refresh prior to test cycle/on demand – source PCS • Establish environment sync up plan • After go-live of every release; within 30-45 days all DEV environments to be synchronized • Environment recycling plan • Production support environments not recycled • Release 1 environments can be used for Release 3 • Release 2 environments can be used for Release 4 • Audit Controls • Data scrambling, TDE/VPD, password changes, audit documentation etc done in PCS • Clearly defined environment management and ownership plans 24 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  25. 25. Environment Ownership Env Role Owner Patch •DBA Env Owner •DBAs •SCM group • Environment ownership DEV •Dev Env Owner •Dev Managers • Role based •SCM group • Has final say FIT •FIT Env Owner •Business Analyst Mgr • Responsible for any audits •SCM group • Responsible for access control SIT •SIT Env Owner •Enterprise Testing Mgr • Available in the region •SCM Group UAT •UAT Env Owner •Business (PDM) •SCM Group Perf Test •PT Owner •Enterprise Testing Mgr •SCM Group Role Responsibility Environment Owner • Decides on environment downtime • Authorizes code/patch migration to this environment • Approves environment access to users • Environment escalation point SCM Group • Implement Change control processes • Ensure that the environment is under SCM process 25 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  26. 26. Benefits of Environment Management • OPEX reduction • Resource optimization [hardware/people] • Predefined Refresh cycles • Recycling plan • Process simplification and automation • Improved cloning times • Opportunity to automate cloning • Improved production uptime • Predefined release cycles • Reduction in adhoc downtime requests • Well defined communication plan • Pre defined release cycles – communicated well in advance • Predefined environment ownership and escalation paths • Installing sense of ownership and accountability • Better Audit Controls • Well defined environment ownerships • Standard environment management process • Controlled environment access 26 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  27. 27. Code migration • Pre Requisites • Finalize version control repository for code and documentation • Clearly define repository ownership and management processes • Version control system directory tree structure similar to EBS app tier • Example • XXPO_TOP structure should be similar to PO_TOP • XXPO_TOP directory structure on file systems and version control system should be same @Dell (from just - 2 global EBS systems) • 500+ RICE components 27 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  28. 28. Code Packaging Code Pack • Code Pack is identified by a unique name and version number DDL/DML • Code pack contains • “Code Unit” to be migrated • Version number of “Code Unit” Package/Procedures/SQLs • Destination directory • Destination Schema Reports • Migration options • Sequence of “Code Unit” defines Forms inter dependencies • Code Packs are created and maintained by developers Java • Developers migrate code to all environments Personalization's • Developer owns one or more “Code Packs” Shell scripts • Every “Code Pack” has only one owner 28 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  29. 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
  30. 30. Code Migration Dev Environment FIT Environment Developer Env - Developer Owner - approved Developer- Migration YES FIT testing ON YES Allow YES Migrate code successfu team code? code in? l? NO NO Env Owner - Develop Code and code NO Test pack- by developer Successf ul? Start ON YES UAT Environment Env Owner - Repeat till Allow production & NO code in? retrofitting Migration changes to all successfu other UAT testing l? team YES environments Developer- Migrate code YES 30 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  31. 31. Code migration • SCM Team defines and manages migration process • Developer responsible for code development and building code packs • Developer owns code migration to all environments • Ensures right version gets migrated • Identifies any defects/dependencies • Repeatable process • Environment owner approves code entry and exit • Minimizes accidents • Ensures code accuracy • Shared Responsibility and ownerships • Same process across all releases [refer to environment strategy slide] • Audit • Process is pre approved by all stakeholders • Properly documented for audit purposes 31 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  32. 32. Benefits • Process standardization and simplification across releases • Installing sense of ownership and accountability • Opportunity for code migration automation • Reduced inconsistencies • Better audit control • Improved code migration efficiency and reduced risks • Reduced downtime • Brings clarity and transparency to business • Optimize resources 32 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  33. 33. Patch and setup migration These processes should be similar to Code migration process 33 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  34. 34. 34 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  35. 35. THANK YOU! Authors • Samir Deshpande • Samir_Deshpande@dell.com • Cell: 512-466-3822 • Cell: 412-89-SAMIR • Vrishab Kakade • Vrishab_Kakade@dell.com • Cell:512-484-6097 • Cell:317-292-6047 35 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  36. 36. To learn more about how Dell can help you drive an Efficient Enterprise visit: • Dell’s onsite TSR for a free quote • Michael Dell’s keynote on Wednesday at 8 a.m. • One of Dell’s 20 conference sessions • www.dell.com/oracle 36 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×