hierarchy data load for compounding objects

[sap_user62]

Hi Friends,

BW-7.4,bpc10.1

I have searched several threads for this issue.

I am trying to load master data(attribute and text) and hierarchy data load from BW which is a compounding object

Master data transformation file

ID = 0CHRT_ACCTS + ID

I select only one chart of accounts to bring in the data, so in conversion file I trim out the compounding attribute. ( if I mention ID = ID in transformation file, it does not get me any data)

Conversion file

Ex            Inte

FCOA*       *

I also select the hierarchies as the top most node, when I run the attribute load.( I select hierarchy top most node, member id and level)

Attribute load is successful, and I get text populated too.

In the master data I do not have chart of accounts appended to my GL account.( which is what i need)

Now I want to load hierarchies using the hierarchy data manager package. Hierarchies are properly maintained in BW and the data is active, however when I run this load, I always get "all the records are rejected"

transformation file

NODENAME= NODENAME   --- ( I tried with NODENAME = 0CHRT_ACCTS + NODENAME -no luck)

HIER_NAME=HIER_NAME

PARENT=PARENT

ORDER=ORDER

VERSION = VERSION

IOBJNM = IOBJNM

Conversion file

HIER_NAME=HIER_CONVERT.xls

NODE_NAME=HIER_CONVERT.XLS!NODE_NAME   -- ( I tried to comment out the last 2 lines too - no luck)

PARENT=HIER_CONVERT.XLS!NODE_NAME

HIER_CONVERT - CONVERSION TAB

EX                   IN

FCOA1000       PARENTH1

HIER_CONVERT - NODE_NAME TAB

EX                  IN

FCOA*             *

could you please point to if I am missing anything.

Thanks for your time

Ed.

[Former Member · Accepted solution]

Hi Ed,

I may have just responded to the same issue raise against an old SCN thread?

Anyway, is it just that you've made an error on your Hierarchy Transformation file?

NODE_NAME=HIER_CONVERT.XLS!NODE_NAME   -- ( I tried to comment out the last 2 lines too - no luck)

Surely this should be "NODENAME" rather than "NODE_NAME" and likewise your Conversion file should be "NODENAME"?

Hopefully that is all it is.

Regards

John Keane

[sap_user62 · Accepted solution]

Thanks John for taking time to reply.

It was a typing mistake, I checked it again

NODENAME =HIER_CONVERT.xls!NODE_NAME

When I validate the transformation file for attributes, i do not get any errors, but the count equals the master data, ( not hierarchy text nodes).

If i validate the hierarchies, it shows "all the records are rejected"

Note- I have removed the chart of accounts for account master data in the conversion file.

Ed.

[Former Member · Accepted solution]

Hi Ed,

I just hope I can help.

In my G/L Account Master Data Transformation file I have the following (which works for us):

*MAPPING
ID=0CHRT_ACCTS+ID
ACCTYPE=0CHRT_ACCTS+ID
RATETYPE=0CHRT_ACCTS+ID
TYPE=*STR(SAP)

*CONVERSION
ACCTYPE=GL_MASTER_CONV.XLS!ACCTYPE
RATETYPE=GL_MASTER_CONV.XLS!RATETYPE

In my G/L Account Conversion file I have 3 worksheets, ID, ACCTYPE and RATETYPE. Although "ID" is not in the "*CONVERSION" section of the Transformation, so my be a legacy left over that's not being used (not sure at the moment without taking it out and testing it).

However, one thing that may be your issue is how it's recognizing and converting your Nodes. This is how we have it set up (we prefix our Account with "GL" and Nodes with "GLN") and our COA is "1002": The "1004" values you see below are referring to the FSV that we are telling it to use for identifying the correct hierarchy format and I believe that this is missing from your Conversion file (based on what you've posted).

EXTERNAL                                                   INTERNAL

100200009*                                                   *SKIP

1002                                                               *SKIP

100200007*                                                   *SKIP

10020000*                                                     GL*

00000000000000000000000000001004*     GLN1004*

0000000000000000000000000001004*       GLN1004*

000000000000000000000000001004*         GLN1004*

00000000000000000000000001004*           GLN1004*

0000000000000000000000001004*             GLN1004*

000000000000000000000001004*               GLN1004*

00000000000000000000001004*                 GLN1004*

1002*                                                             GL*

In the Hierarchy Transformation file I have:

*MAPPING
NODENAME=NODENAME
HIER_NAME=HIER_NAME
PARENT=PARENT
ORDER=ORDER

*CONVERSION
HIER_NAME=GL_HIER_CONV.xls!CONVERSION
NODENAME=GL_HIER_CONV.xls!NODENAME
PARENT=GL_HIER_CONV.XLS!PARENT

And the Conversion file has 3 worksheets called CONVERSION, NODENAME and PARENT.

PARENT is set up simply as:

External           Internal

1004                PARENTH1

CONVERSION is set up as :

External                                                              Internal

10020000*                                                          GL*

00000000000000000000000000001004*          GLN1004*

0000000000000000000000000001004*            GLN1004*

000000000000000000000000001004*              GLN1004*

00000000000000000000000001004*                GLN1004*

0000000000000000000000001004*                  GLN1004*

000000000000000000000001004*                    GLN1004*

00000000000000000000001004*                      GLN1004*

And NODENAME is set up exactly as CONVERSION but without the first line as that is only for base level Accounts.

So, based on this and what information you supplied, it looks like it may well be your CONVERSION worksheet (and possibly NODENAME) that needs a bit of amending.

I hope this, long, reply is of use.

Regards

John Keane

[sap_user62 · Accepted solution]

Thanks John for the detailed reply.

Let me ask this question. If we run "load master data attribute/text from BW infoobjects" and I select import text nodes and I select hierarchy, then does it really matter if there is a transformation/conversion file for hierarchies?

My first step would be just to get the text nodes into BPC for the selected hierarchy which is not working.

In my case the Text nodes of the hierarchy are not numbers, and they do not form a part of master data table, they are like FCOAPNL

i tried the following, but in BPC, I do not get any results with node, which means that the DM package has not pulled any text node to BPC

000000*       GL*    ------ GLAccount

FCOA*        NODE*    - NODE

Ed.

[Former Member · Accepted solution]

Hi Ed,

I don't think it's possible to not have the Nodes in your Master Data. Have you tried to manually create in the Web UI a Dimension Member with a Parent that does not exist in that Dimension? If you try and create one with a non-existent parent, then it'll tell you that parent does not exist and not let you save the data.

Regards

John Keane

[sap_user62 · Accepted solution]

I mean the text node in the hierarchy "FCOAPNL" does not exist in master data table for BW (M or P table). In BW master data we have entries with numericals only.

Yes, you are right, in BPC, the text node should be a dimension member, in order to be a parent.

[Former Member · Accepted solution]

I think I'm missing something here. Can you give me an example of what your 0GL_ACCOUNT is in BW and what the relevant Hierarchy info on this GL Account would be? E.g. Name of Hierarchy (FSV) and Node Name.

Plus, the same example of how this should be in BPC, the Member ID and ParentH1.

Then I might be able to better understand where you're trying to get from and to!

Regards

John Keane

[sap_user62 · Accepted solution]

Thanks John for your reply.

GLaccount data in BW

Attributes (M table)

chart of accounts     GLACCOUNT ....Other properties.......

FCOA                       100001

FCOA                       100002

Hierarchy

description                 infoobject       nodename

fin stat                       0hier_node    FCOAPNL

       Cash Account      0gl_account  FCOA1000001

BPC Data should be like this

ID            Description acctype h1

1000001  Cash            AST    PNL

PNL        fin sta           AST   

I would take a step back, and would want to concentrate on pulling the text node to BPC when i run the attribute load. It does not seem to work out.

[sap_user62 · Accepted solution]

I missed it, the member ID in the hierarchy selection entry was erroneous. I put the technical ID of the node instead of the node name. 😞

[Former Member · Accepted solution]

So, does that mean your problems are all solved now?

Regards

John

[sap_user62]

Any suggestions friends?