The External Commodity Crosswalk (ECOMMX) table is used to crosswalk the supplier’s commodity code to the Advantage client’s commodity code scheme when the buyer checks out from the supplier’s site. This table is used either when the Commodity Crosswalk is enabled on the PunchOut Control table or when the Enable Commodity Code Crosswalk (T/F) parameter is set to True in the Load EDI Invoices chain job. When used for Punchout, the crosswalk table record is populated based on the External Commodity Code scheme specified on the PunchOut Control table. When used in the Load EDI Invoices chain job, the table crosswalks qualifier codes and their related ID’s (found in the IT1, SLN, and SAC segments) to the Advantage client’s commodity code scheme. A combination of Vendor Customer Code (or ALL), Qualifier/Scheme, and External Identifier are used to uniquely derive the commodity code. The Vendor Customer Code field is used to indicate the vendor that the crosswalk record applies to. ALL may be used as a wildcard value to indicate a record is applicable as a default for all vendors.
For Punchout, when the buyer checks out from the supplier site the system uses this table to determine the commodity code to be populated on the Universal Requestor transaction and subsequently the Delivery Order transaction. If no match is found, the buyer is required to select a commodity code on the Delivery Order transaction.
For the Load EDI Invoices chain job, if the parameter is set to True the system uses this table to determine the commodity code to populate on the invoice. If a match is not found on this table, and a default commodity code is not provided, then an EDI 824 error would be created, which would prevent the invoice from being created.
Configuration Points:
Internal Commodity Codes must first be set up on the Commodity table.