BPC NW - Error Importing Master Data from BI to BPC

[Former Member]

Hello,

I am importing MD from BW to BPC; openhub is working as required, and creating the corresponding file in the application server.

However, when I run the package from Data Manager, it is displaying the following error:

"An exception with the type CX_SY_STRUCT_COMP_NAME occurred, but was neither handled locally, nor declared in a RAISING clause.

No Component name specified for Component 6."

I have been looking other posts and OSS notes, and looks a problem related to DB; however in this case we do not have any dump.

Has anyone encountered the same issue?

Thanks&Kind regards,

Begonia

[Former Member · Accepted solution]

Hi,

Are you running any default logic? If so, check the SAP note 1259869.

If not, it could be a program error in SAP BI. Check this 1002923 note for more info.

Kranthi

[Former Member · Accepted solution]

Hello Kranthi,

Thanks for your quick reply. However, when importing master data I do not have any default logic (as appears when importing trx data), and the note that you mentioned 1002923 does not apply to my current version.

Could it be related to the DB eventhough I am not getting any dump (does not happen in NW, but when trying to import data into BPC)?

Thanks&Kind regards,

Begonia

[Former Member]

Hi Begonia Boloqui,

After you extracted master data from BI using Openhub. The file is available in the application server.

Before you run the package from Data Manager.

Please examine the file data contents.

From the Action Pane, Click Manage Data and then clicking Preview data file

System allows you to preview the first 200 lines of a data file. Check whether data record is compatible with dimension definition and the mapping from external to internal members.

Looks like error is with COMP_NAME field?

Hope this information is useful.

Regards,

Rajesh Muppala.

[Former Member]

Hello Rajesh,

Thanks for your reply. I managed to solve the mentioned issue above; however, I am facing now problems on the mapping side:

"Command failed: *COL(4); column index is out of range"

COL(4) refers to the PARENTH1, the BW hierarchy mapped to BPC. I have tried several options, but still displays the same error.

Do you know where can I define this range?

Thanks&Kind regards,

Begonia

[former_member5075]

Hi Begonia,

I am not sure if you have seen this how to guide https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00380440-010b-2c10-70a1-e0b43125...

explaining the master data import process. This should guide you in solving your issues.

regards,

Sreedhar

[Former Member]

Hello Shreedar,

Thanks for your reply. I was following this HTG, but was encountering system issues that have been solved and could load data correctly.

Thanks a lot!

Kind regards,

Begonia

[Former Member]

Hi Begonia,

how did you solve the mentioned problem: "Command failed: *COL(4); column index is out of range". At the moment I'm doing exactly the same thing with the How To Paper "Masterdata Import Automation".

When I run the package, it gives me the same package error.

What can I do?

Thanx for you reply.

Regards,

Cora

Edited by: Cora Boettger on Jun 11, 2009 3:14 PM

[Former Member]

Hello Cora,

This error is due to unmatching structures in the source and destination. In my case this col(4) was the hierarchy, which was not set on the BPC site for this particular dimension.

Check what are the fields in the openhub and put them in the exact order in the mapping section of the transformation file.

In the openhub you can export as many fields as you want, even if not defined in the destination dimension.

Doublecheck carefully the structures, and it will load ok.

Hope this helps.

Kind regards,

Begonia