Currency Bearing consolidation Unit

We are having Matrix consolidation and need to do all consolidation execution by profit center.
What is the benefit of giving this role to profit center than company.
Can someone explain how this helps in operation..

Hi Venkat,
It's not a benefit. It's a must to have currency bearing unit. As I said, every record in ECC belongs to a particular company. And the system must know in which currency all amounts belonging to this company are nominated.
Here is an example of, IMHO, wrong decision of making profit center a currency bearing unit:
Let's say we have 2 companies, C1 (local currency = INR) & C2 (local currency = EUR) and 3 PC, P1, P2, & P3. The matrix looks like following:
___P1_P2_P3
C1_X__X
C2____X___X
In this example transactions involved P2 & C1 will be nominated in INR, but P2 & C2 - in EUR.
What the local currency will you set for profit center P2, INR or EUR?
Edited by: Eugene Khusainov on Apr 7, 2008 7:10 AM

Similar Messages

  • Consolidation Unit - Local Currency

    Experts,
    We need to change the Local Currency for a couple of Consolidation Units/Companies - What are the possible ways to achieve this ?
    1. Delete all transaction data, change the settings and then reload it ?
    Or is there any other better way to take care of this ?
    All answers would be duly appreciated and rewarded with points.
    Thanks,
    Nandita

    Nandita
    Pls find the SAP Link for your Info
    http://help.sap.com/saphelp_sem60ep1/helpdata/en/62/f7e73ac6e7ec28e10000000a114084/frameset.htm
    Thx
    Ramana

  • Setting currency and measurement unit for a field in an ALV report

    Plz give sample code to set currency and measurement unit for a field in an ALV report

    dear friend
    i am seanding you
    the display form
    if you need select form
    and process form also pls keep in touch.
    if help full rewards are expecting.
    yours
    vivek
    FORM build_field_catalog .
      DATA: w_dthigh(10).
      CLEAR fcat.
      fcat-fieldname = 'VBELN'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'COMMERCIAL INVOICE'.
      fcat-seltext_m = 'Commercial Invoice'.
      fcat-seltext_l = 'COMMERCIAL INVOICE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-key = 'X'.
      fcat-hotspot = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'EXNUM'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'EXCISE INVOICE'.
      fcat-seltext_m = 'Excise Invoice'.
      fcat-seltext_l = 'EXCISE INVOICE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-hotspot = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'EXDAT'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'EXCISE DATE'.
      fcat-seltext_m = 'Excise Date'.
      fcat-seltext_l = 'EXCISE DATE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'D'.
      fcat-datatype = 'DATS'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'NAME1'.
      fcat-outputlen = 30.
      fcat-seltext_s = 'CUSTOMER'.
      fcat-seltext_m = 'Customer'.
      fcat-seltext_l = 'CUSTOMER'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-lowercase = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'ZZPD'.
      fcat-outputlen = 15.
      fcat-seltext_s = 'COUNTRY'.
      fcat-seltext_m = 'COUNTRY'.
      fcat-seltext_l = 'COUNTRY'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-lowercase = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'WERKS'.
      fcat-outputlen = 4.
      fcat-seltext_s = 'PLANT'.
      fcat-seltext_m = 'Plant'.
      fcat-seltext_l = 'PLANT'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-key = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'ARKTX'.
      fcat-outputlen = 40.
      fcat-seltext_s = 'MATERIAL DESCRIPTION'.
      fcat-seltext_m = 'Material Description'.
      fcat-seltext_l = 'MATERIAL DESCRIPTION'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-lowercase = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'FKART'.
      fcat-outputlen = 4.
      fcat-seltext_s = 'Billing type'.
      fcat-seltext_m = 'Billing type'.
      fcat-seltext_l = 'Billing type'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      fcat-key = 'X'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'INCO1'.
      fcat-outputlen = 5.
      fcat-seltext_s = 'INCO TERMS'.
      fcat-seltext_m = 'INCO TERMS'.
      fcat-seltext_l = 'INCO TERMS'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'INCO2'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'INCO TERMS DES'.
      fcat-seltext_m = 'INCO TERMS DES'.
      fcat-seltext_l = 'INCO TERMS DES'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      APPEND fcat.
    CLEAR fcat.
    fcat-fieldname = 'FKIMG'.
    fcat-outputlen = 14.
    fcat-seltext_s = 'QUANTITY'.
    fcat-seltext_m = 'Quantity'.
    fcat-seltext_l = 'QUANTITY'.
    fcat-ddictxt = 'M'.
    fcat-inttype = 'P'.
    fcat-datatype = 'QUAN'.
    APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'FKLMG'.
      fcat-outputlen = 10.
      fcat-seltext_s = 'QUANTITY'.
      fcat-seltext_m = 'QUANTITY'.
      fcat-seltext_l = 'QUANTITY'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'QUAN'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'MEINS'.
      fcat-outputlen = 5.
      fcat-seltext_s = 'UNIT'.
      fcat-seltext_m = 'UNIT'.
      fcat-seltext_l = 'UNIT'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CHAR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'KBETR'.
      fcat-outputlen = 8.
      fcat-seltext_s = 'RATE'.
      fcat-seltext_m = 'Rate'.
      fcat-seltext_l = 'RATE'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'NSR'.
      fcat-outputlen = 8.
      fcat-seltext_s = 'Exmill'.
      fcat-seltext_m = 'Exmill'.
      fcat-seltext_l = 'Exmill'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'KURSK'.
      fcat-outputlen = 8.
      fcat-seltext_s = 'EXCHANGE RATE'.
      fcat-seltext_m = 'Exchange Rate'.
      fcat-seltext_l = 'Exchange Rate'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'WAERK'.
      fcat-outputlen = 5.
      fcat-seltext_s = 'CURRENCY'.
      fcat-seltext_m = 'Currency'.
      fcat-seltext_l = 'CURRENCY'.
      fcat-ddictxt = 'M'.
      fcat-inttype = 'C'.
      fcat-datatype = 'CUKY'.
      APPEND fcat.
      CLEAR fcat.
      fcat-fieldname = 'LCURR1'.
      fcat-outputlen = 14.
      fcat-seltext_s = 'GROSS AMT'.
      fcat-seltext_m = 'Gross Amt'.
      fcat-seltext_l = 'GROSS AMT'.
      fcat-ddictxt = 'L'.
      fcat-inttype = 'P'.
      fcat-datatype = 'CURR'.
    fcat-do_sum = 'X'.
      APPEND fcat.
    ================================= *****************
      fheader-typ = 'H'.
      SELECT SINGLE butxt
        FROM t001
        INTO fheader-info
       WHERE bukrs EQ '1000'.
      APPEND fheader.
      CLEAR fheader.
      fheader-typ = 'H'.
      fheader-info = 'Daily Shipments For Exp'.
      APPEND fheader.
      CLEAR fheader.
    Plant
      SORT s_werks BY low.
      READ TABLE s_werks INDEX 1.
      fheader-typ = 'S'.
      WRITE s_werks-low TO fheader-key.
      SORT s_werks BY high DESCENDING.
      READ TABLE s_werks INDEX 1.
      IF s_werks-high NE space.
        CONCATENATE fheader-key 'TO' s_werks-high INTO fheader-info
                                SEPARATED BY space.
      ELSE.
        WRITE fheader-key TO fheader-info.
      ENDIF.
      CLEAR fheader-key.
      fheader-key = 'PLANT : '.
      APPEND fheader.
      CLEAR fheader.
    Billing Typ
    SORT S_FKART BY LOW.
    READ TABLE S_FKART INDEX 1.
    FHEADER-TYP = 'S'.
    WRITE S_FKART-LOW TO FHEADER-KEY.
    SORT S_FKART BY HIGH DESCENDING.
    READ TABLE S_FKART INDEX 1.
    IF S_FKART-HIGH NE SPACE.
    CONCATENATE FHEADER-KEY 'TO' S_FKART-HIGH INTO FHEADER-INFO
                             SEPARATED BY SPACE.
    ELSE.
       WRITE FHEADER-KEY TO FHEADER-INFO.
    ENDIF.
    CLEAR FHEADER-KEY.
    FHEADER-KEY = 'DOCUMENT TYPE : '.
    APPEND FHEADER.
    CLEAR FHEADER.
    Date...
      fheader-typ = 'S'.
    FHEADER-KEY = S_FKDAT-LOW.
      WRITE s_fkdat-low  TO fheader-key.
      WRITE s_fkdat-high TO w_dthigh.
      CONCATENATE fheader-key 'TO' w_dthigh INTO fheader-info
                              SEPARATED BY space.
      CLEAR fheader-key.
      fheader-key = 'PERIOD : '.
      APPEND fheader.
      CLEAR fheader.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
        EXPORTING
          i_list_type     = 0
        IMPORTING
          et_events       = fevents[]
        EXCEPTIONS
          list_type_wrong = 1
          OTHERS          = 2.
      READ TABLE fevents WITH KEY name = 'TOP_OF_PAGE'.
      IF sy-subrc = 0.
        fevents-form = 'TOPOFPAGE'.
        MODIFY fevents INDEX sy-tabix.
        CLEAR fevents.
      ENDIF.
      rptname = sy-repid.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
                        EXPORTING
                          i_callback_program                = rptname
                          it_fieldcat                       = fcat[]
                          i_default                         = 'S'
                          it_events                         = fevents[]
                          i_save                            = 'X'
                         TABLES
                           t_outtab                          = it_output[]
                      EXCEPTIONS
                        PROGRAM_ERROR                     = 1
                        OTHERS                            = 2
    ENDFORM.                    " BUILD_FIELD_CATALOG

  • Concept of Integrated Consolidation Unit of SEM BCS

    HI Experts,
    I'm now in the SEM BCS 4.0 and BW 3.5 implementation. Previously I was the ECCS specialist and before the FI and AM specialist.
    Now I'm in SEM BCS implementation.
    I have one question in connection to the integrated consolidation unit. As the reference, I take the concept of this using the ECCS.
    As you might know, the creation of integrated consolidation unit for using realtime update method in ECCS, is pulled from FI company ID.
    Meanings if I set the configuration properly, I can pull out the company master data as the consolidation unit master data in consolidation monitor.
    Now, in SEM BCS, I want to do the same thing. I mean, off course I can create company ID in R/3 and then create the consolidation unit manually using UCWB. But this scenario can create inconsistency, and I also think this is not the right concept of doing integration between R/3 and SEM BCS.
    My question is : what is the concept of this master data integration, and what is the proper way to do it?
    Any advise on this question is highly appreciated.
    Thank you in advance.
    regards,
    Halim

    Hi Halim,
    You need to build properly your data basis in data model.
    Assign your company to a consolidation unit role:
    http://help.sap.com/saphelp_sem350bw/helpdata/en/dd/f3783bcfef4a2de10000000a114084/frameset.htm
    I sent to you the file concerning BCS that you asked for in another thread.
    Best regards,
    Eugene

  • How to link ECC Company code with BCS Consolidation unit

    I have to create new consolidation unit in BCS, parallelly in SAP R/3 also I have created a company code.
    I could read following in the forum :-
    The Company Codes from ECC are assigned to the characteristic Company in BCS, thus creating a one to one relationship between ECC & BCS company codes.
    BUT HOW TO DO THE SAME.
    Also any advise on Profit centre and cost centre etc in BCS in line with ECC. This is first time I am configuring in BCS,

    Typically in ECC company codes are assigned to a company. The company is typically used for cons unit in BCS, but it is not uncommon for company code to be used as cons unit.
    When company code is used, it is an attribute of the characteristic company and thus in the load mapping, the company is mapped to the attribute company code. This results in company code being mapped to company.
    Otherwise, if company code is in the databasis as the cons unit role, then it is simply mapped to company code to company code.
    For profit center and cost center, these are typically assigned the role subassignment, but it is not uncommon for profit center to be a cons unit for a matrix consolidation. However, these characteristics must first be included in the totals/databasis infocube.

  • Consolidation Unit Clearing account for Income / Expenses elimination

    Hi,
    When companys are leaving the group, where the parent comapany has some income/expenses elimination transactions with the company leaving, there is still balance on the parent company on consolidation unit clearing account with the company leaving the group as partener company.
    This shows incorrectely the retained earning for the parent company for posting leve20 when balances on consolidation unit clearing account is not included. Please advise.
    We are not unsing COI but we are using Group change functionalities when company leaves the grop.
    Furthere, in all auto elimination document type for Balance Sheet Elimination and Income statement elimination, we have assigned same consolidation unit clearing account. Please advise.
    Best Regards,
    UR

    When viewing the results using the standard reporting mode I suspect the balances are okay. Please clarify in detail how the data is being analyzed so we may better assist.

  • SEM-BCS how to make Consolidation Unit with Business Area

    Hi all,
    I am newbie in SEM-BCS and implementing BW-based BCS. Our situation is as follows.
    Situation
    - we have 7 companies worldwide and 4 different Business areas.
       Every company consists of at least two business areas in R/3.
    - we have sales transaction in FI among companies.
    requirement
    - we need consolidated F/S in whole consolidation group and consolidated F/S in Business area level.
    actually, we are planning to make the consolidation unit in company level.
    Do we have to break down consolidation unit in business area? or just breakdown category solves our requirement?
    If we have sales transaction even between business areas within certain company, do we have to make it in business area?

    Following are the answer to your questions…
    Q:   What to do for using this cube in BCS?
    A:    Add the business area to the cube. Generate the data basis and the business area gets added to all ODS/DSO , virtual cube.
    Suggestion: To avoid deleting the Profit center cube, since you can reduce the complication.
    Q:   Is it the problem about DATA BASIS Role?
    A:   No. Assign the role of subassignment or consolidation unit as needed. If you are giving the role of consolidation unit to business area, you need to insert the char Partner business area also in the cube.
    Q:   Is there some materials to solve this situation?
    A:   Refer the matrix consolidation material in help.sap.com from BCS portion.  As per SAP literature any relevant object can be made as second consolidation unit such as business area, functional area etc. Don’t fear. Once you start it the issue will be resolved in few days.
    Expected complication:
    If you are going to make business area as subassignment then it is simple. But if you are making business area as Consolidation unit, go for partner business area in cube.
    Ensure with your BI consultant that all BCS messages are addressed in BI infoobject for business area specifically.
    Things can get complicated only if we allow for it get complicated. But you are doing great.. Keep  posted.. Good luck.!!!..

  • Consolidation unit's hierarchy can not be organized well in BCS

    Hi,gurus here.
    We are using SEM-BCS to analyse business consolidation based on BW.
    In BW,the consolidation unit's hierarchy is good,but when we execute the data load task in BCS,the consolidatioin unit in BCS can not be organized as an entire hirarchy well.
    What's wrong?

    Hi Dan,
    Thanks for your answer.
    Youu2019re saying that although the data is loaded is ignored in the reporting.
    But if data is loaded isnu2019t it considered in the consolidation methods? As in the method for  IU IU Elimination and Reconciliation or Consolidation of Investments?
    Thanks for your help.
    Best regards.

  • Balance carryforward consolidation unit with equity method

    Hi experts,
    One question in relation with balance carryforward in SEM BCS 4.0. Do Additional finantial data of Consolidation unit with equity method must be carried forward to following periods?
    I have a problem with AFD validation for equity method.
    Best regards,
    Beatriz B.

    Thanks Halim,
    I am not using consolidation unit combination. It is only Legal Consolidataion. However, I have fixed the problem by changing the master data of consolidation unit. I have enabled FCEP.
    I have one more question. Do I have to run Consolidation Group Change Task also when I am switching from Equity method to Purchase method for Associate companies?
    When I am changing from Equity to Purchase method all the previous C/I postings are reversed, but the profit of Associates which was already accounted by holding company in the previous period is transfered to Net Income-Method Change and second effect is given to Goodwill (GW is enhanced).
    Hence, post change of method, when I upload TB of Associate, the Net Income is not eliminated to the extent of the profit Adjusted on account of Method change.
    Please suggest,
    Thanks,
    USR

  • "No Fiscal Year Variant assinged to consolidation unit" error for 3EC_CS_1A

    Hi,
    I'm getting following extraction error using RSA3 for datasource 3EC_CS_1A in R3 (4.7) system. Could someone shed some ideas on how to fix it.
    No fiscal year variant assigned to consolidation unit 0000000000000000XX.
    same error is coming for all consolidation units.
    I checked ECMCT table and it has records in it.
    I went to "Consolidation unit change" using CX1N and found out that above consolidation unit has our customer defined "standard fiscal year variant assigned" for the corresponding ledger listed in ECMCT.
    What else might be missing & how to fix it. same error in both DEV & QAS. Appreciate any inputs
    Hari Immadi
    http://immadi.com
    SEM BW Analyst

    thanks for your post.
    I checked T009 and see that fiscal year variants are maintained. K4 as well as "customer defined standard fiscal year variant". what else might be missing.
    Hari Immadi
    http://immadi.com
    SEM BW Analyst

  • Consolidation Unit in the wrong position in Accounting Techniques tree

    Hi all,
    I'm facing a problem with a consolidation unit (A) in the Accounting Techniques tree (T1).
    The issue is resolved when I delete the unit A from the consolidation group tree (T2) but, when I add the unit A to the consolidation group tree (T2) again, the unit appears in two places, and that is not correct.
    I've tried to delete and move the unit through the Accounting techniques tree (T1), but the problem continues.
    Can you help me??
    Thanks in advance.
    Inge Eichhorns

    In some cases it is standard for a cons unit to be included in the Acctg Techniques assignment multiple times. Because the assignments may different at various levels in the hierarchy, especially when not inherited downward.
    One way to check this or change this is to check the assignments via the cons group view by clicking on the cons group and selecting View > Cons Group.
    Edited by: Dan Sullivan on Nov 19, 2009 10:38 PM

  • Consolidation Unit: consolidate only until period 09 (divestment).

    I have another problem related to consolidation:
    I have a consolidation group with several consolidation units assigned to. For one assigned consolidation unit, I want to consolidate only up to period 09. So, I have edited the year and period of divestment (2008/09). I was hopping that, that consolidation unit wasn't proposed in the consolidation monitor for interunit elimination (for period 10).
    Does anybody know what else do I have to do for this purpose?
    Thanks,
    Paula

    This sounds like a minor bug. I suggest you search SAP Notes for solution and if none is found notify SAP via customer message.

  • Consolidation  Unit change from Group A to group B

    When I drag consolidation unit from group A to Group in CX1X and then I run CXCd and error message popped stated  below;
    Entry cannot be posted :B/s and I/S balance of  1.7million.
    I think it might be due to moving from one group to another group. please advise and it is very very urgent. What is the solution to this problem.? It is giving the same error when i try to drag back to the same group.
    Thank you
    Selvam

    Hi,
    Is it a Production system? In Consolidation if a Consolidation Unit is moved from one group to another it will have serious repurcursions. In one of the projects in test system we had this problem. SAP OSS Notes also suggest that Consolidation Unit - if transaction data is already posted - it should not be moved. Especially if Consolidation of Investments is configured it is going to be a problem.
    Thanks
    Murali.

  • Consolidation Unit Hierachy deletion

    The consolidation unit is time dependant, but has many duplicate hierarchies created unwantedly over a period of time. Hence this creates confusion in parameter selection in reports.
    Can the unwanted hierarchies be deleted in development and transported across? Will the deletion of whole hierarchy get sucessfully transported?
    Alternatively rather than deleting the hierarchy , can the hierarchy be put in invisible mode  which will not trouble the users, which selection.
    Edited by: BCS_BPC on Mar 3, 2011 6:05 PM

    Can the unwanted hierarchies be deleted in development and transported across? Will the deletion of whole hierarchy get sucessfully transported?
    - Yes, to both Qs, AFAIK. But, remembering that SAP SEM-BCS has two layers: BCS itself and underlying BW, such excersize is the SAP acrobatics. Without experience it might be very dangerous in sense of damaging data.
    Alternatively rather than deleting the hierarchy , can the hierarchy be put in invisible mode  which will not trouble the users, which selection.
    - No, no invisible mode (in full). One may try achivieng it by different visibility in BCS and BW, but it also requires experience and risky in sense of bringing inconsistency between BCS and BW.

  • Merger of Consolidation units in BCS

    Hi Team,
             Have anybody come across scenario like two consolidation units getting merged into one in BCS,
    How to handle such scenario?
    which functionality should we use ?
    what will be changes in consolidation of investment?
    Please suggest.
    Thanks in advance.
    Sreedhar

    Dear greg misiorek,
                                 As far as I know the consolidation group change task is applicable only if the consolidation unit is
    transfered from one group to other, but In  case of merger of consolidation units within the same group will it this be valid.
    For instance I have a group A under which I have three companies A1, A2, A3.
    but now I have to merge A2  in A1.
    The new structure of  group A  will be companies A1 and A3 only,
    Kind Suggest.
    Sreedhar

Maybe you are looking for