EDI Services Guide December 2010



Similar documents
EDI Specifications Advance Ship Notice (Supplier v4010)

856 Advanced Shipping Notices (ASN)

VDP Program Vendor Guidelines

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

For EDI requirements related to Party America contact members of the Party City EDI Team:

Staples Supplier Electronic Data Interchange Implementation Guide

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

RANDOM HOUSE. EDI Implementation Guide Invoice X12 Version 4010

This document has been provided as a courtesy to anyone who wants to learn more about EDI and how it applies to their TrueCommerce solution.

Electronic Data Interchange

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

MERITOR. EDI Business Process Guide

EDI. Overview. A Practical Guide to EDI and the TrueCommerce EDI Platform

Please to perform testing on warehouse invoices and have 5 digit PO number.

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

Invoice. Transaction Set (810) (Outbound from TI)

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

EDI Specifications Invoice (Supplier v4010)

810 Invoice ANSI ASC X12 Version 4010

Electronic Document Interchange Standards Version 5050

How EDI accommodates GS1 GLN & GTIN

Solar Eclipse Electronic Data Interchange (EDI) Release 9.0.1

Vendor Invoicing EDI 810

Ultramar Ltd IMPLEMENTATION GUIDE

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

Walmart Stores, Inc. Getting Started with EDI Implementation Guideline Document version: 1.0 Published November 2011

ANSI X12 ASN 856 Version

9.0 Electronic Data Interchange (EDI) Requirements

Getting Started with EDI Implementation Guide

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

810 Invoice Revised 01/26/15

ADOBE ANSI X Version: 1.0

Mazda North American Operations EDI Supplier Documentation October 20, 2015

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

How To Use Electronic Data Interchange (Edi)

Electronic Data Interchange

856 Ship Notice/Manifest - R US CANADA

ANSI X12 version Advance Ship Notice

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

LOWE'S COMPANIES, INC. ELECTRONIC DATA INTERCHANGE PARTNER IMPLEMENTATION PACKAGE

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

In-Network Translation User s Guide

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

EDI FAQ Document ABOUT THIS DOCUMENT EDI. This document is a repository of frequently asked questions relating to: 1. EDI. 2. emessaging Standards

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

CHAPTER 3 ELECTRONIC DATA INTERCHANGE (EDI) TABLE OF CONTENTS HOW TO GET STARTED 3-2 REQUIRED EDI DOCUMENTS 3-2 VENDOR ACCURACY AUDIT PROGRAM 3-10

EDI GUIDELINES INVOICE 810 VERSION 4010

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

SUPPLY CHAIN ELECTRONIC COMMERCE PARTNER GUIDE

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

Gentran_Director_Create_a_partner.ppt Page 1 of 60

Document Copying on GXS Trading Grid Messaging Service. Debbie Scott Senior Solution Consultant

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

Implementation Guide to. Application Advice - Freight Bill EDI 824. In Response to CN Invoices. December 31, 2010

Electronic Commerce February 2004

The Great Atlantic & Pacific Tea Co., Inc. Imaging and Workflow Automation (IWA) Vendor Guide to Electronic Invoicing

VENDOR EDI MANUAL SPORTSMAN S GUIDE (SG)

NEXCOM EDI 753 / 754 Supplier Shipping Instructions

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.

824 Application Advice

Communications and Connectivity

997 Functional Acknowledgment

XEROX EDI GATEWAY, INC.

Ariba einvoicing Supplile i r r P O F lilp i T ra r in i in i g

CLOUD-BASED, FULLY-INTEGRATED EDI SOLUTIONS FOR ACUMATICA

Because the 810 implementation ultimately maps to an InvoiceDetailRequest, it must conform to its rules.

Frequently Asked Questions about EDI and Item Setup

Performance EDI User s Manual. Performance EDI

214 Transportation Carrier Shipment Status Message - LTL

Enterprise EDI. (Electronic Data Interchange) ~ Supplier Manual ~

Note: The following information is required on all Merchandise Invoices:

VERSION: ANSI X

ANSI X12 version Text Message

KANSAS CITY SOUTHERN EDI On-Boarding Guide

Electronic Data Interchange EDI. Facilitators:

Supply Chain Merchandise Logistics E-Commerce Purchase Order

EDI. Electronic Data Interchange

EDI 101 Guide 1EDISOURCE BUYER S GUIDE

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

Introduction. Companion Guide to X12 Transactions version 5010

Vendor Partnership Manual. Section 6 EDI

860 Purchase Order Change Request Buyer Initiated

SAP Business One Integration with Radley icaras EDI. Mascidon, LLC March, 2011 Dr. Don Maes

VOLVO Dealer Programs 810 Invoice EDI Guideline

FULLY-INTEGRATED EDI SOLUTIONS FOR NETSUITE

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

Electronic Data Interchange EDI

810 Invoice. Introduction: Heading: Functional Group ID=IN

CREDIT CARD BULK PROVIDER REQUIREMENTS

ANSI X12 version Remittance Advice

Baker & Taylor, Inc. Electronic Data Interchange (EDI) Implementation Guide for Publishers. Revised 2011

3.7 Logistics Execution

MAINE FREQUENTLY ASKED QUESTIONS (FAQ) SUPPLIER TECHNICAL WORKSHOP

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

Transcription:

EDI Services Guide December 2010

Table of Contents Introduction...3 Statement of Intent...3 Implementation Guidelines...4 Communication Methods...4 Supported Transactions...4 Envelope Information...5 Specification Documents...5 Special Notes...6 Customer Guidelines...7 Purchase Order...7 POA...8 Invoice...9 Price Sales Catalog...10 Advance Ship Notice...11 Supplier Guidelines...12 Purchase Order...12 POA...13 Invoice...14 Advance Ship Notice...15 www.fisherwebservices.com Page 2

Introduction Statement of Intent This document defines Fisher Scientifics utilization of the ANSI X12 Standards for doing business electronically. We support a variety of EDI documents for customers and suppliers. This manual provides detailed information and technical specifications for these integrations. All information contained herein is subject to change at the discretion of Fisher Scientific Company, L.L.C. www.fisherwebservices.com Page 3

Implementation Guidelines Communication Methods Fisher Scientific offers a variety of connectivity options to meet both our customer and supplier needs: Value Added Network (VAN) - GXS via ICS platform with interconnects to all major Value Added Networks. FTP - Sterling Connect Enterprise with a personally maintained customer or supplier mailbox on the Test and Production platforms. Secure FTP is also available. AS2 - Fisher Scientific transmits most EDI data to GXS via WebMethods 6.1 (Certificates provided upon request). Direct AS2 connections are also available. Certificates are to be exchanged prior to test date. Third Party Approved Formats - ADX, True Commerce, Softshare, SPS Commerce and DI Central Support Transactions Fisher Scientific supports the following EDI transactions: Customer 810 - Invoice (v2000 thru v4010) 832 - Price Sales Catalog (v3020 & v4010) 850 - Purchase Order (v2000 thru v4010) 855 - Purchase Order Acknowledgement (v2000 thru v4010) 856 - Advance Ship Notice (v3020 & v4010) 997 - Functional Acknowledgement Supplier 810 - Invoice (v2000 thru v4010) 850 - Purchase Order (v2000 through v4010) 855 - Purchase Order Acknowledgement (v2000 thru v4010) 856 - Advance Ship Novice (v3020 & v4010) www.fisherwebservices.com Page 4

Envelope Information Fisher Scientific CUSTOMER Envelope Information Production ISA ID Qualifier 14 Production ISA ID 004321519IBMP Production GS ID 004321519 Test ISA ID Qualifier 14 Test ISA ID 004321519IBMT Test GS ID 004321519 ANSI X12 Version 4010, preferred Primary VAN GXS Fisher Scientific SUPPLIER Envelope Information Production ISA ID Qualifier (For 850, 810 & 867) 09 Production ISA ID Qualifier (For 855 & 856 ONLY) 14 Production ISA ID (For 850, 810 & 867) 004321519VNDP Production ISA ID (For 855 & 856 ONLY) 004321519IBMP Production GS ID 004321519 Test ISA ID Qualifier (For 850 & 810) 09 Test ISA ID Qualifier (For 855 & 856 ONLY) 14 Test ISA ID (For 850 & 810) 004321519VNDP Test ISA ID (For 855 & 856 ONLY) 004321519IBMP Test GS ID 004321519 ANSI X12 Version 4010, preferred Primary VAN GXS Specification Documents All of Fisher Scientifics EDI Specification documents are available for download on our website at www.fisherwebservices.com Page 5

Special Notes Fisher Scientific accepts the basic and extended ANSI X12 character sets for use as a terminator, data element separator and sub-element separator. Please refrain from using these characters in any data contained within the document except for use as a delimiter. Fisher Scientifics system modifies the delimiters received in the customer and supplier data to an asterisk (*) and tilde (~). Any transmissions that contain either of these characters in the data will automatically fail during translation and will require modification and resubmission by the trading partner. Please refrain from using any special characters in transmissions (e.g. á, è, ç, ½). Data contained in documents sent to Fisher Scientific should be limited to standard keyboard character sets. A Functional Acknowledgement (997) is expected for all transactions delivered by Fisher Scientific to our customers and suppliers. www.fisherwebservices.com Page 6

Customer Guidelines Purchase Order Fisher Scientific has the ability to accept purchase orders from customers via 6 methods EDI, cxml, xcbl, Fax, Email or Phone. Fisher Scientific prefers that the customer send a purchasing contact name and phone number on the electronic order for customer service reference. If this information cannot be sent then a default contact name, phone and email address should be provided. All header and line level notes or message segments received are passed with the order. Comments are not read by customer service or the warehouse staff due to the Fisher automated process. Orders are processed and shipped based on either: The address that resides on Fisher Scientifics system or From the address provided in the EDI data in the N1*ST Loop (Address Override). Address override is limited to 5 lines, 25 characters per line. Line 6 of the address is the Attention Line. This line is also limited to 25 characters. Fisher Scientific commonly uses data from the PER segment with an NT qualifier to populate the attention line. If the address that resides on Fisher Scientifics system is to be used, the customer must either pass the Fisher Scientific account number or a ship-to location code in the N104*ST. If the Fisher Scientific account number is sent, it should be 9 digits in length with no dashes (6 digit base with 3 digit destination). An 91 qualifier should be used in the N103. If ship-to location code is sent, it should be limited to 17 characters in length. A 92 qualifier should be used in the N104. The customer must provide all Bill-to and Ship-to account numbers with Ship-to Location Codes prior to go-live. Customer Specific Data from the purchase order can be passed to the invoice, POA or packing list. Fisher Scientific must be notified of this requirement prior to the testing phase so that appropriate test scenarios can be initiated. www.fisherwebservices.com Page 7

The Purchase Order (850) EDI Specification Guide can be found at For information and detail specifications on submitting cxml or xcbl orders please refer to our Integration Services Guide, which can be found at POA Fisher Scientific has the ability to send acknowledgments for customer purchase orders via 4 methods EDI, cxml, Fax or Email. Electronic acknowledgements are based on the order entry method: All order entry sources (internet, EDI, cxml, phone, fax, email) will receive an electronic POA or Electronic order entry sources only (EDI, cxml, xcbl) will receive an electronic POA. If an email acknowledgement is expected, the customer is required to provide either the email address on each purchase order or a default address for all orders. Fisher Scientific does not support an email acknowledgement if the electronic purchase order is received with ANSI X12 version of 3010 or below. If a fax acknowledgement is expected, the customer is required to provide either the fax number on each purchase order or a default fax number for all orders. Back order notifications can be sent via email. This notice is issued when the supplier changes the availability date. Fisher Scientific will provide an order status code as well as the estimated delivery date for each line when a valid date is available. Customer specific data is available on the acknowledgement from information contained on the purchase order. This can be data that is sent at the header of the order or line level data. www.fisherwebservices.com Page 8

The Purchase Order Acknowledgement (855) EDI Specification Guide can be found at For information and detail specifications on receiving cxml purchase order acknowledgements please refer to our Integration Services Guide that can be found at Invoice Fisher Scientific has the ability to send invoices for customer purchase orders via 2 electronic methods EDI or cxml. Electronic invoices are based on the order entry method. All order entry sources (internet, EDI, cxml, phone, fax, email) will receive an electronic invoice or Electronic order entry sources only (EDI, cxml, xcbl) will receive an electronic invoice. Invoices are generated Tuesday through Saturday mornings. There will be a maximum of 200 invoices per envelope. Fisher Scientific has the ability to support credit memos electronically. Detailed functional specifications regarding dollar amount formats must be provided. Invoice numbers are 7 digits in length and are recycled. There is a chance an invoice number will repeat within the same year. If the customer does not have the ability to receive a recycled invoice number, Fisher Scientific is able to add data (single character, date, etc.) to the end of the invoice number to make it unique. This should be discussed with the ecommerce analyst during the invoice implementation phase. Multiple N1 Loops can be provided on the invoice ST-ShipTo, SE-Seller, BT- BillTo, RE-RemitTo, SF-ShipFrom. Customer specific data is available on the invoice from information contained on the purchase order. This can be data that is sent at the header of the order or line level data. www.fisherwebservices.com Page 9

Electronic invoices are based on the order entry method. Miscellaneous charges are always provided at the summary level of the invoice. All possible miscellaneous charges are noted in the functional specifications. Discount terms will always be sent as Net 30. Paper invoices can be turned off after testing or left in a parallel mode for a maximum of 2 weeks from the go-live date based on the customer s discretion. The Invoice (810) EDI Specification Guide can be found at For information and detail specifications on receiving cxml invoices please refer to our Integration Services Guide that can be found at Price Sales Catalog Fisher Scientific supports sending of a price sales catalog via 2 methods EDI or Excel. The standard EDI Price Sales Catalog is based on 15 months of sales history. This sales history will determine the item listing. The master pricing account will determine the contract price. The catalog can be delivered on a Monthly, Quarterly or Yearly schedule. The customer part number can be sent on the price sales catalog if Fisher Scientific maintains a cross reference (speed file) file. The customer can receive either the standard UOM (lowest selling UOM) or both the standard and alternate UOM. If both are requested, 2 LIN segments with the same item number will be sent along with a CTP containing the price per UOM. www.fisherwebservices.com Page 10

All price catalog requests must be approved by the Fisher Scientific Pricing Group to insure up to date pricing. The Price Sales Catalog (832) EDI Specification Guide can be found at Advance Ship Notice Fisher Scientific has the ability to send advance ship notices. The HL segment occurs at various levels within the ship notice. The item level will always be included in the transaction. There are 4 hierarchical levels available Shipment Level, Order Level, Item Level and Tare Level. The Shipping Notice transaction set may contain only one shipment and one order hierarchy, however, there may be one or more item hierarchies. The customer is required to provide their Advanced Ship Notice functional specifications for reference purposes. Advanced Shipment Notices are initiated after the Fisher Scientific order has shipped. It is sent real time. In the case of a shipment that is being sent directly from one of your suppliers, the ASN is initiated after the supplier invoices has been received and matched to the corresponding Fisher Scientific order. The DTM segment can either indicate the Shipped Date or Estimated Delivery Date. This must be specified by the customer as to which is preferred. The Advance Ship Notice (856) EDI Specification Guide can be found at www.fisherwebservices.com Page 11

Supplier Guidelines Purchase Order Fisher Scientific has the ability transmit EDI purchase orders electronically to our suppliers. Purchase orders are sent every hour on the half hour from 6:30 AM EST through 7:30 PM EST, Monday through Friday. Fisher Scientific mandates that a 997 Functional Acknowledgement for all purchase orders be delivered via EDI. MSG segment comments will always be sent on direct ship orders. Fisher Scientific can provide an N1 Loop with the BT-Bill-to, ST-Ship-to and VN- Vendor qualifiers and values The N1 Bill-to loop will provide the Fisher Scientific Duns number The N1 Ship-to loop will provide the Fisher Scientific warehouse codes in the N104. The Fisher Scientific N104 does not represent an identification number for the customer site. The following structure will comprise the N1 Ship-to address for drop shipments: N1 N2 is optional N301 with the customer PO number N302 address line A second N301 and N302 N4 Fisher Scientific provides the customer purchase order number in the N301 of the ship-to address to allow for ease of delivery of the direct shipment orders. If supplier is unable to read the address line from the N302 Fisher Scientific can replace the N301 with the N302. This should be discussed with the ecommerce analyst during the implementation phase. www.fisherwebservices.com Page 12

For the N1 ST loop, if the BEG02 = DS, the value in the N104 does not represent an Identification Number for the Customer Site. For DS orders, the address information specified in the N1-N4 ST loop should be used. The DTM segment will indicate the expected delivery dates. SA Standalone orders will issue an 038 Ship no later than date DS Drop shipment orders will indicate a 367 Due to the customer date The purchase order total in the AMT segment will submit the PO total with 2 decimal positions. The Purchase Order (850) EDI Specification Guide can be found at POA Fisher Scientific has the ability to accept EDI purchase order acknowledgements electronically from our suppliers. Fisher Scientific expects the N1*SF ship from name. The PO number must match the Fisher Scientific PO number. The supplier UOM must match the Fisher Scientific UOM. The supplier vendor catalog number must match the Fisher Scientific product number. Fisher Scientific accepts a secondary POA for re-promise dates if delays are later known. The Purchase Order Acknowledgement (855) EDI Specification Guide can be found at www.fisherwebservices.com Page 13

Invoice Fisher Scientific has the ability to accept and prefer to receive EDI invoices electronically from our suppliers. Fisher Scientific collects invoices throughout the day and processes them into the accounting system once a day. Invoices received after 6:00 PM EST are processed the following evening. All price and UOM differences from what was sent on the purchase order and received on the invoice will cause the order to kick out of the Fisher Scientific AP system and cause a delay in payment. The BIG07 (Transaction Type Code) is a mandatory field for Fisher Scientific and must be sent or the invoice will kick out during translation. The invoice number must be unique. Any duplicates will be rejected. Only the N1*RE is recognized by Fisher Scientific. All other N1 loops will be ignored. A three-character line number in the IT101 is preferred but not required. The supplier must provide in the IT1 either the CB/BP qualifier with Fisher Scientifics part number or the VC/VP qualifier with the supplier s part number exactly as sent on the PO. If both are provided, only the CB/BP will be used. The SLN segment is required from all suppliers submitting line items that are Lot Controlled. If there is more than one lot number for a product, provide as many SLN segments as are needed. (A maximum of 50 are permitted). This segment is not required unless specifically requested by Fisher Scientific. The invoice total dollar amount must match the extended line item dollar values and any freight or miscellaneous charge dollar amounts. www.fisherwebservices.com Page 14

The SAC or ITA miscellaneous charge codes are validated. Those not listed below will be rejected. V4010 A010, C310, C510, C590, D200, D240, D270, D540, D820, F050, F155, F230, G470, G740, G830, H750, I250, I530 and ZZZZ Versions lower than 4010 FS, IN, FA Any charge code not listed above that the supplier expects to send should be discussed with the ecommerce analyst during invoice implementation phase. Partial ship invoices are accepted as long as the line number on the invoice matches that sent on the purchase order. The Invoice (810) EDI Specification Guide can be found at Advance Ship Notice Fisher Scientific has the ability to accept EDI advance ship notices electronically from our suppliers. Fisher Scientific prefers that line volumes higher than 10,000 lines submit a pallet level ASN. Please note that the receiver id is different from the sender id that Fisher Scientific sends on the purchase order. Lot controlled items will require the SLN segment with the lot number and expiration dates. The PRF segment must contain the Fisher Scientific purchase order number. The PO number must appear in the HL 2 loop of the Order HL level. The MAN segment is only required on the Tare level. The SSCC-18 identifier is required. www.fisherwebservices.com Page 15

Recommended Formats: Shipment Level ASN required order BSN HL*1*S DTM*011*CCYYMMDD HL*2*1*O PRF*FISHER PO HL*3*2*P MAN*SM*00000 (optional) HL*4*3*I LIN*1*CB*211992 SN1*1*EA*VALUE FROM PURCHASE ORDER Followed by multiple item loops Pallet Format required order BSN HL*1*S DTM*011*CCYYMMDD HL*2*1*O*1 PRF*FISHER PO HL*3*2*T*1 MAN*SM*00000 (mandatory) HL*4*3*I*1 LIN*1*CB*211992 SN1*1*EA*VALUE FROM PURCHASE ORDER PID*F****DESCRIPTION Followed by multiple item loops The Advance Ship Notice (856) EDI Specification Guide can be found at www.fisherwebservices.com Page 16