SX API errors

If an SX.API error record is generated during the SX.API Full Order Maintenance process, an order is created in the system. The document record status is processed. The stage of the sales order is Stage 1-Ordered, and the approval of the sales order is e. You must make changes before the order processes through credit hold checking and is ready to be picked. An error can be an header or line level error, depending on which piece of data is in question.

Note: If your company uses e as a custom approval code, change the custom approval code. A delay can occur if changes were to SA Administrator Options settings that affect the SX.API process. Signing out of and back into Distribution SX.e does not activate the change for SX.API. Changes reset either when the SX.API appserver is used to process an SX.API call for another company, or when the SX.API server is bounced.

Header-level error messages


Error message	Cause	Action
`Terms Type Not Set Up in System Table – SASTT (4031H)`	The customer is set to allow terms from flat file and the terms received are not defined in SA Table Code Value Setup.	Either create the SA Table Code Value Setup record or update the order with a valid SA Table Code Value Setup term. This error setting is automatically removed when the order is finished.
`Ship To # is Required (5690H)`	Customer record requires a ship to and a ship to was not sent. Optionally, the ship to name and address does not correlate to a valid ship to.	The order is created using the first ship to that has a status of Active and the Job Close Date is greater than today or is not defined. If ship to records are not available, then a default ship to record is created for the customer. The ship to is called default and uses the address information received from the inbound transaction. The order is set to taxable. The state code received or the customer taxable state code is used. The default value of xx may also be used. The order is put on E Hold. You can copy the order to the correct ship to order Copy function in Sales Order Entry. Ensure that you copy the EDI data. The copy function automatically corrects the error when the order is finished. Delete the default shipto record and set up the ship to received in the transaction so this does not occur again.
`Non-Stock Creation Not Allowed – Number of Invalid Products Is NNN (7119H)`	The nonstocks are not allowed abased on the customer or ship to record, or business rules, and the product number cannot be validated in Product Warehouse Product Setup.	The line item is not created, but the product information is stored on a note. You can view the note from Sales Order Entry or from the View Errors and Exceptions window. The order is on E Hold until you review the notes.
`Warning: Kit and Tally Products Not Allowed – Product Count is NNN (8765H)`	Kit and tally products are not allowed using the SX.API Full Order Maintenance process.	If a kit or tally is received, line items are not be created. The basic information is found in header notes and the order is placed on E Hold. You must manually approve the order to get it off E Hold.
`Warning: Default Customer Number Used (8766H)`	Customer record was missing and cannot be validated by the trading partner code, customer number, or customer name.	An order is created with the default miscellaneous customer defined in a business rule. Copy the order to the correct customer number and ensure the setting in the order Copy function is set to copy EDI data. If the default customer number is correct, manually correct the order.
`Product Restriction(s) Found on Sales Line (6943)`	Based on Product Restriction Setup records, the line contains a restricted product that is not allowed.	The line is not included on the order. The line data, which includes the product, quantity ordered, and the product restriction, is stored as an Order Global note. To override the restriction or send the line to lost business, use this information to add the line to the order in Sales Order Entry. You can add the restricted product to the order before or after approving the order. To exclude the restricted product from the order, click Approve Exceptions to approve the order. You are not required to address the restricted product errors.

Line-level error messages


Error message	Cause	Action
`Units Not Set Up in Unit Table – ICSEU or SASTT (4026L)`	The unit of measure received does not exist Product Extended Unit Conversion Setup or SA Table Code Value Setup. The line is created with the EDI unit in the unit field on the sales order line.	Correct the unit of measure. This error setting is automatically removed when the order is finished.
`This is a “Do Not Reorder” Product (5603L)`	Incoming product has a Product Warehouse Product Setup status of Do Not Reorder	The line contains a supersede error, and the order is placed on E Hold. You must select a valid supersede. The order is checked by auto-validation logic, and the error is cleared after the line is selected and dropped. You can then ship the same product number. This error does not occur if an Order processing rules within SXAPI business rule with an attribute value of skipdnrehold is active.
`Non Tax Reason Missing (6330L)`	Non taxable reason is not in Customer Setup.	You must update Customer Setup with a valid nontaxable reason or make the order taxable.
`This is an “Inactive” Product (6348L)`	Incoming product has a Product Setup status of inactive.	The product is created as a non-stock product. You must manually review the quantity shipped versus the quantity ordered.
`Direct Ship Only Product – Non-Stock Created (7117L)`	Incoming product has a Product Setup status of direct ship only.	This product is created as a nonstock with the original product number designated. Change the product and define the additional sources information to create a direct ship PO.
`Supercede Product (8613L)`	Incoming product has a Product Setup status of supersede.	The line contains a supersede error, and the order is placed on E Hold. You must select a valid supersede. The order is checked by auto-validation logic, and the error is cleared after the line is selected and dropped. You can then ship the same product number. This error does not occur if an Order processing rules within SXAPI business rule with an attribute value of skipsuperehold is active.