leading zeros in hierarchy

[Former Member]

Hello all,

While loading the MD hierarchy from BW to BPC, due to the leading zeros in nodename the hierarchy is not getting extracted.

Though there were 4 leading zeros in the MD, i used ID(5:10) in mapping and was successful in extracting it in the desired format. But when I used the same logic for the MD hierarchy, it is not working out. So, I got a BAdi (in UJD_ROUTINE) created and tried to use it in the transformation file and still failed in it.

While debugging the BAdi in the MD transformation file, it was reading all the records. But during debugging in the MD hierarchy transformation file, it is not reading any records. Please Advise.

BAdi, dimension types that I specified...

DATA: lo_dim TYPE REF TO cl_uja_dim,

       lr_dim_data TYPE REF TO if_uja_dim_data,

       lr_hier_en_data TYPE REF TO if_uja_hier,

       lt_mbr_name TYPE uja_t_dim_member,

       lt_mbr_node TYPE uja_t_mbr_node.

[Former Member · Accepted solution]

Hi Mouli....

Try using javascript in Conversion file for removing leading zeroes...

Hope this helps....

Regards,

JP

[Former Member · Accepted solution]

tried it but wasn't of any help. All records are rejected.

in the conversion sheet of conversion file, i maintained 1000 as PARENTH1

[Former Member · Accepted solution]

What if nothing is maintained for Nodename? Are all the nodenames rejected?

[Former Member · Accepted solution]

Please share the Set selection screenshots and validation of transformation file while using the java script!

[Former Member · Accepted solution]

P.S In your transformation file for HIER_NAME, the mapping should be HIER_NAME = HIER_NAME! Why HEID?? Its Standard format!

[Former Member · Accepted solution]

Mouli, While running data manager package, which format have you used "Internal Format" or "External Format"?? If External format, then it should automatically ignore the leading zeros.

Regards,

JP

[Former Member · Accepted solution]

Hi JP,

I tried all, but nothing worked out. I'm working on trail and error method and used all combinations.

external - internal format, set selection/ without set selection to hierarchy 1000, with HIEID and HIER_NAME.

When used 'internal' format, the transformation file is being validated but all records are rejected. When used 'external' format, the validation is failed.

[Former Member · Accepted solution]

Mouli tried everything still not working...means your doing something wrong at somepoint! Its a standard functionality to ignore leading zeroes, cant happen that it wont work!

If you want proper help, then please give your step by step execution with screenshots! Without knowing what error you get on screen how can we help?? Give Validation screenshots too!

Regards,

JP

[Former Member · Accepted solution]

Here the screenshots of validation process and its results in internal and external formats

[Former Member · Accepted solution]

What is the name of the hierarchy? 1000? I dont think so.....From the previous screenshot of BW hierarchy your name is different! Please specify the name of hierarchy in the Set selection.

And DELIMITER = TAB.

Which version of BPC are you suing? 10 or 10.1??

Regards,

JP

[Former Member · Accepted solution]

Hi JP,

Used the DELIMITER =TAB.

The hierarchy is 1000, you can see in the previous screenshots and also in the set selection I've used 1000. And I'm using BPC 10.1

I have created a BAdi and used it in the options. But the main issue is that no records are being read.

[Former Member · Accepted solution]

1000 is the technical ID name of the hierarchy??? Sorry but from the screenshot i can see 1000 as first main node....of hierarchy.

Is the infoobject 0GL_ACCOUNT active on bw side? Is the master data activated in bw??

Regards,

JP

[Former Member · Accepted solution]

The technical ID of hierarchy is NV9HRP1KVY97A552TYU3XK8UF.

yes, the 0GL_ACCOUNT is active and so the master data.

[akos_beres · Accepted solution]

Mouli,

few things to try:

1. Need to include the top level ID of the hiearchy in the MemberID selection filed

2. there should be three conversions Parent=, Hier_name=, Nodename = ... missing parent=

3. switch to external view

If this don't work, please show the conversion file contents.

Akos

PS ... are there any rejected items when you click on the reject button?

have you seen this? 

[Former Member · Accepted solution]

Giving the Member ID has resolved the issue.

I specified the node name of the first line as the member ID and it worked. The main thing is that it was able to read the values with the leading zeros.

As the node name had inconsistency with the leading zeros, I used a BAdi to remove the leading zeros while loading.

Thanks all.