X12 864 Text Message
This Draft Standard for Trial Use contains the format and establishes the data content of the Text Message Transaction Set (864) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide users with a capability to electronically move messages, contracts, explanations, and other one-time communications.
It is the intent of this transaction set to provide electronic communication (messages) for people, not for computer processing. The use of the transaction set to transmit quasi or unique transaction set standards is discouraged.
The use of the Text Message transaction set demands of the sender certain detailed information about the recipient. The transaction set's purpose is to provide communication to the recipient in some human-readable form. The recipient's network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission.
- ~ Segment
- * Element
- > Component
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in 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)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in 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)
Code indicating 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 value in the sender ID element
Code indicating 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
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
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
- >
- Component Element Separator
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
- TX
- Text Message (864)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
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
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 864
- Text Message
Beginning Segment For Text Message
To indicate the beginning of a Text Message Transaction Set
Code identifying purpose of transaction set
- 00
- Original
A free-form description to clarify the related data elements and their content
- BMG02 contains the message subject.
Date/Time Reference
To specify pertinent dates and times
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- FR
- Message From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Name
To identify a party by type of organization, name, and code
Internal Vendor Number
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Seller's Invoice Number
To specify identifying information
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Detail
Message Identification
To identify the beginning of a specific message and to allow the identification of a subject for the message
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- MIT01 contains the message number.
- PLEASE CORRECT AND RESUBMIT
- PLEASE CORRECT AND RESUBMIT
Message Text
To provide a free-form format that allows the transmission of text information
Will repeat for every error on the particular invoice.
Error Msg: Invalid Transaction Type Flag: (The 810 transaction cannot be correctly identified as a Sale(Debit)/Credit/Non-Mdse Invoice)
Correction Required: Correct the Invoice type in the BIG07 & Retransmit
Free-form message text
If you have any questions about the Error Messages or the corresponding Correction Required please contact FDAP@familydollar.com.
Error Msg: Invalid Transaction Type Flag: (The 810 transaction cannot be correctly identified as a Sale (Debit)/Credit/Non-Mdse Invoice)
Correction Required: Correct the Invoice type in the BIG07 & Retransmit
Error Msg: Invalid Supplier Number: (The 810 transaction does not have the correct Family Dollar Supplier Number)
Correction Required: Correct supplier number in the REF02 segment. The Supplier Number is supplied on the 850 in the REF*VR segment.
Error Msg: Invalid Purchase Order: (The purchase order on the 810 is not valid in the Family Dollar Merchandise System, this doesn't affect DSD Vendors)
Correction Required: Correct the purchase order number in the BIG04 with the purchase order that was supplied on the 850 in the BEG02.
Error Msg: Must be a Valid Store or Warehouse: (The correct Family Dollar store/warehouse location number wasn't provided)
Correction Required: Correct the Store/Warehouse location and retransmit the invoice.
Error Msg: Invalid Change Code: (A SAC02 code was sent that is not on the allowed listing)
Correction Required: Correct the SAC02 code and retransmit the invoice. A complete list of accepted SAC codes at the detail and summary level are listed in the 810 specifications.
Error Msg: Number of Charge Codes supplied exceeded maximum: (The invoice/credit contains more than 25 SAC codes)
Correction Required: DO NOT RETRANSMIT! This is for your information only. Please contact Family Dollar AP Department at FDAP@familydollar.com for instructions on how to split the invoice into multiple invoices.
Error Msg: Duplicate Invoice: (The original invoice number is already processed and in our system and the duplicate will not be processed)
Correction Required: DO NOT RETRANSMIT! This is for your information only.
Error Msg: Number Of Order Numbers supplied exceed the maximum: (An invoice/credit may contain up to 25 PO numbers)
Correction Required: DO NOT RETRANSMIT! This is for your information only. Please contact Family Dollar AP Department at FDAP@familydollar.com for instructions on how to split the invoice into multiple invoices.
Error Msg: Number of VBOL supplied exceeded maximum: (An invoice/credit may contain up to 25 VBOL numbers)
Correction Required: DO NOT RETRANSMIT! This is for your information only. Please contact Family Dollar AP Department at FDAP@familydollar.com for instructions on how to split the invoice into multiple invoices.
Error Msg: Invalid SKU: (The SKU billed on the invoice is not present in our system or is different from the one provided on the purchase order)
Correction Required: Correct the SKU and retransmit. Please contact your respective merchandising department to get the correct SKU for your item. Family Dollar SKU is required with a code of "SK" in case you are not sending the item/case UPC or if the case/item UPC has not been provided to the Family Dollar Merchandising Department for a particular SKU.
Error Msg: Invalid UPC: (The UPC billed on the invoice is not present in our system or is different from the one provided on the purchase order)
Correction Required: Correct the UPC (Each/Case) and retransmit. Please provide your respective merchandising department with the correct UPC for a particular SKU. Either an EACH or a CASE UPC is required when you are not sending the Family Dollar SKU. You only need to provide the respective UPC for the UOM that you are using for Billing. UA - CASE (2-5-5) or UP - EACH (1-5-5-1).
Error Msg: Invoice UPC Qualifier: (The UPC qualifier didn't match the UOM that was sent)
Correction Required: Correct the UPC qualifier and retransmit. Family Dollar only accepts invoices in an UOM of EA and/or CA. A qualifier of UA and the corresponding shipper UPC is required when billing in cases and a qualifier of UP and the corresponding shipper UPC is required when billing in eaches.
A field to be used for the control of the line feed of the receiving printer
- MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.
- SS
- Advance to new line before print
Summary
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
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.