EDI Entry Processing Contract Pricing Report matching logic
The EDI Entry Processing Contract Pricing Report uses a specific hierarchy to match the EDI 845 inbound document against all of the valid system values. After a match is found, the search does not continue.
The matching logic depends on how you use EDI 845 inbound data. To match a specific rebate record, the vendor can send the data within a Group code field or Product code field on the inbound file.
Group code hierarchy
- Vendor Product Group
- Rebate Type or Rebate Sub Type
Looks for vendor-specific or non-vendor-specific rebate, can attach a specific vendor number to the Rebate Type.
Validates the Sub Rebate only if the inbound Sub Rebate field is loaded. If loaded, then the Group code must match the Rebate Type and Sub Rebate Type.
- Product Price Type
- Product Category
- Product Line
- Rebate Type or Rebate Sub Type
- Rebate Type or Rebate Sub Type
- Product Price Type
- Vendor Price Group Note: This is the old Vendor Price Group linking to the Product Price Type.
- Product Category
- Product Line
Product code hierarchy
This hierarchy is used if a Product Group is not included in the EDI document. The validation links directly to the specific fields in the EDI 845 inbound document.
- Vendor Product
Product Warehouse Product Setup: Vendor Product, Warehouse, and ARP Vendor
Product Setup : Vendor Product and Vendor
- Product
Product Setup
- Barcode
Product Extended Product Cross Reference Setup for type B (Barcode)
- UPC
Product UPC Number Setup: UPC Setup table links to Product Setup record
- NAED Code
Product Setup record
Product Extended Product Cross Reference Setup for type I (Interchange) and T (Trade Service)
The Product code validation looks through all of the item identifiers until it finds a match. If the flat file contains multiple sets of product identifiers and all fail, then the report displays the first error found based on the hierarchy. If there is a valid match and the first three attempts failed, the report displays the valid data only.
If the vendor sends a vendor product group code and item identifiers, the EDI Entry Processing Contract Pricing Report only attempts to validate the Group data.
For the Group code validation, if a match to the Group code is found, it does not continue looking down through the Group code hierarchy.
The item level totals on the report track and compare the item level lines expected from the vendor to the item level lines received. The Item Level - Inbound TOTAL Section Count shows the total number of lines, or transactions, that match the total Item Record lines. The Item Level - Transactions Sent shows an actual count of the individual Item record transactions. This count is an accumulation of the PAD, ITEM, and PRICE sections within the inbound EDI 845in document. If these two totals do not match, then this error prints on the report: Total Item Level Lines Loaded Does Not Match Lines Sent (6745).