Planning Statistical Key Figures through Separate Program Execution  

PLANSTAGR_PRG

* from Allevo version 3.2.3

High integration level in Allevo sometimes results in wrong output caused by sequentially performed planning steps during the Allevo planning process. This happens because the sequentially performed BAPIs are not designed for this direct sequence. The reason might be the internal caches that are not updated in a correct way. The current constant allows running the BAPI of the primary cost posting in a separate program context (the so called “roll area”) each time the program is called. Thus, the BAPI is forced to attend to new values instead of relying on the previous BAPI’s caches. (We are not talking of a database cache here but of a cache in a function group which is used by the BAPI. The database cache - if available – remains in use in future). 

The following application scenarios are known to date:

· When creating a project per BAPI (e.g. a BAdI in Allevo) and planning values for this project within the same Allevo step, it may happen that the planning BAPI will find an incorrect project structure in the cache. This, in turn, leads to an error when rolling up the planning values (e.g. runtime error, since the above-located WBS element is not found; the exception occurring in this case is not intercepted by SAP, Allevo cannot intercept it in another way either).

To avoid these errors, Allevo offers a special workaround. The activation of this workaround is made via the constant PLANSTAGR_PRG with an X in column Value from.

Note:

The constant transfers the program call of the BAPI to another environment in order to reset the BAPI’s internal variables. Apart from that, no restrictions are caused by the workaround. See also the constant PLANPRIMCOST_PRG.