Ansicht
Dokumentation

ECH_PE_CHECK_BEFORE_ - BAdI: Customer-Specific Check Before Saving in Payload Editor

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

You use this Business-Add-In (BAdI) in the Forward Error Handler (CA-FS-ECH) component. You use this BAdI to determine that the changes to the payload of a postprocessing order can be saved only if certain conditions are met. One of these conditions could be that the user has added an extensive text or an attachment.

The BAdI uses the CHECK_SAVE_ALLOWED method that checks whether saving is permitted.

If you implement this BAdI, you need to trigger the exception CX_FEH_PE_SAVE_NOT_ALLOWED if you want to save a change in payload editor that does not fulfill your conditions. The data is not saved and the user receives a message.

If you want to use your own messages, you can derive new exception classes and assign them to your messages.

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

For more information about the implementation of BAdIs in the context of the enhancement concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

The follow sample implementation is available:

• ECH_TEST_PE_CHECK_BEFORE_SAVE

This sample implementation is assigned to a generic message that indicates that saving is not permitted.

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2113 Date: 20240523 Time: 165301     sap01-206 ( 88 ms )