Walgreens 856 - Advanced Ship Notice Specifications

Modified on Tue, May 26 at 9:49 AM

**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.


X12 856 Advanced Shipment Notification (ASN) for Direct Store Delivery (DSD)

X12 Release 4010

Revised February 23, 2024

Print

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.

The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Delimiters

~ Segment

* Element

> Component

EDI samples

None included

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*00*          *00*          *XX*XXXXXXXXXXXXXXX*XX*XXXXXXXXXXXXXXX*240806*1439*U*00401*000000000*X*X*>~

ISA-01

I01

Authorization Information Qualifier

Required

Identifier (ID)

Code to identify the type of information in the Authorization Information

00

No Authorization Information Present (No Meaningful Information in I02)

ISA-02

I02

Authorization Information

Required

String (AN)

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

Identifier (ID)

Code to identify the type of information in the Security Information

00

No Security Information Present (No Meaningful Information in I04)

ISA-04

I04

Security Information

Required

String (AN)

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

Identifier (ID)

Min 2Max 2

Qualifier to designate 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

String (AN)

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

Identifier (ID)

Min 2Max 2

Qualifier to designate 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

String (AN)

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

Date (DT)

YYMMDD format

Date of the interchange

ISA-10

I09

Interchange Time

Required

Time (TM)

HHMM format

Time of the interchange

ISA-11

I10

Interchange Control Standards Identifier

Required

Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U

U.S. EDI Community of ASC X12, TDCC, and UCS

ISA-12

I11

Interchange Control Version Number

Required

Identifier (ID)

This version number covers the interchange control segments

00401

Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997

ISA-13

I12

Interchange Control Number

Required

Numeric (N0)

Min 9Max 9

A control number assigned by the interchange sender

ISA-14

I13

Acknowledgment Requested

Required

Identifier (ID)

Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0

No Acknowledgment Requested

1

Interchange Acknowledgment Requested

ISA-15

I14

Usage Indicator

Required

Identifier (ID)

Min 1Max 1

Code to indicate 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

String (AN)

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

GS

Functional Group Header

RequiredMax use 1

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

Example

GS*SH*XXX*XXXXXXX*20240806*0518*0*X*004010~

GS-01

479

Functional Identifier Code

Required

Identifier (ID)

Code identifying a group of application related transaction sets

SH

Ship Notice/Manifest (856)

GS-02

142

Application Sender's Code

Required

String (AN)

Min 2Max 15

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

GS-03

124

Application Receiver's Code

Required

String (AN)

Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

GS-05

337

Time

Required

Time (TM)

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

Numeric (N0)

Min 1Max 9

Assigned number originated and maintained by the sender

GS-07

455

Responsible Agency Code

Required

Identifier (ID)

Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T

Transportation Data Coordinating Committee (TDCC)

X

Accredited Standards Committee X12

GS-08

480

Version / Release / Industry Identifier Code

Required

String (AN)

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

004010

Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST

010

Transaction Set Header

RequiredMax use 1

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

Example

ST*856*0001~

ST-01

143

Transaction Set Identifier Code

Required

Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

856

Ship Notice/Manifest

ST-02

329

Transaction Set Control Number

Required

Numeric (N)

Min 4Max 9

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

BSN

020

Beginning Segment for Ship Notice

RequiredMax use 1

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Usage notes

Only one Walgreens Purchase Order number will be accepted on each Ship Notice.

Example

BSN*00*SHID1234*20230617*1137*0001*AS~

BSN-01

353

Transaction Set Purpose Code

Required

Identifier (ID)

Code identifying purpose of transaction set

Usage notes

When sending a code of '00' in the BSN01, the BSN02 must be unique. The code of '05' is used when sending a corrected ASN with the same BSN02 as previously transmitted.

00

Original

BSN-02

396

Shipment Identification

Required

String (AN)

Min 2Max 30

A unique control number assigned by the original shipper to identify a specific shipment

Usage notes

This number cannot contain dashes, spaces, or any other special characters

BSN-03

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

  • BSN03 is the date the shipment transaction set is created.

Usage notes

This field should contain ASN creation date.

BSN-04

337

Time

Required

Time (TM)

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)

  • BSN04 is the time the shipment transaction set is created.

Usage notes

This field should contain ASN creation time

BSN-05

1005

Hierarchical Structure Code

Required

Identifier (ID)

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

0001

Shipment, Order, Packaging, Item

BSN-06

640

Transaction Type Code

Optional

Identifier (ID)

Code specifying the type of transaction

  • BSN06 is limited to shipment related codes.
  • BSN06 and BSN07 differentiate the functionality of use for the transaction set.

AS

Shipment Advice

Detail

HL Loop

RequiredMax 1

HL

010

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

Example

HL*1**S*1~

HL-01

628

Hierarchical ID Number

Required

String (AN)

Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-03

735

Hierarchical Level Code

Required

Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

S

Shipment

HL-04

736

Hierarchical Child Code

Optional

Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

1

Additional Subordinate HL Data Segment in This Hierarchical Structure.

REF

150

Reference Identification Invoice Number

OptionalMax use 1

To specify identifying information

Example

REF*IK*654321*VNAME~

Variants (all may be used)

REFReference Identification Vendor ID Number

REF-01

128

Reference Identification Qualifier

Required

Identifier (ID)

Code qualifying the Reference Identification

IK

Invoice Number

REF-02

127

Reference Identification

Required

String (AN)

Min 1Max 30

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

Usage notes

If an Invoice Number is sent in the REF02, them a DTM01 with a "003" is required (Invoice Date).

REF-03

352

Description

Optional

String (AN)

Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Marketing Vendor Name.

REF

150

Reference Identification Vendor ID Number

RequiredMax use 1

To specify identifying information

Example

REF*VR*123456*XXXXXX~

Variants (all may be used)

REFReference Identification Invoice Number

REF-01

128

Reference Identification Qualifier

Required

Identifier (ID)

Code qualifying the Reference Identification

VR

Vendor ID Number

REF-02

127

Reference Identification

Required

String (AN)

Min 1Max 30

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

Usage notes

This field must contain your Legacy 6-digit Walgreens Marketing Vendor Number or 10-digit SAP Vendor Number, as communicated to you on the Purchase Order. Note: This is NOT the same as your Walgreens Accounts Payable Number, which may be up to 9 digits in length.
 
This value corresponds to Zone F on the Shipping Labe

REF-03

352

Description

Optional

String (AN)

Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Marketing Vendor Name. Corresponds to Zone A on the Shipping Label .

DTM

200

Date/Time Reference Current Schedule Delivery Date

OptionalMax use 1

To specify pertinent dates and times

Example

DTM*067*20230617*1226~

Variants (all may be used)

DTMDate/Time Reference Invoice DateDTMDate/Time Reference Shipped

DTM-01

374

Date/Time Qualifier

Required

Identifier (ID)

Code specifying type of date or time, or both date and time

067

Current Schedule Delivery

DTM-02

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03

337

Time

Optional

Time (TM)

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)

DTM

200

Date/Time Reference Invoice Date

OptionalMax use 1

To specify pertinent dates and times

Example

DTM*003*20230617*1226~

Variants (all may be used)

DTMDate/Time Reference Current Schedule Delivery DateDTMDate/Time Reference Shipped

DTM-01

374

Date/Time Qualifier

Required

Identifier (ID)

Code specifying type of date or time, or both date and time

003

Invoice

DTM-02

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

If an Invoice Date is sent in the DTM02, then the REF01 element with an "IK" qualifier and the REF02 element with an Invoice Number is required.

DTM-03

337

Time

Optional

Time (TM)

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)

DTM

200

Date/Time Reference Shipped

RequiredMax use 1

To specify pertinent dates and times

Example

DTM*011*20230617*1226~

Variants (all may be used)

DTMDate/Time Reference Current Schedule Delivery DateDTMDate/Time Reference Invoice Date

DTM-01

374

Date/Time Qualifier

Required

Identifier (ID)

Code specifying type of date or time, or both date and time

011

Shipped

DTM-02

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03

337

Time

Optional

Time (TM)

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)

N1 Loop

RequiredMax 2

N1

220

Name

RequiredMax use 1

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

Example

N1*ST**92*3W001~

N1-01

98

Entity Identifier Code

Required

Identifier (ID)

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

ST

Ship To

N1-03

66

Identification Code Qualifier

Required

Identifier (ID)

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

String (AN)

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

This must be either the Walgreens Legacy 5-character store number or 4-character SAP Site number, as communicated to you on the Purchase Order.
 
Corresponding to Zone H on the Shipping Label

HL Loop

RequiredMax >1

HL

010

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

Example

HL*2*1*O*1~

HL-01

628

Hierarchical ID Number

Required

String (AN)

Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02

734

Hierarchical Parent ID Number

Required

String (AN)

Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03

735

Hierarchical Level Code

Required

Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

O

Order

HL-04

736

Hierarchical Child Code

Optional

Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

1

Additional Subordinate HL Data Segment in This Hierarchical Structure.

PRF

050

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Usage notes

Only one Walgreens Purchase Order number will be accepted on each Ship Notice.

Example

PRF*PO123456***20230617~

PRF-01

324

Purchase Order Number

Required

String (AN)

Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

This must be either the Walgreens Legacy 6-digit store-level PO Number or the 10-digit SAP Purchase Order number, as communicated to you on the Purchase Order. Use of a value not from either the Walgreens Legacy environment (SIMS) or future SAP system will result in processing issues and may affect proper and timely payment for this transaction. The future Walgreens SAP back-end environment will only support maximum PO length of 10 characters - items sent with values beyond 10 characters will fail in the future Walgreens SAP Environment.

Corresponds to Zone E on the Shipping Label

PRF-04

373

Date

Required

Date (DT)

CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.

Usage notes

This should be the Purchase Order date sent in the BEG05 of the 850 PO document.

HL Loop

RequiredMax 200

Usage notes

Required by Walgreens if marking data is sent at Pack level.

HL

010

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

Example

HL*3*2*P*1~

HL-01

628

Hierarchical ID Number

Required

String (AN)

Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02

734

Hierarchical Parent ID Number

Required

String (AN)

Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03

735

Hierarchical Level Code

Required

Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

P

Pack

HL-04

736

Hierarchical Child Code

Optional

Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

1

Additional Subordinate HL Data Segment in This Hierarchical Structure.

MAN

190

Marks and Numbers

RequiredMax use 1

To indicate identifying marks and numbers for shipping containers

Usage notes

Required by Walgreens if marking data is sent at Pack level. Walgreens allows only one marking value per segment.

When shipping products to Walgreens Stores, each carton must have a UCC-128 shipping label applied, containing a unique SSCC-18 number that matches the value supplied in the MAN02 field.

Example

MAN*GM*X~

MAN-01

88

Marks and Numbers Qualifier

Required

Identifier (ID)

Code specifying the application or source of Marks and Numbers (87)

  • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
  • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.

GM

SSCC-18 and Application Identifier

MAN-02

87

Marks and Numbers

Required

String (AN)

Min 1Max 48

Marks and numbers used to identify a shipment or parts of a shipment

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.

Usage notes

If used, This corresponds to Zone I in the Shipping Label.

HL Loop

RequiredMax 100

Usage notes

Either the Tare (Pallet) loop or the Pack (Case) loop is required.

HL

010

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

Example

HL*4*3*I*0~

HL-01

628

Hierarchical ID Number

Required

String (AN)

Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02

734

Hierarchical Parent ID Number

Required

String (AN)

Min 1Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03

735

Hierarchical Level Code

Required

Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

I

Item

HL-04

736

Hierarchical Child Code

Optional

Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

0

No Subordinate HL Segment in This Hierarchical Structure.

LIN

020

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

Walgreens requires you to send the original Purchase Order line number in both the LIN01 and SN101 elements.

The ordering number qualifier (LIN02) and ordering number (LIN03) must match the original ordering number qualifier (PO106) and ordering number (PO107) sent in the Purchase Order.

Example

LIN*001*UP*ID1*ND*ID2*VN*ID3*VN*ID4*MD*ID5~

If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required

If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required

If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required

If either Product/Service ID Qualifier (LIN-10) or Product/Service ID (LIN-11) is present, then the other is required

LIN-01

350

Assigned Identification

Required

String (AN)

Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification

Usage notes

Failure to use the assigned PO line number from either the Walgreens Legacy system (SIMS) or future SAP system will result in processing errors.

LIN-02

235

Product/Service ID Qualifier

Required

Identifier (ID)

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.

Usage notes

The Primary Item ordering qualifier must be sent in this position. This value is always referenced from the ordering qualifier in your current catalog.

Note: This is the ordering number qualifier sent in the PO106 field of the Purchase Order

EI

Expense Identifier

UI

U.P.C. Consumer Package Code (1-5-5)

UK

U.P.C./EAN Shipping Container Code (1-2-5-5-1)

UP

U.P.C. Consumer Package Code (1-5-5-1)

LIN-03

234

Product/Service ID

Required

String (AN)

Min 1Max 48

Identifying number for a product or service

Usage notes

The primary Item ordering identifier must be sent in this position. This value is always referenced from the ordering number in your current catalog.
 
Note: This is the ordering number sent in the PO107 field of the Purchase Order.

LIN-04

235

Product/Service ID Qualifier

Optional

Identifier (ID)

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

Usage notes

This element is not required/needed for non-Rx transactions.

EN

European Article Number (EAN) (2-5-5-1)

LT

Lot Number

ND

National Drug Code (NDC)

UI

U.P.C. Consumer Package Code (1-5-5)

UK

U.P.C./EAN Shipping Container Code (1-2-5-5-1)

UP

U.P.C. Consumer Package Code (1-5-5-1)

LIN-05

234

Product/Service ID

Optional

String (AN)

Min 1Max 48

Identifying number for a product or service

Usage notes

This element is not required/needed for non-Rx transactions

LIN-06

235

Product/Service ID Qualifier

Optional

Identifier (ID)

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

EN

European Article Number (EAN) (2-5-5-1)

MG

Manufacturer's Part Number

ND

National Drug Code (NDC)

UI

U.P.C. Consumer Package Code (1-5-5)

UK

U.P.C./EAN Shipping Container Code (1-2-5-5-1)

UP

U.P.C. Consumer Package Code (1-5-5-1)

VN

Vendor's (Seller's) Item Number

LIN-07

234

Product/Service ID

Optional

String (AN)

Min 1Max 48

Identifying number for a product or service

Usage notes

This element is not required/needed for non-Rx transactions. For pharmaceutical products, you must supply the 11-digit NDC (5-4-2 format) of the product.
 
Note: This number cannot contain dashes, spaces, or any other special characters

LIN-08

235

Product/Service ID Qualifier

Optional

Identifier (ID)

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

Usage notes

This element is not required/needed for non-Rx transactions.

EN

European Article Number (EAN) (2-5-5-1)

MG

Manufacturer's Part Number

ND

National Drug Code (NDC)

UI

U.P.C. Consumer Package Code (1-5-5)

UK

U.P.C./EAN Shipping Container Code (1-2-5-5-1)

UP

U.P.C. Consumer Package Code (1-5-5-1)

VN

Vendor's (Seller's) Item Number

LIN-09

234

Product/Service ID

Optional

String (AN)

Min 1Max 48

Identifying number for a product or service

Usage notes

This element is not required/needed for non-Rx transactions

LIN-10

235

Product/Service ID Qualifier

Optional

Identifier (ID)

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

EN

European Article Number (EAN) (2-5-5-1)

MD

Method of Delivery Code

MG

Manufacturer's Part Number

ND

National Drug Code (NDC)

UI

U.P.C. Consumer Package Code (1-5-5)

UK

U.P.C./EAN Shipping Container Code (1-2-5-5-1)

UP

U.P.C. Consumer Package Code (1-5-5-1)

VN

Vendor's (Seller's) Item Number

LIN-11

234

Product/Service ID

Optional

String (AN)

Min 1Max 48

Identifying number for a product or service

Usage notes

If using MD indicator, follow with "drop ship" verbiage in LIN-11.

SN1

030

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

Walgreens requires you to send the original Purchase Order line number in both the LIN01 and SN101 elements.

Example

SN1*XXXXXX*10*EA*5*15*EA**IS~

If either Quantity Ordered (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required

SN1-01

350

Assigned Identification

Required

String (AN)

Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • SN101 is the ship notice line-item identification.

Usage notes

Failure to use the assigned PO line number from either the Walgreens Legacy system (SIMS) or future SAP system will result in processing errors

SN1-02

382

Number of Units Shipped

Required

Decimal number (R)

Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes

2 decimal positions will be accepted.

SN1-03

355

Unit or Basis for Measurement Code

Required

Identifier (ID)

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

  • SN103 defines the unit of measurement for both SN102 and SN104.

EA

Each

This UOM measure (EA) is the Mandatory qualifier to be used for vendors on the Three-Way Match Program/Invoice Reconciliation in the Legacy Walgreens environment. Other values, such as "CA," may become available after Walgreens has finished its SAP deployment across all internal systems.

SN1-04

646

Quantity Shipped to Date

Optional

Decimal number (R)

Min 1Max 15

Number of units shipped to date

SN1-05

330

Quantity Ordered

Optional

Decimal number (R)

Min 1Max 15

Quantity ordered

SN1-06

355

Unit or Basis for Measurement Code

Optional

Identifier (ID)

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

EA

Each

This UOM measure (EA) is the Mandatory qualifier to be used for vendors on the Three-Way Match Program/Invoice Reconciliation in the Legacy Walgreens environment. Other values, such as "CA," may become available after Walgreens has finished its SAP deployment across all internal systems.

SN1-08

668

Line Item Status Code

Required

Identifier (ID)

Code specifying the action taken by the seller on a line item requested by the buyer

AC

Item Accepted and Shipped

BP

Item Accepted - Partial Shipment, Balance Backordered

ID

Item Deleted

IS

Item Accepted - Substitution Made

PID

070

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Example

PID*F****DESCRIPTION~

PID-01

349

Item Description Type

Required

Identifier (ID)

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.

F

Free-form

PID-05

352

Description

Required

String (AN)

Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

The item description must be supplied using up to a maximum of 50 characters. Walgreens requests that the Unit of Measure and Quantity be included in the item description

Summary

CTT

010

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 HL segments.
     
    If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.

Example

CTT*1*0000000~

CTT-01

354

Number of Line Items

Required

Numeric (N0)

Min 1Max 6

Total number of line items in the transaction set

Usage notes

this value is the accumulation of the number of HL segments.

CTT-02

347

Hash Total

Optional

Decimal number (R)

Min 1Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
 
-.0018 First occurrence of value being hashed.
 
.18 Second occurrence of value being hashed.
 
1.8 Third occurrence of value being hashed.
 
18.01 Fourth occurrence of value being hashed.

1855 Hash total prior to truncation.
 
855 Hash total after truncation to three-digit field.

Usage notes

This is the Hash total of the SN102

SE

020

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*0*0001~

SE-01

96

Number of Included Segments

Required

Numeric (N0)

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

Numeric (N)

Min 4Max 9

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

GE

Functional Group Trailer

RequiredMax use 1

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

Example

GE*0*00000000~

GE-01

97

Number of Transaction Sets Included

Required

Numeric (N0)

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

Numeric (N0)

Min 1Max 9

Assigned number originated and maintained by the sender

IEA

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*000*000000000~

IEA-01

I16

Number of Included Functional Groups

Required

Numeric (N0)

Min 1Max 5

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

IEA-02

I12

Interchange Control Number

Required

Numeric (N0)

Min 9Max 9

A control number assigned by the interchange sender

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article