https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/af9ef57f504840d2b81be8667206d485/306fb6531de6b64ce10000000a174cb4.html?version=1909.001
Inbound Processing of IDocs Received
Use
The system creates an invoice.
The following table lists the most important data for posting the invoice document:
Prerequisites
The following information is mandatory for processing the IDoc:
Purchase order number and purchase order item or delivery note number
Vendor number
Company code
Tax code
Amounts
If the system cannot determine this information, it cannot process the IDoc. For further information, see Processing EDI Invoices manually.
Features
Determining the Vendor Number
The system first determines an IDoc segment of type E1EDKA1 using the qualifier (E1EDKA1-PARVW) LF (vendor) or RS (invoicing party). The system then determines the IDoc data according to the following priorities:
The vendor specifies the number used for the vendor’s company within your company
The system uses the content of the field Partner number (E1EDKA1-PARTN) to search for a vendor number .
The vendor specifies the number used for your company within the vendor’s company
The system searches for a vendor number that has the contents of the field E1EDKA1-LIFNR in the field Our account number with the vendor (LFB1-EIKTO) .
More than one vendor could have maintained the same number for your company, so the vendor number is only adopted here when the system can clearly determine it.
Determining the Company Code
The system first determines an IDoc segment of type E1EDKA1 using the qualifier (E1EDKA1-PARVW) RE (invoice recipient). Then it determines the company code using table T076B in the following order of priority:
The system uses the content of the field Partner number (E1EDKA1-PARTN) to search for the company code .
The system uses the content of the field Description (E1EDKA1-PARTN) to search for the company code . Note: The system is case sensitive for this.
In Customizing for Logistics Invoice Verification, you configure the company code to be posted to for each partner number.
You specify the customer number from the sending system as the company code name in the invoice. As an alternative to the customer number, you can enter the customer name.
Determining the Tax Code
The system uses table T076 M to convert the tax code from the IDoc segment of type E1EDK04 (header) and type E1EDP04 (items).
The system uses the following order of priority to determine the IDoc data:
Tax type and tax rate in the IDoc, country of the company code
Tax type is ‘VAT’, tax rate in the IDoc, country of the company code
Tax type and tax rate in the IDoc, country not defined
Tax type is ‘VAT’, tax rate in the IDoc, country not defined
In Customizing for Logistics Invoice Verification, you configure for each partner which tax types and tax rates in transferred IDocs correspond to which tax codes in your system. You can configure this to depend on the country of the company code.
The entries for the tax rate in the system should have the same syntax as the tax code transmitted in the IDoc.
You can use customer exit EXIT_SAPLMRMH_011 (enhancement MRMH0002) to determine the vendor number, the company code and the tax code in a different way. For further information, see Customizing for Invoice Verification → Logistics Invoice Verification → Develop Enhancements for Invoice Verification .
Delivery Note Allocation
The vendor transmits an invoice in the form of an IDoc. This invoice contains a delivery note number in IDoc segment E1EDP02 ( Qualifier 16) but no information on the purchase order numbers or purchase order items. The system can determine the purchase order numbers and purchase order items using the delivery note number provided.
The following restrictions apply:
The delivery note number used must exist only once for a vendor.
If a delivery note contains more than one item, the same material number, EAN material or vendor’s material number must occur only once.
If these conditions are not met, the system cannot process the IDoc.
The system determines the allocation of the invoice items to the goods receipt items according to the following priorities:
The system searched for the EAN number segment E1EDP19 (Qualifier 003) .
If no EAN number is transmitted in the IDoc, then the allocation is made using the vendor material number in the segment E1EDP19 (Qualifier 002) .
Processing Returns Items
You can process returns items at EDI invoice receipt. The following conditions must be met:
All delivery items must be either invoice items or credit memo items in a single invoice or credit memo. In other words:
If all the delivery items are invoice items, all the returns items must be credit memo items.
If all the delivery items are credit memo items, all the returns items must be invoice items.
If these conditions are not met, the system cannot process the IDoc.
Posting date
For EDI invoice receipt, the system determines the posting date as the day’s date.
Terms of Payment
The system determines the terms of payment that are posted by IDoc, according to the following rules:
If the IDoc for the invoice contains E1EDK18 segments and at least one of these segments contains a value, days or a percentage, then the values are copied from the IDoc.
If the IDoc for the invoice contains E1EDK18 segments with no values, then the terms of payment are read from the vendor.
If you are dealing with a stock transport order, in other words, the text ‘STOCK TRANSPORT ORDER’ appears in the text field for segment E1EDK18 (Qualifier 004) , and no other IDoc segments are filled in segment E1EDK18 , then the terms of payment are read from the first purchase order in the IDoc.
| Segment | Field | Qualifier | Remark | SAP field | Description |
|---|---|---|---|---|---|
| E1EDK01 | CURCY | Conversion to SAP currency | RBKP-WAERS | Currency key | |
| E1EDK01 | BSART | Invoice (=INVO) Credit memo (=CRME) | RBKP-XRECH | Indicator: post invoice | |
| E1EDKA1 | PARTN | PARVW ‘LF’ or ‘RS‘ | 1. Priority | RBKP-LIFNR | Invoicing Party |
| E1EDKA1 | LIFNR | PARVW ‘LF’ or ‘RS‘ | 2. Priority | RBKP-LIFNR | Invoicing Party |
| E1EDKA1 | PARTN, NAME1 | PARVW ‘RE‘ | Convert using T076B | RBKP-BUKRS | Company code |
| E1EDK02 | BELNR | QUALF ‘009’ | RBKP-XBLNR | Reference document number | |
| E1EDK03 | DATUM | IDDAT ‘012’ | RBKP-BLDAT | Document date | |
| E1EDK03 | DATUM | IDDAT ‘024’ | RBKP-ZFBDT | Baseline date for payment | |
| E1EDK04 | MWSKZ MSATZ | Convert using T076M | RBTX-MWSKZ | Tax code | |
| E1EDK04 | MWSBT | RBTX-WMWST | Tax amount in document currency | ||
| E1EDK18 | PRZNT | QUALF ‘001’ | RBKP-ZBD1P | Cash discount percentage 1 | |
| E1EDK18 | TAGE | QUALF ‘001’ | RBKP-ZBD1T | Cash discount days 1 | |
| E1EDK18 | PRZNT | QUALF ‘002’ | RBKP-ZBD2P | Cash discount percentage 2 | |
| E1EDK18 | TAGE | QUALF ‘002’ | RBKP-ZBD2T | Cash discount days 2 | |
| E1EDK18 | TAGE | QUALF ‘003’ | RBKP-ZBD3T | Deadline for net conditions | |
| E1EDKT2 | TDLINE | RBKP-BKTXT | Document header text | ||
| E1EDP01 | MENEE | For the consistency check | |||
| E1EDP01 | MENGE | RSEG-MENGE | Quantity | ||
| E1EDP02 | BELNR | QUALF ‘001’ | RSEG-EBELN | Purchase order number | |
| E1EDP02 | ZEILE | QUALF ‘001’ | RSEG-EBELP | Purchasing document item number | |
| E1EDP02 | BELNR | QUALF ‘016’ | Use this delivery note number to find the goods receipt | RSEG-LFBNR RSEG-LFGJA RSEG-LFPOS | Document number/fiscal year/reference document item |
| E1EDP04 | MWSKZ | Convert using T076M | RSEG-MWSKZ | Tax code | |
| E1EDP19 | MATNR | QUALF ‘003’ or ‘002’ | Allocation to delivery note | T_DRSEG-MATNR | Delivery note numbers |
| E1EDP26 | BETRG | QUALF ‘003’ | 1. Priority | RSEG-WRBTR | Amount in document currency |
| E1EDP26 | BETRG | QUALF ‘005’ | 2. Priority | RSEG-WRBTR | Amount in document currency |
| E1EDS01 | SUMME | SUMID ‘011’ | 1. Priority | RBKP-RMWWR | Gross invoice amount in document currency |
| E1EDS01 | SUMME | SUMID ‘010’ | 2. Priority | RBKP-RMWWR | Gross invoice amount in document currency |