LC change in Consolidation Unit after first consolidation

Dear All,
Comapny A with LC as MUR been tied to consolidation group and consolidation takes place very quarter but after the first consolidation comp A wants to switch to LC as EUR...
Kindly guide me how to deal with previous data in old LC and config steps related to LC change.
Regards,
Balaji.c

Balaji,
The usual list of rates & items:
B/S:
Investments, Fixed Assets and Equity (except of RE & MI) - historical rates -- might be deviation toward current rate (if the company doesn't want to keep these rates and information)
RE & MI - average rate (should be the same as in P&L)
All other items - current rate.
P&L
All items - average rate (might be average for a period or YTD).
Special considerations for cash flow items. But it's a separate theme.
Edited by: Eugene Khusainov on Apr 25, 2008 11:45 AM

Similar Messages

  • I have change e-mail address after first registration and when I logged in it send new password to my old e-mail address. now I can't use my old profile

    I have change e-mail address after first registration and when I logged in it send new password to my old e-mail address. now I can't use my old profile.
    and I can't install my old adobe X anymore
    what to do?
    Mika

    Change Account https://forums.adobe.com/thread/1465499 may help
    -wrong email https://forums.adobe.com/thread/1446019

  • OracleDataAdapter changes table row state after first Update call

    I have a single dataset containining multiple tables, connected by relation with cascade constraints.
    When I try to do something like:
    OracleDataAdapter da1 = new OracleDataAdapter();
    da1.InsertCommand = previouslyInitializedCommand;
    OracleDataAdapter da2 = new OracleDataAdapter();
    da2.InsertCommand = anotherCommand()
    using (TransactionScope ts = new TransactionScope())
    using (OracleConnecction conn = new OracleConnection(connString))
    conn.Open();
    da1.InsertCommand.Connection = conn;
    da2.InsertCommand.Connection = conn;
    da1.Update(dataset.Table1);
    da2.Update(dataset.Table2);
    ts.Complete();
    The second Update never happens because the first Update call changes Table2 row status to "Unmodified" so no INSERT command is issued.
    Anyone knows how this behaviour can be avoided?

    Hi,
    Maybe take a look here: [http://msdn.microsoft.com/en-US/library/33y2221y%28v=vs.80%29.aspx]
    I would focus on this part:
    Ordering of Inserts, Updates, and Deletes
    In many circumstances, the order in which changes made through the DataSet are sent to the data source is important. For example, if a primary key value for an existing row is updated and a new row has been added with the new primary key value as a foreign key, it is important to process the update before the insert.
    You can use the Select method of the DataTable to return a DataRow array that only references rows with a particular RowState. You can then pass the returned DataRow array to the Update method of the DataAdapter to process the modified rows. By specifying a subset of rows to be updated, you can control the order in which inserts, updates, and deletes are processed.
    DataTable table = dataSet.Tables["Customers"];
    // First process deletes.
    adapter.Update(table.Select(null, null, DataViewRowState.Deleted));
    // Next process updates.
    adapter.Update(table.Select(null, null,
      DataViewRowState.ModifiedCurrent));
    // Finally, process inserts.
    adapter.Update(table.Select(null, null, DataViewRowState.Added));r,
    dennis

  • How to post automatically earnings prior first consolidation

    Hi Gurús:
    I´m starting a new consolidation in SEM-BCS. At the first consolidation (year 2007, period 12), one "consolidation unit" has earnings prior to this date. I would like to know if it´s possible in SEM to create an automatic task in order to distinghish between earnings prior and after first consolidation (because the calculation of the task Consolidation of Investment (CoI) will be different with 2 different data, earnings prior and earnings after first consolidation).
    If its not possible to create an automatic task, can somebody help me about the manual posting in order to correct this data?.
    Note: I´ve customized the item 80 as "earnings prior to first consolidation" and item 8 as "earnings after first consolidation".
    Thank you in advance.
    Juan Perez Cribeiro.

    Hi Eugene:
    At first time, thank you for your suggestion, but I have already made what you say. I know the customizing, but my "main" question is "how to move" this item (in my case, item 80).
    Theoretically, if a subsidiary enters in the consolidation perimeter, for example, in June 2008 (and it´s correctly notified the system), and this subsidiary has "earnings prior the first consolidation" (for example, from January to May 2008), __how (and when) the system moves item 80__?
    Thank you again for your help.
    Yours sincerelly,
    Juan Pérez Cribeiro.

  • Automatic entry for Common Stock , first consolidation in additional data

    Hi,
    I need to know why, after uploading the notification data, the system automatically populates an entry on the additional notification data for 'Changes in Investee Equity' at the activity "First consolidation". I must tell that there were no previous entries because this is the first consolidation on ECCS.
    But, where is configured which FS Item should the system identify as the one related to the Common Stock? it is detecting the P&L carrying forward FSI instead of the common stock...
    Thanks in advance!
    Rushid

    I finally got the solution by myself. In fact this behaviour is due to the configuration on tx CXJ5 of a combination of a set of FSitems + a set o subitems that are linked to one unique consolidation activity (01-first consolidation,16-horizontal mergers, etc.)
    I hope this will help somebody else in a future.

  • Consolidation Unit and Consolidation Group

    Hello Experts,
    We are actually in the blueprinting phase of the SEM implementation and i had a quick question at this stage.
    For ex: Well we have individual company codes 0100, 0200,0300,1000,1100,1200,2000,2100,2200 and 2300.
    0100, 0200 and 0300 being american company codes
    1000,1100 and 1200 being european company codes
    and similarly 2000,2100,2200 and 2300 are asian company codes
    So would America, Europe and Asia be consolidation units then and then Global would be consisting of these 3 consolidation units.
    Correct me if i am wrong anywhere - I am pretty new to SEM.
    Thanks,
    Nandita

    Hi,
    Each of the Company Code will be a Consolidation Unit. So, 0100, 0200, 0300 etc will be Consolidation Units in Consolidation. The integration between Company Code and Consolidation is Company created in FI.
    Consolidation groups can be compared like Cost Center or Profit Center Groups. A group of Consolidation Units (and possibly Consolidation groups) will be come Consolidation groups. In your case, you can think of creating a Consolidation group each for America, Europe, Asia etc. If required you can create a sub group within a Consolidation Group.
    All the Consolidation Groups can be linked at a higher level where the global consolidation required to be done. The top node and groups can be depicted as under:
       GLOBAL
            AMERICA
            EUROPE
            ASIA
    There will not be any Consolidation Units under GLOBAL. Consolidation Units will be under America, Europe and Asia.
    Thanks
    Murali.

  • ECCS - G06020 First consolidation data for unit x in group G2 contains err

    Dear Experts,
      When I try to consolidate the investment, I got error message as below:
    First consolidation data for unit E in group G2 contains error(s)
    Message no. G06020
    Diagnosis
    Investment or equity data was collected for consolidation unit x for a date that is after the period of first consolidation in consolidation group G2. This makes all activities for this unit ineffective after the first consolidation of those activities. This can also affect indirect activities and organizational changes of other consolidation units.
    Procedure
    Correct the investment or equity data for consolidation unit x.
    Then,  I have no idea how to fix the problem. If i changed the investment or investee's equity, the data validation can not be successful. And from the message is said, the date could be critical, but I don't know, which date is incorrect.
    The background information is described as below:
      This is the first consolidation, I have run all tasks of data collection and elimination of AR/AP and Dividends.
      The consolidation is based on purchase method.
    Any suggestion will be appreciated.
    Flex Yang

    How can you solve this problem?, please guide me to solve this problem, i have similar problem, thanks.

  • Change ECCS Hirarchy & first consolidation

    Dear ALl,
    My Company use ECCS Modul and First Consolidation was done at period 04/2004 and Hirarchy are :
    BIG
    --1000
    --BG
    2000
    BPG
    3000
    4000
    5000
    SG
    6000
    7000
    We have processed consolidation every month until period 08/2007.
    Start on period 09/2007 my company want to change the Hirarchy
    BIG
    --7000
    --BG
    2000
    BPG
    3000
    4000
    5000
    SG
    6000
    1000
    Step by step already we did for the change is :
    1. Closing All modul on period 08/2008
    2. Consolidation Process (sub Sequent) on Period 08/2008
    3. Change Account Master Data and trading partner.
    4. Adjust FI Balance from company 1000 to 7000 on period 08/2007
    5. Adjust FI Balance from company 7000 to 1000 on period 08/2007
    6. Change consolidation Unit (tcode: CX1N)
    7.Change Hirachy (tcode :CX1X & CXM1)
    8.First Consolidation process
    Do the steps wrong? Or do you have other step-by- step process for the change?
    We find various error on first consolidation process.
    One of the problem is transaction with account trading partner posted on period 04/2004 as begining balance not allowed to adjust in FI Modul
    How to Adjust Transaction that have trading partner on ECCS Modul.
    Regard
    JPL

    How can you solve this problem?, please guide me to solve this problem, i have similar problem, thanks.

  • Total transfer of equity consolidated unit using organizational change

    Hi,
    We have a scenario where we are doing total transfer of an equity consolidated unit (100% owned) from one company(old parent) to another (new parent)
    The new parent is one level above the old parent in the hierarchy.
    We've used organizational change logic and have set the divestiture dates/flag in the sender consolidation group and accordingly first consolidation dates/flag/OC number in the receiver consolidation group.
    The investment AFD is submitted with "total transfer" with OC number.
    There are multiple scopes of reported data for equity method in our configuration.
    Each scope(equity pickup) is inturn created by reclassifying several equity accounts to a single BCS only item(the scope item)
    When we run COI, the system posts one total divestiture document at the old conso group (where old parent is situtated) and posts a first consolidation, total divestiture, total transfer documents  at the new conso group level (which is one level above the sender conso group)
    The total divestiture document at upper level is reversing the divestiture document posted at old parent.
    The first consolidation document jas only statistical items posted in it.
    The real document to check is the "Totals transfer document" which actually reads the investment (at old parent and new parent) , the equity holdings adjustment data(the scope items) and adjusts the investment in subs at new parent with offset going to divestiture account but of double the value than the expected scope vlaue.
    Issues faced:
    Q1. Consolidation group change tasks (at PL02, 12, 22) are not posting any documents. Is there an issue? Since I am using these tasks for the first time and dont know if this is possible.
    Q2. The total transfer document is reading the equity holdings data as double the expected value( for each of the scopes of equity method). What could be the possible reason? How to fix this?
    Q3. I would appreciate if someone can clarify what kind of postings the system makes as part of divestiture/transfer in case of equity consolidated unit transfer.
    Please help!
    Thanks,
    AJ

    Thanks Dan.
    Appreciate if you can help on the below points as well.
    1. As part of divestiture/transfer postings: The system is reversing some Previous Year(PY) equity accounts into themselves. How can we get the system to eliminate them by posting to COI Clearing account. Basically, we dont want the PY accounts to be touched?
    For the Retained earnings - PY account, the system is actually posting to COI clearing account.
    These PY accounts are part of some scopes for equitization.
    Is there any link between the "balance carry forward" - list of items table and the divestiture postings?
    Does the system check this table while posting/reversing the equity(PY) accounts?
    2. I want to understand the sequence in which the system posts the documents at the old parent and new parent (group) level.
    The same activity number is there  for Total Divestiture, total transfer documents posted at new parent level and total divestiture document posted at old parent level.
    Does the system follow bottom up approach? Thereby creating total divestiture document at old parent level.
    Followed by documents at upper level (new parent level)
    Also , at the upper level(new parent level), does it post documents in the way they are shown in the log? (We havent changed the default sequence maintained in UCWB - COI settings). so it will post first consolidation doc, followed by total divestiture, followed by total transfer docs at the new parent level?
    Is this the reason for the double value being posted at new parent for equity holding data?
    Will studying the statistical items (corresponding to eliminated equity holding items) be relevant here to understand why at upper level there is double the value being posted by system?
    Thanks.

  • BCS  how to change the accounting technique of consolidation unit.

    Hi, expert,
        We have a C/I method with accounting technique 'equity method', but when we assign the method to consolidation unit, the value of 'accounting technique' of consolidation unit  is 3 (mutul stock method ), not 2 (equity method).
       How to crrect this.
      I really appreciate your input on this matter
      Thanks.

    Thanks, Dan and Collet
       In my compandy hierarchy, each consolidation unit with the method is 3, not 2. include inheritance and not inheritance.
       When I double click one of consolidation unit.  a maintain window display,  I change accounting technique in this window, the syste issue another message  UGMD016 ('The value 2 is invalid for characteristic METHOD'
                                                                         Characteristic METHOD has no master record with the value 2.
                                                                         (The non-existing value was stored as an attribute for characteristic and value .)
       This mean that the method is incorrect?
       But the accounting technqiue of the method  is '2 equity method';

  • Consolidation unit change - error: company already used in hierarchy

    Hi all,
    I have Company 1018 moving up in the hierarchy from congroup B to congroup A.
    I have configured the divestiture date as 12/2010 for Company 1018 in congroup B.
    When I try to add company 1018 to congroup A, I get errormessage that u201CCompany 1018 is already used in hierarchiesu201D that it exist in congroup B.
    Could anyone tell me exactly how to add company 1018 to congroup A to avoid this error message.
    I understand that Iu2019m not doing this in correct way.
    Thanks in advance,
    Sveinn Muller.

    Hi,
    SAP Note 702649 refers to when consgroup is moved
    SAP Note 721376 refers to when cons.unit is moved, as it is in my case
    I'm doing this according to below description in SAP Note 721376
    the only problem is when I add 1018 in consgroup A in my example, I get mentioned error.
    CG1
    |- A        First consolidation in 2003/012 (Start)   divestiture accounting > (grater than)  2005/006 (End)
    |- CG2
        |- A    First consolidation in 2003/012 (Start)   divestiture accounting in 2005/006 (End)
    Rgds.
    Sveinn.

  • Consolidation unit change

    Hello, dear colleagues !
    The client works with BCS ver. 4 BW 3.5.
    The earliest date in the system is 12/2006.
    The client mainteins one legal hierarchy of companieis and one hierarchy of Profit centers (matrix scenario).
    The client needs to make some changed in  a profit center hierarchy from 01/2009, wich is to "moove"  some PCs from one node to another in the same hierarchy.
    The client does not want to create a new PCs hierarchy with the new structure, because in the BEX reports the user needs to choose the PC hierarchy, so they don't want to rely on user to remember wich hierarchy he needs to choose.
    What is the best practice to do changes like this?
    Thanks,
    Lilia

    The best practice in the situation is to:
    - set parameters to 01/2009
    - make hierarchy changes
    - update cons group configurations for periods of divestiture/first consolidation according to SAP guidelines (be sure to get this right)
    - for transfers create cons group organization change number (if applicable)
    - post additional financial data for transfer or divestiture/acquisition
    - execute tasks, including cons group changes tasks

  • 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.

  • Reparenting - of equity consolidated units upward in hierarchy

    Hi experts,
    We're doing reparenting of a cons unit (upward in a hierarchy) : The scenario is explained as under:
    There are two hierarchies in a single version. The consolidation units falling under both hierarchies are same. Difference being - H1 is a flat hierarchy with parent A and all other as subsidiaries (100% owned and purchase method consolidated)
    H2: Has multiple levels (conso groups) with overall parent A. All other companies are equity consolidated (ofcourse parents in each group is assigned purchase method, ownership is again 100% of all units)
    In H2: we're doing a reparenting. From a lower conso group(cons group CGB with parent B) a unit(unit C) is moving to the top conso group(cons group CGA with parent A). The master data changes in both conso groups have been made(period/yr of divestiture and period/yr of acquisition set in the sender group and receiver group respectively; added the cons unit C in CGA group).
    The organizational change logic is being used.
    After the conso group change task and COI task are run, in the report there is a difference in the equity PY surplus at level A - overall parent) in both hierarchies.
    There are two equity pickups - A/c1 and A/c2
    The opening balances on these accounts are getting reversed in the divestiture period in old parent.
    Whereas the PY - RE(Previous year - Retained earnings) account is not getting reversed (in itself) but the balance is being posted to COI:Clearing item (COI clearing item defined in COI settings->Appropriation of retained earnings -> Net income tab)
    1. The client doesnt want PY equity surplus to change. In H1 , it is not changing (not reversing) whereas, in H2 it is reversing in the same accounts - balancing to zero.
    2. They'd ideally want the PY surplus to goto the COI clearing.
    They'd like the system to do this entry and not fix this by doing a manual PL30 journal.
    Can you tell me if there is anything in the configuration of COI that can fix this issue?
    Why is the system behaving differently for A/c1 (and A/c2)and PY - RE account?
    Another thing, when I look at the COI documents posted in the H2 hierarchy, I see the A/c1 and A/c2 (scopes of data for equity method) as double the amount in the new cons group (equity holdings data) whereas in the H1 (where only a total transfer doc is posted) I see the accounts (as part of equity data) with the actual value.
    Thanks, AJ
    Edited by: A J on Nov 17, 2009 3:17 PM

    Thanks Dan.
    Appreciate if you can help on the below points as well.
    1. As part of divestiture/transfer postings: The system is reversing some Previous Year(PY) equity accounts into themselves. How can we get the system to eliminate them by posting to COI Clearing account. Basically, we dont want the PY accounts to be touched?
    For the Retained earnings - PY account, the system is actually posting to COI clearing account.
    These PY accounts are part of some scopes for equitization.
    Is there any link between the "balance carry forward" - list of items table and the divestiture postings?
    Does the system check this table while posting/reversing the equity(PY) accounts?
    2. I want to understand the sequence in which the system posts the documents at the old parent and new parent (group) level.
    The same activity number is there  for Total Divestiture, total transfer documents posted at new parent level and total divestiture document posted at old parent level.
    Does the system follow bottom up approach? Thereby creating total divestiture document at old parent level.
    Followed by documents at upper level (new parent level)
    Also , at the upper level(new parent level), does it post documents in the way they are shown in the log? (We havent changed the default sequence maintained in UCWB - COI settings). so it will post first consolidation doc, followed by total divestiture, followed by total transfer docs at the new parent level?
    Is this the reason for the double value being posted at new parent for equity holding data?
    Will studying the statistical items (corresponding to eliminated equity holding items) be relevant here to understand why at upper level there is double the value being posted by system?
    Thanks.

  • Moving consolidation unit mid year

    Hi,
    we need to move 2 consolidation units from 2 different consolidation groups into a new existing consolidation group in June, rather then at year end.  We did some testing on this, but it seems that the historical information of those 2 consolidation units is not transferred into the new consol group in July. Is that to be expected? If not, what is the best way to get the historical data into the new consol group? The managers of the old consol units still need to show the historical data as well. Your help is very much appreciated : )

    The cons unit/group hierarchy is time-dependent. The best way to accomplish this is to execute the cons group changes tasks, which transfers the balance sheet balances "out" of the old cons group and the standard consolidation logic of the virtual infocube function module will automatically include the balances in the new cons group from the period of the change and thereafter.
    Another possibility, is if you are not using any posting level 30 documents types, you can possibly make the change retroactive to the beginning of the year by changing parameters to period 001 for the hierarchy change. In this case, the reporting logic will automatically include the balances in the new cons group and not the old cons group for the entire year.
    It is also important to not "drag-and-drop" for such changes, and to include the cons unit in both new and old cons groups with a period of divestiture in the master data of the old cons group and period of first consolidation of the new cons group.

Maybe you are looking for