Ansicht
Dokumentation

J_3RL_TG_BADI - BAdI: Notice Journal

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Logistics Execution (LE) component. You can use this BAdI to define your own logic for certain functions in the Notice Journal (J_3RL_DOC_CKPT) report.

The following BAdI methods are available:

• SIGN

You can use this BAdI method to define what happens when you choose Signin the Notice Journal(J_3RL_DOC_CKPT) report. This method is intended for determining how outgoing documents are signed electronically and how they are encrypted.

• SUBMIT

You can use this BAdI method to define what happens when you choose Submitin the Notice Journal(J_3RL_DOC_CKPT) report. This method is intended for determining how outgoing documents are submitted to the authorities.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder(transaction SE18).

BAdI Implementations:

• EI_J3RL_NOTICE_COCKPIT

This implementation determines that outgoing documents are processed as follows:

• Documents are signed by including user data from the SU01 transaction into the outgoing XML file.

• Documents are saved locally to the c:/temp/outgoing folder on your computer.

Please note that, on macOS, this function requires a custom implementation.

• Documents are encrypted using the MD5 Hash algorithm

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 2050 Date: 20240523 Time: 215329     sap01-206 ( 35 ms )