Вы находитесь на странице: 1из 36

Managing Oracle EBS Customizations

Driving the Efficient Enterprise

Oracle EBS Customizations Driving the Efficient Enterprise Samir Deshpande - Oracle EBS Technical Architect &

Samir Deshpande

- Oracle EBS Technical Architect & Program Manager Vrishab Kakade – Oracle EBS Apps DBA

Agenda

Why manage customizations?

Typical customizations for E-Business Suite

Challenges managing customizations

Four step strategy to manage customizations

Implementing the strategy

Q&A

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
@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

• Over 35 non prod environments • Over 200 servers 3 Oracle OpenWorld 2010 Managing Oracle

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

• Addition of new functionality Personalization • F o r m s p e r s
• Addition of new functionality Personalization • F o r m s p e r s

Forms personalization

@Dell (from just - 2 global EBS systems) • 500 RICE components
@Dell (from just - 2 global EBS systems)
• 500 RICE components

4

Oracle OpenWorld 2010

Managing Oracle EBS Customizations

(from just - 2 global EBS systems) • 500 RICE components 4 Oracle OpenWorld 2010 Managing

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
Significant impact of customizations on
major upgrades such as 11i to R12

Environment Strategy

Env 1 Dev env for production support and project 2
Env 1
Dev env for production support and project 2
FIT Env for project 1 and Dev for project 3 Env 2
FIT Env for project 1 and Dev for project 3
Env 2
SIT production support then CRP3 for project 2 Env 3
SIT production support then CRP3 for project 2
Env 3
UAT for project 1 and 2 Env 4
UAT for project 1 and 2
Env 4
Env 5 Dev env for project 1
Env 5
Dev env for project 1
Perf Test for project 1 Env 6
Perf Test for project 1
Env 6
SIT production support then CRP3 for project 2 Env 7 Env n Training needs
SIT production support then CRP3 for project 2
Env 7
Env n
Training needs
Have Code, Patches & Setups synchronized across all environments?
Have Code, Patches
& Setups
synchronized
across all
environments?
DR Production
DR
Production
Have Code, Patches & Setups synchronized across all environments?
Have Code, Patches
& Setups
synchronized
across all
environments?

System Dynamics

Business Change Request •New functionality •Enhancements Production Defects Oracle Patches •PSU •Upgrades
Business
Change
Request
•New functionality
•Enhancements
Production
Defects
Oracle Patches
•PSU
•Upgrades
•Functionality
issues
•Up/downstream
system needs
Project
Defects
•Std functionality
issues
•Coding issues

7

Defects •Std functionality issues •Coding issues 7 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

Oracle OpenWorld 2010

Managing Oracle EBS Customizations

Interdependencies

Have Code, Patches & Setups synchronized across all environments?
Have Code, Patches
& Setups
synchronized
across all
environments?

Code, Patch, CR, Defects they could be interdependent – how to identify and manage these dependencies?

– how to identify and manage these dependencies? 8 Oracle OpenWorld 2010 Managing Oracle EBS

Version Control

Version Control Have Code, Patches & Setups synchronized across all environments? • Why this code works
Have Code, Patches & Setups synchronized across all environments?
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?

• Who/when migrated this code? • Who approved? 9 Oracle OpenWorld 2010 Managing Oracle EBS

Global teams

Who changed the code? Why?

Have Code, Patches & Setups synchronized across all environments?
Have Code, Patches
& Setups
synchronized
across all
environments?

Who provided business requirement?

Who owns the code?

How the team will communicate?

How to track changes?

How the team will communicate? • How to track changes? 10 Oracle OpenWorld 2010 Managing Oracle

Documentation

Have Code, Patches & Setups synchronized across all environments?
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?

get updated? • How do these updates get migrated across? 11 Oracle OpenWorld 2010 Managing Oracle
Have Code, Patches & Setups synchronized across all environments?
Have Code, Patches
& Setups
synchronized
across all
environments?

Tracking, migrating, testing and certifying

How to track dependencies?

What to migrate? When?

• How to track dependencies? • What to migrate? When? • Who migrates? How? • How

Who migrates? How?

How to test and certify the change migration?

How? • How to test and certify the change migration? 12 Oracle OpenWorld 2010 Managing Oracle
How? • How to test and certify the change migration? 12 Oracle OpenWorld 2010 Managing Oracle

How to manage EBS customizations?

Strategy

Communicate Automate Standardize Simplify
Communicate
Automate
Standardize
Simplify
Strategy Communicate Automate Standardize Simplify 14 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

14 Oracle OpenWorld 2010

Managing Oracle EBS Customizations

Strategy - Simplify

People

Strategy - Simplify • People • Environment ownership • Code ownership • Roles and responsibilities •

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

Strategy - Standardize

People

Strategy - Standardize • People • Role based • Processes • Environment management • Code build

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

Strategy - Automate

Processes

Strategy - Automate • Processes • Standard process flows • Environment management • Technology • Cloning

Standard process flows

Environment management

Technology

Cloning

Code/Patch/Setup deployment

Strategy - Communicate

People

Strategy - Communicate • People • Stakeholder list and communication plan • Process • Environment strategy

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

Key Success Factors

• Strong support from Management • Willingness to change • Agreed documentation methodology • Adequate
• Strong support from Management
• Willingness to change
• Agreed documentation methodology
• Adequate communication
• Periodic reviews and alignment with strategy

Implementing the strategy to address IT Challenges

• Environment Strategy • Dev/SIT/FIT/Perf Test etc. Significant impact of customizations on major upgrades such
• Environment Strategy
• Dev/SIT/FIT/Perf Test etc.
Significant impact of customizations on
major upgrades such as 11i to R12
• System Dynamics
• Interdependencies
Patch/Code/Setups
• Version control • Global Teams • Documentation • Tracking, migrating, testing and certifying
• Version control
• Global Teams
• Documentation
• Tracking, migrating, testing and certifying

20 Oracle OpenWorld 2010

Managing Oracle EBS Customizations

Documentation • Tracking, migrating, testing and certifying 20 Oracle OpenWorld 2010 Managing Oracle EBS Customizations
Have Code, Patches & Setups synchronized across all environments?
Have Code, Patches
& Setups
synchronized
across all
environments?

Environment Strategy

Env 1 Dev env for production support and project 2 FIT Env for project 1
Env 1
Dev env for production support and project 2
FIT Env for project 1 and Dev for project 3
Env 2
SIT production support then CRP3 for project 2
Env 3
DR
Production
UAT for project 1 and 2
Env 4
Env 5
Dev env for project 1
Perf Test for project 1
Env 6
SIT production support then CRP3 for project 2
Env 7
Env n
Training needs

Environment Strategy

Periodic refresh from Production Clone Stage Prod Clone Support (PCS) Production Support Perf Prod Dev
Periodic refresh from Production Clone Stage
Prod Clone
Support (PCS)
Production Support
Perf
Prod
Dev
FIT
SIT
UAT
Production
Test
Staging
DR
Release 1
TestTest
ProdProd
Dev
FIT
SIT
@Dell
Other
Release 2
Environments
• 300+ interfaces to
external systems
• End to end testing?
Dev
FIT
SIT
Training
@Dell
SandBox
• Several
simultaneous in-
flight projects
Release ‘n’
Conversion
Dev
FIT
SIT
Each release may
have one or more
projects/CRs/Patches
Patch
@Dell
DEVELOPMENTDEVELOPMENT
Virtualization

22 Oracle OpenWorld 2010

Managing Oracle EBS Customizations

Patch @Dell DEVELOPMENTDEVELOPMENT • Virtualization 22 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

Environment Strategy – 7 Steps

Defined environment purpose Establish Release management process to manage all CR/patching etc Develop Environment
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

sync up plan Environment recycling plan Audit Controls 23 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

Environment Strategy – 7 Steps defined

• Defined environment purpose • Establish Release management process to manage all CR/patching etc •
• 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

Environment Ownership

• Environment ownership • Role based • Has final say • Responsible for any audits
• Environment ownership
• Role based
• Has final say
• Responsible for any audits
• Responsible for access control
• Available in the region

Env

Role

Owner

Patch

DBA Env Owner SCM group

DBAs

DEV

Dev Env Owner SCM group

Dev Managers

FIT

FIT Env Owner SCM group

Business Analyst Mgr

SIT

SIT Env Owner SCM Group

Enterprise Testing Mgr

UAT

UAT Env Owner SCM Group

Business (PDM)

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

• Ensure that the environment is under SCM process 25 Oracle OpenWorld 2010 Managing Oracle EBS

Benefits of Environment Management

• OPEX reduction • Resource optimization [hardware/people] • Predefined Refresh cycles • Recycling plan •
• 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

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
@Dell (from just - 2 global EBS systems)
• 500+ RICE components

Code Packaging

Code Pack DDL/DML Package/Procedures/SQLs Reports Forms Java Personalization's Shell scripts
Code Pack
DDL/DML
Package/Procedures/SQLs
Reports
Forms
Java
Personalization's
Shell scripts

Code Pack is identified by a unique name and version number

Code pack contains

“Code Unit” to be migrated

Version number of “Code Unit”

Destination directory

Destination Schema

Migration options

Sequence of “Code Unit” defines inter dependencies

Code Packs are created and maintained by developers

Developers migrate code to all environments

Developer owns one or more “Code Packs”

Every “Code Pack” has only one owner

28 Oracle OpenWorld 2010

Managing Oracle EBS Customizations

Packs” • Every “Code Pack” has only one owner 28 Oracle OpenWorld 2010 Managing Oracle EBS

Code Deployment

• Developer specifies Code pack version to be migrated • Code pack gets checked out
• 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

are maintained for the life of the environment Communicate 29 Oracle OpenWorld 2010 Managing Oracle EBS

Code Migration

Dev Environment FIT Environment Developer Env - Developer Owner - Developer- Migration FIT testing approved
Dev Environment
FIT Environment
Developer
Env
-
Developer
Owner -
Developer-
Migration
FIT testing
approved
YES
YES
Allow
YES
Migrate code
successfu
team
code?
code in?
l?
NO
NO
Env
Owner -
Develop Code and code
pack- by developer
NO
Test
Successf
ul?
Start
UAT Environment
Env
Owner -
Repeat till
production &
retrofitting
changes to all
other
environments
Allow
NO
code in?
Migration
successfu
UAT testing
l?
YES
team
Developer-
Migrate code
YES
30
Oracle OpenWorld 2010
Managing Oracle EBS Customizations
ON
ON
YES

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

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

Patch and setup migration

These processes should be similar to Code migration process

34 Oracle OpenWorld 2010 Managing Oracle EBS Customizations

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

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

of Dell’s 20 conference sessions • www.dell.com/oracle 36 Oracle OpenWorld 2010 Managing Oracle EBS