SPS Document Processing Error on AllowChrgAmt

SPS Document Processing Error on AllowChrgAmt

Release: 12/31/2019
Updated: 7/10/23
Version: All

Q - I received an email from SPS Commerce showing this message:
InvoiceNumber:708241 InvoiceNumber:708241 Missing element: expect AllowChrgAmt before ending ChargesAllowances in line 106,column 25
AllowChrgAmt
- XPath: /Invoice/LineItem/ChargesAllowances/AllowChrgAmt
What does that mean?

A - There’s a Charges Allowances Code A260 attached to the line item. See attached screen below. 


A260 means “Costs related to advertising goods and company brand.” So it seems you have a 1% advertising allowance for this line item. The error message is questioning why there is no allowance amount on the invoice even though there is an allowance code on the invoice (line item). 

If the 1% advertising allowance is not valid, you can delete the _CHRGALLOW01 attribute from the invoice line item (go to Invoice Inquiry for invoice# 708241, use the up arrow key to highlight the line item, bring up the attribute list and delete it) and re-export the invoice again. If it is valid, then you will have to handle this invoice manually through the SPS web form portal. We don’t have a way to handle EDI allowances in Elliott. Allowance is a known issue during sales order import.

The other option is to choose whether the _CHRGALLOW attribute information is exported on a customer by customer basis. This is configured through the Customer EDI Profile Maintenance-> Screen 7-> Field 12. Export CHRGALLOW Attribute. See https://support.netcellent.com/portal/en/kb/articles/feature-optionally-export-chrgallow-attribute-data for more information.

Even if it the 1% advertising allowance is valid, you can still delete this line item attribute and re-export or choose not to export the data. Then at least we will pass SPS checking. What will happen with your trading partner at that point is unknown. They may reject this invoice, which means you will have to handle the invoice through the SPS web form portal, or they may accept the invoice and pay you 1% less anyway. We are not sure what will happen, but it is interesting to explore this direction to give you a guideline on how to handle EDI allowances from trading partners in the future.  


EMK


    • Related Articles

    • DN API (Document Number Handling)

      Release: 1/11/2021 Version: V8.5 and higher DN API: Document Number Increase, Roll Back or Validate In Elliott V8.5, the system supports alphabetic document numbers. The logic to sequentially assigning the next document number is complicated. For ...

    • Btrieve Error 80 In Deferred Processing

      Q - In Deferred Processing, we encounter the following error: Btrieve Error 080 on Order Header File This has been happening for the last 30 days off and on. What might cause this to happen? A - This is what Btrieve Error 80 means based on PSQL ...

    • Alpha Document Number Support (V8.5/V9.0)

      V8.5/V9.0 offers support for alpha numeric document numbers. This gives the user more flexibility on the number of alphabetic characters in next document number. For example, in the scenario of the following “Starting Invoice Number” in A/R Setup: ...

    • Credit Card Processing Error: Chk Viawarp For Dupl

      Q - In A/R -> Processing -> Credit Card Trx Handle, at field "21. Approval No," I press F4 to interface with the credit card payment gateway server, then I receive the message "Credit: AP Error: Chk Viawarp For Dupl." See examples below: When I go to ...

    • Btrieve Error Codes 001 - 199

      MicroKernel (Btrieve) Database Engine Status Codes This section describes status codes that the MicroKernel returns. All status codes are provided in 3-digit formats since the search on this website cannot search 1 or 2-digit words correctly. That is ...