Skip to Content
author's profile photo Former Member
Former Member

ZCOSTCENTER Hierarchy Load Error

Dear All,

Master data load for attributes and text were loaded successfully from ZCOSTCENTER hierarchy from BW to BPC10 NW with data manager package. When proceed to load hierarchy, the following error prompted:

Task name HIERARCHY DATA SOURCE:

Info: Hierarchy node includes text node or external characteristics

Record count: 2

Task name CONVERT:

No 1 Round:

Reject count: 0

Record count: 2

Skip count: 0

Accept count: 2

Task name HIERARCHY DATA TARGET:

Member XYZ does not exist

Submit count: 0

Member XYZ is a parent node that have been manually deleted in BPC dimension.

Thanks

Regards,

Michael Lim

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jun 03, 2014 at 04:16 PM

    Michael,

    While loading the Master data attributes select the option set filter by attribute or hierarchies in set selection option of data manager package. Its a radio button at the bottom of the screen.

    Next when you load hierarchies and you get rejected records, Please verify in BW that are those members present in the hierarchy if yes please check if they have any compounding. You can paste the screenshot of the BW infoobject hierarchy view and DM package logs for a better analysis and help.

    -Nikhil

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Anand,

      Thanks for your suggestion.

      I've successfully loaded the hierarchy node via option "Set filter by attribute or hierarchies"
      in set selection option of data manager package.

      However, when hierarchy load was not successful due to different naming convention of the parent node as parent node undergo conversion when loading hierarchy but not when loading masterdata attributes.

      In this case, when loading hierarchy, it could not map the child node to the parent node.

      Unless conversion happens before DMP load, unsure if there is any other workaround.

      Appreciate if you have any other idea on this.

      Thanks with regards,

      Michael Lim

  • Posted on Jun 03, 2014 at 07:09 AM

    Hi Michael,

    Please check what is the WRITE Mode that you have selected while running the package.

    The Write mode selected should be Update. This option will not delete any existing (including manually created) BPC dimension members.

    Please follow this link - http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02d0b47-3e54-2d10-0eb7-d722b633b72e?QuickLink=index&…


    Wish this helps..


    Regards,

    Bishwajit

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Bishwajit,

      Thanks for providing the link to masterdata load step by step.

      Yup, the write mode is in UPDATE mode.

      However, the scenario is DMP is not reloading the parent node which has been manually deleted instead of the load delete the existing masterdata.

      Thanks.

      Regards,

      Michael

  • author's profile photo Former Member
    Former Member
    Posted on Jun 03, 2014 at 11:09 AM


    Hi Michael!
    Check if the members that you have loaded to BPC correspond to those that exist in the hierachy in BW, it seems like you are missing some member.

    What were your settings when you loaded the base members? Did you select the attribute and hierarchy?

    BR
    Patrick

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.