BEx Analyzer problems after application of support packages

[Former Member]

We recently upgraded to Support Package Stacks 16 & 17 to take us up to patch level 19, and weu2019re having some troubles with BEx.

Before the upgrade using SAPGUI 12 (or any other version) the BEx variable screen functioned fine as usual.

Since upgrading we have had user deterring issues with the variable screen like:

The u201Cchecku201D button locks the screen up and user must stop transaction,

selections in pop-up list screens can cause screen to hang and not populate variable to front screen,

personalization button causes screen to hang while slowly switching from personalized to unpersonalized and must stop transaction

Basis applied a Hot fix but that did not change anything. We have not found any notes as of yet. Is there something we need to do after these SPS upgrades that didn't get done? Any ideas?

Al

[Former Member]

Newer notes solved problem.

[Former Member]

Hi, I stumbled on to Note 1274580. It refers to note 1241303. This note solves both problems mentioned above. The description in 1274580 is more specific in describing this problem. RSRV still returns the same SID errors on the DSO but a LISTCUBE on 0PERS_VAR now shows the personalization entries.

Regards,

JL

[Former Member]

Hi Al.

We have exactly the same problem after the service pack stack 17 (SP19) application on BI 7.0

I found a note that refers to the length of 3 fields that has been changed from 32 to 60. The fields being 0TCTIOBJVAL (reference field for the next 2), 0TCTLOW & 0TCTHIGH. I re-installed the business content for them and reactivated. Then I also re-activated the DSO. All of this made no difference.

I then applied notes 1243421, 1248145 & 1311150 and loaded a BI GUI patch (800) according to note 1243094. Still no change.

The problem seems related to the SIDs of the DSO 0PERS_VAR.

When listing the DSO, no values appear, although there are personalization entries in /BI0/APERS_VAR00. A RSRV check on the ODS reveals that the SID values for most of the characteristics are missing. The problem cannot be fixed by using the Repair option. The description for this check states that: In order to remove the inconsistency, you can load master data for the characteristics from which values were missing in the SID table.

I have checked the master data and found the SID values intact. I have even reloaded master data (0TCTUSERNM), but it made no difference to the RSRV check. I cleaned the ODS and ran the check. Results OK. Running the query and personalizing creates a new entry. Running RSRV again produces the error.

We have this problem in our DEV, QA and PROD systems.

Have you found a solution yet?

Johan Loock