Posting plan data under S/4HANA

PLAN_OP_MODE

* available from version 4.0

Background: with S/4HANA, SAP offers a successor to the classic ERP. A central change is the combination of FI and CO functions in the so-called Universal Journal, which is reflected, for example, in a new, universal line item table ACDOCA (= ACounting DOCuments Actuals) for storing actual data. With version 1610, the ACDOCP table for storing plan data was introduced: so there is now a separation between actual and plan data at table level.

The constant PLAN_OP_MODE decides whether plan data of the Allevo transactions is stored in the Universal Journal or only in tables of the classic ERP planning (e.g. COSP, COSS). Here are the options:

0 = Planning via classic ERP functions (BAPI and tables e.g. COSP/COSS).

1 = Planning only via interface to Universal Journal with the table ACDOCP (currently only for tests).

2 = Planning in classic AND new planning data tables.

Without an entry for the constant, Allevo only works with the classic ERP tables (so like option 0).

Important note: in the current expansion, the data of the classic planning are leading and are also read again as reference data. To accomplish posting to the Universal Journal, Allevo must therefore be operated with option 2: then plan data is additionally stored in ACDOCP (co-posting) and is thus also available in the new SAP reporting, for example. In this case, plan data of ACDOCP should also not be changed parallel in another plan interface: in the worst case they would be overwritten again the next time Allevo is called up.

See also constant S4H_POSTING_MODE with further options when transferring plan data to the Universal Journal (monthly/yearly values, handling of existing data).

---------------------------------------------------------------------------------------------------------------------------------------

* new from version 4.0

First implementation