Skip to Content
0

BPC Optimised for S/4 HANA 1610

Feb 02, 2017 at 11:22 AM

815

avatar image
Former Member

Hello Team,


We have to implement consolidation in S/4 HANA 1610

1)Write back from BPC to S/4

When we post any data I presume it writes back to the the acdocc table (in case of consol) and real time plan cube but actuals table acdoca is not affected

What about retraction to ECC , the customer may want to see plan data back in sap ecc tables to make it available for erp users? Is there any code for planned data retraction?

2)Distribution/assessment in ECC

There is a standard functionality in ECC to distribute costs from sender to receiver cost centre based on % or other drivers.

Now since planning for cost centre is going to be done in BPC , how can we achieve this functionality? I think it will have to be custom one and requires lot of bespoke code.

Thanks in advance

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Lucas Gabriel Feb 26, 2017 at 09:24 PM
0

Hi,

There is a pre-delivered content to integrate Plan and Classic CO tables in 1610 (or even previous releases don't know exactly).

The objects are under InfoArea - /ERP/COOM - Overhead Cost Controlling but unfortunately they only as far as Cost Centre, Projects and Internal Orders. These are based on virtual infoproviders calling ABAP classes for reading and writing data back to CO.

You can implement something similar for COPA using the same structure (BW and ABAP wise).

To read data from COPA use BAPI: BAPI_COPAPLANNING_GETDATA

To save data to COPA use BAPI: BAPI_COPAPLANNING_POSTDATA

Cheers

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member
Feb 27, 2017 at 09:04 AM
0

Hi,

If you want to use Distribution/assessment, then you have such scenario-

Plan costs on primary CEs and CO objects, retract data to 'ECC', run allocation\distribution\activity type planning, extract data to BPC

Share
10 |10000 characters needed characters left characters exceeded
Gersh Voldman
Mar 01, 2017 at 03:24 PM
0

Please check Aggregation levels /ERP/SFIN_A09, /ERP/SFIN_A19 and /ERP/SFIN_A29, and their Planning Functions. They allow sending data back to ERP, allocate/distribute it there and bring it back to IBP.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Oct 25, 2017 at 07:34 PM
0

Hi,

I’m new with this BPC version, maybe you can help me with this question. I must Plan data in Bpc, and also perform the allocation there, nevertheless my client performs the allocation by functional area, not for cost center. So, I must update the worksheet and logic (cost center simulation).

Anyone have updated that templates and logic ? is it very complicated to adapt ?

What do you think is the best approach use BPC-CO(only for allocation), or doing everything in BPC (Plan and allocation.)?

Many thanks!

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Veronica,

you can do both plan and allocation directly in BPC.

Regards

Krushna

0
Former Member

Hi Lucas, I just submited my comments in the answer section as I didn't see Reply button. Appreciate your feedback to my question. Thanks, Jay

0
Jay YM May 29 at 10:13 AM
0

Hi Lucas or Gersh, Was following this discussion thread. As per understanding SAP had Renovated the planning scenario from ECC 6.0 EHP6 in 2011. With this new technologies like WebDynpro/AO was introduced. SAP delivered several predefined contents under /ERP/COOM*. Using this we could send the plan data directly in ERP Tables - KP06, KP26, CJR2, etc. They called it "Renovated Planning". But now fast forward in 2017 with BPC Optimized, we have lost all those planning templates. I don't see KP26(Activity Output planning). Also, to use the A09_WB01(Plan Data Transfer for CC), there are no step by step instruction to use.

Can you please help how we can send plan data to KP26 in BPC Optimized.


Thanks,

Jay

Share
10 |10000 characters needed characters left characters exceeded