on 2023 Oct 02 7:01 PM
We were entering some master data in the DEV system and we had problems processing the Account dimension. Eventually, we got all the attributes into the dimension, but all values for the PARENTH1 hierarchy disappeared and we cannot process the dimension if we add a value for ParentH1, but it will process if we don't.
I have tried both loading via the EPM package and the GUI, with no success.
We had recently added a custom dimension and added an attribute to cost centre in the DEV system. The changes have not been transported and we don't have problems in the TEST or PROD systems. We have backups before the change to the model in DEV but not after.
I have tried following the note 2665809, but to no effect.
This is holding up other work in the system.
We have BPC 11.1 on BW4HANA 2.0
Request clarification before answering.
paulmitch25
paulmitch25What is the error when you process dimension after adding the parentH1 values. Hierarchy parent should also exist as a member first in the dimension.
May be an error screenshot will help in understanding the issue better.
Br.
Nikhil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nikhil,
There is usually no error message. On the member screen it says it has processed successfully , but on the list of dimensions sheet it says "still to be processed" next to the dimension name.
Sometimes It gives a red error on the member sheet, but the popup shows no error details and SLG1 doesn't either.
The system is off at the moment, but I will try to get screenshots in the morning. I hope this helps.
When I try to load using the Excel EPM package it says "fail" and it says next to the rejected record "error in member tables" or something like that.
I hope this helps.
Regards,
Paul
paulmitch25
SAP Note 2665809 mentioned by you covers all steps which you can run from your side to fix the issue. If you have already run these steps and still cannot fix the issue, I would suggest you open a ticket with SAP. One reason I can think of from my experience is special characters in Account member ID's. You can also try this, create a copy of the dimension and see if you face an error in that too, that will clear up a lot of things. The note is comprehensive and outlines all steps we generally use to fix these kind of issues.
Br.
Nikhil
User | Count |
---|---|
6 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.