DataBasis for Legal Consolidation

Dear all,
   We are implementing Legal consolidation with BCS 6.0. We only consolidate data with company level of data. Should we use 0BCS_C50 as our dataBasis or other cube (like 0BCS_C10) and remove the all profit center relayed objects? 
Best Regards,
Jeff

Hi Jeff,
Do not know if the cube 0bcs_c50 was designed for using with EC-CS. I only know that it is treated as obsolete.
The cube has item (0CS_ITEM), subitem (0CS_SITEM) and subitem category (0CS_SITEMCT).
I'm preaty sure that subitem is linked to item as subaccount to account (the same type and length).
The subitem category must be an analog of the MoveType (CHAR 3 both).
The dimension (0CS_DIMEN) is a compounding attribute to the consolidation unit (0CS_UNIT). It's definitely was entered in order to have some surrogate instead of time-version-dependent hierarchy of ConsUnits.
In the modern BCS system we have items with a possibility of creating nodes and MoveType is a separate infoobject.
The hierarchy of 0COMPANY (or the other infoobject) to be used as ConsUnit is version & time-dependent. So, there is no need in Dimension.
More than that. Please compare 0CS_UNIT (C50) & 0COMPANY (C11).
0CS_UNIT - awkward CHAR 18 - with a lot attributes that might be not relevant for your situation, plus compounding attribute.
0COMPANY - simple plain CHAR 6 without any burdening, but with hierarchy version & time dependance.
So, 0BCS_C50 is really obsolete!

Similar Messages

  • Built-in templates for Legal Consolidation in SAP BPC

    Hi guys
    I am doing a demo for legal consolidation and was wondering if there are built-in input scehdules (templates) in SAP BPC to assign the consolidation methods to entities (to let the system know how an entity needs to be rolled up in a group)?
    Also are there any input schedules (templates) to enter the Ownership % and Control % for various subsidiaries under a parent?
    Please let me know.
    Thanks,
    Ameya Kulkarni

    I don't think any of the default applications come with pre-built input templates.  The legal applications does come with a number of pre-configured business rules, but as far as pre-built input templates go none are available.  That being said, it is pretty easy to build a simple input template using the dynamic templates that come with BPC.  Starting with one of these you should be able to configure one of them for your demo without much trouble.  Let me know if you need help with that.
    Nick

  • BPC 5 - Best practices - Sample data file for Legal Consolidation

    Hi,
    we are following the steps indicated in the SAP BPC Business Practice: http://help.sap.com/bp_bpcv151/html/bpc.htm
    A Legal Consolidation prerequisit is to have the sample data file that we do not have: "Consolidation Finance Data.xls"
    Does anybody have this file or know where to find it?
    Thanks for your time!
    Regards,
    Santiago

    Hi,
    From [https://websmp230.sap-ag.de/sap/bc/bsp/spn/download_basket/download.htm?objid=012002523100012218702007E&action=DL_DIRECT] this address you can obtain .zip file for Best Practice including all scenarios and csv files under misc directory used in these scenarios.
    Consolidation Finance Data.txt is in there also..
    Regards,
    ergin ozturk

  • IC elimination for legal consolidation

    I am wokring on legal consolidation and am working on legalapp application.
    I notice that the input schedule template for IC elimination refers to dimension members of application finance. Similarly the Logic file (ICElim.lgx in the server refers to dimension and members of finance application.
    Are we expected to adapt tthe templates and logic files or are we supposed to perform IC elimination in Finance application and then transfer values to Legalapp application.
    How to trigger conolidation process and calculation of minority interest.
    Regards
    Srikaran

    You don't have to copy data from finance to legalapp for the intercompany eliminations.
    You enter Intercompany data directly in the legalapp application for the intersections of IC accounts and intco counterparts.
    Matching is normally done by creating logic that posts the entered ic data directly to the counterpart entity. From this you can create matching reports.
    IC elimination and EQ elimination are being generated by the combination of the stored procedures 'sprunconversion' and 'sprunconso'. The legalapp application has examples for both of them.
    I have never adopted the templates provided by apshell.
    Hope this helps,
    Alwin

  • Best practice data source from ECC 6.0 for legal consolidation in BPC NW7.5

    Hi there,
    after scanning every message in this forum for "data source" I wonder if there isn't any standard approach from SAP to extract consolidation data from ECC 6.0. I have to say that my customer is not using New g/l so far and therefore the great guide "how to get balances from ECC 6.0 ..." does not fully work for us.
    Coming from the old world of EC-CS there is the first option to go via the GLT3 table. This option requires clever customization and the need to keep both GLT0 and GLT3 in line. Who has experiences regarding maintenance of these tables in a production environment?
    We therefore plan to use data source 0FI_GL_4 which contains all line items to the financial documents posted. Does this approach make sense or will it fail because of performance issues?
    Any help is appreciated!
    Kind regards,
    Dierk

    Hi Dierk,
    Do you have a need for the level of detail provided by the 0FI_GL_4 extractor? Normally I would recommend going for the basic 0FI_GL_6 extractor, which provides a much more manageable data volume since it only gives the periodic activity and balances as well as a much smaller selection of characteristics. Link: [http://help.sap.com/saphelp_nw70/helpdata/en/0a/558cabb2e19a4db3097b81bba4fd0e/frameset.htm]
    Despite this initial recommendation, every client I've had has eventually had a need for the level of detail provided by the 0FI_GL_4 extractor (or the New G/L equivalent - 0FI_GL_14). Most BW systems can handle the output of the line-item extractors without much issue, but you should test using production data and make sure your system sizing takes into account the load.
    The major problem you can run into with the line-item extractors is that if your delta somehow gets compromised it can take a very long time (days, sometimes weeks) to reinitialize and this can cause a large load in your ECC and BW system. Also, for the first transport to production, it is important to plan time to initialize the delta.
    Ethan

  • Legal Consolidation: Entity structure question

    Hi Experts,
    Just want to ask if technical Entities are required in order for Legal Consolidation to work in SAP BPC 7.5 NW SP6? I'm using both R-Type (Currencies) and G-Type dimension (Conso Groups). In my first structure, I only have the following set up in my Entity and Groups dimension:
    Entity Dimension:
    ID          EVDESCRIPTION          PARENTH1     CURRENCY     INTCO     FX_TYPE     ELIM
    ALL_COMP     All Company                         
    COMPT1          Company Group 1          ALL_COMP                    
    COMP1          Company 1          COMPT1             USD          I_COMP1          Y
    COMP2          Company 2          COMPT1             USD          I_COMP2          Y
    COMPT2          Company Group 2          ALL_COMP                    
    COMP3          Company 3          COMPT2             USD          I_COMP3          Y
    COMP4          Company 4          COMPT2             USD          I_COMP4          Y
    Groups Dimension:
    ID          EVDESCRIPTION     CURRENCY_TYPE     ENTITY     GROUP_CURRENCY     PARENT_GROUP     STORE_ENTITY     STORE_GROUP_CURR     CONSO_TYPE     DATASRC_LEVEL     STAGE_ONLY     
    GCOMPT1     Company Group 1             G               USD                                   Y               A               
    GCOMPT2     Company Group 2             G               USD                                   Y               A               
    NON_GROUP     Non Group     
    In this set up, my Consolidation results in error "RUN_LOGIC:Accounts and entities do not match data in application OWNERSHIP". But if I change my set up to the following(with technical Entities), I don't get the error:
    Entity Dimension:
    ID          EVDESCRIPTION          PARENTH1     CURRENCY     INTCO     FX_TYPE          ELIM
    ALL_COMP     All Company                         
    COMPT1          Company Group 1          ALL_COMP                    
    COMP1          Company 1          COMPT1          USD               I_COMP1          
    COMP2          Company 2          COMPT1          USD               I_COMP2          
    COMPT2          Company Group 2          ALL_COMP                    
    COMP3          Company 3          COMPT2          USD               I_COMP3          
    COMP4          Company 4          COMPT2          USD               I_COMP4          
    ECOMPT1             Company Group 1                    USD                         Y
    ECOMPT2             Company Group 2                    USD                         Y
    Groups Dimension:
    ID          EVDESCRIPTION     CURRENCY_TYPE     ENTITY          GROUP_CURRENCY     PARENT_GROUP     STORE_ENTITY     STORE_GROUP_CURR     CONSO_TYPE     DATASRC_LEVEL     STAGE_ONLY     
    GCOMPT1     Company Group 1             G          ECOMPT1     USD                         Y          Y               A               
    GCOMPT2     Company Group 2             G          ECOMPT2     USD                         Y          Y               A               
    NON_GROUP     Non Group
    Am I just missing some properties or set up in my first that's why I'm getting the error or do I really need to create technical Entities for consolidation to work??
    Thanks,
    Marvin

    Hi nilanjan,
    I was pertaining to the Entities with ID that starts with "E". Anyway, I tried removing the values "Y" for property "ELIM" in the Entity dimension and removed the values for "ENTITY" and STORE_ENTITY in the Groups dimension and I don't encounter the error and consolidation calculates okay.
    Thanks,
    Marvin

  • Legal Consolidation VS Management Consolidation

    Hi Gurus,
    In the reporting application types
    " Financial type allows to perform Management consolidation function and in Consolidation type allows to perform Legal consolidation function. "
    What is the difference between Management consolidation and legal consolidation ?
    I am bit confused can some one explain me what exactly it mean with an example??

    Hi,
    For the consolidation purpose,the data record contains at least the following fields:
    company
    company-partner
    Profit Centre
    Profit Centre-partner.
    For legal consolidation, only company-related data matters. Because Profit centre data will be taken from the other source.For management consolidation, only Profit centre-related data matters.
    There will be 2 initial data sets,  should be created as Consolidation Areas to meet the business requirements , for example ASML -Legal Consolidation,ASMM-Management Consolidation.This is as according to the best in practice approach to have different sets of data for legal and management reporting.  Management is focused on per segment, per product reporting and statutory focused on the legal entity view. 
    Each consolidation area will only hold the relevant consolidation unit.  That is, the statutory consolidation area will only hold company codes and will not post/process to profit centres at all.  The management view will hold Company codes/profit centres (sub assignment object) and the users will post only to the relevant company codes/profit centres
    Also Pls check these links...
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FILC/FILC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECCS/ECCS.pdf
    http://help.sap.com/saphelp_sem40bw/helpdata/en/67/f7e73ac6e7ec28e10000000a114084/frameset.htm
    Re: Synchronize Master Data between BCS and BW within the same SEM system
    /message/1508507#1508507 [original link is broken]
    http://sap.ittoolbox.com/groups/technical-functional/sap-sem/dataflow-from-r3-to-sem-bcs-950671
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/6e01a04e-0a01-0010-dfbe-951c2c39d169
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/9057475ca611d4b2e30050dadfb23f/frameset.htm
    http://www.sapprofessionals.org/?q=sem_bcs_key_design_considerations_for_integration_points
    http://sapnewbie.blogspot.com/2006/03/sap-sem-bcs.html
    http://www.pragmatek.com/news/BW%20Reprint%20Jun%202004.pdf
    https://forums.sdn.sap.com/click.jspa?searchID=329906&messageID=549616.
    Follow this link.
    https://websmp103.sap-ag.de/sem
    Pls chk under for more detils: Forums -> SAP Solutions-> SEM-BCS.
    media library -> presentations -> SEM-BCS. Here u can find the relative document.
    Hope this helps.
    Regards,
    CSM Reddy

  • Does BPC 5.1 support separate Group/Currency dimensions for Legal?

    Hello All,
    I see in the documentation that I have for BPC 5.1 that currently the Legal Application does not support separate Group & Currency dimensions for Legal Consolidations.  Does anyone know if this is still true?  If not, is there new logic/documentation of this somewhere?
    Thanks,
    Michael

    Hi
    BPC each application can have only one rate dimension and normally its currency but for legal consolidation we use Groups as rate type dimension and where you can include you currencies also.
    The reason being the LC copies the numbers to groups first and then consolidate and similarly it uses same logic to convert into different currencies hence you can use same dimension for both.
    Else create user defined dimension for currencies which would make life miserable.
    Thanks and Regards
    Harish B K

  • Problem with Legal Consolidation for Journal

    Hi BPC Friends
    I have the application icmatching with data and I have written other values with Journal.
    I have run the package legal consolidation.
    I have this problem:
    for the value that I have loaded into the application, the logic consolidation works correctly, indeed it writes a new record with different datasource
    but for the value that I have written into the application using the Journal the logic doesn't work correctly, indeed it writes into the database a new record like the original but with contrary value so I lose also the value that I wrote with the journal
    Could you please help me?
    thanks
    regards
    Michele Medaglia

    Hello Michele,
    Basically what ever data that you input in journal as long as the selection on xdim is fulfilled the script will run normally.
    If its write in reverse and deleted your original data, it must be something wrong in your script, you can check at first.
    If the problem still you can't found, can you share us a little about the script?
    hope helps

  • BPC v7 for Legal and Tax Consolidation

    We need to save data by year using the legal organization structure and currency rates in place in that year.   It needs to be saved for at least 11 years for annual report purposes and tax audit purposes.  There are over 2000 entities including parents in any one years org structure.  Has anyone dealt with large entity hierarchies saved for multiple years?  What is the best way to handle a situation like this.  I know that in Hypereion Enterprise you can consolidate different years data with different organization structures but I am not sure that BPC can handle this.

    SAP BPC's Legal consolidation provides for this very issues. If you can have a look at the IFRS Starter kit for BPC 7.0, it has already the org structure that can change from period to period. The actual hierarchy itself does not change over time, but the way its consolidated is driver by an application called Ownership in which group structures can be defined.
    This will allow you to define structures that are impossible to represent in a traditional hierarchy, eg Joint venture owned by a company's two subsidiaries.
    In the IFRS Kit, there is documentation describing how consolidation works in this way.
    This same functionality is available in both MS and NW version.

  • Template Blueprint for management and legal consolidation for BPC 7.0 NW

    Hi Gurus,
    Does anyone have a template buleprint document for starting with management and legal consolidation in BPC 7.0NW
    If you have request you to share me the documents
    appreciate your help and many thanks in advance
    Deepak

    Hi,
    please find big volume of information from these threads
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b25a12-7082-2b10-5c86-c227b9397fb3?overridelayout=truehttps://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b09d5f42-36a4-2b10-cb82-fa58febeb7c2?overridelayout=true
    Re: Consolidation for SAP BPC
    also you can get latest information from
    http;//service.sap.com/pam
    regards
    nag

  • Legal Consolidation problem

    Hi Experts ,
    Couple of days before , we restored the appset in the our development server .
    After we did the procees all the dimensions and optimization all the application .
    When i runned the legal consoldation , its running but no effect in the database .
    This our legal consolidatio  packaga file  :
    PROMPT(RADIOBUTTON,%CHEKCLCK%,"Select whether to check work status settings when running logic.",1,{"Yes, check for work status settings before running logic","No, do not check work status settings"},{"1","0"})
    PROMPT(SELECTINPUT,,,"Please select category, entity and time for restatement",%CATEGORY_DIM%%TIME_DIM%%CURRENCY_DIM%)
    TASK(Execute formulas,USER,%USER%)
    TASK(Execute formulas,APPSET,%APPSET%)
    TASK(Execute formulas,APP,%APP%)
    TASK(Execute formulas,SELECTION,%SELECTIONFILE%)
    TASK(Execute formulas,LOGICFILE,%APPPATH%\..\AdminApp\%APP%\LegalConsolidation.lgx)
    TASK(Execute formulas,RUNMODE,1)
    TASK(Execute formulas,LOGICMODE,1)
    TASK(Execute formulas,CHECKLCK,%CHEKCLCK%)
    I have one question here , we have the LGF file in the script login , but in the in package file it call in LGX.
    R we need do anything ...
    Regards
    Daya

    We done the both things .
    I done the validated and save , then ran the legal consolidation , the package runned suceessfuly .
    The data is not chnaged..
    Is there any way to track the issue.....
    In my view status , it showed  as
    TOTAL STEPS  1
    1. Default Formulas:        completed  in 0 sec.
    [Selection]
    CHEKCLCK= Yes
    (Member Selection)
    Category: ACTUAL
    Time: 2011.DEC
    Groups: C_OLAM
    Regards
    Dayalan M

  • Currency and Groups Dimensions in Legal Consolidation, BPC 7.5

    Dear BPC Experts:
              I am using BPC 7.5 NW SP03, and building Legal Consolidation now. According to the SAP Library,http://help.sap.com/saphelp_bpc75_nw/helpdata/en/bpc_nw_index.htm, it says in 7.5, the currency and groups dimension are required and should hold currency members and consolidation members seperately. I have couple of questions about this design.
    1. Are GROUPS and CURRENCY dimensions both included in Legal Consolidation Application at the same time?
    2. How to move data in currency diemnsion into corresponding members in GROUPS dimension?
        For example: THe GROUPS member, CG1(its currency is USD). How to let data in currency USD move to CG1.
    3. In Legal Consolidation data package, should I modify the prompt dimension from CURRENCY_DIM into GROUP_Dim?? cause 7.5 has CURRENCY dim in its package setting at default. However, the consolidation package is based on GROUP perspectives.
        Does anyone give me any idea in it? I really appreciate your help.
    Best Regards,
    Fred Cheng

    Hi Collet,
    Thanks for such a quick response. Based on your answer,
    The group-type dimension is used for storing the group component of legal consolidation. The group-type dimension represents the relationship of entities for a given consolidation result. This group is consolidated in a single currency, so there is no need to have another dimension. As of Planning and Consolidation 7.5, you can continue to use the currency-type dimension for this purpose, or you can split it into a group-type dimension (type G) and use a pure currency-type dimension (type R) to allow reporting in multiple group currencies.
    If at all I go by that will that be sufficient to have only Group Dimension and ignore RptCurrency field in BPC 7.5?
    As of now I am having my Group Dimension looks like this.
    Member ID          EVDESCRIPTION        GROUP_CURRENCY        PARENT_GROUP      ENTITY
    G_CG1                XXXX                          USD                                                                 E_CG1
    G_CG2                XXX                            USD                                   G_CG1                   E_CG2
    G_CG3                XXXX                          USD                                   G_CG2                   E_CG3
    So now do I need to enter any RptCurrency Members under Group Member ID column to have RptCurrency ignored once for all. By the way our RptCurrency and Group Currency is USD only.
    Please advise as right now we are not able to have Currency Conversion Functioning properly. I mean when I executed FXTRANSLGF, I am able to my DM status as Successful but saying 0 Submitted   0 Success   0 Fail
    I am unable to crack this. I tired playing Groups and RptCurrency but same result. Successful but no records. We have maintained all Exchange Rates corrctly.

  • Intercompany Elimination is doubling after running Legal consolidation

    Hi BPC Guru's
    Intercompany Elimination is doubling after running Legal consolidation Data Manager Package 2nd time tripples when run 3rd time and so on..Only change is that for resolving an issue with balance carry forward, we had changed the datasource type property for the audit trail members that store the eliminated amounts ealier this was A (Automatic) we changed that to (Manual) M and this is causing the doubling to start because if i change it back to A then there is no doubling..but the eliminated values are incorrect.
    Would be great somebody provides with their expertise.

    Hi Arnold,
    This issue is related to another issue that was discussed on the http://scn.sap.com/thread/3247090
    Till December all was well. Come January, after I run the consolidation package, the rule takes into account the balance from December for each month’s calculation:
    There were 2 suggestions from the above post that i tried:
    Check if “COPYOPENING” property in the Audit Trail dimension should not be “Y” -> It was Y for me but changing it to “N” did not solve my issue.
    Opening Flow should be assigned “FLOW_TYPE” property with the value of “OPENING”
    Both these are done in my system. But still the above issue exists. I also tried to change the rule to “Periodic” type but did not help.
      What I basically want is for BPC to ignore the values from previous year and run the calculation based on only the current month’s data.
    When we first faced this issue during January closing, as a temporary fix, we changed the “DATASOURCE_TYPE” property of the audit members used in Eliminations from A to M. This made the rule not consider December balances in the calculation.
    But doing this gave rise to the doubling issue.
    Any suggestions?
    Regards,
    Shruti

  • Introducing Business Area for Management Consolidation

    Our Business has been using Business Area for all management reporting purpose since SAP had been implemented some 15 yrs back in our organization. They do not want to use Profit Center for management consolidation purpose in SEM-BCS. Our Project Manager wants to go with one data basis with one cons area.
    I have planned to remove all Profit center related characteristics (alloc cons Profit center, cons Profit center grp, cons profit center, Investee unit- profit center and Partner cons profit center) and introduce Business Area with Sub-assignment role. Under Breakdown category, I will create necessary sub-assignment from comp code GL transaction data to Business Area. I can do legal consolidation in the normal course and with sub-assignment and using breakdown category, I can derive Business Area based consolidation and also I can generate both legal and mgmt reports.
    Whether my understanding of the data basis architecture is correct? Is it prudent to proceed further based on my understanding?
    Dan & Eugene: I look forward for your feedback.
    Thanks in Advance,
    Tim

    Dan: <i>For management reporting you may not want to post eliminations between companies where the business areas are the same.</i>
    If the Business wants to see the eliminations between companies, within the same business area, as part of BEx reports, what should I do? They do not want to execute consolidation functions in UCMON but just want to see how the eliminations have taken place between companies with in the same business area. 
    Dan: <i>As long as the partner company and partner business area are consistently included for the intercompany transactions, the eliminations between Legal and Management will agree at the top-level of each hierarchy.</i>
    Have I to introduce one more InfoObject Partner Business Area in the data basis and assign the role Sub-assignment once again?
    Thanks in advance.

Maybe you are looking for