Delta load based MultiProvider scenario with actuals and budget data

[Former Member]

Dear Experts,

We implemented the Delta load based MultiProvider scenario for BCS out of performance reasons.

For us the use case for reporting is reporting mode "Restatement". In that case we have to do an INIT load per closing period (every month) because the organizational hierarchy changes every month.

Till now this INIT takes a long time, because we did not use the correct scenario. We defined a new scenario:

- once (first time with new scenario) an INIT with all data (fiscper and fiscyear) on all reference periods till now (eg April 2011)

- afterwards every closing period only an INIT on the new reference period

This works fine for actuals (all data on all reference periods available till current or closing period).

It does not work in combination with budget data. Because budget data concerns fiscal year/period in future!

Problem:

- If the filter in infopackage is limited to reference period = closing period, also fiscal period/year after or greater than reference period is not loaded into the PSA.

I'm not sure this is a known 'problem' or on purpose (to avoid doubling on data in future).

Question:

- Does anyone have a suggestion on an optimal scenario for R modus, where the INIT on monthly basis is as minimal as possible and also this works for the past 3, current and next fiscal year (budget), so fiscyear 2008 to 2012 has to be available against every reference period till current or closing reference period.

Thanks in advance.

With best regards,

Rick Stoll.

[dan_sullivan · Accepted solution]

The approach you are using is not customary and is therefore difficult to continue.

My suggestion is to discontinue the current aproach and use the cons group changes tasks to avoid this complicated scenario. The hierarchy changes, in the suggested approach, which I consider to be best practice, must not be accomplished via drag-and-drop, but as SAP recommends, which is to add the cons unit in the new cons group node and update both the old and new cons group master data to reflect the correct period of 1st consolidation and period of divestiture.

Edited by: Dan Sullivan on May 24, 2011 8:57 AM

Edited by: Dan Sullivan on May 24, 2011 8:59 AM

[Former Member · Accepted solution]

Thanks Dan for your reply.

We use matrix consolidation on legal (company) and internal management cons. units (profit center). Especially our internal management hierarchies change (from one Cons Group to another) quite often.

Requirement of the business is that they look at the YTD data according to the current hierarchy (restated view). Also previous year is reported according to current hierarchy (comparison with previous year)

Also for budget data they look YTD at the current Actual hierarchy (budget restated)

Mainly to be able to compare actuals vs budget with the same hierarchy.

Do you have experience with this kind of requirements ?

Usage of Cons Group Changes task will only correct book value of balance sheet items, not for the income statement items in previous periods.

In that case the approach you suggest will not work in my opinion.

[dan_sullivan · Accepted solution]

The reporting for year-over-year reporting may still be accomplished with cons group changes to meet your requirements by using the reporting mode Restatement along with the reference period/year.

[Former Member · Accepted solution]

We received a solution for our scenario from SAP:

Activation of unrestricted restatement reporting mode:

• call transaction UC00

• choose menu Environment - "Set Consistency Check for..."

• add new entry "8 Display new data with old hierarchy" = 'X'

This solved our problem.

Regards Rick.

Edited by: Rick Stoll on Jun 28, 2011 1:23 PM