CPKC (formerly Kansas City Southern) X12 824 Application Advice

Kansas City Southern

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.

ISA

ISA

Interchange Control Header

MMax: 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

ISA01
Authorization Information Qualifier
MIDMIN 2 MAX 2ID: I01

Code identifying the type of information in the Authorization Information

ISA02
Authorization Information
MANMIN 10 MAX 10ID: I02

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)

ISA03
Security Information Qualifier
MIDMIN 2 MAX 2ID: I03

Code identifying the type of information in the Security Information

ISA04
Security Information
MANMIN 10 MAX 10ID: I04

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)

ISA05
Interchange ID Qualifier
MIDMIN 2 MAX 2ID: I05

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

ISA06
Interchange Sender ID
MANMIN 15 MAX 15ID: I06

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

ISA07
Interchange ID Qualifier
MIDMIN 2 MAX 2ID: I05

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

ISA08
Interchange Receiver ID
MANMIN 15 MAX 15ID: I07

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

ISA09
Interchange Date
MDTMIN 6 MAX 6ID: I08

Date of the interchange

ISA10
Interchange Time
MTMMIN 4 MAX 4ID: I09

Time of the interchange

ISA11
Repetition Separator
MMIN 1 MAX 1ID: I65

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

ISA12
Interchange Control Version Number Code
MIDMIN 5 MAX 5ID: I11

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.

ISA13
Interchange Control Number
MN0MIN 9 MAX 9ID: I12

A control number assigned by the interchange sender

ISA14
Acknowledgment Requested Code
MIDMIN 1 MAX 1ID: I13

Code indicating sender's request for an interchange acknowledgment

ISA15
Interchange Usage Indicator Code
MIDMIN 1 MAX 1ID: I14

Code indicating whether data enclosed by this interchange envelope is test, production or information

ISA16
Component Element Separator
MMIN 1 MAX 1ID: I15

Type is not applicable; the component 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

GS

GS

Functional Group Header

MMax: 1

To indicate the beginning of a functional group and to provide control information

GS01
Functional Identifier Code
MIDMIN 2 MAX 2ID: 479

Code identifying a group of application related transaction sets

GS02
Application Sender's Code
MANMIN 2 MAX 15ID: 142

Code identifying party sending transmission; codes agreed to by trading partners

GS03
Application Receiver's Code
MANMIN 2 MAX 15ID: 124

Code identifying party receiving transmission; codes agreed to by trading partners

GS04
Date
MDTMIN 8 MAX 8ID: 373

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

GS05
Time
MTMMIN 4 MAX 8ID: 337

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)

GS06
Group Control Number
MN0MIN 1 MAX 9ID: 28

Assigned number originated and maintained by the sender

GS07
Responsible Agency Code
MIDMIN 1 MAX 2ID: 455

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

GS08
Version / Release / Industry Identifier Code
MANMIN 1 MAX 12ID: 480

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

transactionSets

Loop: transactionSets

ST

Transaction Set Header

MMax: 1Area: 1Seq: 0100

To indicate the start of a transaction set and to assign a control number

ST01
Transaction Set Identifier Code
MIDMIN 3 MAX 3ID: 143

Code identifying a Transaction Set

824Application Advice
ST02
Transaction Set Control Number
MANMIN 4 MAX 9ID: 329

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BGN

Beginning Segment

MMax: 1Area: 1Seq: 0200

To indicate the beginning of a transaction set

BGN01
Transaction Set Purpose Code
MIDMIN 2 MAX 2ID: 353

Code identifying purpose of transaction set

00Original
BGN02
Reference Identification
MANMIN 1 MAX 80ID: 127

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

404
BGN03
Date
MDTMIN 8 MAX 8ID: 373

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

BGN04
Time
CTMMIN 4 MAX 8ID: 337

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)

Loop: OTI_loop

Repeat: >1
OTI

Original Transaction Identification

MMax: 1Area: 2Seq: 0100

To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result

OTI01
Application Acknowledgment Code
MIDMIN 1 MAX 2ID: 110

Code indicating the application system edit results of the business data

TATransaction Set Accept
TETransaction Set Accept with Error
TRTransaction Set Reject
OTI02
Reference Identification Qualifier
MIDMIN 2 MAX 3ID: 128

Code identifying the Reference Identification

BLGovernment Bill of Lading
BMBill of Lading Number
BNBooking Number
COCustomer Order Number
CRCustomer Reference Number
GRGrain Order Reference Number
OBOcean Bill of Lading
PUPrevious Bill of Lading Number
SIShipper’s Identifying Number for Shipment (SID)
OTI03
Reference Identification
MANMIN 1 MAX 80ID: 127

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

OTI06
Date
ODTMIN 8 MAX 8ID: 373

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

OTI07
Time
OTMMIN 4 MAX 8ID: 337

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)

OTI08
Group Control Number
CN0MIN 1 MAX 9ID: 28

Assigned number originated and maintained by the sender

OTI09
Transaction Set Control Number
OANMIN 4 MAX 9ID: 329

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

REF

Reference Information

OMax: >1Area: 2Seq: 0200

To specify identifying information

REF01
Reference Identification Qualifier
MIDMIN 2 MAX 3ID: 128

Code identifying the Reference Identification

EQEquipment Number
WYRail Waybill Number
REF02
Reference Identification
CANMIN 1 MAX 80ID: 127

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Loop: TED_loop

Repeat: >1
TED

Technical Error Description

OMax: 1Area: 2Seq: 0700

To identify the error and, if feasible, the erroneous segment, or data element, or both

TED01
Application Error Condition Code
MIDMIN 1 MAX 3ID: 647

Code indicating application error condition

001Car Not in Umler
002Car Not in Correct Status for Billing
003Duplicate Billing
004Invalid Commodity Code
005Route Error
006Duplicate
007Missing Data
008Out of Range
009Invalid Date
011Not Matching
012Invalid Combination
024Other Unlisted Reason
500Misrouted Freight Bill
803Missing or Invalid Payment Method Code
ZZZMutually Defined
TED02
Free-form Message
OANMIN 1 MAX 60ID: 3

Free-form text

SE

Transaction Set Trailer

MMax: 1Area: 2Seq: 0900

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

SE01
Number of Included Segments
MN0MIN 1 MAX 10ID: 96

Total number of segments included in a transaction set including ST and SE segments

SE02
Transaction Set Control Number
MANMIN 4 MAX 9ID: 329

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set