override issue

[Former Member]

Hello, I have a question regarding over rides in LCM. I have a crystal report that I created and promoted it to QA server. then I made some more changes to it in Dev environment and tried to promote it but it will not over ride the report and no changes were made. What am I doing wrong? can someone tell me please? thanks.  This is BOBJ 4.0.

[Former Member]

Hi Vikram,

can you check the status of the promotion job?

Regards,

Thomas

[Former Member]

Thomas, it says Partial Success because i created some new reports so for new reports it says successful but for old reports it says Failure.  if i send only the existing report into qa box it will be a failure.  somehow i need to tell the system that I should be allowed to over write the report changes. is there such a setting in business objects somewhere like import scenario screen in import wizard in BOBJ XI3.1? Where is the setting I can find in BOBJ 4.0? Thanks.

[former_member184594]

Hİ Vikram

Check this KB note 1642935 - LCM Override settings are not working in BI4.0.

This is a known issue with BO 4.0 and will be fixed in FP3 or SP2 Patch 10.  I haven't tested it with FP3 but I tested with SP2 Patch 13 and wasn't fixed.

Reproducing the Issue

1. Create a Crystal Report (CR) with a BW/Bex Connection
2. Setup 2 BI4.0 systems – Origin and Destination Login to the Origin System CMC , and Upload the Crystal Report from Step.1.
3. Login to Origin  system LCM, Define both Origin and Destination systems (Admin options), and the origin system
4. From Admin options, choose overrides, In origin > select the CR as Active. In destination > Edit the CR override and change its BW system connection to a different BW system
5. Create LCM Job by selecting the CR from Step 1 and promote it
6. Login to Destination CMC, choose the CR and check its database configuration – this still shows the original connection which indicates that the override isn’t working

Cause

• This is due to a possible defect in LCM override functionality
• This issue is being tracked under ADAPTs - ADAPT01521266 and ADAPT01588322.

Resolution

• This is currently set to be addressed as part of Feature Pack 3 which is expected to be released in Q1 2012.
• This is also addressed in Patch 2.10

[Former Member]

Zahid,

Resolution

• This is currently set to be addressed as part of Feature Pack 3 which is expected to be released in Q1 2012.
• This is also addressed in Patch 2.10

Am confused here , Did you mean Q1 2013 ?

[former_member184594]

No I don't mean Q1 2013. Beacuase this is already released as part of SP4. I think FP3 was in ramp up at the time. This should be fixed with SP4. If it is not, then you check with SAP or open a message to SAP.

Thanks.

Zahid

[rama_shankar3]

Adding to above points: FP3 and SP4 are technically same. FP3 is upgrade for existing BI4 customers  and BI4-SP4 is a fresh install of BI4 with all FP3 built-oin for new customers. Hope this helps.

Regards,

Rama

[Former Member]

Zahid and Rama Shankar,

Can you please check the post below and let me know if am doing something wrong there??

http://scn.sap.com/thread/3259261

Thanks,

Sree

[Former Member]

Zahid and Rama Shankar,

Can you please check the post below and let me know if am doing something wrong there??

http://scn.sap.com/thread/3259261

Thanks,

Sree

[Former Member]

Hi Vikram,

in order to answer your question it's important we clarify what you are trying to do.

The Promote Overrides feature in LCM (or Promotion Management) is used to change database information in reports/connections during the promotion process. This is especially useful if you want to test your reports in a qa/test environment and then promote them to production without manual interaction on changing the datasource.

I think what you are trying to do is simply promoting a newer version of the report and therefore overwriting it in the destination. Could you confirm that this is the case?

br,

--

Thomas

[Former Member]

Thomas, thanks for reply. yes that is what i am trying to do and i just checked the cuid is the same in both dev and qa boxes.  please help.