on 10-03-2017 1:19 AM
Hi gurus:
I am implementing RTC on S4H 1610 FS02 and I need to configure the work status, so far I have specified:
1) 2 work states: unlocked / locked
1) owner dimension = company code dimension with a hierarchy (just 1 top node and all the company codes on it), the top node is a text node "ALL_ENTITIES"
2) owner - defined by property of company code dimension...in RTCENT I have filled this property with my user id for all the company codes
3) other dimensions: Category / fiscal year-period / fiscal year variant
But when I try to specify the "lock status" I see this error:
I know that there is an option to implement a badi for this, but my scenario is pretty straight forward...do I need to implement that badi in my case?
Regards
Joseph
Apparently the system is failing to identify the owner from the Entity Dim.
As RTC_ENTITY_M currently does not have OWNER property, I'm assuming you enhanced somehow this property. Did you enhanced the
/ERP/ECOMP IO and HANA view liked to the IO as well?
Can you share the Entity Mapping (RTCENT) and BPC Mapping for the Entity Dim?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lucas, for now I am using the dimlist property of the Entity dimension (I know this is not the good practice but I need to test the WorkStatus to be sure that it is working) so I populated this column with my id user then when I run work status for a specific company code it works fine but when I select the top node of the hierarchy is throwing the error message. Have you faced this before?
I haven't used WS in RTC yet. But the only difference is where you're inputting the OWNER.
If you're using DIMLIST, mapped that in the Entity mappings in BPC (DIMLIST field to DIMLIST property) and chose DIMLIST in the Owner Property should be ok.
I'd check:
If nothing solves the issue, I'd open a ticket or look at RSBPCB_SETUSER BAdI
User | Count |
---|---|
15 | |
4 | |
2 | |
1 | |
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.