Promotion Management Overrides

1.     Concept

In a standard development cycle, all the BI content is created in an “Origin” (Dev) system and then moved to other environments. The main challenge faced in this process is updating the Database credentials as per the destination environment.

To overcome this challenge in BI 4.0 we have Promotion Management Overrides. It was present in BOE 3.1 and was known as LCM Mapping. However in BOE 3.1, Mapping was LCM job specific but in BI 4.0 the Overrides are system specific.

You can modify the database credentials for OLAP Connection, Universe Connection, QAAWS Connection and Crystal Reports.

Following is the generalized workflow of LCM Overrides. Database credentials for the entire object in the subsequent LCM jobs will be modified as per the overrides set.

2.     Procedure

Below are the detailed steps with screen shots for the above workflow.

a)     For Movement from Dev to QA

1. Login into CMC àPromotion Management in Development System.
2. Click on “Setting “and browse to “Manage Systems”

3. Highlight the System from which all the content would be migrated to other environments. In most cases it would be the Dev System. Check the “Mark as Origin” box.

1.      4. Save the changes.

2.      5. Browse to “Overrides Settings”.

1.       6. Login into the “Origin” CMS and Scan for Overrides.

1.       7. Once the scan is completed, select the particular override which you want promote and change the status from “Inactive” to “Active” and save the changes.

1.       8. Select the Override which needs to be promoted and click on “Promote Overrides” button.

1.       9.In the subsequent screen, select the required destination server (QA system) and click on “login”. Enter the credentials of “Destination CMS”. The “Export” button will be replaced with “Promote” button. Click on “Promote” to complete the Promotion.

1.       10. Log off from the “Origin CMS” and Login into the “Destination CMS” and again scan for Overrides.

1.     11.  We should see the Override which we promoted from the Origin CMS. Highlight the Override and click on Edit. Make the necessary changes and save it.

2.      12. If the subsequent LCM Jobs contain the same “Connection” object, the connection properties will be automatically updated as per setting defined in previous steps.

b)     For Movement from QA to Production

Repeat steps 1 through 12, but mark “QA” server as “Origin” and “Production” server as “Destination” system.

3.     Exceptions & Corrective Actions

1.      1. Object Export through BIAR files

a.       Export the Overrides to a BIAR file.

b.      Import the overrides biar in the “Destination CMS”

c.       Scan the “Destination CMS” and edit the imported overrides.

Now you can import LCM BIAR files with objects and overrides will work as expected.

2.       2. Reverse flow of Ad-hoc reports from Production to Development

a.       Use a different CMS as your LCM CMS.

b.      Mark your Prod system as “Origin” and follow steps 1 through 12.

4.     Related SAP Notes

8.