Hi Joseph,
BW has no build-in sign reversal logic, you have to model this with a master data attribute in your account dimension and with formula variables in queries. Check the blog
for more details.
Gregor
hi Gregor, good article, I saw it before but I understand that I have to create a bw hierarchy for this and use that hierarchy in my report but actually we are not creating any hierarchy un bw, we are leveraging FSV from S4H so I guess this solution does not apply in my scenario...correct me if I m wrong.
Joseph
Hi Joseph,
The delivered /ERP/GL_ACCT is indeed, based on the FSV. Now the problem is that the signage handling hasn't been implemented in the standard virtual info object. If you take a look in the info object above, you will notice that the hierarchy is handled by ABAP via class CL_FCOM_IP_HRY_READER_GLACCT. This class retrieve hierarchy from tables HRRP_* (hence the need to perform t-code HRRP_REP - FIN Runtime Hierarchy Replicator to replicate FSV to the info object) and these tables do not hold the sign information.
To be able to retrieve the signage, you need to enhance this class (suggest creating a copy of it). The good news is that the interface in this class already support this sort of situation so the implementation would be pretty straight forward.
Check methods:
IF_RRHI_VIRT_HIER~GET_NODES_WITH_SIGNREVERSAL
In here, you can lookup table RTC_EXT_SKA1 to read the BPC account type or even SKA1 to read the account group and determine the sign.
Also, you will need to activate the signage capability in the method
IF_RRHI_VIRT_HIERARCHIES~GET_CAPABILITIES
Simply include the following line of code:
r_s_capablities-hiesignch = abap_true.
Cheers,
Lucas
Hi Guys
I am also facing this issue... Implemented the note 2531080. GL Account Sign Still not working
1. Introduced Formula variable with Hierarchy attribute
2. Formula variable is used in Calculated KF.
3. The query shows NONEX for this column.
I see my Hierarchy in the table HRRP_DIRECTORY. What else I am missing?
Thanks
Rajesh
Add comment