Skip to Content

Consoldiation Account Data Loads

Hi all,

In loading Account members from ERP into BW for BPC, we need to populate certain properties for the consolidation to work (ACCTYPE, RATETYPE, DIMLIST etc.).

The 0ACCOUNT object from ERP will only have on it a balance sheet indicator which is not enough detail to derive the properties. We need to be using the full ERP Chart of Accounts and use ERP Financial statement version for the hierarchies. It is impractical to manually maintain the properties in BPC for each account and account hierarchy nodes.

What is the best approach in loading the properties? We can leverage the Account Range groups from ERP and map those in a DSO in BW. That could be in turn used in a transformation up update the account properties. However that approach will no address the account nodes needing an AccType.

I was hoping there is a best practice / approach for this.

Many thanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Aug 22, 2016 at 08:21 AM

    Just an update,

    We are using the SKA1 extraction as a basis for the account ranges. This populates a custom characteristic which has the acctype / rate type properties which can be manually updated in BW. There are only about 40-50 ranges, so its not too troublesome. We will also use it for exception to the range rules.

    I think this is probably the most workable solution for the attributes, and we can extended it for other attributes if needed (i.e. DIMLIST TYPEELIM etc.)


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 08, 2016 at 11:49 AM

    Hi Tim,

    If you have so many transformations to be done for data coming from ERP...then my suggestion for you is to create a staging cube in BW same structured(same info objects) like BPC cube.... Load the data both master and Transaction from ERP --->BW cube(standard)----->Staging cube in BW(for BPC) ----> then BPC.

    Do all the mappings conversions transformations on BW side....because BW ETL is robust. In the end any complex transformations needs BW ETL processes like routines BADI's etc!

    This approach would be most convenient!

    For Acctype, if there are serial nos used to recognised the Chart of accounts then you can put a logic like Acct nos starting with 1XXXXXX are AST, with 2XXXXXX are LEQ etc.....If not then ask the business for any distinguisher in system.

    For would depend on the business case actually....but normally P&L accounts are AVG and Balance Sheet are END/CLO. You can used the Balance sheet flag for this or ACCTYPE.

    Other properties that are needed to run business rules, need to be maintained manually only I guess!

    Hope this helps....



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Timothy Atkins

      Maybe you can load that flat file in the info object used for Accounts?...😊 But I guess that will be a tedious activity for the users....will need to train them in doing that. Or can consult the BW consultant in automating that process... Its just a suggestion! I havent worked on Embedded version so....


  • Posted on Aug 10, 2016 at 10:56 PM


    I recently created a number of InfoObjects for a consolidation model in BPC embedded and I did it all manually. I created all the attributes, e.g. ACCTYPE, RATETYPE and so on. Then created all dimensions in RSD1. Then I used BPC web client, believe it or not BPC web client Administration works for this, and I populated the dimensions. It is cumbersome but I am a BPC person, so I don't have that much experience loading data from ERP.



    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.