BPC 10.1 UJO_READ_EXCEPTION_000

[carlos_snchez]

Hi all,

After chaging an ACCOUNT from LEQ to INC, we are facing the following reporting issue related to ACCOUNT hierarchy:

We have changed member properties, the hierarchy and processed the dimension successfully several times,  but the reporting issue has not been solved. We can only create reports using account basemembers.

We have run UJA_DATA_CHECKER program and shows no errors.

We have also applied SAP note 1673094.

Our system: BW    Release 740 SP-level  0012

                   BPC: Release  810 SP-level  0007

Any ideas?

Thanks,

Carlos

[Former Member · Accepted solution]

Hello Carlos,

I have solved the ACCOUNT hierarchy problem applying the following note:

2190242 - UNCAUGHT_EXCEPTION related to hierarchy invalidation in CL_RSDRH_HIER_CACHE

Basically, it is a import to SP 13 for SAP BW 7.40.

After the implementation, I no longer have issues with the ACCOUNT hierarchy.

It seems that it was a problem of synchronization between BPC side and BW side. The ACCOUNT hierarchy in BW side remained always in M version (Modified), instead A version (Active). We had differents hierarchies structures in both sides (a lack of synchronization). Now, it is synchronised, with the hierarchy in A version.

The problem was only in ACCOUNT dimension, no more.

Hope that helps,

Regards,

Manu

[carlos_snchez · Accepted solution]

Hi Manu,

After applying the note (2190242) our issue was solved.

Thanks!!

Regards,

Carlos

[Former Member]

Hello Carlos, Vadim,

I have got the same issue that you comment. I am in BPC 10.1 and here are the details of my error:

- Refreshing a existing report, I had exactly the same error that appears in the screenshot above. With the dimension ACCOUNT, too.

Code: UJO_READ_EXCEPTION_000

Description: MDX statement error: dimension [*technical name dimension* PARENTH1] unknown.

- Until last week, I have never had this error, wich appeared after we upgraded some system components.

Old components system:

Current components (after upgrading):

As you can see, SAP_BW Release 740 was upgraded to SP 12 and CPMBPC Release 810 was upgrade to SP 7.

It seems that the error has come from this upgrades.

- I checked UJA_DATA_CHECKER. No errors.

- Following the note 1673094, I also tried to add "MDX_USE_CLASSIC_PARSER" with value "X" in RSADMIN table. But does not work.

- How I have solved this temporarily? Creating a new hierarchy (like PARENTH2) in ACCOUNT dimension. Copy PARENTH1 to PARENTH 2. Delete PARENTH1 and use the new hierarchy. This is a good provisional solution.

Hope that this information helps.

Kind regards,

Manu

[carlos_snchez]

Thanks Manu,

Last week we created a new environment and copied everything, it was working Ok until this afternoon.

Now Account Hierarchy is corrupted again.

Thanks for your suggestion but we are going to report it to SAP, hope they will fix it quickly.

Regards,

Carlos

[Former Member]

Hi Carlos,

You are welcome. As soon as I find out something, I will let you now. Same for you.

Thanks.

Suerte!

Manu

[Former Member]

Carlos,

The new hierarchy which I created yesterday, called PARENTH2, is already corrupted again.

FYI. I hope they can get that right.

Regards,

Manu

[former_member186338]

Hi Carlos,

Can you show the account hierarchy? And the changed account in it?

Vadim

[carlos_snchez]

Hi Vadim,

See the account hierarchy, I changed the parent ACCTYPE.

In addition, when I check the BW object I can see that account PARENTH1 hierarchy has always two lines(active and modified), even after processing the dimension from BPC. Other dimensions hierarchies have only the active version.

Regards,

Carlos

[former_member186338]

I was talking about Web Administration Client for ACCOUNT dimension...

[former_member186338]

And what is the ACCTYPE of T65100 and for the base members of T61000?

[carlos_snchez]

[carlos_snchez]

All ACCTYPE are EXP.

I can´t remember exactly wich account I changed, what I can tell you is the changes where reversed immediately.

Should I check that all ACCTYPE are correct? I am pretty sure they are, but...

[former_member186338]

Ups, you started with the change LEQ to INC, now - all EXP...

"I can´t remember exactly wich account I changed" - strange...

[carlos_snchez]

I have checked all the ID´s ACCTYPE using a Backup file and are correct.

[carlos_snchez]

As I said, ACCTYPE property is populated correctly for all the IDs. I have check it, that can´t be the problem.

As I told you, the change was reversed inmediately.

[former_member186338]

Then - not enough info to propose something...

Continue playing with the model, try to create a new one with this account dimension, or...

[carlos_snchez]

Yes, I know the workarounds. I guess I will end up doing that..

Thanks for your time