FourKites X12 990 Response to a Load Tender
FourKites
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
transactionSets
Loop: transactionSets
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Code identifying a Transaction Set
Beginning Segment for Booking or Pickup/Delivery
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Code identifying action on reservation or offering
Code identifying the Standard Carrier Alpha Code
Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code identifying the Reference Identification
Date/Time
To specify pertinent dates and times
Code specifying type of date
Charge Detail
To specify special charge code and the associated monetary amount
Monetary amount
Code identifying type of special charge or allowance
Remarks
To transmit information in a free-form format for comment or special instruction
Free-form information
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 that must be unique within the transaction set functional group assigned by the originator for a transaction set
functionalGroupHeader
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Code identifying a group of application related transaction sets
Code indicating the version, release, and industry identifier of the EDI Standard being used, including the GS and GE segments; if the code in DE455 in the GS segment is X, then DE 480 positions 1-3 are the version number; positions 4-6 are the release level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if the code in DE455 in the GS segment is T, other formats are allowed.
interchangeControlHeader
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Date of the interchange
Time of the interchange
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 value in the sender ID element
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
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
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
A control number assigned by the interchange sender
Type is not applicable; the component data element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
Code indicating sender's request for an interchange acknowledgment
Code identifying the type of information in the Security Information
Code indicating whether data enclosed by this interchange envelope is test, production or information
Code identifying the type of information in the Authorization Information
Code specifying the version number of the interchange control segments, the version of the data elements within the control segments, and the code values within those data elements.
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer