cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error during the import of the hierarchy from InfoObj

0 Kudos
500

Hello experts,

we import master data and their hierarchy from BW InfoObj.

In the first step, we import the master data and texts with some skips. If the master data have a specific attribute, they will be skipped. It works without problems.

In the next step, we try to import the hierarchy. But the skipped members cannot be found now and it submits no records/ hierarchy.

Member xxxx does not exist.

How can I skip the "skipped" members during the hierarchy import?

Thanks a lot!

View Entire Topic
0 Kudos

Step 1: Importing Masterdata and Text

Transformation File:

*OPTIONS

FORMAT = DELIMITED

HEADER = YES

DELIMITER = ,

AMOUNTDECIMALPOINT = .

SKIP = 0

SKIPIF =

VALIDATERECORDS=YES

CREDITPOSITIVE=YES

MAXREJECTCOUNT=

ROUNDAMOUNT=

*MAPPING

RELEVANT_BUDG=JCBATTR1

*CONVERSION

RELEVANT_BUDG=RELEVANT_BUDG.XLS

Conversion File:

EXTERNAL INTERNAL

X *SKIP

* *

(Members with Attribute JCBATTR1 = X are skipped)

Step 2: Importing Hierarchy

Transformation File:

*OPTIONS FORMAT = DELIMITED

HEADER = YES

DELIMITER = ,

AMOUNTDECIMALPOINT = .

SKIP = 0

SKIPIF =

VALIDATERECORDS=YES

CREDITPOSITIVE=YES

MAXREJECTCOUNT=

ROUNDAMOUNT=

*MAPPING

HIER_NAME=HIER_NAME

*CONVERSION

HIER_NAME=BUDG_HIER.xls

Conversion File:

EXTERNAL INTERNAL

J_JCBDFGF_1 PARENTH1

(Hierarchy J_JCBDFGF_1 has very straight forward structure: Every member under TOTAL node)

While importing the hierarchy, it goes through every member and tries to put under TOTAL node, but it does find the skipped member (which have Attribute JCBATTR1= X) and stops importing the hierarchy.

I could use a second conversion file to filter the skipped members, but it is then hardcoded and not dynamic. (Attribute JCBATTR1 values could change frequently)

former_member186338
Active Contributor
0 Kudos

If it's only single TOTAL you can add 2 steps after importing Masterdata and Text:

Export all members to text file with a fixed name (excluding TOTAL).

Then import this text file with:

*MAPPING

PARENTH1=*STR(TOTAL)

...

Former Member
0 Kudos

Hi Manalsuren,

skipping members in Hierarchy load need to be done in routine, *skip will not work in the transformation file. basically you need to "modify" the hierarchy before it submits to the database.

Andy

former_member186338
Active Contributor
0 Kudos

For the single fixed TOTAL export/import to text file work's OK, tested!

0 Kudos

Thank you for quick response. I'll check with file export/import.

Is there any alternative, just in case I get bit complex hierarchy structure in future?

former_member186338
Active Contributor
0 Kudos

Only routine badi!