Ford Motor Company X12 870 Order Status Report
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. Codes agreed to by trading partners.
Code identifying party receiving transmission. Codes agreed to by trading partners.
Date sender generated a functional group of transaction sets.
Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).
Assigned number originated and maintained by the sender.
Code used in conjunction with Data Element 480 to identify the issuer of the standard.
Code indicating the version, release, subrelease and industry identifier of the EDI standard being used. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (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.
Beginning Segment for Order Status Report
To indicate the beginning of an Order Status Report.
Code indicating the reason for sending the report
Code identifying a group of orders and items.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Date (YYMMDD).
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: HL_loop
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
Code defining the characteristic of a level in a hierarchical structure.
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser.
Date assigned by the purchaser to Purchase Order.
Reference Numbers
To specify 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.
Loop: PO1_loop
Purchase Order Baseline Item Data
To specify basic and most frequently used purchase order line item data
Alphanumeric characters assigned for differentiation within a transaction set.
Quantity ordered.
Code identifying the basic unit of measurement.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
Identifying number for a product or service.
Loop: ISR_loop
Item Status Report
To specify detailed purchase order/item status.
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction.
Date (YYMMDD).
Quantity
To specify quantity information.
Code specifying the type of quantity.
Numeric value of quantity.
Code identifying the basic unit of measurement.
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 specified 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 left most 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.