BAdI name	Description
/AEB/WU_PREF_CHK_1	Check for declaration of origin for destination country This BAdI, called in conjunction with function module /AEB/WU_PB_DET_INV_PREF_TEXTS or /AEB/WU_PB_DET_CUS_PREF_TEXTS, indicates whether a declaration of origin is allowed for a given destination country.
/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 synchronization (report: /AEB/WU_SYNC).
/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/WF_EXPORT_01	File creation: single file written This BAdI is called as soon as a file has been completely written to the file system when exporting data. The BAdI lets you react to the completion of the file.
/AEB/WF_LP_READ_01	Use parameter 3 in the file path This BAdI allows you to use parameter 3 when maintaining the file path. The placeholder will then be replaced with a value from this BAdI at runtime.
/AEB/WU_DOOI_CHK_01	Determination of additional data for the EUJapan agreement This BAdI lets you maintain the additional data, origin criteria and exporter name for the EU-Japan agreement.
/AEB/WU_DOO_CHK_01	Determination of additional data for the agreement between EU and Great Britain. This BAdI lets you maintain the additional data, like the exporter name.
/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/WF_EXPORT_01

The handle_single_file_written method is called after each .csv file created by the /AEB/WU_RETRY_EXPORT job. This method can be used to indicate to an external process that the writing of the file is complete. To signal this, a second file with the same file name, but with a different file extension .rdy is written in this sample implementation. The external process can then react to the creation of the .rdy file, and only then import the .csv file. The .rdy file can then be discarded.

METHOD /aeb/if_ex_wf_export_01~handle_single_file_written.
DATA:
  filename TYPE string.
  
filename = im_file_name.
REPLACE '.csv' WITH '.rdy' INTO filename.
OPEN DATASET filename FOR OUTPUT IN TEXT MODE ENCODING UTF-8.
CLOSE DATASET filename.
ENDMETHOD.

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:

/aeb/cl_wu_pb_spbt_contexts=>c_wu_export (/AEB/WU_EXPORT program)