on 01-12-2018 6:41 AM
Dear All,
In standard BPC Consolidation Carry forward executed every month (if monthly consolidation). Is it same process Carry forward program to be executed monthly basis in RTC also ? Because now in RTC, consolidation model is periodic not YTD. When we are using YTD only balance carry forward is required to be executed monthly. (In RTC, opening balance stores is ACDOCC in period 000.2017.)
2.According to the decision on carry forward, I can change the logic of time variable in BEX queries of all the reports.
3.In Standard SAP currency conversion program only transfer the data to group level, our customer requirement currency translation happens in Accounting itself (in FI). For consolidation we pick the group currency value for consolidation. In BPC Model I have assigned currency translation in Accounting mode. In that case how the G_NONE data moves to consolidation group. Is that mean technically currency conversion has to happen even though translation happens in Accounting.
4.Elimination entity is required or not in RTC. But I have created elimination entity and assigned in BPC entity setup. But consolidation engine is not picking the data from ACDOCA table and posting to ACDOCC for consolidation process. If elimination entity is not required in RTC, where the consolidated group values gets stored in BPC ? Consolidation engine is not picking ACDOCC (flexi load) data also for further process.
Please let me know if you need any further clarification on the questions.
Regards,
Raja.A
Hello Syed,
To be clear all values in ACDOCx tables are periodic. Therefore, if you want to see value as YTD in your reports, then you need to adopt the BEx solution for generating YTD values. Here is a link to a blog that should help with the reporting aspect:
Report and input value with YTD in BPC Embedded Model
Best Regards,
Leila
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello wasay safder,
In response to your questions (shown below), after some internal discussions we created KBA 2809105 - How YTD works for consolidation rule in embedded modelBPC embedded model stores data in periodic storage type. For "elimination and adjustment" business rule, by default, it calculates data in YTD mode and stores result data in perodic type. If the option"Apply to Periodic" is checked, it calculates data in perodic mode and stores data in perodic type.
Q1) As per my understanding data coming from S/4HANA (ACDOCA) for balance sheet accounts is already in YTD nature (as balance sheet items are point accounts), for e.g. Feb.2018 Movements for BS accounts will be YTD values, Correct?
Q2) Data coming from S/4HANA (ACDOCA) for P&L accounts is Periodic in nature and BW will process that data on periodic basis, therefore at the query level we can just use restricted key figures to present the YTD totals, Correct?
Q3) In RTC, within the /ERP/GL_ACCOUNT dimension we have ACCTYPE property where P&L accounts are INC or EXP and BS accounts are AST or LEQ. Does this have any impact on how the data is retrieved/viewed from S/4HANA? For e.g. the way it use to determine how data is displayed in reports for BPC Standard?
Q4) If we run BCF once in the beginning of the year then Dec.2018 (closing flow) will be copied to Jan.2019 (opening flow). But what about the opening balances for all the other months, e.g. Feb.2020, Mar.2020 etc? Do we have to run BCF each month?Q5) My understanding is that even in RTC, the END flow is a hierarchy parent node which rolls up the OPENING and MOVEMENTS flow, Correct?Really appreciate your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks a lot for your response leila.lappin. This surely helps to understand better how to consolidation rules work in BPC Embedded.
Can you please help in confirming the below?
Balance Sheet accounts have Opening flow and Movements flows which rolls up to END flow. In RTC we get all the data directly from ACDOCA table in S/4HANA. Opening flows are populated by Balance Carry Forward. But what I want to understand is if the data for BS accounts coming from ACDOCA against the Movement flows (e.g. Asset Additions) will be point in time (YTD) by default for each month? Or we will have to create YTD calc in reports to show the point in time (YTD) values?
Really appreciate you help.
Best Regards,
Syed Wasay
Hello,
For you question 3, where you get the translated currency from FI, I thought that integration rule may be helpful. According to my reading in a BPC model with integration enabled, the elimination rule will copy the translated data from G_NONE to different groups and going through elimination. You can find more details BPC NW Wiki - How to use BPC integration rule
I know the business objective of having integration rule is different from what you have described, but I am wondering if it can be used for your purpose. The reason is the following information from the wiki page.
Rules with integration type:
The integration rule definition re-uses the framework of Elimination and Adjustment rules, but has some differences:
This is a simplistic answer and I hope it helps.
Best Regards,
Leila Lappin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Leila Lappin,
Thanks for the reply. I feel, integration mode wont be helpful for my requirement. I have to execute Account based calculation for Profit or Loss to Balance sheet retained earnings account. Data should be available in group level before the elimination and adjustment rules been executed.
Note: I need force close, swap entity, destination audit should be available for my elimination and adjustment rules. that's why integration rule will not be helpful.
Regards,
Raja
Hi Raja,
Are you translating in S4 or in BPC?
This how the process was explained to me by SAP..
If translating in S4, then you can only go integration mode. Your data will not be visible at different scope levels, only the eliminations will be visible at the next scope level. You also will not be able to utilize force interco, swap entity etc.
It seems like your requirement will require you to translate in BPC
Regards,
Jurgen
Hello,
BPC carry forward (CF) in BPC embedded and RTC works as per following. This information is provided in KBA
2563592 - Carry forward in RTC - YTD and periodic. Please let us know if this is helpful so we can improve the KBA. Thank you
Best Regards,
Leila Lappin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi leila.lappin,
We are currently implementing Real Time Consolidation (RTC) for S/4HANA 1709 which utilizes BPC Embedded model and want to get some clarifications/guidance on the following questions (mainly with regards to Balance Carry Forward configuration).
Q1) As per my understanding data coming from S/4HANA (ACDOCA) for balance sheet accounts is already in YTD nature (as balance sheet items are point accounts), for e.g. Feb.2018 Movements for BS accounts will be YTD values, Correct?
Q2) Data coming from S/4HANA (ACDOCA) for P&L accounts is Periodic in nature and BW will process that data on periodic basis, therefore at the query level we can just use restricted key figures to present the YTD totals, Correct?
Q3) In RTC, within the /ERP/GL_ACCOUNT dimension we have ACCTYPE property where P&L accounts are INC or EXP and BS accounts are AST or LEQ. Does this have any impact on how the data is retrieved/viewed from S/4HANA? For e.g. the way it use to determine how data is displayed in reports for BPC Standard?
Q4) If we run BCF once in the beginning of the year then Dec.2018 (closing flow) will be copied to Jan.2019 (opening flow). But what about the opening balances for all the other months, e.g. Feb.2020, Mar.2020 etc? Do we have to run BCF each month?
Q5) My understanding is that even in RTC, the END flow is a hierarchy parent node which rolls up the OPENING and MOVEMENTS flow, Correct?
Really appreciate your help.
Best Regards,
Syed Wasay
User | Count |
---|---|
14 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.