Ansicht
Dokumentation

MIRRORMAP - ICT - Map Product Types and Transaction Types

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Define a mapping table for different product and transaction types.

The direction Outgoingmust be assigned to the sending company code and Incomingto the receiving company code.

0001 ,,,,51A ,,100 ,,Fixed-Term Deposit ,,Outgoing ,,Mirrored

ABCD,,,,,,51A ,, 200 ,, Fixed-Term Deposit ,,Incoming ,,,,Mirrored

In this case, an outgoingfixed-term deposit (51A 100) sent by company code 0001 is displayed as product type 51A and transaction type 200 (that is, as an incomingfixed-term deposit) for the receiving company code ABCD.

The meta-text must be the same for outgoing and incoming transactions. We recommend a descriptive name (for example, "Fixed-Term Deposit").

Example:

TRM1 51 ,,,,100,,Fixed-Term Deposit,,Outgoing ,,Mirrored

If a fixed-term deposit is carried out with SUB AT for example, the following logic is used:

TRM2 51,,,,200,,Fixed-Term Deposit,,Incoming,,Mirrored

A fixed-term deposit (transaction type 100) in company code TRM1 therefore means an incoming fixed-term deposit in company code TRM2 (SUB AT). In this context, the meta-text has a primary control function.

CoCd ,,PType ,,TType,,Meta-Text,,,,,,Direction,,Function

TRM2,,51,,100,,Incoming Fixed-Term Deposit,,Incoming,,Mirrored

TRM2,,51,,200,,Fixed-Term Deposit,,,,Incoming,,Mirrored

General Material Data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 1645 Date: 20240523 Time: 214809     sap01-206 ( 26 ms )