Ansicht
Dokumentation
/BSNAGT/MSG_OUT_BADI - BAdI: Outbound Message Processing
Fill RESBD Structure from EBP Component Structure BAL Application Log DocumentationThis documentation is copyright by SAP AG.
This Business Add-In (BAdI) can be used to enhance the capabilities of the connector for SAP Multi-Bank Connectivity. You can use this BAdI to enhance the supported message types and improve how outgoing message types are handled.
A BAdI implementation can be assigned for each message type. The implementing class contains several methods that are called by the connector during the outbound handling to apply outbound security, prepare the extended header, or process steps that must be executed after the outgoing message is sent.
The standard implementations are inherited from a default implementation, which is always called when a specific implementation for the given message type is not found.
Implementations that are added for specific message types must also inherit from the default implementation. Only redefine methods that are different from the methods in the default implementation.
This BAdI contains the following methods:
- APPLY_SECURITY_OUT(Apply Outbound Security)
- PREP_EXT_HEADER_BEF_SEC(Prepare ExtendedHeader before Security)
- PREP_EXT_HEADER_AFT_SEC(Prepare ExtendedHeader after Security)
- BASE64_ENCODE(Encode MessageContent Base64)
- PROC_AFTER_SEND(Processing after Sending)
- DETERMINE_TRANS_LAYER_CAT(Determine Transport Layer Category)
- PROC_BEFORE_SEC(Processing before Security)
The following BAdI implementations are delivered by SAP:
- /BSNAGT/BADI_MESSAGE_OUT_DEF
- Default BAdI implementation for outbound messages
- /BSNAGT/BADI_OUT_PAIN00100102
- Outbound handler for PAIN.001.001.02 messages
- /BSNAGT/BADI_OUT_PAIN0010103
- Outbound handler for PAIN.001.01.03 messages
- /BSNAGT/BADI_PING_TEST_OUT
- Ping test for outbound messages
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).
For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> Customer-Specific ABAP Development -> Enhancement Framework.
This BAdI uses the interface /BSNAGT/IF_BADI_MESSAGE_OUT.
For more information, display the interface in the Class Builder (Transaction SE24).
rdisp/max_wprun_time - Maximum work process run time General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 3588 Date: 20240423 Time: 203647 sap01-206 ( 55 ms )