Epicor Prophet 21 SOA, AP, and OA validations. Epicor Prophet 21 SOA, and AP deliveries. Includes standard, custom, and cross-reference validations.
______________________________________________________________________________________Epicor Prophet 21 SOA Validations
Validations specific to Epicor Prophet 21 sales order automation (SOA).
Header
|
Address ID by Connection Name |
The system retrieves the address from the cache. If cache doesn’t exist, it retrieves the address from the ERP. |
|
Contact ID Lookup
|
If contact details are mapped on the document, then an API or cross-reference lookup uses the Contact Email Address or Contact name to retrieve the associated contact ID. If contact details are not mapped on the document, the system sets a default contact value from a cross-reference table. |
|
Contract ID Validation |
The system associates contract numbers with items on PO, which is required for Contract Pricing to be populated within the ERP when a sales order is created. |
|
Customer ID (Vendor ID) |
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 Location ID |
If Sales Rep ID is not present, the system retrieves the Sales Rep ID from the ERP. |
|
Ship To ID |
Address to which the product will be delivered. The system compares the mapped Ship To Street Number and Postal Code with the available Ship To Physical Address in the ERP for the Customer ID and the Company ID. It then returns the appropriate 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. It then returns a list of line items the includes both document values and ERP values for comparison. Subsequent processes can consume these lists. |
|
Item 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. |
|
Minimum Order Quantity (MOQ) |
Minimum amount allowed to be ordered. The system validates that quantity is greater than or equal to minimum order quantity. |
|
Order Quantity |
Number of items in an order. The system validates the document’s order quantity with the given ERP quantity. |
|
Part Number |
From internal and external Stock Keeping Units (SKUs). The system compares document’s part numbers to the ERP’s part numbers. |
|
Part Number by Connection Name |
Retrieves part number from cache. If cache doesn’t exist, get it from ERP. |
|
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. |
|
Unit of Measure (UOM) |
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. |
|
Unit Price |
The price of an individual unit as described by the UOM. The system compares the document's unit price to the ERP unit price for a given tolerance level. |
|
Validate Quote |
The system matches PO line to quote line in ERP using the part number and quantity (if necessary). Then it validates Quantity, UOM, and Unit Price against each quote line. |
Footer
|
Freight Tolerance Validation |
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, Alert on |
Availability of information: tax appropriate for sale. Evaluates documents for whether federal or state tax information is available. |
|
Total |
The sum of prices listed as line-items, less applied discounts. Evaluates whether the mapped total matches the calculated total within a set tolerance. |
______________________________________________________________________________________
______________________________________________________________________________________
Epicor Prophet 21 AP Validations
Validations specific to Epicor Prophet 21 Accounts Payable (AP).
Header
|
Customer ID |
The numeric identification of that customer or vendor. Using a cross-reference table, the system matches the ERP to determine if the document's customer ID is valid. |
|
Direct Ship (Drop Ship) |
The system obtains PO Type from Invoice and displays it in Exception Manager. |
|
Due Date |
Date that product or service is due or requested delivery date. The system evaluates whether the date is mapped and that the date lies in the future. |
|
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. |
|
PO Number |
The system matches the PO number with the ERP. |
|
Sales Location ID |
If Sales Rep ID is not present, the system retrieves it from the ERP. |
|
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
|
Line Count |
Validate unique lines against ERP’s lines. |
|
Item 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. |
|
Order Quantity |
The system matches the document’s part number and order quantity with the ERP’s. |
|
Part Number |
From internal and external Stock Keeping Units (SKUs). The system compares document’s part numbers to the ERP’s part-numbers. |
|
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. |
|
Unit Price |
The system compares the document's unit price to the ERP unit price information for a given tolerance level. |
|
UOM Quantity Price Conversion |
The system matches the ERP through the API, if available. Otherwise the system completes the process using cross-reference tables, converting the document's UOM to the PO's UOM. |
|
Unit of Measure (UOM) |
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. |
|
Unit Price |
The price of an individual unit as described by the UOM. The system compares the document's unit price to the ERP unit price for a given tolerance level. |
|
Validate Quote |
The system matches PO line to quote line in ERP using the part number and quantity (if necessary). Then it validates Quantity, UOM, and Unit Price against each quote line. |
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 |
The sum of prices listed as line-items, less applied discounts. Evaluates whether the mapped total matches the calculated total within a set tolerance. |
______________________________________________________________________________________
______________________________________________________________________________________
Epicor Prophet 21 OA Validations
Validations specific to Epicor Prophet 21 Vendor Order Acknowledgements (OA).
Header
|
Customer ID |
The numeric identification of that customer or vendor. Using a cross-reference table, the system matches the ERP to determine if the document's customer ID is valid. |
|
Direct Ship (Drop Ship) |
The system obtains PO Type from Invoice and displays it in Exception Manager. |
|
Due Date |
Date that product or service is due or requested delivery date. The system evaluates whether the date is mapped and that the date lies in the future. |
|
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. |
|
PO Number |
The system matches the PO number with the ERP. |
|
Sales Location ID |
If Sales Rep ID is not present, the system retrieves it from the ERP. |
|
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
|
Line Count |
Validate unique lines against ERP’s lines. |
|
Item 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. |
|
Order Quantity |
The system matches the document’s part number and order quantity with the ERP’s. |
|
Part Number |
From internal and external Stock Keeping Units (SKUs). The system compares document’s part numbers to the ERP’s part-numbers. |
|
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. |
|
Unit Price |
The system compares the document's unit price to the ERP unit price information for a given tolerance level. |
|
UOM Quantity Price Conversion |
The system matches the ERP through the API, if available. Otherwise the system completes the process using cross-reference tables, converting the document's UOM to the PO's UOM. |
|
Unit of Measure (UOM) |
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. |
|
Unit Price |
The price of an individual unit as described by the UOM. The system compares the document's unit price to the ERP unit price for a given tolerance level. |
|
Validate Quote |
The system matches PO line to quote line in ERP using the part number and quantity (if necessary). Then it validates Quantity, UOM, and Unit Price against each quote line. |
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 |
The sum of prices listed as line-items, less applied discounts. Evaluates whether the mapped total matches the calculated total within a set tolerance. |