X12 180 Return Merchandise Authorization and Notification
This Draft Standard for Trial Use 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.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify 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 to identify 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)
Qualifier to designate 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
Qualifier to designate 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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate 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
- AN
- Return Merchandise Authorization and Notification (180)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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 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
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
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) 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
Beginning Segment
To indicate the beginning of a transaction set
Example: BGN005555050720041200
Code identifying purpose of transaction set
- 00
- Original
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BGN02 is the transaction set reference number.
ID used to uniquely identify this transaction.
Purchase Order Reference
To provide reference to a specific purchase order
Example: PRF*789012
Identifying number for Purchase Order assigned by the orderer/purchaser
This element contains the BJs Wholesale Club assigned purchase order number. Returning an invalid purchase order number will result in a failure to process the message.
Detail
Baseline Item Data
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: BLIVN2233445*****SK115599
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.
This qualifier indicates that the vendor assigned SKU for the product is included in the BLI02.
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
The vendor assigned SKU for the product.
Numeric value of quantity
The quantity that has been returned to the supplier. This quantity cannot exceed the quantity that has already been reported as shipped.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Return Disposition Reason
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**DA
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Example: SACCG47011****PP
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- G470
- Restocking Charge
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Code indicating method of handling for an allowance or charge
- 01
- Bill Back
- 02
- Off Invoice
- 03
- Vendor Check to Customer
- 04
- Credit Customer Account
- 05
- Charge to be Paid by Vendor
- 06
- Charge to be Paid by Customer
- 07
- Optional
- 08
- Off Gross Quantity Invoiced
- 09
- Allowance To Be Issued by Vendor
- 10
- Allowance To Be Issued by Reseller
- 11
- Charge Denied by Vendor
- 12
- Cancel Allowance
- 13
- Provide Amount
- 15
- Information Only
- 18
- Non-Payable Tax
- 20
- Accrual Fund
- 21
- Flat Fund
- 25
- Cash in Advance
- CA
- Calculate and Add to Invoice
- CC
- Collect
- PP
- Prepaid
- ZZ
- Mutually Defined
Purchase Order Reference
To provide reference to a specific purchase order
Example: PRF135792468***1
Identifying number for Purchase Order assigned by the orderer/purchaser
This PO number must be identical to the PO number in the header PRF segment.
Date/Time Reference
To specify pertinent dates and times
Example: DTM05005072004
Code specifying type of date or time, or both date and time
This qualifier indicates that the date the supplier received the returned goods is included in the DTM02.
- 050
- Received
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.