General notes on implementation
Please note the following general instructions for implementation.
Placement of calls in the coding
If there is already existing coding in your SAP system in one of the user exits, customer exits, and BAdIs documented in the following sections, the calls of the AEB functions (includes) must be carried out accordingly:
- Make sure that the AEB includes are always called, i.e. they must not be skipped by executing the existing coding (e.g. exits/returns) or unfavorable placement.
- If the existing coding changes data that is also used by the add-on, the calls of the AEB includes must take place afterwards. Otherwise, the data changes are not taken into account by the add-on.
Important notes for integration with Trade Compliance Management
Depending on the configuration, existing blocks in the business object are read because of the calls of the AEB includes and changed in the course of the compliance check. If the existing coding changes the contents of blocks, this must be done before the AEB includes are called.
Example: An existing code in the SAVE_DOCUMENT_PREPARE user exit of the sales document sets a delivery block. The AEB include must then be called afterwards in order to take the new value into account.
Triggers for screenings of sales documents and deliveries
For sales documents and deliveries, the compliance screening is carried out when the call is made in the SAVE_DOCUMENT_PREPARE user exit. The call in the SAVE_DOCUMENT user exit creates or updates the entry in the Compliance Monitor. Even if the SAVE_DOCUMENT user exit is not run, the document can still be screened. Observe this note for special processes, such as simulations.