Skip to Content

Flexible upload of master data and hierarchies of consolidation infoobjects is declared to be possible. It is stated in help information. There is even the OSS Note 607766 for Uploading master data of Hierarchies.


However, it doesn’t work properly if you create a file for upload with the proposed format. For example, for the hierarchy like this:

image


the proposed format of a file for upload is recommended like the following:


image


The document says that “Note that remarks in parentheses are only intended to relate the entry to the hierarchy drawing above, and are not a part of the file content.”

Loading the file like this creates the item hierarchy, but nodes are loaded incorrectly, just one node and several leaves.

I had to play with the file format and, finally, succeeded. The proper format of the file is provided later in this blog.


Step-by-Step Procedure

Flexible Upload Method Creation

Execute UCWB transaction or go in SEM-BCS Consolidation Workbench from SAP menu. Choose Process View and double click on Flexible Upload method.


image


In the open Flexible Upload frame right click on a free area and choose <Create>.


image

Position cursor to the new method row, click on the left part of it and type in a code of the method to be created.


image

In the details frame of the method type in the method name and choose <Items> row from a drop down menu for a Data Type.


image


After that in the <Field Catalog> tab you’ll see a predefined structure of the fields for uploading hierarchies. You can not add or delete fields here. Though, you

may change sequence of the fields within the structure by drag and drop.


image


From the right pane drag and drop fields into <Header> and <Data Rows> nodes of the structure.

Choosing Version, Chart of Accounts and Cons Area fields is important. If you don’t select them, you may not see uploaded data.


image


In the <Settings> tab choose the column width and a column separator, comment row sign, update mode and <Use Row and Data Rows> as Row Types.


image


Save the method.


Format of the File for Upload

Now we return to the proper file format. The part of the file for master data load is shown below. image


Here we see the first two lines with comments explaining the rows structure. The 2nd row contains the header’s data. They allow data to arrive to the proper version, items catalog and consolidation area.

Pay attention to the fact that with <Row Type> set to “Header Row and Data Rows” in the flexible upload method definition, we need to specify in the first column the row type as following:

  • 1  –  for data header,
  • 2  –  for data rows,
  • 3  –  for hierarchy rows.

And below is the part of the file for hierarchy upload.


image


The hierarchy row starts with “3”. “BS” in the second column is the hierarchy name.

The first hierarchy node (BSROOT in our case) is a text node and created automatically. You need only to provide the node’s name.


IMPORTANT: The missing part of the file (comparing with the format recommended in help and the note shown earlier) is located in the <Node> column.

The cell in this column corresponding to the particular node should remain blank for nodes whose parent is the first text node BSROOT (i.e. for nodes of the 1st hierarchy level).

For the nodes of the lower levels specify in the corresponding cell of <Node> column just the node code (shown in the picture with a blue rectangular).

The columns shown here as <Short> and <Long>, as per help, may contain the short and long descriptions of the hierarchy to be created. However, I was not able to upload these descriptions.


The file format explained here is a prerequisite for the proper hierarchy load. And as far as I know, this important detail is missed in the SAP documents. Since you may rearrange fields in the <Hierarchy> node of the flexible upload method structure, just note that the <Node> column in the file should correspond to the <Item> field in the structure:


image


The Method Execution

You don’t need to assign the method to task and consolidation monitor tasks hierarchy. Execute it simply from a context menu of the method and choose the file to be uploaded.


image

After method finishes the import you may look at the upload log, to make sure that everything was uploaded smoothly.


image


The Result

To see the data loaded, double click on <Item> row.


image


The frame for hierarchies opens. Expand nodes and see the hierarchy structure.


image


Double click on any node or leaf and see that all attributes of the item has been loaded.


image

Do not forget to press the <Save> icon for saving uploaded data.

So, by using the flexible upload we can load texts and attributes of FS Items, and their hierarchy in one go! Though, you may load them separately, master data first, and then the hierarchy (using two different flexible upload methods and data files).

You can compare the master data of FS Item in SEM-BCS with the corresponding infoobject in SAP BW (0CS_ITEM by default) and see that the Item infoobject in BW has different master data. Flexible upload allows us to bring into BCS the proper attributes of FS Item. By using the older technique of synchronizing master data in BW and BCS (with the programs like UGMDSYNC) you may fetch into BCS only data visible in BW.

To report this post you need to login first.

15 Comments

You must be Logged on to comment or reply to a post.

  1. Dirk Herzog
    Great Work, Eugene!
    Unfortunately only a handful of SDNers will be able to understand what it’s all about because it is more directed towards BCS consultants. But those of us that do BCS consulting will really appreciate your work.

    Dirk

    (0) 
  2. Benjamin Maier
    During the migration process problems have been reported for this blog. The blog content may look corrupt due to not supported HTML code on this platform. Please adjust the blog content manually before moving it to an official community.
    (0) 
  3. K-D Vo
    If I have multiple hierarchies to load for one FS Item, what parameter setting do I have to change to make sure that file I’m going to load is going to be a new hierarchy and not overwrite the previous file I just loaded?

    K-D

    (0) 
  4. Shade Adekoya
    During the migration process problems have been reported for this blog. The blog content may look corrupt due to not supported HTML code on this platform. Please adjust the blog content manually before moving it to an official community.
    (0) 
  5. Amit Sharma
    Hi Eugene,
    This is a very good blog and indeed a very helpfull one.Just one thing i needed to know is whish “Catalogue” is to be specified.Motreso in header selecteion you have selected “Con Atrea” but that doenot appear in the upload spreadsheet.
    Moreso does the above presumes that all the masters and transaction data are already available in SEM?

    Best Regards
    Amit

    (0) 
    1. Eugene Khusainov Post author
      Hi Amit,

      Frankly, didn’t get your question about “Catalogue”.
      Cons Area (?) I selected in the header structure corresponds with “60” in the upload file.
      At the moment of this particular example execution, I had to have in SEM-BCS just breakdown categories. No other master or transaction data were required.

      Best regards,
      Eugene

      (0) 
  6. SAPEPM con
    Hi Eugene,

    While trying to append some new FS items to an existing hierarchy I’m facing issues.

    As suggested by you, I am mapping the ‘Node’ column in the load file to ‘Item’ in the method.

    However in this case the nodes are text nodes (e.g. ‘INTERNALACCRUALS’)  and system seems to be taking this as an Item and hence truncates it to the length of Item and then isseus error message that ‘the value of Item is invalid.

    Please note that the nodes as well as the hierarchy already exist and we are just trying to append new FS items to the hierarhcy.

    We are on version 4.0.

    I’m sure I’m doing something wrong but not able to figure out what. Please could you help me with this?

    Best Regards,

    SSC

    (0) 
  7. Venkat reddy

    Hi experts,

    much help full blog…

    Hi Eugene,

    I am trying to upload consilidation unit ->Cons. profit centre hierarchy

    I am facing the same problem, one node with several leaves loaded with flexible upload. I followed the order of field catalog in my file format.

    Please find below file format which i uploaded and suggest me the changes required for file format.

    * Hierarchy Cons. PC Group From Value To Value Long Text Medium Short text Successor First Cons at EOP Period of first cons Period of Divestiture Year of first cons Year of Divestiture
    3 95 95
    3 95 999999 11 12 2012 9999
    3 95 3252
    3 3252 8371
    3 95 183
    3 95 5790
    3 5790 151 1 12 2000 9999
    3 5790 2502 1 12 2000 9999

    the result of hierarchy is

    95 Hierarchy

       95 – Node

           999999

           3252

           183

           5790

    Expected result is

    95 Hierarchy

       95 – Node

           999999

           3252

                  8371

           183

           5790

                   151

                   2502.

    Kindly suggest me the changes in needed in file format.

    Best Regards,

    venkat

    (0) 
    1. Eugene Khusainov Post author

      Hi Venkat,

      There is one more column in the file in my blog: “Node”. If your node is not a child of the main hierarchy’s root,  repeat there the node code (see the blog above).

      (0) 
      1. Venkat reddy

        Hi Eugene,

        Thanks for your quick response, i checked the option Predecessor/successor in Hierarchy in Settings tab and maintained Hierarchy & Cons. PC group as Predecessor, Cons. PC group & Cons. Profit centre as Successor, then generated file format in the order of field catalog.

        run the flexible upload method, it works fine..

        Regards,

        Venkat

        (0) 

Leave a Reply