Rite Aid
/
Planning Schedule with Release Capability
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Rite Aid. Contact Rite Aid for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Rite Aid logo

X12 830 Planning Schedule with Release Capability

X12 Release 5010

This X12 Transaction Set contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations.

The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    0100
    Transaction Set Header
    Max use 1
    Required
    BFR
    0200
    Beginning Segment for Planning Schedule
    Max use 1
    Required
    N1 Loop
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

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

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code identifying the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    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)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code identifying the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    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)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

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

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    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

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

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

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    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

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I65
    Repetition Separator
    Required
    Min 1Max 1

    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
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code indicating sender's request for an interchange acknowledgment

    0
    No Interchange Acknowledgment Requested
    1
    Interchange Acknowledgment Requested (TA1)
    ISA-15
    I14
    Interchange Usage Indicator
    Required
    Min 1Max 1

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

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    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

    RequiredMax use 1

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

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    PS
    Planning Schedule with Release Capability (830)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

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

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    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)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    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
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    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

    005010
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

    Heading

    ST
    0100

    Transaction Set Header

    RequiredMax use 1

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

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    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).
    830
    Planning Schedule with Release Capability
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    BFR
    0200

    Beginning Segment for Planning Schedule

    RequiredMax use 1

    To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates

    Usage notes

    BFR0012345 54321*BBR2018040820180428*20180408~

    Example
    BFR-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    • If BFR01 contains the value "04" (Net Change), BFR09 is required.
    00
    Original
    BFR-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    • BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.
    BFR-04
    675
    Schedule Type Qualifier
    Required

    Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast

    BB
    Customer Production (Consumption) Based
    BFR-05
    676
    Schedule Quantity Qualifier
    Required

    Code identifying the type of quantities used when defining a schedule or forecast

    R
    Replacement Quantities
    BFR-06
    373
    Date
    Required
    CCYYMMDD format

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

    • BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.
    Usage notes

    Forecast horizon start date

    BFR-07
    373
    Date
    Required
    CCYYMMDD format

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

    • BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.
    Usage notes

    Forecast horizon end date

    BFR-08
    373
    Date
    Required
    CCYYMMDD format

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

    • BFR08 is the date forecast generated: The date the forecast data was generated.
    Usage notes

    Date forecast generated

    N1 Loop
    RequiredMax >1
    N1
    2300

    Party Identification

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Usage notes

    N1VN**9254321~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    VN
    Vendor
    N1-03
    66
    Identification Code Qualifier
    Required

    Code designating the system/method of code structure used for Identification Code (67)

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    Min 2Max 80

    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.
    Usage notes

    Vendor Number Assigned by Rite Aid

    Detail

    LIN Loop
    RequiredMax >1
    LIN
    0100

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    LIN*IN0306130UI01182236130~

    Example
    LIN-02
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    IN
    Buyer's Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    UA
    U.P.C./EAN Case Code (2-5-5)
    UI
    U.P.C. Consumer Package Code (1-5-5)
    VN
    Vendor's (Seller's) Item Number
    LIN-05
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    UIT
    0200

    Unit Detail

    RequiredMax use 1

    To specify item unit data

    Usage notes

    UIT*PC~

    Example
    UIT-01
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    PC
    Piece
    FST Loop
    RequiredMax >1
    FST
    4100

    Forecast Schedule

    RequiredMax use 1

    To specify the forecasted dates and quantities

    • At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually exclusive.
    Usage notes

    FST768DF20180408*20180414~

    Example
    FST-01
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    FST-02
    680
    Forecast Qualifier
    Required

    Code specifying the sender's confidence level of the forecast data or an action associated with a forecast

    • As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date of a flexible interval.
    D
    Planning
    FST-03
    681
    Timing Qualifier
    Required

    Code specifying interval grouping of the forecast or product activity

    • If FST03 equals "F" (indicating flexible interval), then FST04 and FST05 are required. FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval.
    • If FST03 equals "B" (indicating shipping/delivery), then FST04 and FST05 are required. The FST04 will represent the shipping date, and the FST05 will represent the delivery date.
    F
    Flexible Interval (from Date X through Date Y)
    FST-04
    373
    Date
    Required
    CCYYMMDD format

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

    Usage notes

    Beginning day

    FST-05
    373
    Date
    Required
    CCYYMMDD format

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

    Usage notes

    Ending day

    SDQ
    4200

    Destination Quantity

    RequiredMax use 50

    To specify destination and quantity detail

    Usage notes

    SDQEA9200010768000350000810~

    More than one SDQ segment may be sent for each forecast schedule sent in an FST segment.

    Example
    If either Identification Code (SDQ-05) or Quantity (SDQ-06) is present, then the other is required
    If either Identification Code (SDQ-07) or Quantity (SDQ-08) is present, then the other is required
    If either Identification Code (SDQ-09) or Quantity (SDQ-10) is present, then the other is required
    If either Identification Code (SDQ-11) or Quantity (SDQ-12) is present, then the other is required
    If either Identification Code (SDQ-21) or Quantity (SDQ-22) is present, then the other is required
    If either Identification Code (SDQ-19) or Quantity (SDQ-20) is present, then the other is required
    If either Identification Code (SDQ-17) or Quantity (SDQ-18) is present, then the other is required
    If either Identification Code (SDQ-15) or Quantity (SDQ-16) is present, then the other is required
    If either Identification Code (SDQ-13) or Quantity (SDQ-14) is present, then the other is required
    SDQ-01
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    EA
    Each
    SDQ-02
    66
    Identification Code Qualifier
    Required

    Code designating the system/method of code structure used for Identification Code (67)

    • SDQ02 is used only if different than previously defined in the transaction set.
    92
    Assigned by Buyer or Buyer's Agent
    SDQ-03
    67
    Identification Code
    Required
    Min 2Max 80

    Code identifying a party or other code

    • SDQ03 is the store number.
    SDQ-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SDQ-05
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-06
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-07
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-08
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-09
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-10
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-11
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-12
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-13
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-14
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-15
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-16
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-17
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-18
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-19
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-20
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-21
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    SDQ-22
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    Summary

    CTT
    0100

    Transaction Totals

    RequiredMax use 1

    To transmit a hash total for a specific element in the transaction set

    • Number of line items (CTT01) is the accumulation of the number of LIN segments.
      If used, hash total (CTT02) is the sum of the values of the quantities (FST01) for each FST segment.
    Usage notes

    CTT*2~

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    0200

    Transaction Set Trailer

    RequiredMax use 1

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

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

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

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    Functional Group Trailer

    RequiredMax use 1

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

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*830*000001169~
    BFR*00*07437 33672**BB*R*20180327*20180625*20180327~
    N1*VN**92*33672~
    LIN**IN*0306130*UI*01182236130~
    UIT*PC~
    FST*2736*D*F*20180327*20180402~
    SDQ*EA*92*00010*864*00029*288*00035*240*00050*0*00053*336*00054*288*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*720~
    FST*432*D*F*20180403*20180409~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*432*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*1488*D*F*20180410*20180416~
    SDQ*EA*92*00010*864*00029*288*00035*0*00050*0*00053*0*00054*0*00055*0*00056*336*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*1872*D*F*20180417*20180423~
    SDQ*EA*92*00010*0*00029*0*00035*240*00050*0*00053*336*00054*288*00055*0*00056*0*00080*0*00081*288~
    SDQ*EA*92*00088*720~
    FST*720*D*F*20180424*20180430~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*432*00056*0*00080*288*00081*0~
    SDQ*EA*92*00088*0~
    FST*3264*D*F*20180501*20180507~
    SDQ*EA*92*00010*864*00029*288*00035*240*00050*192*00053*336*00054*0*00055*0*00056*336*00080*0*00081*288~
    SDQ*EA*92*00088*720~
    FST*288*D*F*20180508*20180514~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*288*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*2160*D*F*20180515*20180521~
    SDQ*EA*92*00010*864*00029*288*00035*0*00050*0*00053*0*00054*0*00055*432*00056*336*00080*240*00081*0~
    SDQ*EA*92*00088*0~
    FST*2064*D*F*20180522*20180528~
    SDQ*EA*92*00010*0*00029*0*00035*240*00050*192*00053*336*00054*288*00055*0*00056*0*00080*0*00081*288~
    SDQ*EA*92*00088*720~
    FST*720*D*F*20180529*20180604~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*432*00056*0*00080*288*00081*0~
    SDQ*EA*92*00088*0~
    FST*3024*D*F*20180605*20180611~
    SDQ*EA*92*00010*864*00029*288*00035*0*00050*192*00053*336*00054*0*00055*0*00056*336*00080*0*00081*288~
    SDQ*EA*92*00088*720~
    FST*528*D*F*20180612*20180618~
    SDQ*EA*92*00010*0*00029*0*00035*240*00050*0*00053*0*00054*288*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*2448*D*F*20180619*20180625~
    SDQ*EA*92*00010*816*00029*288*00035*0*00050*0*00053*336*00054*0*00055*432*00056*336*00080*240*00081*0~
    SDQ*EA*92*00088*0~
    LIN**IN*0330294*UI*01182230294~
    UIT*PC~
    FST*0*D*F*20180327*20180402~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180403*20180409~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180410*20180416~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180417*20180423~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180424*20180430~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180501*20180507~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180508*20180514~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180515*20180521~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180522*20180528~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180529*20180604~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180605*20180611~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180612*20180618~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    FST*0*D*F*20180619*20180625~
    SDQ*EA*92*00010*0*00029*0*00035*0*00050*0*00053*0*00054*0*00055*0*00056*0*00080*0*00081*0~
    SDQ*EA*92*00088*0~
    CTT*2~
    SE*87*000001169~

    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.