edi implementation guide business... · x12 specifications. edi documents are posted using an html...

EDI Implementation Guide

Merchant Partner Program

Original Publication Date: July 7, 2003 Revision Date: October 3, 2006

Distribution: Quixtar Software QA Testing, internal website

EDI IMPLEMENTATION GUIDE .........................................................................................................................................1 THE EDI DOCUMENT ............................................................................................................................................................3

What is it Exactly?..............................................................................................................................................................3 What will Quixtar accept?..................................................................................................................................................3 Functional Acknowledgment ..............................................................................................................................................3

COMMUNICATION.................................................................................................................................................................4 What is the method of transmission?..................................................................................................................................4 Sample HTML File to send EDI (867) document to QA server:.........................................................................................6 Sample HTML File to send EDI(867) document to production server: .............................................................................6 Portal Support for Partners................................................................................................................................................8

1 EDI COMMISSION DATA (X12 4010 867) ..................................................................................................................9 2 EDI ORDER DATA (X12 4010 867).............................................................................................................................29 3 EDI SALES DATA (X12 4010 867)...............................................................................................................................49 APPENDIX A – B2B SETUP..................................................................................................................................................70

Purpose The purpose of this document is to describe the communication and data specifications for posting XML/EDI documents to relay sales, commission or order status data to Quixtar. Its audience is the technical staff at the customer site charged with implementing the relationship.

The EDI Document

What is it Exactly? ANSI X12 documents have been used for decades to exchange business information. Though traditionally used with a VAN (Value Added Network), these can be exchanged directly over the internet as well thus saving VAN charges. We will accept EDI documents via a VAN. We use AT&T Global network, via an HTTP/S post, or via an HTTP post with AS2 encryption. If you opt to send your EDI data FTP through our VPN, that can be arranged with the Quixtar Testing Team.

What will Quixtar accept? We are currently using an 867 document in version 4010 for all three types of data: Orders, Sales and Commissions. The format of the document varies however. This document contains the EDI Mapping Specifications for each type of data. We will reject any document that is not valid EDI per the ANSI X12 specifications. EDI documents are posted using an HTML form, or an equivalent automated process (raw EDI is not accepted). See data sample later in this guide.

Functional Acknowledgment The 997 Functional Acknowledgment is used by Quixtar to verify receipt of documents sent by our trading partners. Quixtar will acknowledge each document by the group (GS) and set (ST) control numbers sent on the 867 document. Acknowledgments are returned within 12 hours after the receipt of your 867. If you do not receive an acknowledgment within that time frame, please contact the Integration Center (616-787-1648 or integrationcenter@accessbusinessgroup.com) within 24 hours from your transmission date. If you receive a rejected or partial acknowledgment, you need to correct the error and resend only the 867s that were rejected. In some cases, the 997 cannot be returned (i.e., 867 is transmitted via FTP). If that is the case, you will receive an EMAIL acknowledgment of failed documents only. It is your responsibility to ensure that your company’s SPAM blocker will permit messages from Quixtar and that your EMAIL addresses are valid and current. Please provide an EMAIL address for a group rather than individual people.

Communication What is the method of transmission? Access Business Group maintains a B2B Gateway open to Internet traffic which will handle sending and receiving the XML or EDI documents for Quixtar’s Merchant Partners. This system can be accessed via an HTTPS* post to a proxy server located inside our DMZ**. We require that posts be made via SSL*** to protect your data. External firewall holes will have to be configured to allow you access to this server. See Appendix A for the B2B HTTPS SETUP document that will enable us to set up access to the proxy server. It also provides our URL information so you can set up your communications. There are no return documents defined except for the X12 997. Errors will be returned via email to the address you specify. If you opt to deliver EDI documents via EDIINT (AS/2)****, we will need to exchange certificates and you will post to a different URL. Note that using EDIINT is via HTTP not HTTPS, so your userid and password are unencrypted, and visible to anyone snooping the data traffic (Such an entity could then post any data as you).

* The HTTP protocol layered over the Secure Socket Layer (SSL) protocol to allow secure data transfer using encrypted data streams.

** Abbreviation for "Secure Sockets Layer". SSL is a transaction security standard that provides data encryption, server authentication, and message integrity.

*** DMZ (demilitarized zone) is a computer host or small network inserted as a "neutral zone" between a company's private network and the outside public network. It prevents outside users from getting direct access to a server that has company data.

****AS2 (Applicability Statement 2) is a specification for Electronic Data Interchange (EDI) between businesses using the Internet's Web page protocol, the Hypertext Transfer Protocol (HTTP). Security, authentication, message integrity, and privacy are assured by the use of encryption and digital signatures. Another important feature, non-repudiation, makes it impossible for the intended recipient of a message to deny having received it.

HTTP Specifics: Http headers need to be set with the following name/value pair: Content-Type = ‘text/xml’ if sending xml Content-Type = ‘plain/text” if sending unformatted flat files A response will be returned on all posts which will confirm that a transmission has been successfully received. Partners need to check the Http Response Status Code from our server. If it is not 200, you must resend the document . If a successful response is not received, it will be your responsibility to retransmit the document. What mechanism you use to post the document to us is your choice. We require an email address for our system to return errors to you. The HTTP response 200 merely says we successfully received your document. It does not guarantee that we processed it. If we encounter problems with the format of the data, we will send an email to the specified email address to inform you of the problem.

Sample HTML File to send EDI (867) document to QA server: <HTML> <Body bgcolor="#00AAFF"> <FORM action="https://test.e-abg.com:443/invoke/wm.tn/receive" method=post> <center> <H2>Access Business Group</H2> <h3>This web page is used to send test EDI to https://test.e-abg.com:443/invoke/wm.tn/receive</H3> </center> <TABLE> <TBODY> <TR> <TD><INPUT type=Submit name="Submit EDI" value=Submit> <B><I><FONT color=white> EDI:</FONT></I></B> </TD></TR> <TR> <TD><TEXTAREA cols=100 name=edidata rows=20></TEXTAREA> </TD></TR></TBODY></TABLE></FORM> <b> <FORM action="https://test.e-abg.com:443/invoke/wm.server/disconnect" method=post> If you post multiple partner's data, after posting each one, go back to this page and <INPUT type=Submit name="Click Here" value=Logout><br> After logging out, then go back here again to post the next partner's data. <p> Note: This web page is provided as is. Its usage, modification, and security of it, are not the responsibility of Alticor, Access Business Group, or Quixtar. This page is a template example of how partner data may be handled via a web page running on a partner's server. This web page is only useful from servers which Alticor has recognized as authenticated servers, and will not function from any other machine. Please contact the Quixtar Integration Center for further information or if you have any questions about posting data to us. (616)787-1648 or IntegrationCenter@Quixtar.com </BODY> </HTML>

Sample HTML File to send EDI(867) document to production server: <HTML> <Body bgcolor="#00AAFF"> <FORM action="https://www.e-abg.com:443/invoke/wm.tn/receive" method=post> <center> <H2>Access Business Group</H2> <h3>This web page is used to send EDI to https://www.e-abg.com:443/invoke/wm.tn/receive</H3> </center> <TABLE> <TBODY>

<TR> <TD><INPUT type=Submit name="Submit EDI" value=Submit> <B><I><FONT color=white> EDI:</FONT></I></B> </TD></TR> <TR> <TD><TEXTAREA cols=100 name=edidata rows=20></TEXTAREA> </TD></TR></TBODY></TABLE></FORM> <b> <FORM action="https://www.e-abg.com:443/invoke/wm.server/disconnect" method=post> If you post multiple partner's data, after posting each one, go back to this page and <INPUT type=Submit name="Click Here" value=Logout><br> After logging out, then go back here again to post the next partner's data. <p> Note: This web page is provided as is. Its usage, modification, and security of it, are not the responsibility of Alticor, Access Business Group, or Quixtar. This page is a template example of how partner data may be handled via a web page running on a partner's server. This web page is only useful from servers which Alticor has recognized as authenticated servers, and will not function from any other machine. Please contact the Quixtar Integration Center for further information or if you have any questions about posting data to us. (616)787-1648 or IntegrationCenter@Quixtar.com </BODY> </HTML>

Portal Support for Partners There are currently a series of web pages available for partners to submit documents and view documents. The web page to view documents is https://www.e-abg.com:/WmTNWeb/ for production, and https://test.e-abg.com:/WmTNWeb/ for test. You must enter your posting userid and password when prompted. Your userid may be different that the id used by the application (such as a Quixtar Merchant Partner ID). If you do not know, or have forgotten your userid or password, please contact the Integration Center at 616-787-1648 or IntegrationCenter@Quixtar.com Near the upper right hand corner of the page is a link for help in using this page. Clicking on the Analysis/Transactions link will bring up a page where you can specify your selection criteria for searching for documents (we only maintain the last 45 days of data on the system). If you want to submit an EDI document, the link for production is https://www.e-abg.com:/WmEDIforTN/submitEDI.html and the link for test is https://test.e-abg.com:/WmEDIforTN/submitEDI.html Again you will have to authenticate with your userid and password. Paste in your valid EDI data, and change the http://localhost:5555/invoke/wm.tn/receive to https://www.e-abg.com/invoke/wm.tn/receive or https://test.e-abg.com/invoke/wm.tn/receive Click on "Submit"

1 EDI Commission Data (X12 4010 867)

867 Product Transfer and Resale Report

Functional Group ID=PT Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to: (1) report information about product that has been transferred from one location to another; (2) report sales of product from one or more locations to an end customer; or (3) report sales of a product from one or more locations to an end customer, and demand beyond actual sales (lost orders). Report may be issued by either buyer or seller. Notes: Commissions are the result of the billing and collection process. Commission Data will contain only those records where collection or refund has occurred and will be transmitted monthly to Amway/Quixtar. Sample Data: ISA~00~ ~00~ ~01~9012345720000 ~01~9088877320000~000706~092 0~U~00200~000000001~0~T~:| GS~PT~901234572000~908887732000~000706~0920~1~T~004010| ST~867~0001| BPT~18~~20000706| CUR~VN~CAD| REF~VR~392039493020342| PTD~DS~~~IV~1234567890098765432176895| DTM~003~20000706| DTM~194~20000706| DTM~324~20000706| REF~11~~123456789012345| REF~U5~~987654321098765| REF~PD~~1234| QTY~01~100| LIN~~ZZ~SKU1234567890| AMT~LP~250| REF~44~612-555-1212| CTT~1| AMT~TS~250| SE~16~0001| GE~1~1| IEA~1~000000001|

Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BPT Beginning Segment for Product Transfer and

Resale M 1

Must Use 040 CUR Currency O 1 060 REF Reference Identification O 12 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - PTD >1 M 010 PTD Product Transfer and Resale Detail M 1 Must Use 020 DTM Date/Time Reference O 10 020 DTM Date/Time Reference O 10 020 DTM Date/Time Reference O 10 Must Use 030 REF Reference Identification O 20 030 REF Reference Identification O 20 030 REF Reference Identification O 20 LOOP ID - QTY >1 Must Use 110 QTY Quantity O 1 Must Use 120 LIN Item Identification O 1 Must Use 140 AMT Monetary Amount O 12 190 REF Reference Identification O >1 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - CTT 1 Must Use 010 CTT Transaction Totals O 1 n1 Must Use 020 AMT Monetary Amount O 12 M 030 SE Transaction Set Trailer M 1

Transaction Set Notes 1. The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is

the sum of the value of quantities (QTY02) for each QTY segment.

Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 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).

Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 867 Product Transfer and Resale Report M ST02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set

functional group assigned by the originator for a transaction set

Segment: BPT Beginning Segment for Product Transfer and Resale Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit

identifying data Syntax Notes: 1 If either BPT05 or BPT06 is present, then the other is required. Semantic Notes: 1 BPT02 identifies the transfer/resale number. 2 BPT03 identifies the transfer/resale date. 3 BPT08 identifies the transfer/resale time. 4 BPT09 is used when it is necessary to reference a Previous Report Number. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M BPT01 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 18 Reissue Commissions or Recurring Charges M BPT03 373 Date M DT 8/8 Date expressed as CCYYMMDD File Creation Date. The date the 867 Transaction Set was created.

Segment: CUR Currency Position: 040 Loop: Level: Heading Usage: Optional (Must Use) Max Use: 1 Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: 1 If CUR08 is present, then CUR07 is required. 2 If CUR09 is present, then CUR07 is required. 3 If CUR10 is present, then at least one of CUR11 or CUR12 is required. 4 If CUR11 is present, then CUR10 is required. 5 If CUR12 is present, then CUR10 is required. 6 If CUR13 is present, then at least one of CUR14 or CUR15 is required. 7 If CUR14 is present, then CUR13 is required. 8 If CUR15 is present, then CUR13 is required. 9 If CUR16 is present, then at least one of CUR17 or CUR18 is required. 10 If CUR17 is present, then CUR16 is required. 11 If CUR18 is present, then CUR16 is required. 12 If CUR19 is present, then at least one of CUR20 or CUR21 is required. 13 If CUR20 is present, then CUR19 is required. 14 If CUR21 is present, then CUR19 is required. Semantic Notes: Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.

Data Element Summary Ref. Data Des. Element Name Attributes M CUR01 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an

individual VN Vendor M CUR02 100 Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified CAD Canada USD United States

Segment: REF Reference Identification Position: 060 Loop: Level: Heading Usage: Optional Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification VR Vendor ID Number REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Merchant Partner ID - 15 characters

This is required unless the ISA Partner ID = Merchant Partner ID

Segment: PTD Product Transfer and Resale Detail Position: 010 Loop: PTD Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To indicate the start of detail information relating to the transfer/resale of a product and provide

identifying data Syntax Notes: 1 If either PTD02 or PTD03 is present, then the other is required. 2 If either PTD04 or PTD05 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M PTD01 521 Product Transfer Type Code M ID 2/2 Code identifying the type of product transfer BN Return DS Drop Ship Sale PTD04 128 Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification IV Seller's Invoice Number PTD05 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Unique Order/Invoice or Return/Credit ID. Up to 25 characters. If all or

part of a commission is returned, a Unique Invoice Number MUST be provided.

Segment: DTM Date/Time Reference Position: 020 Loop: PTD Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 003 Invoice Date invoice was created (Billing Date) DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD

Segment: DTM Date/Time Reference Position: 020 Loop: PTD Mandatory Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 2 If DTM04 is present, then DTM03 is required. 3 If either DTM05 or DTM06 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 194 Period End Billed Through Date DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD

Notes: Mandatory only when PTD01=BN

Data Element Summary

Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 324 Returned Date of Return DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD

Segment: REF Reference Identification Position: 030 Loop: PTD Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 20 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 11 Account Number Number identifies a telecommunications industry account REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content Customer's Unique ID Number/Account Number (15 Characters)

Segment: REF Reference Identification Position: 030 Loop: PTD Mandatory Level: Detail Usage: Optional Max Use: 20 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Notes: Mandatory for each Sub Account

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification U5 Successor Account REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content Customer's Sub Account Number (15 Characters)

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification PD Promotion/Deal Number REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content Not to exceed 4 characters

Segment: QTY Quantity Position: 110 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To specify quantity information Syntax Notes: 1 At least one of QTY02 or QTY04 is required. 2 Only one of QTY02 or QTY04 may be present. Semantic Notes: 1 QTY04 is used when the quantity is non-numeric. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 01 Discrete Quantity QTY02 380 Quantity X R 1/15 Numeric value of quantity Can be defaulted to one.

Segment: LIN Item Identification Position: 120 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required. 2 If either LIN06 or LIN07 is present, then the other is required. 3 If either LIN08 or LIN09 is present, then the other is required. 4 If either LIN10 or LIN11 is present, then the other is required. 5 If either LIN12 or LIN13 is present, then the other is required. 6 If either LIN14 or LIN15 is present, then the other is required. 7 If either LIN16 or LIN17 is present, then the other is required. 8 If either LIN18 or LIN19 is present, then the other is required. 9 If either LIN20 or LIN21 is present, then the other is required. 10 If either LIN22 or LIN23 is present, then the other is required. 11 If either LIN24 or LIN25 is present, then the other is required. 12 If either LIN26 or LIN27 is present, then the other is required. 13 If either LIN28 or LIN29 is present, then the other is required. 14 If either LIN30 or LIN31 is present, then the other is required. Semantic Notes: 1 LIN01 is the line item identification Comments: 1 See the Data Dictionary for a complete list of IDs. 2 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.

Data Element Summary Ref. Data Des. Element Name Attributes M LIN02 235 Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in

Product/Service ID (234) ZZ Mutually Defined M LIN03 234 Product/Service ID M AN 1/48 Identifying number for a product or service Product Type - Class of service or SKU.

Segment: AMT Monetary Amount Position: 140 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 12 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments:

Notes: List Price is required (AMT01=LP)

Data Element Summary Ref. Data Des. Element Name Attributes M AMT01 522 Amount Qualifier Code M ID 1/3 Code to qualify amount CX Actual Actual IBO Cost (Cost of product to distributor) LP List Price Net sale amount of the customer's order in dollars.

This does NOT include tax, shipping, and/or postage. OU Profit IBO Profit PB Billed Amount Total amount due on the period bill Full billing for entire month; Retail amount to

customer VO Commission Earned This is the amount Amway will receive from the billing YL Partial Annuitization Pro-rated or Partial Bill Amount M AMT02 782 Monetary Amount M R 1/18 Monetary amount The amount in dollars. Will be negative on returns. Sign is leading and

positive is assumed if not present.

Segment: REF Reference Identification Position: 190 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 44 End Use Number Represents the final use or form of the material being

manufactured or sold REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier This number is specific to services that require a number or code to access

(i.e. phone number, ordinal number, etc.).

Segment: CTT Transaction Totals Position: 010 Loop: CTT Optional (Must Use) Level: Summary Usage: Optional (Must Use) Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and

correctness.

Data Element Summary Ref. Data Des. Element Name Attributes M CTT01 354 Number of Line Items M N0 1/6 Total number of line items in the transaction set Number of orders (count total number of QTY segments within the

transaction).

Segment: AMT Monetary Amount Position: 020 Loop: CTT Optional (Must Use) Level: Summary Usage: Optional (Must Use) Max Use: 12 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M AMT01 522 Amount Qualifier Code M ID 1/3 Code to qualify amount TS Total Sales The total of commission and non commission sales

needed to calculate intersell amount M AMT02 782 Monetary Amount M R 1/18 Monetary amount Return the total sum of the values of list price (LP) not including tax,

shippping, and/or postage from the AMT01 LP element.

Segment: SE Transaction Set Trailer Position: 030 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments

(including the beginning (ST) and ending (SE) segments) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set.

Data Element Summary Ref. Data Des. Element Name Attributes M SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE

segments M SE02 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set

2 EDI Order Data (X12 4010 867) 867 Product Transfer and Resale Report

Functional Group ID=PT Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to: (1) report information about product that has been transferred from one location to another; (2) report sales of product from one or more locations to an end customer; or (3) report sales of a product from one or more locations to an end customer, and demand beyond actual sales (lost orders). Report may be issued by either buyer or seller. Notes: Order Status data is a daily collection of all new, changed, or cancelled orders (registrations). This data is sent to Amway/Quixtar and processed to permit basic customer service inquiry and provide a basis for recurring charges/commissions. Sample Data: ISA~00~ ~00~ ~01~9012345720000 ~01~9088877320000~000705~170 4~U~00200~000000001~0~T~:| GS~PT~901234572000~908887732000~000705~1704~1~T~004010| ST~867~0001| BPT~08~~20000705| REF~VR~392039493020342| PTD~SC~~~7G~A7733| DTM~771~20000705| DTM~007~20000815~~~UN~QMBR| DTM~ZZZ~20000820| REF~11~~123456789012345| REF~U5~~987654321098765| N1~53~ARTHUR JONES~12~9012345918341| N3~PO BOX 123~157 WEST 57TH STREET| N4~CINCINNATI~OH~43017~US| PER~CW~~EM~ARTHUR@JONES.COM| N1~DS~BEVERLY SIMPSON~MI~111222333| QTY~01~1| REF~44~614-555-1212| CTT~1| SE~19~0001| GE~1~1| IEA~1~000000001|

Resale M 1

060 REF Reference Identification O 12 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - PTD >1 M 010 PTD Product Transfer and Resale Detail M 1 Must Use 020 DTM Date/Time Reference O 10 020 DTM Date/Time Reference O 10 020 DTM Date/Time Reference O 10 Must Use 030 REF Reference Identification O 20 030 REF Reference Identification O 20 LOOP ID - N1 5 Must Use 050 N1 Name O 1 Must Use 070 N3 Address Information O 2 Must Use 080 N4 Geographic Location O 1 100 PER Administrative Communications Contact O 3 LOOP ID - N1 5 Must Use 050 N1 Name O 1 LOOP ID - QTY >1 110 QTY Quantity O 1 190 REF Reference Identification O >1

Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - CTT 1 010 CTT Transaction Totals O 1 n1 M 030 SE Transaction Set Trailer M 1

Transaction Set Notes 1. The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is

Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M BPT01 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 08 Status Order Status (Registration) Data M BPT03 373 Date M DT 8/8 Date expressed as CCYYMMDD File Creation Date. The date the 867 Transaction Set was created.

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification VR Vendor ID Number REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Merchant Partner ID - 15 characters

This is required unless the ISA Partner ID = Merchant Partner ID

Data Element Summary Ref. Data Des. Element Name Attributes M PTD01 521 Product Transfer Type Code M ID 2/2 Code identifying the type of product transfer BK Modification Order Status Change BQ Other Issue from inventory, when a specific reason type is not

otherwise provided Order Status Expired DS Drop Ship Sale Sale - Order Status Add RA Reapplication of Order Reactivate Order SC Scrap Order Status Cancellation PTD04 128 Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification Use only when PTD01=SC 7G Data Quality Reject Reason PTD05 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Cancel Reason Code (5 char max)

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 771 Status DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 007 Effective Must Use DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD Must Use DTM05 1250 Date Time Period Format Qualifier X ID 2/3 Code indicating the date format, time format, or date and time format UN Unstructured Must Use DTM06 1251 Date Time Period X AN 1/35 Expression of a date, a time, or range of dates, times or dates and times Used to identify a vendor specific number (i.e., QMBR, AMB, QXR). Not to

exceed 15 characters.

Data Element Summary Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time ZZZ Mutually Defined Used for partner specific date. DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD

Segment: REF Reference Identification Position: 030 Loop: PTD Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 20 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 11 Account Number Number identifies a telecommunications industry account REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content Customer's Unique ID Number or Account Number (15 characters)

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification U5 Successor Account REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content Customer's Unique Sub Account Number (15 characters)

Segment: N1 Name Position: 050 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 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.

2 N105 and N106 further define the type of entity in N101.

Data Element Summary Ref. Data Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an

individual 53 Registered Owner Unique code of entity owning the equipment N102 93 Name X AN 1/60 Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification

Code (67) 12 Telephone Number (Phone) N104 67 Identification Code X AN 2/80 Code identifying a party or other code

Segment: N3 Address Information Position: 070 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M N301 166 Address Information M AN 1/55 Address information N302 166 Address Information O AN 1/55 Address information

Segment: N4 Geographic Location Position: 080 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a

location. 2 N402 is required only if city name (N401) is in the U.S. or Canada.

Data Element Summary Ref. Data Des. Element Name Attributes N401 19 City Name O AN 2/30 Free-form text for city name N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks

(zip code for United States) N404 26 Country Code O ID 2/3 Code identifying the country

Segment: PER Administrative Communications Contact Position: 100 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M PER01 366 Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named CW Confirmed With PER03 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number EM Electronic Mail PER04 364 Communication Number X AN 1/80 Complete communications number including country or area code when

applicable

2 N105 and N106 further define the type of entity in N101.

individual DS Distributor N102 93 Name X AN 1/60 Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification

Code (67) MI Member Identification Number N104 67 Identification Code X AN 2/80 Code identifying a party or other code

Segment: QTY Quantity Position: 110 Loop: QTY Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify quantity information Syntax Notes: 1 At least one of QTY02 or QTY04 is required. 2 Only one of QTY02 or QTY04 may be present. Semantic Notes: 1 QTY04 is used when the quantity is non-numeric. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 01 Discrete Quantity QTY02 380 Quantity X R 1/15 Numeric value of quantity Can be defaulted to one.

Segment: REF Reference Identification Position: 190 Loop: QTY Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 44 End Use Number Represents the final use or form of the material being

manufactured or sold REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier This number is specific to services that require a number or code to access

(i.e. phone number, ordinal number, etc.).

Segment: CTT Transaction Totals Position: 010 Loop: CTT Optional Level: Summary Usage: Optional Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and

correctness.

transaction).

3 EDI Sales Data (X12 4010 867) 867 Product Transfer and Resale Report

Functional Group ID=PT Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to: (1) report information about product that has been transferred from one location to another; (2) report sales of product from one or more locations to an end customer; or (3) report sales of a product from one or more locations to an end customer, and demand beyond actual sales (lost orders). Report may be issued by either buyer or seller. Notes: Sales are the result of an actual sale of an item. Sales Data will contain only those records where a shipment or return has occurred. This data is reported to Amway/Quixtar monthly. Sample Data: ISA~00~ ~00~ ~01~9012345720000 ~01~9088877320000~000705~170 2~U~00200~000000001~0~T~:| GS~PT~901234572000~908887732000~000705~1702~1~T~004010| ST~867~0001| BPT~53~~20000705| CUR~VN~CAD| REF~VR~392039493020342| PTD~DS~~~IV~1234567890098765432176895| DTM~003~20000705| REF~SO~~123456789012345| REF~PD~~1234| N1~DS~MAGGIE MCGILLICUTTY~MI~90123459183| PER~CW~~EM~MAGGIE@MCGILLICUTTY.COM| N1~ST~BEVERLY SIMPSON~12~614-555-1212| N3~PO BOX 123~157 WEST 57TH STREET| N4~CINCINNATI~OH~43017~US| QTY~01~1| AMT~LP~100.01| ITA~C~~~06~~~360~~~~~~~SAB| CTT~1| AMT~TS~100.01| SE~18~0001| GE~1~1| IEA~1~000000001|

Resale M 1

Must Use 040 CUR Currency O 1 060 REF Reference Identification O 12 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - PTD >1 M 010 PTD Product Transfer and Resale Detail M 1 Must Use 020 DTM Date/Time Reference O 10 030 REF Reference Identification O 20 030 REF Reference Identification O 20 LOOP ID - N1 5 Must Use 050 N1 Name O 1 Must Use 100 PER Administrative Communications Contact O 3 LOOP ID - N1 5 Must Use 050 N1 Name O 1 Must Use 070 N3 Address Information O 2 Must Use 080 N4 Geographic Location O 1 LOOP ID - QTY >1 Must Use 110 QTY Quantity O 1 Must Use 140 AMT Monetary Amount O 12 141 ITA Allowance, Charge or Service O 10

Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

LOOP ID - CTT 1 Must Use 010 CTT Transaction Totals O 1 n1 Must Use 020 AMT Monetary Amount O 12 M 030 SE Transaction Set Trailer M 1 Transaction Set Notes 1. The number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is

Comments:

Notes:

Ref. Data Des. Element Name Attributes M BPT01 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 53 Completion M BPT03 373 Date M DT 8/8 Date expressed as CCYYMMDD File Creation Date. The date the 867 Transaction Set was created.

Segment: CUR Currency Position: 040 Loop: Level: Heading Usage: Optional (Must Use) Max Use: 1 Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: 1 If CUR08 is present, then CUR07 is required. 2 If CUR09 is present, then CUR07 is required. 3 If CUR10 is present, then at least one of CUR11 or CUR12 is required. 4 If CUR11 is present, then CUR10 is required. 5 If CUR12 is present, then CUR10 is required. 6 If CUR13 is present, then at least one of CUR14 or CUR15 is required. 7 If CUR14 is present, then CUR13 is required. 8 If CUR15 is present, then CUR13 is required. 9 If CUR16 is present, then at least one of CUR17 or CUR18 is required. 10 If CUR17 is present, then CUR16 is required. 11 If CUR18 is present, then CUR16 is required. 12 If CUR19 is present, then at least one of CUR20 or CUR21 is required. 13 If CUR20 is present, then CUR19 is required. 14 If CUR21 is present, then CUR19 is required. Semantic Notes: Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.

Notes:

Data Element Summary Ref. Data Des. Element Name Attributes M CUR01 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an

individual VN Vendor M CUR02 100 Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified CAD Canada USD United States

Notes:

Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification VR Vendor ID Number REF02 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Quixtar's Merchant Partner ID - 15 characters

This is required unless the ISA Partner ID = Quixtar's Merchant Partner ID

Notes:

Ref. Data Des. Element Name Attributes M PTD01 521 Product Transfer Type Code M ID 2/2 Code identifying the type of product transfer BN Return DS Drop Ship Sale Original order PTD04 128 Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification IV Seller's Invoice Number PTD05 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier Merchant Partners Unique Order/Invoice or Return/Credit ID. Up to 25

characters. This is the tracking number the merchant provides the customer to identify the order. If all or part of an order is returned, a Unique Invoice Number MUST be provided.

Notes:

Ref. Data Des. Element Name Attributes M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 003 Invoice Billing Date 004 Purchase Order 324 Returned DTM02 373 Date X DT 8/8 Date expressed as CCYYMMDD

Notes:

Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification SO Shipper's Order (Invoice Number) REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content This can be either the PO number or a tracking number from when the order

was placed on the web. 15 characters.

Notes:

Ref. Data Des. Element Name Attributes M REF01 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification PD Promotion/Deal Number REF03 352 Description X AN 1/80 A free-form description to clarify the related data elements and their content Not to exceed 4 characters

2 N105 and N106 further define the type of entity in N101. Notes:

individual DS Distributor N102 93 Name X AN 1/60 Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification

Code (67) MI Member Identification Number N104 67 Identification Code X AN 2/80 Code identifying a party or other code This field MUST contain the Distributor ID Number (11 digits).

Segment: PER Administrative Communications Contact Position: 100 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. 3 If either PER07 or PER08 is present, then the other is required. Semantic Notes: Comments:

Notes:

Ref. Data Des. Element Name Attributes M PER01 366 Contact Function Code M ID 2/2 Code identifying the major duty or responsibility of the person or group named CW Confirmed With PER03 365 Communication Number Qualifier X ID 2/2 Code identifying the type of communication number EM Electronic Mail PER04 364 Communication Number X AN 1/80 Complete communications number including country or area code when

applicable Distributor's e-mail address

2 N105 and N106 further define the type of entity in N101. Notes:

Ref. Data Des. Element Name Attributes M N101 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an

individual ST Ship To N102 93 Name X AN 1/60 Free-form name N103 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification

Code (67) 12 Telephone Number (Phone) N104 67 Identification Code X AN 2/80 Code identifying a party or other code Ship to customer's telephone number

Segment: N3 Address Information Position: 070 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:

Notes:

Ref. Data Des. Element Name Attributes M N301 166 Address Information M AN 1/55 Address information N302 166 Address Information O AN 1/55 Address information

Segment: N4 Geographic Location Position: 080 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is required. Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a

location. 2 N402 is required only if city name (N401) is in the U.S. or Canada.

Notes:

Ref. Data Des. Element Name Attributes N401 19 City Name O AN 2/30 Free-form text for city name N402 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N403 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks

(zip code for United States) N404 26 Country Code O ID 2/3 Code identifying the country

Segment: QTY Quantity Position: 110 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Purpose: To specify quantity information Syntax Notes: 1 At least one of QTY02 or QTY04 is required. 2 Only one of QTY02 or QTY04 may be present. Semantic Notes: 1 QTY04 is used when the quantity is non-numeric. Comments:

Notes:

Ref. Data Des. Element Name Attributes M QTY01 673 Quantity Qualifier M ID 2/2 Code specifying the type of quantity 01 Discrete Quantity QTY02 380 Quantity X R 1/15 Numeric value of quantity Can be defaulted to one.

Segment: AMT Monetary Amount Position: 140 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 12 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments:

Notes: List Price is required (AMT01=LP)

Ref. Data Des. Element Name Attributes M AMT01 522 Amount Qualifier Code M ID 1/3 Code to qualify amount CX Actual Actual IBO Cost (Cost of product to distributor) LP List Price The net sale amount of the customer's order in dollars.

This does NOT include tax, shipping and/or postage. PB Billed Amount Total amount due on the period bill Full billing for entire month; retail amount to

customer M AMT02 782 Monetary Amount M R 1/18 Monetary amount The amount in dollars. Will be negative on returns. Sign is leading, and

positive is assumed if not present.

Segment: ITA Allowance, Charge or Service Position: 141 Loop: QTY Optional (Must Use) Level: Detail Usage: Optional Max Use: 10 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If either ITA10 or ITA11 is present, then the other is required. 4 If ITA15 is present, then ITA02 is required. 5 If ITA17 is present, then ITA12 is required. Semantic Notes: 1 ITA09 is the allowance or charge percent. 2 ITA10 is the quantity basis when the allowance or charge quantity is different from the

purchase order or invoice quantity. 3 ITA12 is the quantity of free goods. Comments: 1 If ITA01 equals "A" - allowance or "C" - charge, then at least one of ITA06, ITA07, or ITA08

must be present. 2 ITA02 identifies the source of the code value in ITA03 or ITA15. 3 If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence. 4 ITA13 is used to clarify the allowance, charge, or service. 5 ITA15 specifies the individual code list of the agency specified in ITA02. 6 ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment.

Notes:

Ref. Data Des. Element Name Attributes M ITA01 248 Allowance or Charge Indicator M ID 1/1 Code which indicates an allowance or charge for the service specified C Charge M ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2 Code indicating method of handling for an allowance or charge 06 Charge to be Paid by Customer ITA07 360 Allowance or Charge Total Amount O N2 1/15 Total dollar amount for the allowance or charge Two decimal positions assumed, no decimal allowed. ITA14 150 Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance SAB Shipping and Handling SST Sales Tax (State and Local)

Segment: CTT Transaction Totals Position: 010 Loop: CTT Optional (Must Use) Level: Summary Usage: Optional (Must Use) Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and

correctness.

transaction).

Segment: AMT Monetary Amount Position: 020 Loop: CTT Optional (Must Use) Level: Summary Usage: Optional (Must Use) Max Use: 12 Purpose: To indicate the total monetary amount Syntax Notes: Semantic Notes: Comments:

Data Element Summary Ref. Data Des. Element Name Attributes M AMT01 522 Amount Qualifier Code M ID 1/3 Code to qualify amount TS Total Sales The total of commission and non commission sales

needed to calculate intersell amount M AMT02 782 Monetary Amount M R 1/18 Monetary amount Return the total sum of the values of list price (LP) not including tax,

shippping, and/or postage from the AMT01 LP element.

Appendix A – B2B Setup Please provide the following information about your TEST server. Company Name: ____________________________________________ Contact Name: _____________________________________________ Contact Phone: _____________________________________________ Contact e-Mail: _____________________________________________ Host Name: ____________________________________________

(for example, https://testserver.mymerchant.com)

Outbound Static IP Address: ___________________________________________ (address ABG will receive from, for example, 12.345.678.90)

Inbound Email Address :________________________

(Address Quixtar sends errors to; for example: monitored@myco.com) It is your responsibility to ensure that your company’s SPAM blocker will permit messages from Quixtar and that your EMAIL addresses are valid and current. Please provide an EMAIL address for a group rather than individual people. Access User ID: ___________________________________________

(User name our server will give when logging onto your server. Required for EDI/997 to be returned.)

Access Password: __________________________________________ (Password our server will give when logging onto your server)

Access Business Group information for sending EDI documents: Test Server Host Name: test.e-abg.com EDI URL: https://test.e-abg.com:443/invoke/wm.tn/receive EDIINT URL: http://test.e-abg.com:4080/invoke/B2BUtil.inbound.EDIINT/receive Trading Partner User ID: Trading Partner Password: (to be provided separately)

Production Server Host Name: www.e-abg.com URL EDI URL: https://www.e-abg.com:443/invoke/wm.tn/receive EDIINT URL: https://www.e-abg.com:4080/invoke/B2BUtil.inbound.EDIINT/receive Trading Partner User ID: Trading Partner Password: (to be provided separately)

edi implementation guide business... · x12 specifications. edi documents are posted using an html...

Documents

edi implementation guide 830 ansi x12 v4010 … aiag 830 rev...

b2bgateway edi for freestyle commerce...

title: representation of x12 data elements and · web...

implementation guidelines for ansi asc x12 edi...

coupa x12 edi 810 invoice specifications

california electronic data interchange (edi ... electronic...

etendering international standards project - jacic ·...

introduction ansi x12 standards - global health care ·...

advance ship notice message ansi x12 asn 856 · pdf...

implementation guidelines for ansi asc x12 edi conventions...

edi for contract manufacturers - b2bgateway.net · ansi x12...

implementation guidelines for ansi asc x12 edi conventions...

electronic data interchange (edi) - bnsf railway€¦ ·...

ansi asc x12 - edi systems | edi software | … asc x12 edi...

implementation guidelines for ansi asc x12 edi conventions...

edi x12 transaction set index

ansi asc x12 edi transactions for supply chain and

electronic data interchange (edi) course · trade (edifact)...

implementation guidelines for ansi asc x12 edi …

auria edi implementation guide for ver 3060 x12 – 856 ·...