Parameter for Directly Starting the Module „Flexible Planning“

ACTIVE_FP_PARAM

// Allevo Version 3.3 and later

After calling the corresponding function module, the extra Allevo module Flexible Planning can directly be started in the Allevo main menu by clicking the button „Transfer plan data“ (see also constant  ACTIVE_FP).

The constant ACTIVE_FP_PARAM is designed to further refine the start options with additional control parameters. Currently the following applications are provided for: 

1. Not in all cases the planner has all authorizations required for posting via Flexible Planning (e.g. for activity outputs which require the authorization to post to the receiving cost center). In such cases it can be useful to execute the posting via an RFC call, which only requires the user defined for the RFC destination to have the necessary authorization (installation via type R/3 link SM59 with firmly defined user and password; target system and client to be selected like in the current SAP system).

2. If a high number of postings is done through Flexible Planning, this may reduce the posting performance. In this case, it is recommended to run the interface in the background: Allevo then does not wait for the end of the program run.

The following setttings are possible:

§ BACKGROUND must be set in the constant’s column Value from in order to execute the background task.

§ Any other entry in the column Value from is interpreted as RFC destsination, previously defined via SM59 (otherwise an error prompt is shown when the program is started). Only one RFC destination per layout can be addressed.

§ A number combination of 0s and 1s can optionally be entered in the column Value to, determining which satellite is addressed. 

ú 0 or blank are the standard settings, i.e. the standard execution of Flexible Planning

ú 1 means background calling or activation via RFC destination

The combination 001, for example, means that the Flexible Planning is only activated for the table /KERN/IPPSAT03 via RFC destination (the correponding RFC link must be entered in the column Value from).

Without an entry in the Value to column, all active satellites are posted to via a RFC link.

If Flexible Planning is used to process data from several satellites, Allevo generates one order per each satellite in the background processing. These orders may be executed in parallel via SM58. This is not critical as long as the posting records/objects don’t bloc each other. When processing identical objects, only the last access to Flexible Planning may be active in the background.

NOTE: The satellites concerned must in addition be activated via the constants ACTIVE_SAT and SAT_FP. Background processing is only relevant for saving plan data. The constant SAVE_LOG can be helpful to control the processing via the SAP Application Log. The calls for background processing are effectuated via the SAP transaction SM58.

New for Allevo Version 3.4 and later: Execution in the background

Background execution via several satellites is done successively and no longer in parallel via SM58. This avoids that postings on one object block each other. The sequential processing in addition respects the individual order corresponding to constant ACTIVE_SAT_SORT.