SAP BPC Real time Consolidation on S4HANA 1809

[former_member582629]

Hi All,

I want few clarifications regarding SAP BPC Real time consolidation in BPC 10.1 on S4 HANA 1809.

1. I am having 10 SAP and 1 non SAP companies to be in Consolidation

- How the modeling/Architecture will be in this scenario.

2. What will be BW level structure for the same like ADSO / Composite Providers will be designed for Rate / Ownership and Consol models in RTC?

3. We have FI accounting getting closed every month , so the consolidation will be done at every month , so how the consolidation process will gets triggered in RTC ( what will be triggering point )?

4. Is it essential that we need to use ACDOCC ? can't we use any of the Z-ADSO for the final consolidation result to be stored in ? what will be the difference if i will use Z-ADSO for consolidation data to be stored instead of ACDOCC ?

Waiting for your positive and prompt response on the same .

Regards,

Sanjay Gajera

+91 89050 74894

[former_member186338 · Accepted solution]

"We have FI accounting getting closed every month , so the consolidation will be done at every month" - you simply don't need RTC for your requirements.

Implement BPC Embedded or BPC standard.

[former_member582629 · Accepted solution]

Hi Vadim,

thanks for your response.

Here is my confusion i am having , when RTC basically getting used ?

1. if its accounting on daily base ?

2.what approach we have to use if the accounting is getting closed every monthly basis .??

3. Client has requested for RTC , whether RTC is possible in this situation or not at all , so i can convey to client straight forward that there will be Embedded Consolidation here on top of S4HANA 1809 box.

Please clarify above doubts.

Thanks and appreciating your suggestions here.

Regards,
Sanjay Gajera

+91 89050 74894

[former_member186338 · Accepted solution]

sgajera

RTC - means real time. It means that you can consolidate at any moment. But I don't know business cases when it's required 🙂

For normal monthly consolidation you need to implement BPC standard/embedded. For sure you can use some predefined content for RTC to get actual data. But results can be written to any infoprovider.

"Client has requested for RTC" - Client simply don't understand what it means. And it's your job to explain.

P.S. For example, now I have finished BPC standard implementation on S4 HANA 1809. Working absolutely fine and the customer is happy to use EPM reporting (not Analysis).

[former_member582629 · Accepted solution]

Hi Vadim ,

Agree to your suggestions. So we will be going with Embedded BPC for this Consolidation for sure.

Now few clarifications required in term of Embedded BPC - Consolidations implementations.

1. I can have my own ADOSs/ Composite providers and Aggregation levels to build input schedules and to store the consolidated results. I no need to use ACDOCC here.

2. All business rules for eliminations and other processes , will be written in Planning functions on top of Aggregation level and the result will be stored to created planning enabled ADSOs.

3. Planning functions will be triggered via Business Rules of BPC web portal where we will assign Planning functions to trigger the eliminations and other processes.

4. P&L / Balance sheet and Cash flow ( Statutary and Management ) reporting will be derived using BEx queried created on top of final Result ADSO where we have stored all consolidated result after Business rules executions.

Please confirm , whether my above understanding is clear of still there is a gap in my understanding .

Regards,
Sanjay Gajera

+91 89050 74894

[former_member186338 · Accepted solution]

sgajera

1,2,3,4 - Yes!

You will have to use ACDOCA to get actual data, but consolidation result can be stored in any suitable object.

Please accept the correct answer.

P.S. By the way, why not to implement BPC standard? The reporting for BPC standard is better then for embedded.

[former_member582629 · Accepted solution]

Hi Vadim,

Thanks for the clarifications.

Actually , Client have opt for BPC RTC and they want the same to be done in Optimized BPC environment .

Planning is already been implemented in Optimized BPC version , so for consolidation as well we need to use the same platform.

Here the single box is being used for S4H and BW both as embedded BW system. so Actuals will be from ACDOCA via using Hana calculations views , and we will follow the embedded architecture for rest of the development which will be assigned to BPC model at front end portal.

Thanks again for the valuable details you have provided.

Regards,

Sanjay Gajera

[former_member186338 · Accepted solution]

sgajera

"Planning is already been implemented in Optimized BPC version"

But Optimized BPC version = BPC Embedded + BPC Standard 🙂

[former_member582629 · Accepted solution]

Hi Vadim,

Have below details required if you can help with .

1. How the elimination process with be implemented in this scenario ?

2. How the elimination process will be triggered here . (usually in std. BPC we used to use Business rules from BPC admin and assign Data manager packages with that which will have the elimination logic inside it.)

Please advise on this .

Thank,
Sanjay Gajera

[former_member186338 · Accepted solution]

sgajera

"1. How the elimination process with be implemented in this scenario ?

2. How the elimination process will be triggered here . (usually in std. BPC we used to use Business rules from BPC admin and assign Data manager packages with that which will have the elimination logic inside it.)"

The way that is used in BPC Embedded! Rules setup, then Consolidation monitor.

If you have little experience with Embedded I recommend to implement standard!

[former_member582629 · Accepted solution]

Hi Vadim,

I have started working on this approach you have suggested .

Below is the elements / objects i have considered for Consolidation - ADSO.

ZA_L_CONS ADSO ACCOUNT Dimensions /ERP/GL_ACCT ENTITY Dimensions /ERP/ENTITY 0FISCPER Dimensions 0FISCPER 0FISCVARNT Dimensions 0FISCVARNT CATEGORY Dimensions /ERP/CATEGORY INTCO/Trading Partner Dimensions /ERP/PENTITY RPTCURRENCY Dimensions 0CUURENCY - /ERP/RTCCURR AUDIT/Data Source Dimensions /ERP/AUDIT USRDFND Dimensions /ERP/RMODEL SIGNEDATA KeyFigure /ERP/RTC_AMO 0FISCYEAR Dimensions 0FISCYEAR Chart of Accounts Dimensions /ERP/CHRTACCT FLOW Dimensions /ERP/FLOW

Here , for /ERP/ENTITY and /ERP/PENTITY - its pulling data using hana views being a standard objects.

My doubt is that , can i use /ERP/COMPCODE and /ERP/TDP ( Company code and Trading partner ) in place of ENTITY and PENTITY for this ??

as i want all company codes and trading partners for specific Chart of accounts for the consolidations , this chart of accounts is not available in ENTITY and PENTITY info objects.

Please advise the way to proceed forward with the solution.

Regards,

SG.

[former_member186338 · Accepted solution]

sgajera

Sorry, but your post is unreadable

[former_member582629 · Accepted solution]

Hi,

Now we are doing Currency translation steps for consolidation in RTC / Embedded consolidation.

we want to map flow type for closing balance , we are not able to see the same in ACDOCA table -transaction type for closing balance .

Which transaction type we need to select to map with closing balance flow type.

please advise on the same. we are using RTCTTY and dimension we are using is /ERP/FLOW for flow.

Waiting for your prompt response with the solution.

Regards,
SG

[former_member186338 · Accepted solution]

sgajera

Sorry, but you have to provide very detailed description of your system!

Is it a standard RTC setup or???

[former_member582629 · Accepted solution]

HI Vadim,

Thanks for the response.

Its embedded set up , as you advised - our accountings getting closed every month end - so RTC is not possible here.

We have used all standard infoobjects of RTC for our data modeling .

Below is the structure . We have created 3 ADSOs for consolidation like ,

ZA_L_CONS - Consolidation ADSO
/ERP/GL_ACCT
/ERP/ENTITY

0FISCPER - 0FISCVARNT

/ERP/CATEGORY

/ERP/GROUP

/ERP/PENTITY

/ERP/RPTCURR

/ERP/AUDIT

/ERP/FLOW

/ERP/RTC_AMO - Key figure.

ZA_L_OWN - Ownership ADSO

O_ACCOUNT

/ERP/ENTITY

0FISCPER - 0FISCVARNT

/ERP/CATEGORY

/ERP/GROUP

/ERP/PENTITY

ZO_K_OWND - Key figure for Ownership data

ZA_L_RATE - Rate ADSO
R_ACCOUNT

/ERP/ENTITY

0FISCPER - 0FISCVARNT

/ERP/CATEGORY

/ERP/RTCCURR

/ERP/RTC_AMO - Key Figure for Rate data

Here , we are maintaining FLOW data using RTCTTY transaction code as we have used standard info object /ERP/FLOW. here we have to mapp Opening / Closing flow so as a transaction type - it is only showing us types for opening but not able to see closing balance transaction types . so which entry we should map with Closing balance flow type in the dimension.

Also how we are get this opening and closing transactions entries from ACDOCA table as a actual transaction data - we want to run currency conversion here. we are doing embedded consolidations but using RTC standard info objects to have all master data available using standard HANA views.

Request to please advise on this if i have made any mistake in the model setup .

Hope this gives you sufficient details.

Regards,
SG.

[former_member186338 · Accepted solution]

sgajera

Still not clear how you work with Actual data...

[former_member582629 · Accepted solution]

Hi Vadim,

I have /ERP/SFIN_v01 for actual financial data .

Is this source correct for getting financials from S4H ?

[former_member186338 · Accepted solution]

Sorry, I can't answer what is correct and what is not in your embedded setup. To do this I have to spend minimum one day investigating your system. Unfortunately not for free.