Simple example for Mirror transactions
Customizing settings under
Financial Supply Chain Management > Treasury and Risk
Management > Transaction Management > Distribution of Mirror Transactions.
Step 1) Maintain Relevant Product Types and Transaction Types
(Table: VTBMDEX), define the sender (outgoing) side:
Company Code Product Type Transactn Type Activity Activity
Cat. Counterparty
0001 51A 100 01
10 YHW01
Step 2) Map Product Types and Transaction Types (Table:
VTBMDMAP), mapping outgoing side and incoming side using MetaText:
Company Code Product Type Transactn Type MetaText Direction
Function
0001 51A 100 HMI - 01
YHW1 51A 200 HMI + 01
Step 3) Process Incoming Data (Table: VTBMDINFKT), define receiver (incoming) side:
Company Code Product Type Transactn Type Activity Activity
Cat. Counterparty Activity
YHW1 51A 200 01 10
DEUBA
01
Step 4) Assign Company Code to Partner (Table: VTBMDPARTNER),
assign counterparty to company code:
Company Code Counterparty
0001 DEUBA
YHW1 YHW01
System first uses the sender side from step 1) to select the
outgoing side of step 2), then find the incoming side using the MetaText, find
the entry in step 3) to create mirrored deal, checking the assignment of
company code and counterparty in each step.
Hints:
- There is a report RFTB_MIRROR_CUSTOMIZING_CHECK
which can be used to check the customizing settings for mirror via SE38. - Simulate in FTR_CREATE for the receiver side, if
deal can be created/saved correctly, e.g. in some cases, field portfolio is
mandatory for receiver side; if it is not assigned in sender transaction,
mirrored transaction will not be created. - Check tcode SM58 immediately to see if error
occurs after you have created a transaction for sender deal.