Vendor rebate claim response error messages

When vendor rebate claim responses are received, an internal record is created for every error, exception, or informational message that is found during validation. If you use ION processing, the messages are displayed in ETCC. If you use standard flat file processing, the messages are displayed on the EDI Entry Processing Rebates Report.

Transaction set rejection error messages

Transaction set rejection errors cause the entire transaction set to be rejected including all records in the file for the header record involved. Correct the errors before updating the transactions.

This table shows the transaction set rejection errors that can occur when you receive vendor rebate claim responses. The cause or corrective action and error number is also shown.

Message Cause or corrective action Error #
Invalid Trading Partner

Records with a missing or an invalid trading partner code or vendor number are not accepted.

Verify that the trading partner code for the vendor is defined in your EDI third-party software and specified on the Vendor Setup-eCommerce record.

Verify that the EDI 849 document contains the valid trading partner code or vendor number for the vendor.

1
Warning: Unknown Contract Number

Records with an invalid contract number are not accepted.

Verify the contract number in PD Pricing Setup.

Verify that the contract number in the EDI 849 document is valid.

2
Invalid Transaction Purpose Code

Rebates are not accepted for items with a transaction purpose code, ANSI X12 Segment BRC0, not equal to ‘00.’

Verify that the third-party EDI Mapper/transformation is correct.

 3

Line rejection error message

Line rejection errors cause the affected lines to be rejected, but not the entire document. Correct the errors before updating the transactions.

This table shows the line rejection errors that can occur when you receive vendor rebate claim responses. The cause or corrective action and error number is also shown.

Message Cause or corrective action Error #
Line Validity Error

An item record was received with a Validity Code other than “V”.

In ETCC, review the item and specify V for the Validity Code after the data is correct. Alternatively, cancel the item update.

 10
Item Reject Reason (from EDI Document)

An item record was rejected by the vendor with a specific Reject Reason Code.

In ETCC, review the item and clear the Reject Reason Code after the data is correct. Alternatively, cancel the item update.

 11
PDER Found but not in Printed State

A Line Reconciliation record is found, but the status is Disputed or Updated.

The Line Reconciliation record has already been processed. Contact the vendor to determine why a response to a rebate claim was sent again.

 15
Claim Found but PDER not Found

A claim record is found, but a corresponding rebate record is not found.

Compare your Line Reconciliation records for the claim with the information provided on the EDI 849 document to determine if the information sent by the vendor is invalid.

 16
Contract Status Message (from EDI Document)

A contract record was received with a Contract Status Code other than “oc” or “va”.

If the Contract Status Code Detail message was sent, review it and the contract data in ETCC. Specify oc or va to correct the Contract Status Code. Alternatively, cancel the update.

19
Contract Validity Error

A contract record was received with Validity Code other than “V”.

In ETCC, review the contract data and specify V for the Validity Code after the data is correct.

 20
Contract Reject Reason (from EDI Document)

A contract record was received with Contract Reject Reason Code.

In ETCC, review the contract data and clear the Reject Reason Code after the data is correct. Alternatively, cancel the update.

 21

Line exception messages

Exception, or warning, messages identify exceptions that stop transactions from processing, but do not cause data to be rejected. We recommend that you review each exception to ensure that your vendor receipts are updated correctly.

This table shows the warning messages that can occur when you receive vendor rebate claim responses. The cause or corrective action and error number is also shown.

Message Cause or corrective action Error #
Unknown Quantity Unit of Measure

The EDI Quantity Unit of Measure for a line item in the EDI 849 document does not exist in Distribution SX.e.

Verify that the EDI Unit of Measure in the EDI 849 document is valid. If it is valid, set up the EDI Unit of Measure in one of these functions:

  • SA Table Code Value Setup-Unit Conversion
  • Product Extended Unit Conversion Setup
 4
Unknown Price Unit of Measure

The EDI Price Unit of Measure for a line item in the EDI 849 document does not exist in Distribution SX.e.

Verify the EDI Price Unit of Measure in the EDI 849 document is valid. If it is valid, set up the EDI Unit of Measure in one of these functions:

  • SA Table Code Value Setup-Unit Conversion
  • Product Extended Unit Conversion Setup
 5
Total Lines Processed Do Not Match Total Lines Sent

For ION processing, verify that the total of item rebate records equals the value in SXVendorRebateClaim/RebateClaim/Total/ItemCount.

For standard flat file processing, verify that the total of item rebate records equals the value in the Total Item Records field in the Total section of the flat file.

A problem with the third-party EDI Mapper/transformation may exist.

6
No Corresponding Rebate Found

A corresponding rebate was not found. A Temporary Receipt is created in PD Rebate Reconciliation Entry after the update is performed in ETCC.

 7
Rebate Quantity <> Claimed Quantity This message is generated if the actual quantity does not equal the claim quantity for a Line Reconciliation record. 8
Paid Unit Amount <> Claimed Unit Amount

This message is generated if the actual amount does not equal the claim amount for a Line Reconciliation record.

This message is only generated if the actual claim amount must match the claim amount.

9
Prod from Inbound File Doesn't Match Invoice Line Prod

Product on the inbound EDI 849 does not match the product on the Distribution SX.e invoice line that is associated with the rebate record.

Compare your Line Reconciliation records with the EDI 849 document to determine if the information sent by the vendor is invalid. Verify these values:

  • Order number
  • Order suffix
  • Line item number
  • Sequence number
  • Claim number
  • Contract number

If the data is incorrect, verify that the third-party EDI Mapper/transformation is correct.

 12
Payment Below Underpayment Tolerance Limit This message is generated if the actual amount for a Line Reconciliation record exceeds the underpayment tolerance specified in Vendor Setup. 13
Payment Above Overpayment Tolerance Limit This message is generated if the actual amount for a Line Reconciliation record exceeds the overpayment tolerance specified in Vendor Setup. 14
No Corresponding Distribution SX.e Rebate Found, Temporary Receipt will be created

This message is generated if a Line Reconciliation record does not exist for a rebate and a temporary receipt is created.

Compare your Line Reconciliation records with the rebate information that is provided on the EDI 849 document. Determine if the information sent by the vendor is invalid.

 17
No Claim# Provided, Temporary Receipts Created

This message is generated if a claim number is not provided on the inbound EDI 849 and temporary receipts are created.

Determine the claim number that is associated with the temporary receipts. You must specify the claim number on the temporary receipts to create a vendor receipt record. You can then reconcile the claim.

18
Contract Follow-Up Reason (from EDI Document) A Follow-up Action Code was sent in with the contract record. In ETCC, review the contract data and Follow-up Action Code detail and then update the transaction. Alternatively, cancel the transaction. 22