BusinessObjects 4.3 SP4 - Patch 2/3/4/5 Issues

[MichaelGrackin]

We are currently running BusinessObjects 4.3 SP2 - Patch 12 in our production environment.  We installed BusinessObjects 4.3 SP4 - Patch 3 on our sandbox and found a number of issues pertaining to different behavior from Webi in this patch compared to our current production version.  Significant enough differences for use to postpone upgrading to SP4 until a stable patch is released.

Has anyone else encountered issues with the BusinessObjects 4.3 SP4 (any patch level)?

What we found with BusinessObjects 4.3, SP4, Patch 3:

1. We have a number of documents with multiple queries MERGED in the Webi document. We found the Extend Merged Dimension Values setting behaves differently in BOB43, SP4, Patch 3 compared to how it behaves in BOB43, SP2, Patch 12. SAP says the Extend Merged Dimension Values setting is “fixed” in the SP4, Patch 3 because it was “wrong” in previous versions. I am still going round with SAP on this because there is no documentation, that i can find or that they can provide, indicating this was found to be an issue and subsequently “fixed”.
2. Auto Merge Dimensions setting is also behaving differently. If a user just opens a document and refreshes, Webi creates additional MERGED dimensions in the document. No editing of the document was done. Webi just created new MERGEs which, of course, caused issues with the document.
3. In addition, we have also found some (not all) detail variables in the Webi document are losing their association with the dimension to which it is associated when the document is refreshed.  [UPDATE - 07/25/2024]  I did some futher research on this issue and found the associations were changed before the document was even refreshed.  We promoted the documents from BOB43, SP2 to BOB43, SP4 and simply opened a document in edit mode without a refresh and the associations were changed.  Not sure if the promotion job changed them or if the Webi application in BOB43, SP4 changed them when it opened the document.

[emmetmullally]

We have encountered numerous #TOREFRESH errors on reports that have a hierarchy object as part of the report block. These reports work fine in our production system which is 4.3 SP3 Patch 3. Implemented SP4 on our sandbox client to fix auto-refresh issue and hit these #TOREFRESH issues. Installed SP4 patch 3 and then patch 4 (which was supposed to resolve this issue) and issues still exist. These are Webi docs built off a BW query datasource.

[googaroots]

Hi all,

we installed BusinessObjects 4.3 SP4 - Patch 4 on our production environment.

What we found with BusinessObjects 4.3, SP4, Patch 4:

1. BI Event Trigger in process chains from SAP BW aren't working anymore. Nothing has changed in our network/BW environment. 

[jemstar]

We just moved from SP02 to SP04 a week ago 

Regarding each of your points

1) I would be interested in understanding this change in behaviour - can you elaborate further please?

2) If Auto-merge dimensions is not selected under Data Options, then this is a bug. I've done a quick test on efashion and it is working as expected. Perhaps only an issue with existing webis?

3) Again, very serious if this is happening - perhaps it is a specific scenario - copying variables or changing data source?

regards

James

[MichaelGrackin]

Auto Merge Dimensions is turned ON in the Webi document. My understanding is this feature should trigger when changes are made to queries and then run. This is NOT what we are doing. The Auto Merge is being triggered when an end user opens the document and refreshes the document. Merges should NOT be changed when a user opens and refreshes. They are not making changes to the document. They are just viewing it.

[MichaelGrackin]

Thanks for sharing your findings.  All our data sources are Oracle.

Maybe Patch 5 will have this resolved?

[TomNather]

Did Patch 5 resolve these issues? I am testing SP4 Patch 5 currently but going to take a look at Patch 6 this week to see if there are fixes I might of missed