As part of Demand Management processing, order transactions are automatically generated by (or manually created in) the Epicor application from inbound EDI demand. The resulting order transactions can be viewed or edited in Sales Order Entry.
These order transactions consist of records in the following main database tables:
• OrderHed - Contains order header information that can be viewed or edited in the Header or Summary sheets. When an order is generated from demand entries, this information is based on the data contained in the DemandHead table record, which itself is generated from the Demand Header row on the inbound EDI transaction.
• OrderDtl - Contains order line detail information that can be viewed or edited in the Lines sheet. When an order is generated from demand entries, this information is based on the data contained in the DemandDetail table record, which itself is generated from Demand Detail rows on the inbound EDI transaction.
• OrderRel - Contains order release information that can be viewed or edited in the Releases sheet. When an order is generated from demand entries, this information is based on the data contained in the DemandSchedule table record, which itself is generated from Demand Schedule rows on the inbound EDI transaction.
• Firm or unfirmed order releases are created, depending on the demand type (FIRM or UNFIRM) associated with the transaction type stored in Data Position 5 on the Demand Header row in the inbound EDI transaction.
• This status is indicated by the Not Firm or Firm Release indicators in the Releases sheet.
Tip The Epicor application also generates unfirm order releases if a Material Requirements Planning license is not installed and you process an inbound EDI transaction that contains a transaction type associated with a FORECAST demand type. If you have an installed Material Requirements Planning license, the Epicor application generates a normal forecast transaction that can be viewed in Forecast Entry. Refer to Forecast Transaction Generated from Inbound EDI Demand for more details.
The precise timing and method used by the Epicor application to generate an order transaction from inbound demand is dependent on the setting of the Accept Type field in the Customer Maintenance > Documents or Ship To > Documents sheet for the customer (or ship to customer) trading partner associated with the inbound EDI transaction. The Accept Type field specifies if inbound EDI documents should automatically be accepted or rejected for this customer trading partner:
• If set to Always Accept, the Epicor application automatically processes demand for this customer trading partner, regardless of whether there are errors in the inbound EDI document.
• When Service Connect runs the EDI workflow, the DemandEntry Process Demand WebService step (in the Main_DemandHead Update workflow) automatically creates demand entries in the Epicor application and immediately generates sales order and forecast entries at the time the inbound EDI file is successfully processed by Service Connect. This eliminates the need to manually use the Process selection in the Demand Header section of the Demand Entry Actions menu to process the demand. • In cases where the inbound EDI transaction does contain errors (for example, a Date Change action
request is received with insufficient lead time, and a Stop or Warning condition would normally be applied), the Epicor application automatically overrides any System Rejection flags, processes the demand and subsequent sales order and forecast entries despite the error condition.
• If set to Accept If No Errors, the DemandEntry Process Demand WebService step (in the
Main_DemandHead Update workflow) automatically processes demand and immediately generates sales order and forecast entries for this trading partner only if there are no errors in the inbound EDI document. This eliminates the need to manually use the Process selection in the Demand Header section of the Demand Entry Actions menu to process the demand.
• In cases where the inbound EDI transaction does contain errors (for example, a Date Change action request is received with insufficient lead time), the Epicor application handles it in the normal manner- it applies
Stop (with System Rejection) or Warning conditions, depending on the settings for the customer trading partner in the Customer Maintenance > Customer > Demand or Ship To > Demand sheets.
• It does not immediately generate sales order and forecast entries in these situations.
• Manually Accept - Demand from this incoming document for this ship to customer trading partner should only be manually processed.
• In this case, Service Connect creates demand entries but you must manually process them using the Process
selection of the Demand Header section in the Demand Entry Actions menu.
• It only creates order releases at the time you do this manual processing. Refer to the Application Help for more details.
Programs and Their Modifiers
These are the values you can modify for the item:
• Hold- When selected, this check box indicates that this order is currently not in process and will not be displayed on various reports. The Hold indicator appears as green if the order is manually placed on hold. • A Hold Order by Demand indicator appears next to the Hold indicator if the order has been generated
from a demand contract in Demand Entry and the Hold Orders for Review check box has been selected for the demand contract in the Demand Contract Entry Header or Summary sheets. This indicator does not appear for orders that are manually placed on hold.
Tip If the Allow Shipments for Orders on Hold check box has been cleared for this company in the Company Configuration > Modules > Materials > Shipping/Receiving sheet, this prevents processing of shipments for sales orders that have been placed on hold. This affects shipment programs such as Customer Shipment Entry and Master Pack Shipment Entry throughout the Epicor application. Sales order holds must first be removed in order to process shipments.