Business Release in BI

Changes to be promoted in Production system for all the IT system in a big organization that include several regional instances has to adhere to the business release time line.

This is to ensure the impacts are accessed and minimal risk is introduced to the production environment. There is also a need to cross check the dependent changes that ensures the correct sequence of importing the changes in all different systems are followed.

This is very important as:

• Prevent newest changes to be overwritten by old transport(emphasize in orphan transport and transport not in build list)
• Datasource not imported first or replicated after . Eg shared datasources like 2LIS_02_SCL (Purchase Order History) which is shared between SRM and BI (Procurement solution).
• Data loading and transport sequence (top down dependency and cross solution dependency)
• Inactive objects discovered later and development system is opened for new changes, thus re-transport is impossible
• Shared datasource and dataflow are not impacted.eg OTIF(sales forecast) and COPA(sales volume)
• The conversion of logical system name is done in parallel (done in the same BR) for all the 'target' system like BI and APO that feeds on the same ERP system when the feed system change its logical system name.