Implementation Guidelines

Transcription

1 Implementation Guidelines 870 Order Status 08/01/2016

2 Table of Contents q Electronic Commerce Information General contact and setup information you will need to properly set up Menards in your systems. q Business Rules 870 Order Status This outlines the general requirements and expectations of the program. Also presents the status codes accepted by Menards as well as when to use them. q Order Status Flow Chart This outlines the lifecycle of an order and when certain status codes are expected. q Trading Partner 870 Order Status Checklist This outlines the testing process and defines the scenarios to be tested. q Menard, Inc. ASC X12 (V4010) Mapping Specifications This is the EDI mapping specification for the 870 document. Any questions concerning the definition and/or use of these segments should be communicated immediately to avoid possible misunderstandings. q Menard, Inc. 870 Business Examples Generic examples of what the EDI data should look like are provided. q EDI Mapping Specifications Text Message These are the EDI mapping specifications for the 864 document. Any questions concerning the definition and/or use of any of the segments should be communicated immediately to avoid possible misunderstandings. q 864 Business Examples This is example data according to the 864 specifications provided Menard, Inc Menard Drive Eau Claire, WI Phone: (715) Fax: (715)

3 General Information: Electronic Commerce Information Address: Menard Inc Partners Website: Attn: EDI Dept Supplier Portal: Menard Drive Eau Claire WI Contacts: Brian Fechter EDI Coordinator Heidi Franko EDI Analyst Tyler Moldenhauer EDI Analyst Kirsten Sadler EDI Analyst Shirley Mance EDI Specialist Document Information: Standard: ASC X.12 Version / Release: Documents Presently Traded: 810 Invoice 856 Advance Ship Notice 850 Purchase Order 864 Text Message 852 Product Activity (VMI/SBT Programs Only) 870 Order Status Report 855 PO Acknowledgment (VMI Programs Only) 997 Functional Acknowledgment Transmission Information: Primary Value Added Network: If your company is unable to support direct AS2 connection please contact us for list of existing VAN connections your company may utilize to facilitate EDI communications with Menards. EDI/INT Software: BizManager v3.3 AS2 URL: AS2 ID: PAS2 AS2 IP Address: AS2 MDNs: Synchronous Encryption Algorithm: DES3 168 Signature Algorithm: SHA1 160 Authorization Information Qualifier (ISA 01): 03 Authorization Information (ISA 02): Internal Menards Vendor # Security Information Qualifier (ISA 03): 01 Security Information: (ISA 04): Internal Menards Vendor # Interchange ID Qualifier (ISA 05): 01 Interchange Sender ID (ISA 06): P Functional Group Sender ID (GS 02): Segment Delimiter: Element Delimiter: Sub Element Delimiter: ~ (7E) * (2A) > (3E)

4 BUSINESS RULES 870 ORDER STATUS EXPECTATIONS: We expect our vendors to provide status on all purchase orders received via EDI. We expect our vendors to provide an initial status update within 1 business day of the order being transmitted. We expect our vendors to provide shipment status by or before the date of physical receipt of the order. We expect our vendors to provide an 870 each time the status of an order changes or pertinent expected ship date information changes. We expect our vendors to provide status updates throughout the life of an order We expect our vendors to provide line item detail with their order status updates We expect our vendors to send status updates in a logical sequence. For example, we don t want an estimated shipment date after you ve already advised shipment of the product. We expect our vendors to monitor the following for the 870s sent: o 997s for acceptance or rejection. Rejections will require corrected 870 to be sent. o 864s for validation issues which will require corrected 870 to be sent. APPLICABLE STATUS CODES: Conditional statuses noted in table below are required when scenario is encountered for example you do not have the option to send a partial status update when/if you partially ship and order/item then you must provide the appropriate partial shipment update. CODE USE WHEN REQUIRED? IN In Process Sent if ED status date not known within 1 business day of Conditional Menards transmitting the order. ED should be sent ASAP afterwards. ED Expected Ship Date Sent when an expected ship date is known or previously Required provided expected ship date has changed for the order. Should be sent within 1 business day of the order being transmitted. PR Partial Shipment Sent when part of the order is being shipped with the Conditional remainder to follow on a future shipment. - If an order/item is being short shipped and there will be no future shipments, the corresponding CC or DD status should be provided on the order/item. - PR status should only be sent if future shipment(s) will be made against order/items. CC Shipped in full to Menard Sent when the order has shipped complete or the remainder Required of a partially shipped order has shipped complete to a Menards location. DD Shipped in full to Guest Sent when the order has shipped complete or the remainder Required of a partially shipped order has shipped complete to our guest or their jobsite location. DE Deleted/Canceled Order Confirmation that the order has been canceled in your system. Should be sent after communication of your intentions with the ordering location. Conditional NOTES: It is very important to provide timely and accurate information. Our team members have a system to review the data that you send to us should they want to check on the status of an order. Our guests can also review the status of their special orders online at In addition, we provide automated updates to our guests as status changes should our guests want to be notified in that manner. This is all a function of the 870 updates you supply to us.

5 BUSINESS RULES 870 ORDER STATUS An acceptable 870 Order Status document will contain valid data in all of the Mandatory segments below as well as the Conditional segments when the condition requires its use. Condition does not mean you have the option to send if scenario dictates it be included then it must be provided. Element Description Detail Usage Each 870 sent needs to have a unique report # provided. 870 s sent with BSR03 Report # duplicate report # s will be refused and require corrected update be sent. Mandatory REF02 VR Vendor # This element should contain your Menard Inc. assigned vendor #. Mandatory N102 OB Ordered By Location This should contain the value from the N102 - OB of the 850. Mandatory N102 ST Ship To Location This should contain the value from the N102 ST or BS of the 850. Mandatory PRF01 PO # PO # from the BEG03 of the 850. Mandatory ISR01 Status code Refer to available status codes referenced on previous page. Mandatory ISR02 Status date All status dates should be the date the status was reached with the exception of the ED status, the ED status date should be the expected ship date for the order not today as with the other status updates. Mandatory PO101 Sequence # Sequence # received in the PO101 of the 850 must be returned in the PO101 of the 870 for each line item. Mandatory PO102 Qty Order QTY from the PO102 of the 850 must be returned in the PO102 of the 870 for each line item, unless QTY adjustment has been agreed to. Mandatory PO103 Ordering UOM Ordering UOM from the PO103 of the 850 must be returned in the PO103 of the 870 for each line item. Mandatory PO107 Menards SKU # SKU # from the PO107 of the 850 must be returned in the PO107 of the 870 for each line item. Mandatory PO109 Vendor Part # Vendor assigned internal part # for the line item. Mandatory PID05 Item description Valid item description. Mandatory QTY01 Quantity qualifier - Use the 39 qualifier when an item has shipped - Use the QV qualifier when line item is being canceled. Conditional QTY02 Shipped or Canceled Qty - When QTY01=39, QTY02 should reference the QTY shipped. - When QTY=QV, QTY02 should reference the QTY canceled. Conditional N102 CN Contact name Vendor Contact name Conditional N104 CN Contact phone # 10 digit phone #: no dashes, parenthesis, or spaces Conditional TD505 Hauler name I.E. Fed Ex Ground Conditional REF01 Tracking Qualifier - Use the 2I qualifier for small parcel shipments (Fed Ex, etc) - Use the BM qualifier when shipping via common carrier - Use the AAO qualifier only when shipping via common carrier and BOL# is not available. Conditional Tracking # or - When Qual = 2I Small parcel tracking number Bill Of Lading # or - When Qual = BM Bill of Lading # REF02 Trailer # Use/provide only 1 qualifier / tracking number per line item. Conditional Conditional Notes: The QTY*39, N1, TD5, and REF segments are only used when there is a shipment status being provided. The QTY*QV should only be used when line item is being canceled.

6 High-Level Flow Order Transmitted to Vendor IN -In Process should be transmitted No Within 1business day, is Expected Ship Date known? Decision made/agreed to by both parties to cancel the order No Yes Is Expected Ship Date known? Yes ED -Expected Ship Date should be transmitted DE Deleted/ Canceled should be transmitted Shipment leaves for destination Was the order shipped complete, or remainder of order shipped? No PR -Partially Shipped should be transmitted. Item status should reflect PR, CC or DD. Yes CC -Shipped Complete should be transmitted Yes Is the order shipping to amenard location? No DD -Delivery Complete should be transmitted

7 Trading Partner 870 Order Status Checklist Listed below are the scenarios which will be tested the only exception being scenario s 4 and 5 only one or the other of 4 or 5 will be tested dependent on what current business arrangement is for handling of back orders for stock shipments. All test cases must be approved before a scenario receives a passing grade. We will provide sample 850 data to be used for the test 870 generation. Note: The intent of this section is for you to generate the requested statuses based on appropriate systematic triggers within your respective systems. Your assigned analyst will provide you with list of the test PO s along with which PO to use for each scenario. SCENARIO 1: Special order with unknown initial estimated shipping date Vendor receives a special order to be filled and shipped to a Menards location. Upon review, your internal stocking status is unclear as perhaps you are having trouble with a raw materials supplier. Since the estimated shipping status is not immediately known with confidence, an IN status is sent to Menards within 1 business day of transmission of the order. As soon as the estimated shipping date is known, an ED status is sent to Menards followed by the shipped complete status. SCENARIO 1 Test Case IN status at Order & Item level. ED status at Order & Item level. CC status at Order & Item level. Approved SCENARIO 2: Standard order with on-time delivery to Menards Vendor receives an order to be filled and shipped to a Menards location. Upon review, sufficient inventories are in place to meet the order request and the expectation is that the vendor will ship on time. The vendor submits an expected ship date status within 1 business day of transmission of the order and later submits a ship-complete status the day the product ships. SCENARIO 2 Test Case ED status at Order & Item level. CC status at Order & Item level. Approved

8 Trading Partner 870 Order Status Checklist SCENARIO 3: Special order with on-time delivery shipped direct to the Guest Vendor receives a special order to be filled and shipped directly to our Guest, not to a Menard Inc. location (note DD versus CC status code for the shipment update). Upon review, sufficient inventories are in place to meet the order request and the expectation is that the vendor will ship on time. The vendor submits an expected ship date status within 1 business day of transmission of the order and later submits a ship-complete status the day the product ships. SCENARIO 3 Test Case ED status at Order & Item level. DD status at Order & Item level. Approved SCENARIO 4: Cancel Backorder program. Standard order with on-time delivery to Menards shipped incomplete. Vendor receives an order to be filled and shipped to a Menards location. Upon review, adjustments need to be made such that the order will be shipped on time, but not in the requested quantities for logistical reasons. The vendor submits an expected ship date status within 1 business day of transmission of the order and later submits a ship-complete status the day the product ships but with one or more QTY s shipped < QTY ordered. SCENARIO 4 Test Case ED status at Order & Item level. CC status at Order & Item level. Approved SCENARIO 5: Accept Backorder program. Standard order with on-time delivery to Menards shipped incomplete. Backorder shipment will follow with remaining quantities. Vendor receives an order to be filled and shipped to a Menards location. The vendor submits an expected ship date status within 1 business day of transmission of the order. When it comes time to ship, there are insufficient quantities to fill the order request. The vendor submits a partial shipment status at time of initial shipment, and a ship-complete status when the remaining backorder is shipped to Menards. Plan to include at least one sku not shipped and a sku partially shipped at time of partial shipment. SCENARIO 5 Test Case ED status at Order & Item level. PR status at Order level, appropriate CC, PR, or ED at Item level. CC status at Order & Item level for remaining items. Approved

9 Trading Partner 870 Order Status Checklist SCENARIO 6: Accept Backorder program. Special order with on-time delivery to our Guest shipped incomplete. Backorder shipment will follow with remaining quantities. This scenario is identical to Scenario 5 except that the shipment is for a special order shipping direct to our Guest s home versus a Menard Inc location. SCENARIO 6 Test Case ED status at Order & Item level. PR status at Order level, appropriate DD, PR, or ED at Item level. DD status at Order & Item level for remaining items. Approved SCENARIO 7: Standard order with a revised estimated shipping date Vendor receives an order to be filled and shipped to a Menards location. Upon review, sufficient inventories are in place to meet the order request and the expectation is that the vendor will ship on time. The vendor submits an expected ship date status within 1 business day of transmission of the order. At some point in the future, it is determined that the order will have to ship later than expected. The vendor submits a revised expected ship date when known, and later submits a ship-complete status the day the product ships. SCENARIO 7 Test Case ED status at Order & Item level. ED status at Order & Item level with revised est. shipping date. CC status at Order & Item level. Approved SCENARIO 8: Canceled Special order Invalid information Vendor receives a special order to be filled and shipped to a Menards location. Upon review, the vendor determines there is not sufficient or accurate information to process the special order. Upon contacting the location that placed the order to discuss the situation, it is agreed that the order will be cancelled. Cancellation update is meant only to be a confirmation order has been cancelled cancellation status should NEVER be transmitted in effort to communicate an order/item needs to be cancelled, only that previously agreed order/item has officially been cancelled on your end. Test Case DE status at Order & Item level. SCENARIO 8 Approved

10 Trading Partner 870 Order Status Checklist SCENARIO 9: Canceled Special order Guest no longer wants product Vendor receives a special order to be filled and shipped to a Menards location. Upon review, sufficient inventories are in place to meet the order request and the expectation is that the vendor will ship on time. The vendor submits an expected ship date status within 1 business day of transmission of the order. Prior to the order being shipped, our Guest decides to cancel the order. The ordering location contacts the vendor to place the cancel request. The vendor transmits cancellation update as confirmation order has been cancelled on their end. Cancellation update is meant only to be a confirmation order has been cancelled cancellation status should NEVER be transmitted in effort to communicate an order/item needs to be cancelled, only that previously agreed order/item has officially been cancelled on your end. SCENARIO 9 Test Case ED status at Order & Item level. DE status at Order & Item level. Approved ADDITIONAL NOTES Your assigned analyst will request what specific update(s) to generate and submit for review and when please do not transmit or generate any of the 870 updates prior to being requested to do so. In some instances once the unit tests in this section have been successfully completed, we may request to enter into a parallel testing mode. This is essentially defined as production on your end, but the ISA15 will remain as a T for testing until the parallel period is over. The length of the parallel period will be a function of our volume together as well as any issues identified/noted corrections to be made. Is most cases the parallel testing period will be skipped. Upon completion of unit testing your assigned EDI Analyst will advise whether parallel testing period will be performed.

11 ASC X12 (V4010) Mapping Specifications 870 -Order Status (08/01/16) ISA- Interchange Control Header ISA01 I01 Authorization Information Qualifier ID 2/2 03 =Additional Data Information ISA02 I02 Authorization Information AN 10/10 Authorization ID (Menard assigned vendor #) ISA03 I03 Security Information Qualifier ID 2/2 01 =Password ISA04 I04 Security Information AN 10/10 Security Password (Menard assigned vendor #) ISA05 I05 Interchange ID Qualifier ID 2/2 Sender's ID Qualifier ISA06 I06 InterchangeSender ID AN 15/15 Sender's ID ISA07 I05 Interchange ID Qualifier ID 2/2 Receiver's ID Qualifier ISA08 I07 Interchange Receiver ID AN 15/15 Receiver's ID ISA09 I08 Interchange Date DT 6/6 YYMMDD ISA10 I09 Interchange Time TM 4/4 HHMM ISA11 I10 Interchange Control Standards Identifier ID 1/1 U = ASC X12 ISA12 I11 Interchange Control Version Number ID 5/ ISA13 I12 Interchange Control Number NO 9/9 Sender's Interchange Control Num ISA14 I13 Acknowledgment Requested ID 1/1 0= No Ack (TA1) Requested ISA15 I14 Test Indicator ID 1/1 P=Production Data, T=Test Data ISA16 I15 Component Element Separator AN 1/1 > GS -Functional Group Header GS Functional Identifier Code ID 2/2 RS = Order Status GS ApplicationSender's Code AN 2/15 Sender's Identifier GS Application Receiver's Code AN 2/15 Receiver's Identifier GS Date DT 8/8 Date (YYYYMMDD) GS Time TM 4/4 Time (HHMM) GS06 28 Group Control Number NO 1/9 Sender's Group Control Number GS Responsible Agency Code ID 1/2 X = ASC X12 GS Version/ Release/Industry Identifier Code AN 1/ ST -Transaction Set Header ST Transaction Set Identifier Code ID 3/3 870 = Order Status ST Transaction Set Control Number NO 4/9 Sender's Transaction Set Control Number BSR -Beginning Segment for Order Status Report BSR Status Report Code ID 1/2 3- Unsolicited Report BSR Order/Item Code ID 1/2 PA = Selectedorders -all items BSR Reference Identification AN 1/30 Status Report Document Number assigned by Sender BSR Date DT 8/8 Order Status Report Date (YYYYMMDD) EDI Mapping Specifications xls Page 1of 4

12 ASC X12 (V4010) Mapping Specifications 870 -Order Status (08/01/16) REF -Reference Identification REF Reference Identification Qualifier ID 2/2 VR =Vendor ID Number REF Reference Identification AN 4/8 Vendor Accounts Payable Number assigned by Menards Level 1Loop ID -N1 N1 -Ship To Location N Entity Identifier Code ID 2/3 ST = Ship To N Name AN 1/30 Return Ship to location received in N102 of the 850. N1 -Ordered By Location N Entity Identifier Code ID 2/3 OB = Ordered By N Name AN 1/30 Return Ordered By location received in N102 of the 850. End Loop ID -N1 Level 1Loop ID -HL (Order Level) HL -Hierarchical Level HL Hierarchical ID Number AN 1/12 Unique Number assigned by Sender HL Hierarchical Level Code ID 1/2 O = Order PRF -Purchase Order Reference PRF Purchase Order Number AN 12/12 PO# assigned by Menard, Inc ISR -Order Status Report ISR Shipment/Order Status Code ID 2/2 See implementation packet for applicable status codes. ISR Date DT 8/8 YYYYMMDD EDI Mapping Specifications xls Page 2of 4

13 ASC X12 (V4010) Mapping Specifications 870 -Order Status (08/01/16) Level 2Loop ID -HL (Item Level) HL -Hierarchical Level HL Hierarchical ID Number AN 1/12 Unique Number assigned by Sender HL Hierarchical Level Code ID 1/2 I= Item PO1 -Baseline Item Data PO Assigned Identification AN 1/6 Menard, Inc Item Sequence Number from PO101 of 850. PO Quantity Ordered R 1/15 Quantity Ordered PO Unit or Basis for Measurement ID 2/2 Menard, Inc Ordering Unit from PO103 of 850. PO Product / Service ID Qualifier ID 2/2 SK =SKU PO Product / Service ID AN 7/7 Menard, Inc SKU # from PO107 of 850. PO Product / Service ID Qualifier ID 2/2 VP =Vendor Part Number PO Product / Service ID AN 1/48 Vendor Part Number assigned by Vendor PID -Product / Item Description PID Item Description Code ID 1/1 F=Free-Form PID Description AN 1/80 Item Description ISR - Item Status Report ISR Shipment/Order Status Code ID 2/2 See implementation packet for applicable status codes. ISR Date DT 8/8 YYYYMMDD QTY -Quantity Usage: Conditional (Shipment or Cancellation Status Only) QTY Quantity Qualifier ID 2/2 39 =Shipped Qty; QV = Canceled Qty QTY Quantity R 1/15 QuantityShipped or Canceled N1 -Name (Vendor Contact Information) Usage: Conditional (Shipment Status Only) N Entity Identifier Code ID 2/2 CN = General Contact N Name AN 1/60 Contact Name N Identification Code Qualifier ID 2/2 12 =Telephone Number N Identification Code AN 10/10 Contact Phone #. No parentheses or dashes. EDI Mapping Specifications xls Page 3of 4

14 ASC X12 (V4010) Mapping Specifications 870 -Order Status (08/01/16) TD5 -Carrier Details Usage: Conditional (Shipment Status Only) TD Routing AN 1/35 Carrier Name REF -Reference Identification Usage: Conditional (Shipment Status Only) 2I =Tracking Number REF Reference Identification Qualifier ID 2/2 BM =Bill of Lading # REF Reference Identification AN 1/30 Carrier Assigned Tracking or BOL # End Loop ID -HL (Item Level) End Loop ID -HL (Order Level) CTT -Transaction Totals CTT Number Of Line Items NO 1/6 Total Number Of PO Line Items SE -Transaction Set Trailer SE01 96 Number of Included Segments NO 1/10 Total Number of Segments SE Transaction Set Control Number NO 4/9 Transaction Set Control Number GE -Functional Group Trailer GE01 97 Numberof Transactions Sets Included NO 1/6 Total NumberofTransaction Sets GE02 28 Group Control Number NO 1/9 Group Control Number IEA- Interchange Control Trailer IEA01 I16 Number of Included Functional Groups NO 1/5 Total Number of Functional Groups IEA02 I12 Interchange Control Number NO 9/9 Interchange Control Number EDI Mapping Specifications xls Page 4of 4

15 Menard Inc. 870 Business Examples The following pages provide 870 examples for each of the status codes. The 850s below are what is referenced in the 870 example data. Please note the guest special order represents two open sku line items. Stock Order Shipped to Menards Location Special Order Direct to Guest ST*850*0001~ ST*850*0001~ BEG*00*SA*ECWE ** ~ BEG*00*DR*KRNY ** ~ REF*VR*WIDGE001*WIDGET CORP INC~ REF*VR*WIDGE001*WIDGET CORP INC~ PER*OC*Bradley Talmage*TE* ~ CSH*BK~ FOB*PP*DE*MENARDS DC PLANO, IL~ DTM*106* ~ CSH*BK~ TD5****U*FEDEX-FTN~ ITD************NET 30 DAYS~ N1*ST*Smith, Bob*92*KRNY~ DTM*106* ~ N2*Ship To:*Smith, Bob~ TD5****ZZ*MENARD PREF HAULER~ N3*123 E CENTER~ N9*KD**SHIP PRODUCT DIRECTLY TO THE~ N4*ANYWHERE*NE*68850~ N9*KD**STORE.~ PER*CN**TE* ~ N1*BS*3011*92*ECWE~ N1*BT*3200*92*KRNY~ N2*Menard, Inc.*EAU CLAIRE WEST~ N2*Menard, Inc.*KEARNEY~ N3*3210 N CLAIREMONT AVE~ N3*6411 FIRST AVENUE~ N4*EAU CLAIRE*WI* ~ N4*KEARNEY*NE* ~ PER*CN**TE* *FX* ~ PER*CN**TE* *FX* ~ N1*OB*3011*92*ECWE~ N1*OB*3200*92*KRNY~ N2*Menard, Inc.*EAU CLAIRE WEST~ N2*Menard, Inc.*KEARNEY~ N3*3210 N CLAIREMONT AVE~ N3*6411 FIRST AVENUE~ N4*EAU CLAIRE*WI* ~ N4*KEARNEY*NE* ~ PER*CN**TE* *FX* ~ PER*CN**TE* *FX* ~ PO1*1*28*EA*10.72*FX*SK* ~ N1*LW*Smith, Bob~ PID*F****HIGH QUALITY WIDGET~ N3*123 E CENTER~ PO1*2*15*EA*9.45*FX*SK* ~ N4*ANYWHERE*NE*68850~ PID*F****SUPER GADGET~ PER*CN**TE* ~ CTT*2~ PO1*2*1*EA*61*FX*SK* *VP*ABC123~ SE*27*0001~ PID*F****WIDGET CORP INC SPECIAL ORDER~ PID*F****VENDOR PART # ABC123~ PID*F****OPEN SKU ITEM ABC123~ PO1*5*2*EA*57.89*FX*SK* *VP*DEF456~ PID*F****WIDGET CORP INC SPECIAL ORDER~ PID*F****VENDOR PART # DEF456~ PID*F****OPEN SKU ITEM DEF456~ CTT*2~ SE*33*0001~

16 Menard Inc. 870 Business Examples Status Code: IN - In Process When: When an expected ship date is not available within 1 business day of the 850 transmission. Use: Conditional Examples: Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ REF*VR*WIDGE001~ N1*OB*3011~ N1*OB*3200~ N1*ST*3011~ N1*ST*SMITH, BOB~ PRF*ECWE ~ PRF*KRNY ~ ISR*IN* ~ ISR*IN* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PO1*2*1*EA***SK* *VP*ABC123~ PID*F****HIGH QUALITY WIDGET~ PID*F****ABC123~ ISR*IN* ~ ISR*IN* ~ HL*3**I~ HL*3**I~ PO1*2*15*EA***SK* *VP*1235ABCD~ PO1*5*2*EA***SK* *VP*DEF456~ PID*F****SUPER GADGET~ PID*F****DEF456~ ISR*IN* ~ ISR*IN* ~ CTT*2~ CTT*2~ SE*18*0001~ SE*18*0001~

17 Menard Inc. 870 Business Examples Status Code: ED Expected Ship Date When: Within 1 business day of 850 transmission, or when known after an IN status was provided. Use: Mandatory Examples: Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ REF*VR*WIDGE001~ N1*OB*3011~ N1*OB*3200~ N1*ST*3011~ N1*ST*SMITH, BOB~ PRF*ECWE ~ PRF*KRNY ~ ISR*ED* ~ ISR*ED* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PO1*2*1*EA***SK* *VP*ABC123~ PID*F****HIGH QUALITY WIDGET~ PID*F****ABC123~ ISR*ED* ~ ISR*ED* ~ HL*3**I~ HL*3**I~ PO1*2*15*EA***SK* *VP*1235ABCD~ PO1*5*2*EA***SK* *VP*DEF456~ PID*F****SUPER GADGET~ PID*F****DEF456~ ISR*ED* ~ ISR*ED* ~ CTT*2~ CTT*2~ SE*18*0001~ SE*18*0001~

18 Menard Inc. 870 Business Examples Status Code: PR Partial Shipment When: Order/Item has partially shipped and future shipment will be made against order/item. Use: Conditional Examples: Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ REF*VR*WIDGE001~ N1*OB*3011~ N1*OB*3200~ N1*ST*3011~ N1*ST*SMITH, BOB~ PRF*ECWE ~ PRF*KRNY ~ ISR*PR* ~ ISR*PR* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PO1*2*1*EA***SK* *VP*ABC123~ PID*F****HIGH QUALITY WIDGET~ PID*F****ABC123~ ISR*PR* ~ ISR*DD* ~ QTY*39*20~ QTY*39*4~ N1*CN*CUSTOMER SERVICE*12* ~ N1*CN*CUSTOMER SERVICE*12* ~ TD5*****JB HUNT~ TD5*****FED EX~ REF*BM* ~ REF*2I* ~ HL*3**I~ CTT*1~ PO1*2*15*EA***SK* *VP*1235ABCD~ SE*22*0001~ PID*F****SUPER GADGET~ ISR*CC* ~ Note second line item from example B is omitted as QTY*39*15~ it has not yet shipped. N1*CN*CUSTOMER SERVICE*12* ~ TD5*****JB HUNT~ REF*BM* ~ CTT*2~ SE*26*0001~ Note first line item from example A only shows 20 of 28 shipping.

19 Menard Inc. 870 Business Examples Status Code: CC Shipped Complete When: Order/Item has shipped complete to Menards location. Use: Mandatory Examples: Example A - Order Shipping to Menards Location BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ N1*OB*3011~ N1*ST*3011~ PRF*ECWE ~ ISR*CC* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PID*F****HIGH QUALITY WIDGET~ ISR*CC* ~ QTY*39*8~ N1*CN*CUSTOMER SERVICE*12* ~ TD5*****JB HUNT~ REF*BM* ~ CTT*1~ SE*26*0001~ Example B - Order Shipping Direct to Guest CC status applies only to orders shipping to a Menards location. Orders shipping direct to Menards Guest will have DD status provided when order/item ships complete. Note first line item from example A only references the remaining 8 of the original 28 shipping complete. 20 of the 28 had shipped in the PR example. Note second line item from example A is omitted as it shipped complete in the PR example.

20 Menard Inc. 870 Business Examples Status Code: DD Shipped Complete When: Order/Item has shipped complete to Guests home/jobsite. Use: Mandatory Examples: Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest DD status applies only to orders shipping direct to Menards Guest. Orders shipping direct to Menards BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ location will have CC status provided when REF*VR*VENDR001~ order/item ships complete. N1*OB*3156~ N1*ST*SMITH, BOB~ PRF*LAFS ~ ISR*DD* ~ PO1*5*2*EA***SK* *VP*DEF456~ PID*F****DEF456~ ISR*DD* ~ QTY*39*12~ N1*CN*CUSTOMER SERVICE*12* ~ TD5*****FED EX~ REF*2I* ~ CTT*1~ SE*22*0001~ Note first line item from example B is omitted as it shipped complete in the PR example.

21 Menard Inc. 870 Business Examples Status Code: ED Backorders canceled When: Estimated ship date is sent with backordered item(s) canceled. Use: Conditional Examples: Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ REF*VR*WIDGE001~ N1*OB*3011~ N1*OB*3200~ N1*ST*3011~ N1*ST*SMITH, BOB~ PRF*ECWE ~ PRF*KRNY ~ ISR*ED* ~ ISR*ED* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PO1*2*1*EA***SK* *VP*ABC123~ PID*F****HIGH QUALITY WIDGET~ PID*F****ABC123~ ISR*ED* ~ ISR*ED* ~ HL*3**I~ HL*3**I~ PO1*2*15*EA***SK* *VP*1235ABCD~ PO1*5*2*EA***SK* *VP*DEF456~ PID*F****SUPER GADGET~ PID*F****DEF456~ ISR*DE* ~ QTY*QV*15~ ISR*DE* ~ QTY*QV*2~ CTT*2~ CTT*2~ SE*18*0001~ SE*18*0001~ Note canceled line item has DE status sent at item level. Second option is to omit canceled line item. Note once a line item has had canceled status sent it should be omitted from all further status reports.

22 Menard Inc. 870 Business Examples Status Code: CC/DD Backorders canceled When: Order is shipping complete but backordered item(s) have been canceled. Use: Conditional Examples: Line item is canceled at shipment stage. Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ REF*VR*WIDGE001~ N1*OB*3011~ N1*OB*3200~ N1*ST*3011~ N1*ST*SMITH, BOB~ PRF*ECWE ~ PRF*KRNY ~ ISR*CC* ~ ISR*DD* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PO1*2*1*EA***SK* *VP*ABC123~ PID*F****HIGH QUALITY WIDGET~ PID*F****ABC123~ ISR*CC* ~ ISR*DD* ~ QTY*39*28~ QTY*39*4~ N1*CN*CUSTOMER SERVICE*12* ~ N1*CN*CUSTOMER SERVICE*12* ~ TD5*****JB HUNT~ TD5*****FED EX~ REF*BM* ~ REF*2I* ~ HL*3**I~ PO1*5*2*EA***SK* *VP*DEF456~ PO1*2*15*EA***SK* *VP*1235ABCD~ PID*F****DEF456~ PID*F****SUPER GADGET~ ISR*DE* ~ ISR*DE* ~ QV*39*2~ QTY*QV*15~ CTT*1~ CTT*2~ SE*22*0001~ SE*23*0001~ Note canceled line item has DE status sent at item level. Second option is to omit canceled line item.

23 Status Code: DE Canceled order When: Entire order has been canceled. Use: Conditional Examples: Menard Inc. 870 Business Examples Example A - Order Shipping to Menards Location Example B - Order Shipping Direct to Guest BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ BSR*3*PA*UNIQUE VENDOR DEFINED #* ~ REF*VR*WIDGE001~ REF*VR*WIDGE001~ N1*OB*3011~ N1*OB*3200~ N1*ST*3011~ N1*ST*SMITH, BOB~ PRF*ECWE ~ PRF*KRNY ~ ISR*DE* ~ ISR*DE* ~ PO1*1*28*EA***SK* *VP*1234ABCD~ PO1*2*1*EA***SK* *VP*ABC123~ PID*F****HIGH QUALITY WIDGET~ PID*F****ABC123~ ISR*DE* ~ ISR*DE* ~ QTY*QV*28~ QTY*QV*1~ HL*3**I~ HL*3**I~ PO1*2*15*EA***SK* *VP*1235ABCD~ PO1*5*2*EA***SK* *VP*DEF456~ PID*F****SUPER GADGET~ PID*F****DEF456~ ISR*DE* ~ ISR*DE* ~ QTY*QV*15~ QTY*QV*2~ CTT*2~ CTT*2~ SE*20*0001~ SE*20*0001~

24 EDI Mapping Specifications 864 -Text Message (08/01/16) ISA- Interchange Control Header ISA01 I01 Authorization Information Qualifier ID 2/2 03 = Additional Data Information ISA02 I02 Authorization Information AN 10/10 Authorization ID (Menard Assigned Vendor #) ISA03 I03 Security Information Qualifier ID 2/2 01 = Password ISA04 I04 Security Information AN 10/10 Security Password (Menard Assigned Vendor #) ISA05 I05 Interchange ID Qualifier ID 2/2 Sender's ID Qualifier ISA06 I06 Interchange Sender ID AN 15/15 Sender's ID ISA07 I05 Interchange ID Qualifier ID 2/2 Receiver's ID Qualifier ISA08 I07 Interchange Receiver ID AN 15/15 Receiver's ID ISA09 I08 Interchange Date DT 6/6 YYMMDD ISA10 I09 Interchange Time TM 4/4 HHMM ISA11 I10 InterchangeControl Standards Identifier ID 1/1 U = ASC X12 ISA12 I11 InterchangeControl VersionNumber ID 5/ ISA13 I12 InterchangeControl Number NO 9/9 Sender's InterchangeControl Num ISA14 I13 Acknowledgment Requested ID 1/1 0 = No Ack (TA1) Requested ISA15 I14 Test Indicator ID 1/1 P = Production Data, T = Test Data ISA16 I15 Component Element Separator AN 1/1 > GS -Functional Group Header GS Functional Identifier Code ID 2/2 TX = Text Message GS Application Sender's Code AN 2/15 Sender's Identifier GS ApplicationReceiver'sCode AN 2/15 Receiver's Identifier GS Date DT 8/8 Date (YYYYMMDD) GS Time TM 4/4 Time (HHMM) GS06 28 GroupControl Number NO 1/9 Sender's GroupControl Number GS Responsible AgencyCode ID 1/2 X = ASC X12 GS Version/ Release/Industry Identifier Code AN 1/ ST-Transaction Set Header ST Transaction Set Identifier Code ID 3/3 864 = Text Message ST Transaction Set Control Number NO 4/9 Sender's Transaction Set Control Number BMG -BeginningSegment for Text Message BMG Transaction Set Purpose ID 2/2 BMG Description AN 1/80 Purpose 18 = Reissue required on 810 document 44 = Reissue required on 870 document 54 = Approval on 810 document Invoice Number (BIG02 of the 810) ReportNumber (BSR03of the870)

25 EDI Mapping Specifications 864 -Text Message (08/01/16) MIT-Message Identification MIT Reference Identification AN 1/30 PO Number MIT Description AN 1/80 HighLevel Summary Loop ID -MSG MSG -Message Text MSG Free Form Message AN 1/264 Free Form Message End Loop ID -MSG SE -TransactionSet Trailer SE01 96 Number of Included Segments NO 1/10 Total Number of Segments SE Transaction Set Control Number NO 4/9 Transaction Set Control Number GE -Functional Group Trailer GE01 97 Number of Transactions Sets Included NO 1/6 Total Number of Transaction Sets GE02 28 Group Control Number NO 1/9 Group Control Number IEA- Interchange Control Trailer IEA01 I16 Number of Included Functional Groups NO 1/5 Total Number of Functional Groups IEA02 I12 Interchange Control Number NO 9/9 Interchange Control Number

26 864 Business Examples Below are several generic 864 message examples. This is not an all inclusive list of error messages you could see in response to bad 870 data but covers the different formats and types of messages you could see returned for 870 s. Please note 864 messages will NOT be returned for any 870 document rejected during translation the 997 rejection would be the only communication returned for a document rejected during translation. Invalid SKU/Sequence Combination: The below 864 would be generated when the sequence number and/or SKU number on the 870 does not match what was sent on the 850. Corrected 870 should be sent immediately under new ISA/GS Control # s. ST*864*0005~ BMG*44*ED12RHIN ~ MIT*RHIN *INVALID DATA ON 870~ MSG*SKU: nnnnnnn SEQUENCE: nnn is not a valid SKU/Sequence combination for this PO.~ MSG*Refer to PO107 and PO101 of the 850 for proper SKU/Sequence for this line item.~ MSG*SKU: nnnnnnn SEQUENCE: nnn is not a valid SKU/Sequence combination for this PO.~ MSG*Refer to PO107 and PO101 of the 850 for proper SKU/Sequence for this line item.~ MSG*This 870 will not be processed. Please make necessary corrections and resubmit the 870 for processing.~ SE*9*0005~ Invalid Order By Location and PO# Combination: The below 864 would be generated when there is an invalid yard number in the N102 (N1*OB segment) or PO number in the PRF01 on the 870. Corrected 870 should be sent immediately under new ISA/GS Control # s. ST*864*0004~ BMG*44*ED11WCHE ~ MIT*WCHE *INVALID DATA ON 870~ MSG*Orderedby Location: nnnn PO #: WCHE is not valid ordered by location and PO # combination.~ MSG*Refer to PRF01 and N1 OB of the 870~ MSG*This 870 will not be processed. Please make necessary corrections and resubmit the 870 for processing.~ SE*7*0004~ SKU not Numeric: The below 864 would be generated when the data in the PO107 on the 870 is not of valid EDI format (something other than the Menard Inc 7 digit SKU number being returned). Corrected 870 should be sent immediately under new ISA/GS Control # s. ST*864*0001~ BMG*44* ~ MIT*HCDC *INVALID DATA ON 870~ MSG*SKU NOT NUMERIC~ MSG*Refer to PO107 of the 870~ MSG*This 870 will not be processed. Please make necessary corrections and resubmit the 870 for processing.~ SE*7*0001~ Duplicate Report # used: The below 864 would be generated when the report number in the BSR04 has been sent through on a previous 870 update. The report number must be unique for each 870 sent. Corrected 870 should be sent immediately under new ISA/GS Control # s. ST*864*0001~ BMG*44*DS ED~ MIT*NAPE *INVALID DATA ON 870~ MSG*Report#: DS ED has been used as a report# on a previous 870 update.~ MSG*This occurrence is considered a duplicate. Refer to BSR03 of the 870~ MSG*This 870 will not be processed. Please make necessary corrections and resubmit the 870 for processing.~ SE*7*0001~