Table Schematic for Demand_Header Row Sample
DALTON-CONTRACT
7
• The value that appears in this data position must be a valid demand contract number, previously entered into Demand Contract Entry in the Epicor application.
• Refer to Entering Demand Contracts for more details.
Identification number for the customer number associated with the EDI record.
Mandatory, Character CustID
DALTON
8
• The value that appears in this data position must be a valid customer identification number, previously established in Customer Maintenance in the Epicor application.
• Refer to Defining Trading Partners in Customer Maintenance for more details.
Sample Record Data Element Description Type Plug-in Field or Dictionary Name Example Record Data Value Row Data Position
Identification number for the bill to customer number associated with the EDI record. Optional, Character BTCustNum No Value in Example 9
• If a value appears in this data position, it must be a valid bill to customer identification number, previously established in Customer Maintenance in the Epicor application. If a value exists in this field, it should exist as an alternate bill to number that is defined for the customer. Refer to Defining Trading Partners in Customer Maintenance for more details. • If left blank, the default is the sold to
customer in Field #8.
Identification number for the customer purchase order associated with the demand contract. It Mandatory,
Character PONum
E100500-51
10
denotes the purchase order number your trading partner is using to purchase the demand items from your company.
• For changes, the value that appears in this data position must be a valid purchase order number associated with the demand contract number, as previously entered into Demand Contract Entry in the Epicor application.
• Refer to Entering Demand Contracts for more details.
Tip The concatenated demand contract number and customer purchase order number together form a primary key in the Epicor application for resulting demand entry records.
Ship to customer identification number. If blank, the default is the sold to customer for the trading partner. Optional, Character ShipToCustID No Value in Example 11
Indicates the ShipTo code for shipments generated from this record.
Optional, Character Ship_Code
P1
12
• This should not be left blank; the value in this position must exist in the ShipTo table for the sold to customer in the Epicor application.
• The <blank> ship to references the main customer address. This does not default to the ship to code at the releases.
Sample Record Data Element Description Type Plug-in Field or Dictionary Name Example Record Data Value Row Data Position
Denotes if a One Time Ship (OTS) address is being used. Optional, Boolean UseOTS false 13
Earliest date before which the order cannot be shipped. Purchased items should not be shipped Optional, Date DNS_Before No Value in Example 14
prior to this date. This information is used in the Demand Entry > Header sheet.
Latest date after which the order cannot be shipped. Purchased items should not be shipped Optional, Date DNS_After No Value in Example 15
after to this date. This information is used in the Demand Entry > Header sheet.
Latest date by which your trading partner wishes the associated purchased items to be Optional, Date CancelAfterDate No Value in Example 16
shipped to prevent cancellation. Items that cannot be shipped prior to this date should be cancelled.
Indicates the Free On Board (FOB) point for shipments generated from this record. Optional, Character FOB No Value in Example 17
• Can be left blank, but if there is a value, it must exist in the FOB table in the Epicor application.
• If left blank, the default value for transactions generated from this record come from the demand contract in the Epicor application.
Indicates the ship via method for shipments generated from this record.
Optional, Character Ship_Via
BEST
18
• Can be left blank, but if there is a value, it must exist in the ShipVia table in the Epicor application.
• If left blank, the default value for transactions generated from this record come from the demand contract in the Epicor application.
Indicates the sales terms for orders generated from this record.
Optional, Character Terms_Code No Value in Example 19
• Can be left blank, but if there is a value, it must exist in the Terms table in the Epicor application.
• If left blank, the default value for transactions generated from this record
Sample Record Data Element Description Type Plug-in Field or Dictionary Name Example Record Data Value Row Data Position
come from the demand contract in the Epicor application.
Indicates the allocation priority for orders generated from this record.
Optional, Character Priority_Code No Value in Example 20
• Can be left blank, but if there is a value, it must exist in the AllocationPriority table in the Epicor application.
• If left blank, the default value for transactions generated from this record come from the demand contract in the Epicor application.
Indicates if orders generated from this record must be shipped complete. As an order release Optional,
Boolean Ship_Complete
false
21
is selected for picking during the Auto Pick process in the Order Allocation program, all releases with a ship date less than or equal to the given cutoff date also have to be picked complete otherwise they will not be selected. • The default is true when the
Customer.ShippingQualifier is set to 0 (Ship Order 100% complete).
• If left blank, the default value for transactions generated from this record come from the demand contract in the Epicor application.
Contains comments for the overall order. Optional,
Character Order_Comment
Ord Comm
22
These comments print on sales
acknowledgments, and also appear on the Order Comments sheets in Demand Entry and Sales Order Entry after the Epicor application generates demand entries and orders.
Contains invoice comments for the overall order. The Epicor application copies them into the Invoice Detail table as defaults.
Optional, Character Invoice_Comment
Inv Comm
23
These comments appear on the Invoice Comments sheets in Demand Entry and Sales Order Entry after the Epicor application generates demand entries and invoices.
Indicates if order based discounting should be applied automatically or manually triggered by the user as a menu option.
Optional, Boolean Order_Discount
false
Sample Record Data Element Description Type Plug-in Field or Dictionary Name Example Record Data Value Row Data Position
If left blank, the default value comes from the demand contract in the Epicor application.
Indicates if this row is being run in a test mode. Optional,
Boolean Test_Record
false
25
Indicates the purchase order type. Optional, Character PO_Type No Value in Example 26
Type of acknowledgement expected by the trading partner. Optional, Character Ack_Type No Value in Example 27
Type of acceptance expected by the trading partner. Valid types are as follows:
Optional, Character Accept_Type No Value in Example 28
• Manual - The Epicor application or Service Connect creates demand entries but you must manually process them using the Process selection in the Demand Header section in the Demand Entry Actions menu. Order releases and forecast entries are only created at the time you perform this manual processing.
• Accept if no Errors - The Epicor application should automatically process demand for this customer 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.
• Always Accept - The Epicor application should automatically process demand for this customer trading partner, regardless of whether there are errors in the inbound EDI document. This 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.
This is an override value for the Accept Type
field setting specified for the trading partner in the Customer Maintenance > Document sheet.
Indicates if your customer trading partner would like to reset the cumulative quantities stored Optional,
Boolean ResetCums
false
29
to-date for previous transactions related to this demand record.
If set to true, the Epicor application resets these cumulative quantities.
Sample Record Data Element Description Type Plug-in Field or Dictionary Name Example Record Data Value Row Data Position
Indicates if the resulting invoice for this demand record should be flagged as an Evaluated Receipt Settlement invoice.
Optional, Boolean ERSOrder
false
30
Indicates if the customer purchase order for this demand record should be cancelled.
Optional, Boolean CancelPO
false
31
Transaction control number for the EDI message on which the demand was received. Used to track the document in the EDI processor. Optional,
Character TCtrl_Number
1
32
Batch control number for the EDI message on which the demand was received. Used to track the document in the EDI processor.
Optional, Character Batch_Number
1
33
Used as an EDI Reference of the inbound demand. This value is used as the default schedule at the schedules.
Optional, Character Sched_Nbr
13-03
34
Indicates the currency code for orders and invoices generated from this record. Optional, Character Cur_Code No Value in Example 35
• Can be left blank, but if there is a value, it must exist in the Currency table in the Epicor application.
• If left blank, the default value for transactions generated from this record come from the demand contract in the Epicor application.
Used with the Currency module. When set to true, the currency rate can be changed by the Optional,
Boolean Lock_Rate
false
36
user and cannot be changed by the Epicor application.
OTS customer name. Optional, Character OTSName No Value in Example 37
Note If UseOTS (Data Position 13) is set to true, this is a mandatory entry.
First address line of the OTS drop ship mailing address. Optional, Character OTSAddress1 No Value in Example 38
Second address line of the OTS drop ship mailing address. Optional, Character OTSAddress2 No Value in Example 39
Third address line of the OTS drop ship mailing address. Optional, Character OTSAddress3 No Value in Example 40
Sample Record Data Element Description Type Plug-in Field or Dictionary Name Example Record Data Value Row Data Position
City for the OTS drop ship mailing address. Optional, Character OTSCity No Value in Example 41
Resale identification number (if any) for the OTS drop ship mailing address.
Optional, Character OTSResaleID No Value in Example 42
State or province name for the OTS drop ship mailing address. Optional, Character OTSState No Value in Example 43
Zip or postal code for the OTS drop ship mailing address. Optional, Character OTSZip No Value in Example 44
Country portion of the OTS drop ship mailing address. Optional, Character OTSCountry No Value in Example 45
Note If UseOTS (Data Position 13) is set to true, this is a mandatory entry.
OTS fax number. Optional, Character OTSFaxNum No Value in Example 46
OTS telephone number. Optional, Character OTSPhoneNum No Value in Example 47
OTS contact name. Optional, Character OTSContact No Value in Example 48
OTS ship to customer identifier. Optional,
Character OTSSaveCustID
blank
49
Denotes the type of record in which OTS information is being saved in the Epicor application. Optional, Character OTSSaveAs blank 50
• blank (no value) - No saved OTS information
• C - Saved in Customer record • P- Saved in Prospect record • S- Saved in Suspect record • T- Saved in Ship To record
Fields reserved for EDI custom development. Optional, Character EDI_Custom1 Custom1 Custom10 51 - 60