 |
| ||||||||
How do I map Payment Terms to Suppliers using the PurchaseOrgSupplierCombo.csv file?
Customers using an SAP back-end system can assign existing payment terms to suppliers using PurchaseOrgSupplierCombo.csv file.
- Current contents of the file can be exported by navigating to Manage > Core Administration > Data Import/Export > Export.
- Search for and run the task, Export Purchase Org To Supplier Mapping.
- Edit the file as needed.
- Import the file back into the system by navigating to Manage > Core Administration > Data Import/Export > Import.
- Search for, and run the task, Import Purchase Organization To Supplier Mapping.
The file includes the following columns:
- EKORG
- PurchaseOrg.UniqueName
- The unique internal identifier of a purchasing organization. This value must match a purchasing organization defined in PurchaseOrg.csv.
- LIFNR
- Supplier.UniqueName
- The unique internal identifier of a supplier. This value must match a supplier defined in Supplier.csv.
- XERSY
- ERSVendor
- The Evaluated Receipt Settlement (ERS) vendor indicator. A Boolean field that must be configured with X for true, and No or (null, no value) for false.
- ZTERM
- PaymentTerms.UniqueName
- The unique internal identifier of a payment term. This value must match a payment term defined in PaymentTerms.csv.
The contents of the EKORG, LIFNR, and ZTERM columns must match information already loaded from the corresponding import file. In other words, each of these other files must be imported with the needed information first, before the PurchaseOrgSupplierCombo.csv is loaded.
Loading the PurchaseOrgSupplierCombo.csv file before loading the details that it references will cause the system to generate an error, since the PurchaseOrgSupplierCombo.csv does not define these values; it merely searches for them. If the values are not already defined, the search will fail and the payment term will not load successfully into the system.
Core Procurement > Core Administration