Periodic consolidation

What are the pros and cons of definiing a consolidation applicaiton as periodic in BPC.
If defined as periodic,Will it impact the report being run in YTD measure.

Hi,
First of all you should choose what type of sequence you want your data to be (YTD or Periodic).
Please check the below thread for the same issue discussed in detail.
BPC Consolidation application - YTD or periodic
Hope it helps.
Regards,
Raghu

Similar Messages

  • Multi-period consolidation

    Hi there,
    We have a consolidation process that includes the following steps:
    - carry-forward of LC balances
    - conversion to group currency
    - carry-forward of group currency balance for equity accounts
    - consolidation automatic adjustments
    To ensure that closing balances are correct, this 4-step process needs to run for each month. However, if we submit 2 or more months, it executes all months at each step.
    How can I run these stored procedures one month at a time when the user selects multiple months (which he may do when he consolidates a budget, a forecast or a long-term plan).
    Thanks in advance,
    Regis

    Hi Jungho,
    We tried this method but to no avail. We are now reconsidering the approach of capturing monthly flows rather than YTD flow which seems to be the most common practice.
    Thanks,
    Regis

  • Multiperiod Consolidation Consolidation Cycle

    We have selected Multiperiod Consolidation in the cons area and created a Consolidation Cycle, but the system will not allow us to save the cons frequencies to the cycle. When we attempt to save this, the system message is that there is no changes to be save.
    We have assigned the cycle in the version combinations and this is saved.
    We have regenerated the cons area and checked the authorizations with no luck in resolving this.
    If anyone has encountered this and resolved it it would be most appreciated if you would please share the resolution with us.
    Thanks, Dan

    Dear Dan,
    As per my understanding first period,year of the multi-period consolidation is must.
    Starting period of the multi period consolidation will be mentioned at "version combinations" and year period limit will be mentioned while defining "consolidation cycle".
    May be its worth re-visiting consolidation cycle creation.
    how many "delta years" manetioned in consolidation cycle?
    One more point. First period mentioned in version combination should be in sync with cosnolidation frequency mentioned in consolidation cycle.
    Thanks
    Kamal

  • Report Painter: Error RG102 when executing report

    Hi All!
    I need help with an error I'm facing with Report Painter...
    When executing a report with a large amount of variables and columns I'm receiving the error:
    Message no. RG102: Syntax error in GP3NDZHLG3MURI7VJEVF29KI876800, row 0
    If in the General Data Selection instead of using a Variable for the Version I use a fix value, it works OK. However, other reports are working properly with the same Gen. Data Selection.
    Does anyone has an idea of the cause of this report?
    Thanks!

    Hi All,
    I will try to clarify a little bit on my Issue.
    First of all, it's not a BW issue, but a Reporting Problem with the Report Painter for the Consolidation (EC-CS).
    The row is configured with a Set of Data regarding a Consolidation Item that includes all the P&L Accounts. It is configured to 'Expand'.
    Regarding the columns, I have a large number, between 40 and 50 mixing Ratio with Characteristics and Formulas. Within them, I'm using as well variables for Period, Consolidation Unit and so on.
    In the Selection Screen I have configured the following paramters
    Version - 100
    Dimension - T1
    Cons chart/acct - C1
    Ledger - US
    Cons group (Set and Variable) ZSETUNV
    Year for CG breakdwn (Variable) ZEJERAM
    Period for CG breajdw (Variable) ZPERAM
    With all the above-mentioned configurations the report works great. However, if in the Selecion Parameteres I try to replace the Version (Instead of having fix value 100, to have a variable ZVER) in order to deal with several versions in the same report when I save and execute I receive the posted error:
    Message no. RG102: Syntax error in GP3NDZHLG3MURI7VJEVF29KI876800, row 0
    Does anyone has an idea if there is a Maxium of Variables for Report Painter or any idea which may be the origin of this error?
    Thanks again!

  • Exchange Rate Calculations in FDM

    I have a requirements where data import into FDM will happen in local currency but export into HFM will happen in USD. we would need to multiply the input amounts with exchange rate amounts.
    has anyone handled such a requirement? any pointers in this regard would be useful

    Just out of curiousity - why would you do the currency translation inside FDM and not in HFM? HFM is a consolidation tool that has built in currency translation functionality. It does not require any scripting in HFM to do this. FDM does not have native currency translation functionality and any solution would involve heavy customization.
    You would have to do this through customization in FDM, though it will be extremely involved. You will have to try to store FX rates for the Balance sheet (End of month rates) and for the P&L accounts (Average rate or weighted average). Many companies translate the values for the P&L using the periodic consolidation method. This does not take a local currency YTD balance and multiply it by that month's P&L rate - instead it takes period 1's periodic value at the Period 1 FX rate, takes period 2's local currency value * the period 2 FX rate, etc. It then adds all periods together to get a YTD USD balance. Building that functionality into FDM (periodic consolidation), in addition to grabbing the right FX rates for each account type would be very customized.
    I would push back on this requirement if possible. I struggle to see the value add if it is something that HFM can do with 15 minutes of set up versus hours of FDM customization.
    Regards,
    Robert Cybulski, CPA
    Finit Solutions

  • Some EC-CS features not found in BCS

    Hello,
    in EC-CS there are two quite important features which don't see in BCS. They are:
    1) Multy-period consolidation (for consolidation several periods at once).
    In budget consolidation it's often required to consolidate annual figures in monthly detail. Due to the fact BCS can't process several periods at once, we have to perform consolidation 12 times per budget. Has anybody got experience how to simplify the procedure? I guess multy period consolidation in EC-CS was the standard way to do this.
    2) Equity aging report settings in CoI.
    In BCS I can't see the way to post to MI items with subitem breakdown, in other words to map CoI activities to movement types (which was possible in EC-CS). This is required for Shareholder's equity report where each equity item (including MI) must be broken down by movement type. What are practical recommendations?
    Thank you

    Dan, thanks for clarification.
    Alexey,
    Knowing how sophisticated the stockholders equity report might be in the former SU countries, I see here 2 issues: 1) a construction of the report itself, in general and 2) breaking down the MI.
    Issue #1, IMHO, is to be solved by proper combination of items/subitems and movement types. MoveTypes might be assigned/determined in different stages of data flow: in ECC, manually, during data load to/from staging cube, in BCS. Everything is dictated by the complexity of the report and the dataflow features.
    Issue #2. Frankly, I do not think that a reclass might help you to get what you need. Probably, sufficient number of subitems in equity and items for counterpart MIs would service better.
    And a little advice reg. you BEx query -- it's not necessary to use cell editor. You may use the following trick.
    Set several equity items in a column. And one of this items and a specific MoveType in a row (setting up the item is optional). Doing so, you'll get amount of this (row) item  accompanied by the determined MoveType on the intersection of a column and a row. Most likely, just in one cell only. It's much easier than using the cell editor.

  • Limited usage of GTS

    Hi,
    I know SAP Business-All-In-One pre-configured scenario for GTS.
    I also did have a look at related Customizing documentation.
    But I still question myself about the relevancy to my challenge of linking SD Sales with MM Purchasing.
    My requirement is quite simple.
    For domestic (no international trade) public contracts we are involved in I need to:
    1. set up price conditions, volumes and validity dates/periods for contracted materials by sold-to-party
    2. set up price conditions, volumes and validity dates/periods for contracted materials with (multiple) vendors
    3. automate the execution of sales order intake (assignement to contract, ordering with vendor, delivery confirmation, invocing and customer billing)
    4. perform periodical consolidated contract review on both sell and buy side.
    Of course all interesting functional pieces of this process can be found in SD and MM but nothing is available to streamline the process and to make it lean.
    Would you see GTS helpful here at a reasonable implementation price?
    Or maybe should I go for Abap coding and some paper output reports?

    Hi Dave,
    Thanks for recalling the key features of GTS.
    I am not specifically keen on reports but I need to make the whole SD and MM stuff working in a more lean manner.
    Today I can only set up separate contacts in SD and MM.
    Each of those can be analysed on tis own in terms of history of order calls.
    But processing orders is still "classical".
    Ideally I would like not only trigger a PPreq out of sales order item (direct delivery) but even directly a PO.
    It would also be nice to have a single and common view of SD and MM contracts in terms of history, target quantity and value, remaining "to be produced".
    It seems to me that GTS (or rather GTM?, SAP is so confusing with all those marketing novelties...) provides some features of this kind.
    Remember that I am in a public contract and the contracting parties are binded not only by price agreement but also by the quantity to be ordered and delivered. Hence contract reviews, whether quarterly or annually, are key managing milestones where the parties agree how to make sure the contract will be executed as signed.

  • Inter Unit Elimination

    Hi,
    Can any body explain, what is inter unit elimination in consolidation and why this has to be carried out, with simple example?
    Regards,
    Praisty

    IC elimination has to do with group reporting. If 2 business units are part of same group. And there is a business transaction between them. For example, one business unit sells goods or services to the other. This transaction will not result in any net profit/loss or even net asset/liablity situation at the group level, where we have to report on the consolidated basis.
    The popular way to achieve this in SAP is to use trading partner for these transactions. And during consolidation these lines with TP will be eliminated while generating the periodic consolidated reports.
    Thanks
    Ron

  • BCS validation partner entity entity

    Hello
    is it technical possible to create a BCS validation rule which checks whether partner entity identic to the entity?
    As I see I cannot use any fix selections for that because I have to compare whithin each IC upload the combination of loading partner entity and entity.
    Is there any possibility to use variables in teh selections?
    Thanks & regards,
    Elvira

    I have executed another task - reclassification and in this task I get an error for each data line (each consilidation unit), that entity = partner entity:
    Loading Entity (8140) = Partner Entity ()
    This is not understandable for me because I have added my validatio only to the validation task.
    Thereby the variable for partner entity (&2) is not filled.
    In the How To for validations I have seen that only caracteristics with the following roles can be used in conditions:
    Group Currency
    Version
    Posting level
    Fiscal Year
    Posting period
    Consolidation unit
    Consolidation group.
    All other caracteristics would be ignored.
    The role partner unit is not on this list. Do I see it right, that there are no chance to compare the consolidation unit with partner unit? Our partner entity is assigned to the role partner unit.

  • Consolidation in special posting period

    Hi All,
    I am using the Fiscal year variant April to March with 4 special posting periods in ECC. I am using the same in BCS too.
    I am taking the data through LFDS with posting period move.
    I am using quarterly consolidation which is period 3, 6, 9 and 12. However I have balances appearing in special posting periods 13 - 16 in source cube. My first consolidation is happeing for period 12. 2008
    How do I take care of the transactions posted in Sepcial posting periods 13 - 16.
    1. Should I be running the COI in period 16 too. Should I be running it as subsequent consolidation or make period 16 itself as first consolidation.
    2. I am also thinking of making the changes in the source cube 0FIGL_C10 with an additional field called consolidation posting period and write a routine to update additional period field as 12 wherever the posting period is 13 to 16. Then extract the data into BCS for period 12 and have only consolidation frequency till period 12. Can I proceed with this approach ?
    Pl give a standard and correct approach to be followed in case of special posting periods considering all the above facts.
    Thanks in advance
    Srinivasan

    Hi Srinivasan,
    1. Should I be running the COI in period 16 too. Should I be running it as subsequent consolidation or make period 16 itself as first consolidation.
    - I don't think that you should.
    2. I am also thinking of making the changes in the source cube 0FIGL_C10 with an additional field called consolidation posting period and write a routine to update additional period field as 12 wherever the posting period is 13 to 16. Then extract the data into BCS for period 12 and have only consolidation frequency till period 12. Can I proceed with this approach
    - I like the idea.
    Pl give a standard and correct approach to be followed in case of special posting periods considering all the above facts.
    - Didn't see such written approaches and doubt that they exist.

  • Consolidation rule "Aborted" on changing DefaultView from YTD to Periodic

    Hi Everyone,
    Here's my situation. I have a calculated account Current Year Earnings calculated as follows:
    Value=HS.Value.Member
    +if (Value<>"[Proportion]" and Value<>"[Elimination]" and Hs.Entity.Isbase("","")) Then+
    +Hs.Exp "A#EarningsCurrentYear=A#TotalIncome.I#[ICP Top]+A#TotalExpenses.I#[ICP Top]"+
    +end if+
    Now I found that for the month of May, this was doubling the expected value which I found out was being caused as the default view for the current scenario being YTD. Since I wanted to calculate the figure only for the month, I changed the default view to Periodic.
    After that when I ran the consolidation, it showed "Aborted" with an error code. It indicated that the error was encountered in the Sub Caculate() routine.
    What can be the reason?
    Any suggestions would be really helpful. If this does not work, how can I calculated this for the month only?
    Thanks,
    Sayantan
    PS: Data has been loaded for the Periodic member. There are no Line Items for any account.

    You cannot specify the value dimension on the left hand side of any expression. Nor can you specify Year, Period, or Entity. All of these are the "page" dimensions, which is why you have a condition for them.
    Also, I don't see how your value dimension condition would ever be true: it is not possible to be in both [Proportion] and [Elimination] at the same time. You have an "AND" operator there.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • BPC Consolidation application - YTD or periodic

    Hi,
    YTD or Periodic - For legal consolidation (IFRS, USGAAP), what would be the best option for a customer with ECC, BW and BPC landscape. Are there any major issues in mapping specific consolidation process in YTD application (like reconciliation with ECC data ect).

    Hello Lokesh,
    The IFRS focuses mainly on the reporting aspects of financial results of an enterprise. Consolidated or not, for all listed companies, these requirements impose strict norms that need to be adhered to for reporting the financial results. Therefore, if an enterprise has many subsidiaries and the numbers are reported for the group as per the IFRS norms, it still presupposes that ALL the norms have been adhered to.
    In respect of Business Objects Planning and Consolidation, SAP has come up with a Starter Kit for IFRS adoption. It is pre-configured with all reports, controls and rules for performing, validating and publishing a statutory consolidation in accordance with IFRS standards. An enterprise may have the desired setting for its Consolidation Definition. One of the settings is choosing a pre-defined variant that allows it to have either Periodic or YTD setting to be selected for a given category, data period and currency. For more information, follow this link:
    http://help.sap.com/businessobject/product_guides/bofc10/en/FC10_SK_IFRS_ConfDesc_en.pdf
    In my view, for legal consolidation, the consolidated financial information is valid only if it is YTD. The periodic values are needed only for calculating the movements - for Statement of Cash Flows. This aspect is well taken care of in the Consolidation Processing u2013 either Full Processing or Incremental processing.
    If you want to reconcile the balances as per ECC, BI as well as BPC, you have to consider only the YTD values.
    Hope this gives adequate information for clarifying your doubt.
    Chakrapani

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

  • Consolidating with fiscal periods and calendar periods

    Hi, Does anyone have any information out there on how to configure the system to pull data for fiscal period for some companies and calendar period for other companies?  Or any horror stories about trying to do it that way.
    Thanks.

    Stacy,
    For consolidation as a whole only one fiscal year variant is allowed. However, there is possibility of collecting data of different fiscal year variant and using appropriate currency translation rates as per that units fiscal year variant.
    For example, if you have consolidation fiscal year variant as 31st March ending and you have one unit X as fiscal year variant 31st december ending, in this case the 12th period data of consolidation unit X will be translated using exchange rate as on 31st dec and not as on 31st March.
    Hope this might be helpful to you...though no direct response to your question.
    Best Regards,
    UR

  • Periodic conversion & consolidation

    Hi,
    I have to setup a periodic conversion & consolidation.
    Can anyone help me with the following issues:
    1) in the business rules, currency conversion rules, has someone a file for which combinations I have to set Y to "apply to periodic"?
    2) As data is entered on quarterly basis, where and how in the time dimension do I have to change this? (I thought I change the monthnum of the time dimension --> Now march is 3, but I change it in 1)??
    Hopefully someone understands what my problems are.
    Thanks,
    Benjamin

    Hi all,
    I experienced this problem in 7.5NW SPO04.
    I've put some notes in the following thread :
    Re: Currency Conversion in BPC NW 7.5, SP3
    Hopefully it will help.
    Thanks.
    Brad.

Maybe you are looking for