Parameter for Direct Activation of the CO-PA Interface

ACTIVE_COPA_PARAM

// Allevo version 3.3 and later

The CO-PA interface can be directly started from the Allevo main menu by clicking the button „Transfer plan data“, thus calling the corresponding function module. See also constant SATxx_COPA for activating this function.

The constant ACTIVE_COPA_PARAM allows to further refine the activation options with additional control parameters. Currently, the following applications are provided for:  

1. Not every planner has all authorizations required for booking in CO-PA. In such cases, it is useful to execute the interface via RFC call with only the user defined for the RFC destination is required to have the necessary authorizations (via type R/3 connection 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 via the CO-PA interface this may reduce the 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 settings 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 destination, 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 oft he interface

ú 1 means background calling or activation via RFC destination

The combination 001, for example, means that the CO-PA interface is only activated for the table /KERN/IPPSAT03 via RFC destination (the corresponding RFC link must be entered in the column Value from).  

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

NOTE: The satellites concerned must in addition be activated via the constants ACTIVE_SAT and SATxx_COPA. Background processing is done via SAP transaction.

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.