Mirror functionality, like the name described, when you create a transaction, the system can create another transaction with opposite direction automatically. So you do not need to create it again in the system which can save lots of time. But in order to do that, you need to finish some setting. The main path exists in
SPRO->Financial Supply Chain Management
->Treasury and Risk Management
->Distribution of Mirror Transactions
The first step you need to do is to tell the system when creating transaction with
some production type, transaction type, activity and business partner, we need to create a mirror transaction. This should be done under
“Maintain Relevant Product Types and Transaction Types”
Then, it’s necessary to assign the business partner to the company code. By this step, the system can know in which company code the mirror will be created. For example, if you create a transaction in company code A with business partner B, then you need to assign a business partner C to A, and assign a company code D to business partner B. Then the system can create a mirror transaction with company D and business partner C. This is set under:
“Assign Company Code to Partner”
After completing the mapping of company code, it’s necessary to map the production type and transaction type which can determine the production type and transaction type in the mirror transaction. This is done under
“Map Product Types and Transaction Types”
At this step, each pair of mapping should have unique METATEXT. I see some example before that some companies do not use unique METATEXT which causes some tricky problems.
Then, you can also do the mapping on the flow type level. This can be done under “Map Flow Types”. But there is some functionality limitation
Additional flows (e.g. fees) cannot be mapped
Entries in condition details are not transferred
Nominal position changes during the term are not transferred
Changes to the transaction are not transferred
Flow modifications are not transferred
At last You maintain for processing incoming data from the view of the receiving company code with the product types/transaction types already mirrored under “Process Incoming Data”.
After all the customizing is finished, you should be able to see the mirror transaction. But in case, there it’s not, you can use report FTB_MIRROR_CUSTOMIZING_CHECK to check the customizing.
Also Mirror transaction is create via LUW in SM58, so in case, it’s not created, the error can be shown in SM58 most of the time.