Sage X3 SOA validations and delivery. Includes standard, custom, and cross-reference validations.
SOA Validations
Validations specific to Sage X3 sales order automation (SOA).
Header
Bill To ID |
Address to which the product will be billed. The system matches the document’s bill-to address information to the ERP’s, by first retrieving the location ID. |
Customer ID Number (Vendor ID Number) |
The numeric identification of that customer or vendor. The system matches the Customer ID or Vendor ID with the ERP’s record. |
Document Number |
PO Number or other specified document number. The system retrieves the PO Number as document ID. |
Mandatory Value |
A required value specified by the customer. The system checks for one or more given fields that are designated as mandatory. |
Payment Terms |
The terms by which the payment will be made. For example, “Net 30.” The system matches the document's payment terms with the ERP’s. |
Sales Area |
The system retrieves the matching ERP values. It returns a list of both document and ERP values for use in subsequent processes. Endpoint: API_PRODUCT_SRV/A_Product?$filter=Product eq '<id>'&$expand=to_Valuation |
Ship To |
Address to which the product will be delivered. The system matches the document’s ship-to address information to the ERP’s, simply or by first retrieving the ship-to ID. Possible ERP Fields used: Company Name, City, Street, Postal Code, Country, Ship To Id. |
Line Items
Due Date |
The system evaluates whether it is mapped and that the date lies in the future. |
Get Line-Item Data |
The system retrieves line-item information for subsequent validations. Will return a list of line items the includes both document values that subsequent processes can consume. |
Minimum Order Quantity (MOQ) |
Minimum amount allowed to be ordered. The system matches the document's MOQ with the ERP’s. |
Order Quantity |
Number of items in an order. The system validates the document’s order quantity with the given ERP quantity. |
PO Line Number |
Checks for PO line number. When successful, the system displays the PO line number in Exception Manager. It will be the PO line to run any line validations against. |
Part Number |
From internal and external Stock Keeping Units (SKUs). The system compares document’s part numbers to the ERP’s part-numbers. |
Product Availability |
Determines whether the product is in inventory. The system matches the item’s part number to the ERP’s part number. It then matches its quantity against a previous record of availability in part-number inventory. |
Product Category |
Using part numbers, the system retrieves the product category from the ERP. |
|
|
Unit of Measure (UOM) |
To validate a UOM, such as “package” or “Dozen,” the system matches the document’s part number to the ERP’s part number. It then matches the document’s UOM to the ERP’s UOM. |
Footer
Freight Tolerance |
Freight carrier and associated information. (Example: FedEx or UPS; Air or Five-day ground; weight and quantity). Evaluates documents for whether freight information is available and quantities accurate within the given tolerance. |
Tax |
Availability of information: tax appropriate for sale. Evaluates documents for whether federal or state tax information is available. |
Total Validation |
The sum of prices listed as line-items, less applied discounts. Evaluates whether the mapped total matches the calculated total within a set tolerance. |
______________________________________________________________________________________