Issue/Solution: Errors with IDOC message type PEXR002/REMADV

Message type PEXR2002/REMADV, can used to create remittance advice for customer using EDI 820 or other common formats. The following errors are common to appear in basic type PEXR2002 and message type REMADV as the mapping of IDOC fields to customer or company code is not very intuitive.

FD 16 - Company code could not be determined for intermediate document 
FD 17 - Customer/vendor could not be determined for intermediate document

To resolve the errors above, it's very important to understand how standard SAP function module to process Remittance Advice determines the relevant Customer or Company Code records.

Customer Determination
The Customer to whom remittance advice is to be posted is determined using segment with the following alternatives

1. Based on Partner Profile, as configured in WE19 if the partner is of type "KU" - customer
2. If partner type is not "KU", Segment E1EDKA1 is checked the following order of precedence where the partner function E1EDKA1-PARVW = "AG"

• Based on field LIFNR (Vendor) if Partner Function (PARVW) = "AG" (Sold to Party) against KNA1-KUNNR (Customer Account Number)

• Yes: Field LIFNR in the IDOC is validated against KUNNR in table KNA1

• Based on Our Number at Vendor/Customer (Name1) if the Partner Function (PARVW) = "AG" (Sold to Party) againt KNBK-KOINT , where KNBK-KOINT is Customer's Bank Account Holder Name as maintained in customer master Payment Transaction tab  

Company Code Determination 

1. Based on configuration in OBCA 

• Company Code Name assigned to the partner type and partner number is checked against the fields PARTN and NAME1 in segement E1EDKA1, where Partner Function (PARVW) = "BE"

2. Based on Details of the bank account in segment E1IDB02 where Partner function(PARVW)= "BB"

Some more details may be found in SAP Note 63485
https://service.sap.com/sap/support/notes/63485