Inbound processing is not using the Transaction Map listed on the Partner Profile
Debug report, EBDI041, lists the correct Application Definition loaded, but the wrong partner specific Transaction Map is loaded.
The transaction maps used as partner specific maps; meaning they are listed on the partner profile, have the USE field as 'G' in the Transaction Maps definitions.
G is used to denote a General Transaction Map
P is used to denote a Partner Specific Transaction Map
The inbound process creates a temp file with all transaction maps linked to the application definition that is processing at that time. The general maps are put into the file first, followed with partner specific maps. When the partner is located and a map is listed on the profile the process will use this map, as long as it is part of the temp file created (regardless of the USE field value). The problem occurs when all transaction maps have a USE code of G. The process has to choose the map based of the general map rule, of document type (i.e. 810) and standards version (i.e. 004010). When more than one map exists for the 810 in version 004010 (because they are intended to be partner specific) it will choose the first map it finds (these maps are listed in the temp file in alphabetical order).
Diagnosing the problem
Review the transaction map definition to see what the USE field is. When maps are to be partner specific the USE field needs to be set to P.
Resolving the problem
Once these maps were corrected with a 'P' USE code the correct map was loaded in the EBDI041 report, and used for mapping the data.