Ford Motor Company X12 862 Shipping Schedule
Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)
3 schema elements found
This Draft Standard schema for Trial Use contains the format and data contents of the schema for use within the context of an Electronic Data Interchange (EDI) environment.
Navigation
3 total elements
ISA
Interchange Control Header
To start and identify an interchange of one or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information.
Information used for additional identification or authorization of the sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.
Code to identify the type of information in the Security Information.
This is used for identifying the security information about the sender or the data in the interchange. The type of information is set by the Security Information Qualifier.
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.
Identification code published by the sender for other parties to use as the receiver ID to route data to them. The sender always codes this number in the sender ID element.
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.
Identification code published by the receiver of the data. When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them.
Date of the interchange.
Time of the interchange.
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer.
This version number covers the interchange control segments.
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
Code sent by the sender to request an interchange acknowledgment.
Code to indicate whether data enclosed by this interchange envelope is test or production.
This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).
GS
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related Transaction Sets.
Code identifying party sending transmission.
Code identifying party receiving transmission.
Date sender generated a functional group of transaction sets.
Time (HHMM) expressed in 24-hour clock time when the sender generated a functional group of transaction sets (local time at sender's location). (Time range: 0000 through 2359.)
Assigned number originated and maintained by the sender.
Code used in conjunction with the version data element to identify the issuer of the standard.
Code indicating the version, release, and industry ID of the EDI standard being used. Positions: 1 - 3, Major Version Number; Positions: 4 - 6, Release Level of Version; Positions: 7 - 12, Industry or Trade Association ID (Optionally assigned by user).
transactionSets
Loop: transactionSets
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set.
Identifying control number assigned by the originator for a Transaction Set. Also see: Data Interchange Control Number (28.)
Beginning Segment for Shipping Schedule
To indicate the beginning of a shipping schedule.
Code identifying purpose of transaction set.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Code which qualifies the type of dates used in the forecast.
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Code which qualifies the types of quantities.
Loop: N1_loop
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity or a physical location.
Code designating the system/method of code structure used for Identification Code (67).
Code identifying a party.
Loop: LIN_loop
Item Identification Detail
To specify basic item identification data.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
Identifying number for a product or service.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
Identifying number for a product or service.
Unit Detail
To specify item unit data.
Code identifying the basic unit measurement.
Reference Numbers
To transmit identifying numbers.
Code qualifying the Reference Number.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named.
Free form name.
Code identifying the type of communication number.
Complete communications number including country or area code when applicable. Also see: Communications Number Qualifier (365).
Loop: FST_loop
Forecast Schedule
To specify the forecasted dates and quantities
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Code specifying the sender's confidence level of the forecast data.
Code specifying interval grouping of the forecast.
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Code specifying type of date or time, or both date and time.
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359). Also see: Time Qualifier (176).
Loop: JIT_loop
Just-In-Time Schedule
To identify the specific shipping/delivery time in terms of a 24-hour clock and the associated quantity.
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359). Also see: Time Qualifier (176).
Loop: SHP_loop
Shipped/Received Information
To specify shipment and/or receipt information
Code specifying the type of quantity.
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Code specifying type of date or time, or both date and time.
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Reference Numbers
To transmit identifying numbers.
Code qualifying the Reference Number.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight and quantity.
Code identifying the type of packaging. Part 1. Packaging form. Part 2. Packaging Material.
Number of units (pieces) of the lading commodity. Also see: Unit of Measurement Code (355.)
Code defining the type of weight.
Numeric value of weight. Also see: Weight Qualifier (187), Weight Unit Qualifier (188), Unit of Measurement Code (355.)
Code identifying the basic unit measurement.
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier.
Code identifying type of equipment used for shipment.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred).
Transaction Totals
To transmit a hash total for a specific element in the transaction set
Total number of line items in the transaction set.
Sum of values of the specific data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the leftmost digits if the sum is greater than the maximum size of the hash total of the data element. Example: -.0018 First occurrence of value being hashed. .18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence of value being hashed. ------. 1855 Hash total prior to truncation. 855 Hash total after truncation to three digit field.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments, including the beginning (ST) and ending (SE) segments.
Total number of segments included in a transaction set including ST and SE segments.
Identifying control number assigned by the originator for a Transaction Set. Also see: Data Interchange Control Number (28.)