cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

for IT edocument, we have RE with debit and credit memo with same tax code, how to distingush?

S0009323523
Newcomer
0 Kudos
112

hello experts:

thanks first

you know for MIRO it is RE document type, but we have normal MIRO, and credit memo also.

both are RE type, and tax code is also same. eg: tax code E4

so how to do this value mapping via     /AIF/VMAP   ---->   GET_DOC_TYPE_EXT

it should be different node, right? like REE4 (debit) --> TD01   and  REE4 (credit) ---> TD04

thanks again for your advice

Accepted Solutions (0)

Answers (1)

Answers (1)

umasaral
Contributor
0 Kudos

Hi 

1. Define Value Mapping in AIF:
Go to the AIF transaction `/AIF/VMAP`.
Select `GET_DOC_TYPE_EXT` for the mapping configuration.

2. Create Separate Mappings for Debit and Credit:
Create two entries in the value mapping table:
For Debit Entries:
Source: `REE4`
Target: `TD01`
For Credit Entries:
Source: `REE4`
Target: `TD04`

3. Use Additional Fields for Differentiation:
Since both MIRO types have the same document type (RE) and tax code (E4), consider using additional fields in the payload to differentiate between debit and credit. This could be a specific field that indicates the type of transaction (e.g., a flag or indicator).

4. Modify Mapping Logic:
Ensure that the mapping logic in AIF checks the additional field. If the field indicates a credit transaction, it should map to `TD04`, while a debit transaction should map to `TD01`.

5. Test the Mapping:
Perform tests to ensure that the correct document types are assigned based on the values passed in the interface. Check the logs in AIF for any errors or issues during the mapping.

By following these steps, you should be able to successfully configure value mapping for your MIRO transactions, distinguishing between debit and credit memo scenarios.