Further BAdI definitions

BAdI name	Description
/AEB/WU_MMDS_01	Synchronization material data This BAdI handles additional events during the synchronization of the material data. This BAdI runs per material and destination country during the journal synchronization (report: /AEB/01_JE_WORKER or /AEB/WU_JE_WORKER).
/AEB/WU_DOC_CUS_01	Data change any object This BAdI makes it possible to change data after is has been populated by default to determine the declaration of origin.
/AEB/WU_DOC_INV_01	Data change invoice This BAdI makes it possible to change data after is has been populated by default to determine the declaration of origin.
/AEB/WU_DOC_SD_01	Data change order This BAdI makes it possible to change data after is has been populated by default to determine the declaration of origin.
/AEB/WU_DOC_DLV_01	Data change delivery This BAdI makes it possible to change data after is has been populated by default to determine the declaration of origin.
/AEB/01_QTSK_CTRL_01	Limiting the processes to be used by QCTSK This BAdI offers the possibility to limit the used processes from server groups for QCTSK.
/AEB/01_SHM_01	Activation of shared memory for texts

BAdI /AEB/01_QTSK_CTRL_01

The parameter of the BAdI is a runtime context object. It offers the following methods:

GET_RUNTIME_CONTEXT (Provides the runtime context from which the task was created)
GET_USED_SERVER_GROUP_NAME (Provides the used server group)
GET_SERVER_GROUP_MAX_WPS_COUNT (Provides the maximum number of processes of the server group)
GET_MAX_WPS_TO_USE_COUNT (Provides the maximum number of processes to be used)
GET_INITIAL_FREE_WPS_COUNT (Provides the number of free processes at initialization)
SET_MAX_WPS_TO_USE_COUNT (Sets the maximum number of processes to be used)

The runtime context is used to define the number of processes to be used per use case. At the moment, the following possible runtime context exist: