Epicor Eclipse Validations Sales Order Automation (SOA) Accounts Payable (AP)

Epicor Eclipse SOA and AP validations. Includes standard, custom, and cross-reference validations.

SOA Validations

AP Validations

Epicor Eclipse SOA Validations

Validations specific to Epicor Eclipse sales order automation (SOA).

Header

Customer ID

The numeric identification of that customer or vendor.

Using company name, street, postal code, the system matches the document's customer ID to the ERP.

Document Number

PO Number or other specified document number.

The system retrieves the PO Number as document ID.                            

Mandatory Value

 

The system checks for one or more given fields that are designated as mandatory.

Ship To

The system matches the document’s ship-to address information to the ERP’s.

Line Items        

Due Date

The system evaluates whether it is mapped and that the date lies at 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.

Minimum Order Quantity (MOQ)

Minimum amount allowed to be ordered.

The system validates that quantity is greater than or equal to minimum order quantity

Part Number

The system retrieves the Product ID using the Customer Number and the Part Number. 

Product Availability

The system matches the item’s part number to the ERP’s part number and then matches its quantity against a previous record of availability in part-number inventory.

Unit of Measure (UOM)

The system matches the document’s Part Number to the ERP’s Part Number and matches the document’s unit of measure (UOM) with 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.

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. 

______________________________________________________________________________________

______________________________________________________________________________________

Epicor Eclipse AP Validations

Validations specific to Epicor Eclipse 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

The system retrieves the PO Type from the ERP to display 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.

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 Item

Line Count

Validate unique lines against ERP’s lines.

Extended Part Number Validation

Validate the part numbers extracted off an AP invoice against the part numbers found on the matching Purchase Order.

Mandatory Value

The system validates that the fields defined in the Mandatory Fields lookup table are not empty.

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.

Product Availability

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.

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.

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.