Ansicht
Dokumentation
TCORFVC_MAPPING - Define Format-Dependent Mapping Rules
Fill RESBD Structure from EBP Component Structure rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
In this IMG step, you can define mapping rules for incoming and outgoing correspondence messages in a given format. The mapping tool is the name given to the Mapping Configuration screen that you can access using the following path:
SAP IMG -> Financial Supply Chain Management -> Tresury and Risk Management -> Transaction Manager -> General Settings -> Correspondence -> Correspondence Messaging Interface -> Define Format-Dependent Mapping Rules
For outbound/inbound messages, you map the source type to the target type. These types can be DDIC types (like TCORY_CODATA for correspondence object) or manually created (this is typically done for SWIFT messages and as part of sample customizing). Typically for outbound messages, you map from source type TCORY_CODATA to a manually created target type. For inbound messages, the opposite applies.
To use the mapping tool, see the following documentation:
- Mapping Tool Screen - contains a description of each part of the mapping tool screen.
- Scope - explains how mapping rules are built.
- Navigation - explains navigation between different mapping configurations.
- Maintain mapping - explains the structure of mapping configuration.
- Buttons - explains functions used in mapping configuration.
- Service Methods - describes all available service methods provided by SAP. Customers can create their own service methods.
The formats must already be defined in the IMG activity Define Formats. BADI_TCORF_FORMAT_SINGLE has a filter format and, for format group "SWIFT MT messages", BAdI implementation BADII_TCORI_SWIFT_FORMAT_S. This is a default implementation and is implemented within class CL_TCORI_BADI_SWIFT_FORMAT_S. This class uses the mapping tool (class CL_TCORF_MAPPING). If you have not changed this behavior or are still using class CL_TCORF_MAPPING, the mapping tool is called.
Mappings are delivered for the following SWIFT standard formats:
| Outgoing Messages | Incoming Messages |
|---|---|
| MT300 | MT300 |
| MT320 | MT320 |
| MT395 | MT395 |
| MT399 | MT399 |
| MT502 | MT509 |
| MT540 | MT515 |
| MT541 | MT535 |
| MT542 | MT536 |
| MT543 | MT544 |
| MT545 | |
| MT546 | |
| MT547 | |
| MT548 | |
| MT566 | |
| ACK | |
| NACK |
- To create a new mapping, select the direction (incoming/outgoing) and the format of the mapping.
- In the definition of the mapping, you also need to define a service class in which you can implement complex operations that are required in the mapping. For SWIFT formats, SAP delivers the class CL_TCORI_SWIFT_SERVICE. This class can be used as a super-class for your own service class if you want to enhance the delivered standard functionalities.
- The mapping definition also contains the source and target table types. If you leave this field empty, a generic mapping object is used.
- If you have a generic target structure, you must first define the structure of the target.
- To fill the fields of the target structure, you must define rules for each component in the target that you want to fill.
- The basic operations are:
- LOOP - only for table- or structure-type targets
- SELECT - only for fields and structures
- MOVE - only for fields
- CALL - only for fields
- Parameter groups are used for service method calls (CALL) and they are format-independent.
- Conditions can be used in any operation. They are format-independent.
Outgoing MT300 is defined with source TCORY_CODATA (Treasury correspondence object data) and with a generic target. Incoming messages are defined the other way round.
BAL Application Log Documentation General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 5551 Date: 20240523 Time: 180754 sap01-206 ( 72 ms )
