Detected duplicate members ID when loading texts and attributes from InfoObject "0PROFIT_CTR"

[former_member407019]

When entering the infoobject "0PROFIT_CTR" in the hierarchy that must be loaded to BPC "10001000", it can be seen that there are members and nodes with the same ID.

What I did in the transformation file was to use the function that allows to identify the IOBJNM if it is (0HIER_NODE or 0PROFIT_CTR). When validating the transformation file, it comes up successfully, however, running the integration package does not load the information correctly. I would like to know if I need to consider anything additional or if this formula definitely can't work.

The conversion file that is being used is the following:

In the execution of the package the data entry works correctly.

When viewing the dimension, the following can be observed:

The downside is that in the previous example the child (0PROFIT_CTR) is loading

CBN_1000CO1B

But node (0HIER_NODE) is loading

CO1B (The error presented here is that it is omitting the "1000", as it should load the data

1000CO1B

Now, when loading the hierarchies, the following duplicates error appears:

[former_member186338]

Perfect details!

But please, change you name from anonymous diegofeliperozo to some real one. I don't like to answer anonymous persons.

[former_member186338 · Accepted solution]

I can't check it now but try something like

NODENAME=*IF(NODENAME=*STR() THEN *STR(X);IOBJNM=*STR(0PROFIT_CTR) THEN *STR(CBN_)+NODENAME;IOBJNM=*STR(0HIERNODE) THEN *STR(1000)+NODENAME;NODENAME)

not sure it will work...

[former_member407019]

Yes of course, I share the transformation file used for the hierarchy below:

And this is the related conversion file:

Where do you tell me that I should concatenate the IOBJNM and the ID to make it unique? In the text and attribute transformation file? And in the conversion file what should I consider?

[former_member186338]

During Hierarchy load you have to perform the same IF logic like you did it for master data load!

P.S. Your recent post is not an "answer", use comment instead.

[former_member186338]

Not sure about the syntax of your IF line in transformation:

Test:

ID=*IF(ID=*STR() THEN *STR(X);IOBJNM=*STR(0PROFIT_CTR) THEN *STR(CBN_)+ID;IOBJNM=*STR(0HIERNODE) THEN *STR(1000)+ID;ID)

By the way, it's better to provide not only screenshot but the text line also 🙂

Result will be:

CBN_1000CO1B for base

1000CO1B for node

[former_member407019]

Hi, thks for share the information. I have applied the function again and loaded the dimension. Now they show correctly, but the error continues when loading hierarchies because it mentions duplicates.

[former_member186338]

diegofeliperozo

Sorry, but if you want a solution - use your real name.

[former_member407019]

Actually I have tried to make the change from my profile, but it appears shaded and without being able to edit, this is the image, I do not know how to make them modify me and place my data correctly.

[former_member186338]

diegofeliperozo

If you are using P-account like me you can edit:

If you are using S-account you can change the name on support portal. But it's a very bad idea to use S-ID - it's owned by the company, not by you. And SAP Community is a community of people, not companies.

[former_member407019]

As you can see this user S is mine and is personal, I acquired it when I had to register to take the certification exam. It is not a company s-id, it is personal.I don't understand what the point is, besides I work independently. When trying to edit it does not allow me.

[former_member186338]

diegofeliperozo

Then open SAP notes portal and click on you user icon -> User profile and edit header...

[former_member407019]

I have already made the corresponding change to my profile. Thanks in any case for the help you gave me

[benniejayfguevarra]

Hi,

Can you share the transformation file you used when loading the hierarchy? You can concatenate the IOBJNM and ID so it will be unique, then do the required adjustments in the conversion file for the ID of the Parent and the Child nodes.

Hope this helps,

Bennie