BPC Consolidation application - YTD or periodic

[Former Member]

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

[Former Member · Accepted solution]

Hi,

Nilanjan, (I posted this on one recent thread and found the thread was already marked answered, hence posting it in this relevant thread)

Since the ACCT TYPE governs whether the data will be stored as periodic(P&L account - INC,EXP) or YTD (BS accounts-LEQ,AST), can you suggest what does the YTDINPUT parameter of application does?

I am not sure whether and based on what criteria, the YTDINPUT parameter should be set to periodic or YTD for the consolidation application. (Though in most cases it is set to YTD only)

In my scenario, the system landscape is ECC->BW->BPC.

Thanks for your help.

Apeksha

[Former Member · Accepted solution]

Hi,

This decision would typically be based on the fact whether you want the data to be in periodic fashion or in YTD fashion. If your source is in YTD format, its better to have your application as YTD.

When the application has YTDINPUT as N, the data would look like

JAN   FEB   MAR
100   200   150

The same data with YTDINPUT would be

100   300   450

Hope this helps.

[former_member200327 · Accepted solution]

Hi Apeksha,

Account type doesn't govern how data is stored - it governs how it's reported. Application type controls how data is stored - YTD or Periodic.

You have to make your decision based on your reports/scripts. If you report (or run scripts) mostly on on Periodic values, then set to Periodic. If mostly YTD values being processed then YTD is a more efficient choice.

If you have an almost equal mix I'd suggest using Periodic because your data goes through BW (which stores it in Periodic fashion) and this will save you one transformation.

Regards,

Gersh

[Former Member]

Also, the inversion concept (used in SEM BCS ) is not required to be used in BPC if the application works in YTD. This also means that if the document is still valid in the next period it has to be re-posted.

I would think that the YTD solution would be more appropriate and would agree with Chakrappani above.

Regards,

Bhairavi

[Former Member]

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

[Former Member]

Dear Chakrapani,

Thanks for the valuable insight. Although I can understand the importance of YTD reporting for IFRS and other purposes but still not sure how does it impact the application property of YTD or periodic.

I believe that the reporting (YTD/ Periodic) is separately controlled by the Account Type (LEQ/AST/INC/EXP). Application property is used only for the 'storing' of data. Now if this understnading of mine is correct, please could you further enlighten the impact of application type (YTD/Periodic) on the reporting?

Best Regards

SSC

[Former Member]

Thanks to all for sharing the information.

In the below starter kit for BPC 7.5NW, YTD application and YTD data input is suggested.

https://websmp105.sap-ag.de/~sapidb/002007974700001545002010E/75NWSKIFRS.pdf