Ansicht
Dokumentation

BADI_TCORF_META - BAdI: Metatype-Dependent Mandatory Steps (Process Events)

PERFORM Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

You can use this Business Add-In (BAdI) in the Transaction Manager (FIN-FSCM-TRM-TM) component to implement metatype-dependent steps of the messaging interface. The header and the content of the incoming and outgoing messages is formatted or parsed.

The BAdI is called during the creation of the formatted content (and header information) of an outgoing correspondence message and during converting incoming message content and header into a structured mapping object. The implementation has to convert the structured mapped content into a formatted, unstructured outgoing format. For incoming messages it converts unstructured, formatted messages into structured, parsed content in the form of a message object.

You must implement this BADI for all meta-types in your system. In the standard system there is a default implementation for the meta-types SWIFT MT, SWIFT SAP and FAX formats. For any new meta-type, you must define a new implementation.

The BAdI is filter-dependent. The filter is the meta-type.

You must have exactly one active implementation for a given meta-type.

• BADII_TCORI_FAX_FORM,,FAX Adapter - implementation of process methods

• BADII_TCORI_SWIFT_MT,,SWIFT Adapter - implementation of process methods

• BADII_TCORI_SWIFT_SAP,,Meta-type "SWIFT MT formats with SAP IP4"

To display the default code, choose Goto -> Default Code -> Display in the BAdI builder.

This BAdI uses the interface IF_TCORF_BADI_META..

For more information, display the interface in the Class Builder.

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Material Data  
This documentation is copyright by SAP AG.

Length: 1771 Date: 20240608 Time: 015140     sap01-206 ( 37 ms )