promotion management overrides.pdf

8
Generated by Jive on 2014-09-22+02:00 1 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.  

Upload: enioterra

Post on 13-Apr-2018

227 views

Category:

Documents


0 download

TRANSCRIPT

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 1/8

Generated by Jive on 2014-09-22+02:00

1

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 thesubsequent LCM jobs will be modified as per the overrides set.

 

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 2/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

2

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”

 

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 3/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

3

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.

 

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 4/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

4

 

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.

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 5/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

5

 

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.

 

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 6/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

6

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

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.

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 7/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

7

 

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

 

SAP Note Description

1805615 How to backup and restore the Promotion

Management Overrides Database in BI 4.x

1801682 How to reset the "LCM Overrides database" in BI

4.0

1628154 Promotion Management (LCM) usage across multi

domain environment

1634962 How to import or export a LifeCycle Manager BIAR

file in BI 4.0 using command line utility

1651890 How to export a Job to a LifeCycle Manager BIAR

file in BI 4.0

7/27/2019 Promotion Management Overrides.pdf

http://slidepdf.com/reader/full/promotion-management-overridespdf 8/8

Promotion Management Overrides

Generated by Jive on 2014-09-22+02:00

8

1651874 How to import a LifeCycle Manager BIAR file in BI

4.0

1777956 BI 4.0: Promotion Overrides not working for

Dashboards

8.