With the advent of S4 HANA, the approach to planning is constantly evolving. In-memory computing, columnar database storage, and newer tables with each version of S4 HANA are making planning more flexible and efficient. Financial planners and cost accountants are looking for more Microsoft Excel-like planning tools for their processes. SAP Analytics Cloud is also offering much flexibility to businesses as a planning tool. The new planning tables in the S4 HANA ERP system, ACDOCP, and ACCOSTRATE have made their mark in a typical S4 HANA environment. Amid all these innovations, the cost accounting business function still wonders how these tools will, and tables come into play to help with the cost center planning around overheads, and their absorption into a product cost to reflect the contribution margin. This blog will demystify the S4 HANA planning approach and lay out an approach to Integrate cost center planning concerning product cost planning.
Before S4 HANA, during SAP ECC days, cost accountants usually would use the standard transaction codes such as KP26, and KP06 to load plan activity type dependent and independent data in terms of quantity (volume) and plan costs. Typically, a cost-center plan cycle would be something like as shown in Figure 1. This process diagram has simplified a few sub-processes such as planning of volume or Input Quantities for the cost centers/activity types that could be planned and transferred using the SAP long-term planning (LTP) or even through a manual upload. Nevertheless, the basic high-level steps remain as shown in Figure 1.
Currently, with S4 HANA (up to version 2022), there are a couple of new CO or managerial accounting planning tables that are built on the premise of in-memory processing. These tables are ACDOCP and ACCOSTRATE. Many of the Fiori plan versus actual comparison apps run based on these AC* tables. SAP Analytics Cloud (SAC) also Integrates with these tables better. Additionally, the S4 HANA most powerful allocation tool i.e. universal allocation or manage allocation also uses these tables. Based on all these contexts, cost-center planning processes are designed around these tables. While following this approach, the cost center activity type-driven overhead allocations become problematic. Till the latest version of S4 HANA, the cost center activity type automatic rates calculation transactions or corresponding Fiori apps are still all original old school CO tables based. To address this type of limitation a hybrid approach can be adopted. Adopting such a hybrid approach will result in the best of both worlds based on the current system design. Figure 2 process flow summarizes the high-level system design.
This hybrid approach circles around the following main steps:
Figure 3 shows the First transfer program that moves the cost center plan data from the ACDOCP table to the CO table.
Figure 4 shows the transfer program that moves the cost center/activity type dependent plan data from the ACDOCP table to the CO table.
Figure 5 shows the Statistical Key Figure (SKF) plan data transfer from the FINSSKF table to the COSR table.
Figure 6 shows the transfer program that moves the cost center/activity type plan data from the CO table to ACDOCP.
Figure 7 shows the transfer program that moves the cost center/activity type plan rates data from the CO tables to ACDOCP.
In conclusion, I would like to mention that using the above-suggested hybrid approach, the old-school CO/ERP transactions could be very well integrated with the modern-day S4 transactions/app. This also offers scalability to Integrate the planning with SAP Analytics Cloud (SAC).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |