BPC Ownership + Consolidation Monitor (Base configuration)

[heiko0815]

Hi everybody,

I'm trying to set up the real time consolidation using BPC 10.1 on S/4HANA with an embedded BW.

The RTC Model is created, as are both Infocubes. (Ownership and the Consolidation Cube)

Also the mapping between the attributes and Dimensions within the BPC Webclient is done.

Furthermore i have configured the businesspartners accordingly, so that right now i also have some records within the ACDOCA which can be used for consolidation.

What i am trying to do now is to run the consolidation from the BPC Webclient. However when i try to click on the Consolidation monitor, I get the error message "Member does not exists in dimension /ERP/RGROUP. Also i am not able to change the fiscal year/ period within the filter. It stays at 0002011 unable to be changed. Category and RTC Groupt with ENTITY however can be changed. But the error message stays the same.

What i tried to do is to enter some masterdata for /ERP/RGROUP which should fit the selection but i also does not work.

In addition to that i have a second problem when trying to access the ownership manager.

This time the error message i get is "Failed to get ownership data".

Unfortunately I cannot find any further documentation concerning this matter.

Do you have an idea what might be wrong with my configuration?

Thanks in advance

Heiko

[heiko0815]

Hi again,

thanks for your help.

My member IDs for /ERP/RGROUP do not have leading zeros. In fact it is 1010 and 1710. I also included G_NONE.

I also checked the hierarchy that i have created for /ERP/RGROUP all members were included within that hierarchy. I also tried without a hierarchy, but still no success.

However now i am at least able to access the Ownership manager editor. I get a message that is has been updated.

But i am not able to save or calculate anything. When saving i get the message:

Please enter a valid value for characteristic /ERP/GL_ACCT. Please enter a valid value for characteristic /ERP/GL_ACCT. Please enter a valid value for characteristic /ERP/PENTITY. Value YCOA/METHOD for characteristic G/L Account is not valid Value YCOA/PGROUP for characteristic G/L Account is not valid Value 100/ONE for characteristic RTC Partner Entity is not valid Write Back ended with errors

But within the Ownership manager i cant even enter values for those characteristics.

Only GROUP and METHOD are possible to be entered.

When i hit the calculate button, again i get the other message that the Member does not exist in /ERP/RGROUP

Any more ideas what i am doing wrong?

Thanks again in advance

Heiko

[former_member323496]

Hello Heiko,

You solved the issue of "Value 100 / ONE for characteristic RTC Partner Entity is not valid"?

Best Regards.

[Arantes]

Hello,

About messages related /ERP/PENTITY as: "Please enter a valid value for characteristic /ERP/PENTITY. Value 100/ONE for characteristic RTC Partner Entity is not valid Write Back ended with errors".

Ensure the value of "Non-inteco Member in Ownership" is "<RTC Dimension>NONE" (for example "100NONE" for the dimension "100") was assigned on BPC Webclient > Advanced Setting of your model, check if all parameters are the same as RTCMD.

Best Regards

[former_member588786]

You have to complete the properties in the GROUP dimension, specially Currency Type property.

[heiko0815]

Hi everybody,

so i was able to sort out the issue with the not selectable period.

Apparently the virtual time hierarchies were not activated within the transaction /nRSRHIERARCHYVIRT .

However i am still facing the Member not found issue.

Maybe issue lies within the attributes of /ERP/RGROUP ?

Thanks again and best regards

Heiko

[lucas_costa3]

What about the Currency Type property? Have you included "N" for the G_NONE member and "G" for the others?

[former_member588786]

Thank you very much Lucas, your help helped me too. Again thanks.

[lucas_costa3]

Also remember to include G_NONE in your group dim.

[damovand]

Hello,

You might be facing multiple issues. Both of the following situations will result in members not being found.

• If you have member IDs starting with leading zeroes, confirm if you have enabled Alpha conversion for the dimensions that is having the issue.
• In the modelling layer, through BPC web client Administration modelling, if you have pre-defined a hierarchy for a dimension any member that does not belong to the pre-defined hierarchy will not be accessible. Please check and confirm the configuration and check the members that show up as missing.

Best Regards,

Leila Lappin