Customer EDI Exception Settings

Customer demand is transmitted through several EDI documents:

  • 850 Purchase order - purchase order sent by the customer. You can also add a check on 850 purchase orders before they are added to sales order detail.

  • 860 PO change - change requests to the purchase order made by the customer.

  • 862 Shipping schedule - shipping schedule which contains firm demand listing part number, quantity and due date.

  • 866 Line sequence - line sequence information provided by the customer.

  • 830 Planning schedule - planning schedule which can transmits both firm and planned customer demand.

EDI 830 Document Codes

Code 0 - All incoming 830 documents are ignored:

  • Customer demand forecasting must be determined by an internal forecast

Code 1 - All firm and planned customer demand is loaded into OnRamp:

  • Firm demand is added to the customer sales order schedule

  • Planned demand is added to the customer forecast table

  • MRP cannot ship against customer forecast

Code 2 - There is no distinction between firm and planned demand:

  • All customer requirements are added to sales order schedule

  • MRP will not be able to show which demand is firm or planned

  • Shipments can be made against planned demand

Code 3 - Populates customer forecast tables with planned demand:

  • All firm demand is ignored

  • Firm demand must be loaded via EDI 862 or manually, which populates the Sales Order schedule

  • Sales Order schedule is used for shipping

Code 4 - Loads future planned demand into the customer forecast table:

  • Used to eliminate noise from past due data

  • Assumes that past due dates have been replaced by firm demand loaded elsewhere

Code 5 - Loads demand based on a raw material authorization (RMA) date supplied by the customer:

  • RMA date indicates customer approved RMA purchase

  • Important for parts with long lead times

  • Only loads firm and planned demand within RMA date

  • Demand is split between Sales Order schedule and customer forecast table

Sales Order Match Criteria

Set the sales order match criteria to have OnRamp add the demand to the correct sales order:

  • Must find PO and Part - Checks the sales order and only adds the EDI demand if the purchase order and part are found.

  • Must find PO, Part, and CustRev - Checks the sales order and only adds the EDI demand if the purchase order, part, and customer revision are found.

  • Must find Part and CustRev - Checks the sales order and only adds the EDI demand if the part and customer revision are found.

  • Must find Part - Checks the sales order and only adds the EDI demand if the part is found.

  • Find Part and Custom, no Auto Add - Checks the sales order and finds the part and customer but will not add demand items.

Full Refresh Type

  • None - The full refresh 830 is ignored by OnRamp.

  • Next Friday - Only demand after the next Friday is deleted and refreshed with the new schedule. Anything less than next Friday is untouched.

  • Use Lock - Deletes demand after the lock period and replace with the new schedule. Anything within the lock period is untouched. The lock period is set to Today plus the Schedule Lock Days.

  • No Lock - Deletes all demand and replace all with the new schedule regardless of schedule lock days. This is a true full refresh.

850 SO Match

Set the 850 EDI document sales order match criteria to have OnRamp add the demand to the correct sales order:

  • Match with PO, Ship To, and Part - Checks the sales order and only adds the EDI demand if the purchase order, ship to address, and part match.
  • Match with PO, Ship To, Part, and Rev - Checks the sales order and only adds the EDI demand if the purchase order, ship to address, part, and revision match.
  • Match with Part, Ship To, and Rev - Checks the sales order and only adds the EDI demand if the ship to address, part, and revision match.
  • Match with Part, Ship To - Checks the sales order and only adds the EDI demand if the ship to address and part match.

Price Check

Add a price check to validate before uploading any EDI data into OnRamp.

Schedule Lock Days

The number entered in the Schedule Lock Days field will determine for far back, or forward OnRamp will look at the dates when loading the demand.

If Schedule Lock Days is set to 0, then only demand with a due date of today or greater is loaded into OnRamp. To load demand with past due dates, enter a negative number in the schedule lock days. The demand with a date that is past due will load with a due date of today.