Ansicht
Dokumentation

LCM_ESIGN_FILTER - Filter e-Signature Documents

General Material Data   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Use this Business Add-In in CM-LTcomponent while creating an e-Signature Envelope, to filter the documents that are in process for e-Signature. For example, you can use this BAdI to exclude certain file formats.

You must ensure the following Customizing setting is enabled:

Define the parameters to activate e-Signature in Manage Legal Transactions and Manage Legal Documents applications by configuring the settings under Enterprise Contract Management> General Settings> Define e-Signature Parameters.

To create a BAdI implementation, you can use the transactions SE18 or SE19, or you can use the Custom Logic app in the front-end system. If you use the Custom Logic app, the following applies:

• The app provides a special ABAP language version ABAP for Key Users. This makes the implementation of BAdIs for business experts and implementation consultants easier.

• The app ensures that you can use only released interfaces.

If you use the transactions SE19 or SE18 to create a BAdI implementation, the implementation is not visible in the Custom Logic app.

If several BAdI implementations exist, the system runs through the implementations in the following order:

1.,,Implementations created in the transactions SE18 or SE19.

2.,,Implementation created in the Custom Logic app.

BAdI method documentation:

You can use this method filter e-Signature documents from the selection that was made when the e-Signature process was triggered. For example, you can use this to exclude documents with certain file formats.

The documents to be sent with the current e-Signature envelope will be deleted from the CHANGING parameter CT_LGLCNTNTMDOCUMENTUUID.

Changing:

CT_LGLCNTNTMDOCUMENTUUID

When the BADI is called, it contains a list of Legal Document GUID (LglCntntMDocumentUUID) of all documents to be sent with this e-Signature envelope. The BAdI returns the list of Legal Document GUID to be finally sent with the current envelope (i.e. it removes all GUID to be filtered).

Do not add additional Legal Document GUID which were not provided when the BAdI is triggered. The system will not consider these GUID for processing.

Please refer to the example class implementation CL_LCM_ESIGN_FILTER_EXAMPLErelated to this BAdI.

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 2704 Date: 20240523 Time: 194606     sap01-206 ( 48 ms )