cancel
Showing results for 
Search instead for 
Did you mean: 

Remove Compounded IOBJ for Hierarchy Members in End Routine

Former Member
0 Kudos

Need some help on this one.

I am trying to remove Compounded IOBJ (0CO_AREA) in this case from 0COSTCENTER from both dimension members and as well as the hierarchy node names that get loaded during Master Data Load.

1) Suppresscharacter will not work as the Hierarchy Node Names have Controlling Area Value "TSO" in several places

2) The IF Logic on the How To Document is throwing this error because the node name are long and getting out of range error

"

3) End Routine BADI seems to be the place. However, For some reason the CO_AREA is getting removed only for base members and not for Node names.

Is there another COMPONENT for Hierarchy Node names during Master Data Loads? The standard Component "NODENAME" didn't work.

  • Suppress controlling area from ID

ASSIGN COMPONENT `ID` OF STRUCTURE <ls_data> TO <lv_id>.

if <lv_id> is not initial.

shift <lv_id> left by 3 places.

CONCATENATE 'CC_' <lv_id> INTO <lv_id>.

endif.

I would like to USE BADI and need help in giving the COMPONENT name to pick up Hierarchy nodenames.

Thanks,

Gopal Krishnamurthy

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

I imagine you are using the standard Data Manager package for loading Hierarchies. I would try the following, don't use that package instead in your end routine populate a PARENTH1 field in your target structure yourself and this will generate the hierarchy the way that you want to using the ID on the record as the NODENAME for the BW hierarchy representation. If you are already loading from an existing hierarchy, there is a code example of how to do this in the How To Guide for Loading Master Data from BPC 7.0.

This is a bit of a workaround but I believe it will solve your issue.

Cheers, Scott

Former Member
0 Kudos

Hi Gopal,

Text nodes are transferred as part of master data(attributes) load. So include this logic in the end routine BADI for master data

checking for value TSO.

Regards,

Kalyan.

Former Member
0 Kudos

Thanks Scott and Kalyan. I've used the End Routine BADI and got past the following

1) Remove Compunded IOBJ and on Hierarchy Text Nodes

2) Remove Leading Zeroes

However, I am only able to load only MD and one text nodes for one hierarchy at a time. When I use more than one hierarchy, I get the Field Symbol not assigned error and I am of the opinion that the BADI is not able to maintain the Workarea for second Hierarchy onwards when we utilize the BADI. It is clearly failing in BADI and thinking of opening a Note with SAP. May be you can share your thoughts on this.