Avoid Zero Delta Planning

NO_ZERO_DELTA

(* extended in version 3.4)

Usually, only absolute plan values are entered in Allevo. When posting via BAPI, SAP determines the difference to the previously planned value itself and posts it as delta record in the individual plan items. If Allevo transfers the same value several times to BAPI, SAP therefore writes several delta documents having the value zero.

In order to avoid writing these unnecessary documents, the constant NO_ZERO_DELTA may be activated in Allevo. The value to be planned (or the quantity to be planned) is then compared to the value already existing in SAP before. Posting via BAPI is only initiated if a discrepancy is found.

In current Allevo versions (from 2.9.10), the constant NO_ZERO_DELTA may be restricted to certain row definitions via column Value to (as comma-separated list). The row definitions must be specified precisely; e.g. “A1“ if the constant shall be activated for row definition A1 (and not only “A“).

The constant NO_ZERO_DELTA is activated by entering X in column Value from; the following entries are possible:

· If X is entered, planning data will be written in SAP only if the content was modified compared to the previous state (before, planning data are read directly from the SAP tables before). From version 3.2, also P (= positive list of row definitions) may synonymously be entered.

· An entry N activates the constant just like an X but permits a negative list in the row definitions: in this case, Value to contains those row definitions that the constant shall NOT be valid for (from 3.2).

· For entry Y (from version 3.3), planning data are not determined right from the SAP tables but via appropriate BAPI functions (for primary costs, secondary costs and statistical key figures, periods and years respectively).

Note:

The constant NO_ZERO_DELTA primarily serves to avoid zero data records. Activation can cause the postings to require more time since each cost element containing a planned value is checked for delta records with the value zero. However, the opposite may also happen, i.e. the SAP posting can be accelerated: e.g. if additional queries or posting are set up behind in Customizing. In general, a performance improvement can be expected for profit center posting, since no BAPI functions are available in this case and Allevo does not use any Input functions for data transfer here (NO_ZERO_DELTA for PC is possible from version 3.2.21). NO_ZERO_DELTA in combination with rule planning is only possible in Allevo version 3.0.5 and later (see also LSTAR_VARIATOR). NO_ZERO_DELTA for profit center is possible from version 3.2.21. From Allevo 3.1, the constant is available also when using Allevo FP.

Exceptions:

Planning of zero documents can NOT be prevented for the following transactions:

· Activity type dependent planning via a rule type is active (constant LSTAR_VARIATOR)

· Delta planning is active (via column definition)

· Planning of activities and prices

· In case of deviations of the plan period and the validity of cost centers (e.g. the cost centers is only valid from January to August, but periods January to December are to be planned).

Note:

If there are already many zero data records existing in the system, report RKPLNC27 may be useful to remove entries in COSP and COSP.

New from version 3.4

Support during profit center planning for the old general ledger. See additionally constant PLAN_PC_IN_LOOP during period planning.