Saks Fifth Avenue
/
Retail Return Merchandise Authorization and Notification
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Saks Fifth Avenue. Contact Saks Fifth Avenue for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Saks Fifth Avenue logo

X12 180 Retail Return Merchandise Authorization and Notification

X12 Release 4050

This X12 Transaction Set contains the format and establishes the data contents of the Return Merchandise Authorization and Notification Transaction Set (180) for use within the context of an Electronic Data Interchange (EDI) environment.
This transaction set can provide for customary and established business and industry practice relative to the returning of merchandise to the vendor. This transaction set may satisfy request for returns, authorization or disposition of the return, notification of return, or notification of consumer return.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI sample
  • Saks Off 5th Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/saks-fifth-avenue/retail-return-merchandise-authorization-and-notification/01HBZVDZFCJ7RKP6Q4KAH8G6JR
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
BGN
0200
Beginning Segment
Max use 1
Required
N9
0600
Extended Reference Information
Max use 10
Required
PER
0700
Administrative Communications Contact
Max use 2
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
Identifier (ID)

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
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 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
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

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
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

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
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
I65
Repetition Separator
Required
String (AN)
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
Identifier (ID)

Code specifying the version number of the interchange control segments

00405
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2001
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 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
Identifier (ID)
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
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

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
Identifier (ID)

Code identifying a group of application related transaction sets

AN
Return Merchandise Authorization and Notification (180)
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

Required
Date (DT)
CCYYMMDD format

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

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 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
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

004050
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2001

Heading

ST
0100
Heading > ST

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
Identifier (ID)

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).
180
Return Merchandise Authorization and Notification
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

BGN
0200
Heading > BGN

Beginning Segment

RequiredMax use 1

To indicate the beginning of a transaction set

Example
BGN-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
07
Duplicate
BGN-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

  • BGN02 is the transaction set reference number.
Required
Date (DT)
CCYYMMDD format

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

  • BGN03 is the transaction set date.
N9
0600
Heading > N9

Extended Reference Information

RequiredMax use 10

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
String (AN)
Min 2Max 3

Code qualifying the Reference Identification

N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

N9-03
369
Free-form Description
Optional
String (AN)
Min 1Max 45

Free-form descriptive text

PER
0700
Heading > PER

Administrative Communications Contact

RequiredMax use 2

To identify a person or office to whom administrative communications should be directed

Example
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

NT
Notification Contact
Required
String (AN)
Min 1Max 60

Free-form name

N1 Loop
RequiredMax >1
N1
1200
Heading > N1 Loop > N1

Party Identification

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

ID
Issuer of Debit or Credit Memo
Required
String (AN)
Min 1Max 60

Free-form name

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.
N1 Loop end
Heading end

Detail

BLI Loop
RequiredMax >1
BLI
0100
Detail > BLI Loop > BLI

Basic Baseline Item Data

RequiredMax use 1

To specify basic item data: item identification, quantity, and price

  • Quantity is specified either in the BLI segment (BLI03) or in the QTY segment.
Example
BLI-01
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

  • BLI01, BLI02, and BLI08 through BLI13 provide for four different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model, SKU.
EN
EAN/UCC - 13
UP
UCC - 12
BLI-02
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

BLI-03
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

BLI-04
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

EA
Each
PID
0200
Detail > BLI Loop > PID

Product/Item Description

RequiredMax use 5

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

Example
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.
S
Structured (From Industry Code List)
PID-02
750
Product/Process Characteristic Code
Required
Identifier (ID)

Code identifying the general class of a product or process characteristic

08
Product
PID-03
559
Agency Qualifier Code
Required
Identifier (ID)

Code identifying the agency assigning the code values

  • Use PID03 to indicate the organization that publishes the code list being referred to.
VI
Voluntary Inter-Industry Commerce Standard (VICS) EDI
PID-04
751
Product Description Code
Required
String (AN)
Min 1Max 12

A code from an industry code list which provides specific data about a product characteristic

  • PID04 should be used for industry-specific product description codes.
RDR
0300
Detail > BLI Loop > RDR

Return Disposition Reason

RequiredMax use 1

To indicate the disposition of the item, the reason for return by the returnee, the response to the reason for return, and whether the item was used

Example
RDR-01
1292
Returns Disposition Code
Required
Identifier (ID)

Code indicating the disposition of a contested item

DI
Dispose
RDR-02
1293
Return Request Reason Code
Required
String (AN)
Min 2Max 2

Code indicating the reason for the return from the party returning, or requesting to return, the items

RDR-04
352
Description
Required
String (AN)
Min 1Max 80

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

BLI Loop end
SE
2300
Detail > SE

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
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

Detail end

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
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

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
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

EDI Samples

Saks Off 5th Sample

ISA*00**00**01* 6989867*ZZ* RECEIVERID*200809*0930*^*00405*002103991*0*P*>
GS*AN*006989867*RECEIVERID*20200809*0930*2133991*X*004050VICS
ST*180*2116371
BGN*00*0000508360*20200803
N9*DP*000000000000680
N9*SR*000100
PER*NT*CARLONE-ELRAFEI26
N1*ID*SAKS*92*0621
BLI*UP*999997297913*1*EA
PID*S*08*VI*VIRNJJ
RDR*DI*SR**STOCK ADJUSTMENT
BLI*UP*999997189966*1*EA
PID*S*08*VI*VIR8P9
RDR*DI*SR**STOCK ADJUSTMENT
BLI*UP*999997311510*1*EA
PID*S*08*VI* VIRR3W
RDR*DI*SR**STOCK ADJUSTMENT
BLI*UP*999997431188*1*EA
PID*S*08*VI*VIP8GL
RDR*DI*SR**STOCK ADJUSTMENT
SE*19*2116371
GE*1*2133991
IEA*1*002103991

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.