Ford Motor Company X12 860 Purchase Order Change Request
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.
The Version Code is used in conjunction with the Functional Identifier to specify an exact version of an EBDI standard. Format of the version is: Positions Content. 1 - 3 Major Version Number. 4 - 6 Release Level of Version. 7 - 12 Industry or Trade Assoc. 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 (Order Change Request)
To indicate the beginning of the purchase order change request transaction set and transmit identifying numbers and dates.
Code identifying purpose of transmitted set.
Code specifying the type of Purchase Order or Change to Purchase Order.
Identifying number for Purchase Order assigned by the orderer/purchaser.
Date assigned by the purchaser to Purchase Order.
Date assigned by the sender to the acknowledgment.
Date of the purchase order change request.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Code identifying the functional area or purpose for which the note applies. Also see: Free Form Message (3).
Free-form text.
Loop: POC_loop
Line Item Change
To specify changes to a line item
Identifying number or code for a purchase order line item.
Code specifying the type of change to the line item.
Quantity ordered.
Quantity left to receive as qualified by the unit of measure.
Code identifying the basic unit measurement.
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
Identifying number for a product or service.
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.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning and ending (SE) segment)
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.)