Parent member not getting created while Loading 0COSTCENTER Master Data from BW to BPC,

[Former Member]

Hello Everyone,

I am trying to Automate Master Data of Cost Center in BPC. I am achieved my first step in creating the Cost Center Ids in BPC. The ids that that are not in BPC gets created when DM package(INOBJ_MASTER) is executed. However, I am getting difficulty in creating parent members in BPC.

I have maintained the Transformation and Conversion file for both the Master data load and the Hierarchy load.

Also, I have selected in Hierarchy tab(Set Selection) Import text node - Yes

Version: SAP BPC 10.1

Could anyone please help me in resolving the issue of creating parent nodes and then maintaining the hierarchy.

Attached are screenshots of BW Hierarchy and Transformation & Conversion files.

Screenshot of BW Hierarchy:

Screenshot of MD Load Transformation file

Conversion file screenshots for MD load:

CONVERSION tab:

Screenshot of Transformation file for Hierarchy load

Conversion file screenshot for Hierarchy Load:

CONVERSION tab:

COST_CTR tab where the mapping of Parent has been done

Steps: while executing DM for MD load

Step1: Set selection of Infoprovider

Set Selection of Hierarchy

Please note when the package is executed using the second option of "Attributes OR Hierarchies". package gets failed with error:

[Message] --------------------------------------------------------------

Task name

MASTER DATA SOURCE:

Record count: 4105

Task name

TEXT SOURCE: Record count: 4047

Task name CONVERT: No 1

Round:

Error found in system Error in Admin module or a component used by Admin module

Detected duplicate member ID '100010003'

Detected duplicate member ID '100010003'

Detected duplicate member ID '100010003'

Detected duplicate member ID '100010003'

Detected duplicate member ID '10001000'

Detected duplicate member ID '10001000'

Detected duplicate member ID '10001000'

Step: Language selection: Selected English

Step 2: Chosen "Update mode"

Step 3: Chosen External format

Step 4: Chosen correct transformation file

Step 5: Clear member before overwrite mode- "No"

Step 6: Filter Master Data: "No"

Please let me know any information required.

[former_member186338]

If you want my answers - please prepare your post in a readable form:

1. Check for missing line breaks (better to use CODE button for Transformation text)

2. Instead of incorrect "Insert File" use "Insert Image" to have your post readable.

[Former Member]

Hi Vadim,

I have edited the question in more readable format, Hope this helps you.

[former_member186338]

Sorry, but looks like you have no time to add descriptions of your screenshots! No idea about tab names of conversion screenshot...

What is this??

Also missing:

Conversion file for hierarchy load 0COST_CTR_HIER.xls

Screenshots of all selection screens

Error can be done on each step!

[former_member186338]

"Not able to post comment" - comments are limited for images (only 2!)

[Former Member]

Hi Vadim,

Sorry for the confusion.

I have edited the Question and added screenshots with description.

Please check

[former_member186338 · Accepted solution]

In order to remove leading "1000" both from nodes and base members use:

1. External format

2. Mapping ID=ID

3. Conversion:

js:%external%.toString().replace(/^1000/,'')

"^" - means at the beginning of string

[Former Member · Accepted solution]

Hello Vadim,

I tried using the conversion code you gave it worked and remove "1000" from the Ids. It was successful for Parent nodes. However, we have some cost center Id's that starts with 1000; this code removed that too.

Is there a way If this code only to be applied for the parent node. if this is possibe I will try otherwise I will check with the client and go ahead with parents containing 1000 in parent nodes.

Thank you so much for your kind help. I appreciate the efforts.

[former_member186338 · Accepted solution]

rishabh.gupta2

Sorry, but I don't understand you!

js:%external%.toString().replace(/^1000/,'')

will remove only first "1000" from ID:

"1000100012".toString().replace(/^1000/,'')

will result in

100012

[former_member186338]

I see you have 3 cases:

Nodes:

1000x...x where x - characters

0000....0001000d...d where d - digits

Base members:

1000d...d where d - digits

And the expected result is:

Nodes:

x...x

d...d

Base members

d...d

Is it correct?

[former_member186338]

P.S. Actually I suspect that with "external" you don't have nodes like

0000....0001000d...d

You have

1000d...d

[former_member186338]

Just tested - nodes will also come without leading zero's

[former_member186338]

I see 2 issues:

1. On the selection screen you are using: "Set filters by Attributes AND Hierarchies". Incorrect! Use: "Set filters by Attributes OR Hierarchies"

With your current setting parents will not pass filter!

2. parseint in conversion - all parents will not be loaded! strange idea!

[former_member186338]

P.S. Please read:

https://blogs.sap.com/2013/01/21/bpc-10-nw-master-data-attributestext-and-hierarchy-loading-process-...

https://blogs.sap.com/2013/01/21/bpc-10-nw-master-data-attributestext-and-hierarchy-loading-process-...

[Former Member]

Hello Vadim,

I tried as suggested in Point 1, Chosen - "Set filters by Attributes OR Hierarchies". But this gave an error during DM packages execution.

[Message]

--------------------------------------------------------------

Task name

MASTER DATA SOURCE:

Record count: 6763

Task name

TEXT SOURCE: Record count: 4047

Task name CONVERT:

No 1 Round:

Error found in system Error in Admin module or a component used by Admin module

Detected duplicate member ID '100010003'

Detected duplicate member ID '100010003'

Detected duplicate member ID '100010003'

Detected duplicate member ID '100010003'

Detected duplicate member ID '10001000'

Detected duplicate member ID '10001000'

Detected duplicate member ID '10001000'

Detected duplicate member ID '100010011'

Detected duplicate member ID '100010011'

It seems that the system is taking parent node of each Cost center as a separate item, Attaching the text file containing full error message.

Could you please look the message and suggest.

error-while-md-load-oct-9.txt

Also, I did not understand your second point in the Comment. "2. parseint in conversion - all parents will not be loaded! strange idea!"

Thank you,

error-while-md-load-oct-9.txt

[former_member186338]

rishabh.gupta2

Look on the node name:

1000000_ALL

Result of parseint will be:

1000000

Resulting in duplicates!

[Former Member]

Hello Vadim,

I have used "js:parseInt(%external%)" to removed leading 0 from the Id as in our Cost center we have Ids with 9 and 10 characters, hence Ids with 9 characters have 0 as the first character.

Is there a work around for this?

[Former Member]

Hello Vadim,

Adding to my above point for leading zeros, we have parent nodes containing zeros too which are of different characters length.

I tried loading MD using

But with this, Parent nodes that were created contains 1000XXX_ALL and 00000000000000000000000010001001.

Here 1000 is controlling area, is there a way I can remove 1000 from parent nodes created.

error-while-md-load-oct-9.txt

[former_member186338]

rishabh.gupta2

If you select "external" on DM prompt:

then you will have no leading zero's for base member ID's!

Please show samples of your original base members and parents in BW

[Former Member]

Hello Vadim,

Thank you for the suggestion, choosing "external format" created members without leading zeros,

However, after executing package for hierarchy I am getting an error as "members not found" This is because in Node name of hierarchy Cost centers start with "1000".

Is there a way to remove "1000" from the Node name(at least for Cost center) using the IF condition in the mapping section of the transformation file.

attaching the screenshot of the BW hierarchy.(Block in the image has been hidden due to Company name/Id)

[Former Member]

Hello Vadim,

I am able to achieve the Hierarchy and resolve the error for Cost center not found by using if condition in mapping:

NODENAME=*IF(IOBJNM=*STR(0COSTCENTER) THEN NODENAME(5:14);NODENAME)

and running the package in external format.

However, still issue of parent nodes created with "1000" as leading character is there.