12.5 S4TWL Planning – P&L, ProfitCenter, CostCenter, ORder, Project : ACDOCAP

2270407 : S4TWL – Profit and Loss Planning, profit center planning, cost center planning, order planning, and project planning

Reason and Prerequisites : This Simplification Item is relevant if:
• Profit Center Planning is used if entries exist in Table GLPCP (check with SE16).
• CO-OM Planning is used if entries exist in Table COEJ (check with SE16).
• P&L Planning is used: Use ST03N (on the production system, if possible) to check transaction profile of the complete last month, whether the following transactions have been used: FSE5N, FSE6N, FAGLPLSET, GP12N, GP12NA
• Production/process order planning is used if planned cost calculation is active for the combination of plant and order type and is carried out automatically when the production order (CO01 or CO02) or the process order (COR1 or COR2) is created, changed or released.Use Customizing T-codes COR4 and OPL8 to check whether plan costs are determined for production order and process orders.

Business Value

  • The universal journal is the unifying element for Accounting. The same unifying approach is taken in planning, meaning that wages and salaries planned on a cost center are automatically assigned to the correct profit centers, functional areas, company codes, and so on and targets set by profit center can automatically be broken down to the ssigned cost objects. In many organizations planning tasks had been moved to a data warehouse on account of the lack of flexibility in the ERP tables. With the new approach it is possible to move many planning tasks back into SAP S/4HANA, reducing complexity and total cost of ownership.
  • Where additional flexibility is required (for example to build a model to calculate headcount costs), it is possible to extend the planning model using SAP BPC tools to get the best of both planning approaches.
  • From SAP S/4HANA 1610 it is possible to store the results of planning in a new table, ACDOCP, that has the same structure as the universal journal (ACDOCA). Plan/actual reporting is provided by comparing the entries in the two tables.
  • Integration to SAP Analytics Cloud is also via the new table and master data and reference data can be sourced from SAP S/4HANA to SAP Analytics Cloud.


CO-OM planning, P&L planning, and profit center planning are now covered by SAP BPC for S/4HANA Finance (formerly known as Integrated Business Planning) (SAP Note 2081400).  If you do not want to use SAP BPC for S/4HANA but classic FI-GL and CO-OM planning functions instead, you can continue to use the classic planning transactions. Bear in mind, however, that in this case the planning results are written to the totals tables and require “plan integration” to share data between plans. Reports designed specifically for use with S/4 HANA Finance do not read these totals tables, so the planned data will only be visible in Report Writer/Painter transactions.

  • FI-GL Planning – SAP Note 2253067 describes how to reactivate
  • Profit Center Planning (classic) – SAP Note 2345118 and 2313341 describe how to reactivate
  • Cost Center Planning by Cost Element – no longer in menu but can be used in SAP S/4 HANA
  • Order Planning by Cost Element – no longer in menu but can be used in SAP S/4 HANA
  • Project Planning by Cost Element – no longer in menu but can be used in SAP S/4 HANA
  • Project Planning Overall – no longer in menu but can be used in SAP S/4 HANA

Customer project required to activate SAP BPC for S/4HANA Finance and adapt the delivered queries to customer needs. Customers preferring to delay such a project can reactivate the classic planning transactions using the SAP Notes described above.

Note that it is also possible to run the two solutions in parallel. SAP Note 2061419 describes how to retract data from SAP BPC for S/4HANA Finance into the totals tables so that this data can be used as a basis for cost center allocations and activity price calculation and order/project budget setting and settlements and to extract the data back to SAP BPC for S/4HANA Finance so that it is available for reporting when the planning cycle is complete.

Transaction KEPM (Profitability Planning) supports both account-based CO-PA within the universal journal and costing-based CO-PA and is still in the menu. The investment planning and budgeting transactions are still in the menu and supported. As an alternative to transaction KEPM, you can now use the new planning applications in SAP BPC for market segment planning (amounts by market segment – available from 1511), sales planning (quantities and prices by market segment – available from 1610) and product cost simulation (valuation of sales quantities using product cost estimate – available from 1610).

Planning data is also created automatically when production/process orders are saved or released. This planned data currently updates both table CKIS and COSP/COSS and the new planning table, ACDOCP. The new table stores two types of planned values for the production order: the planned costs (as in CKIS) and the standard costs adjusted for the order lot size (previously only accessed during target cost calculation). The two types of planned values are assigned to plan categories (PLANORD01:Production order plan costs and PLANORD02:production order standard costs) and provide the basis for target cost calculation in the SAP Fiori apps Production Cost Analysis and Analyze Costs by Work Center/Operation.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.