Supplier Integration Guideline

This guideline is intended to provide all necessary information to suppliers in order to receive and
confirm orders as well as to send advanced shipment information of electronic format. The first part
provides an overview of the possible transactions and summarizes general information which is not
transaction specific. After that, in the second part, all message specific information is provided.
Finally, in the appendix, frequently asked questions are answered.

If there are questions related to the content of this guideline, please get in touch with the EMEA
Supplier E-Commerce team: ecommerce.supplier.emea@thermofisher.com

Table of Contents
Introduction............................................................................................................................................. 2
Prerequisites for business partners:.................................................................................................... 2
Connectivity ............................................................................................................................................. 3
Security ............................................................................................................................................ 3
Message specific information ................................................................................................................. 3
Purchase Order .................................................................................................................................... 4
Field Definitions ............................................................................................................................... 4
Order Response ................................................................................................................................... 7
Dispatch Advice ................................................................................................................................... 9
Appendix................................................................................................................................................ 10
Appendix A: Reference Lists .............................................................................................................. 10
Connectivity AS2............................................................................................................................ 10
Connectivity HTTPS........................................................................................................................ 10
Appendix B: Frequently Asked Questions ......................................................................................... 10
Which date and time format is used? ........................................................................................... 10
Which decimal format is used? ..................................................................................................... 11
What das the field definition mean? ............................................................................................. 11
Which encoding is used? ............................................................................................................... 11
Which unit of measure codes are used? ....................................................................................... 11

Version 2.0 - 20160712

Introduction
Fisher Scientific Europe supports electronic processing of B2B transactions (Business to Business)
with suppliers via commonly used E-Commerce standards. There are currently three message types
that are supported by Fisher Scientific Europe:

Purchase Order – This message is sent to the supplier and contains all order related information.

Purchase Order Confirmation – This message is sent by the supplier as a response to Fisher Scientific
Europe’s purchase order to indicate the successful processing of the order and contains expected
shipping dates, prices, etc..

Advance Shipment Notice – This message is sent as a response to Fisher Scientific Europe to indicate
that the goods where shipped including the shipment date, shipped quantities, additional batch
information (if applicable), etc.

Fisher Supplier
cXML Purchase Order

cXML Order Confirmation

cXML Shippment Notice

The intention is to have an automatic processing of the order, the order confirmation and the
shipment notice. In certain occasion purchase order include comments on header or on line level and
will need to be manually processed on supplier side, as the comments contain special instructions
for the supplier.

Fisher’s interface is based on the Ecommerce Standard cXML Version 1.2.024. (http://www.cxml.org)

HTTPS is the way of choice for exchanging the cXML messages. Alternatively AS2 connections can be
used as well.

Prerequisites for business partners:

 The supplier supports one of the following transfer protocols:
o HTTPS using port default port 443. (Preferred)
o AS2
 The supplier must be able to provide valid SSL certificates.
 The supplier has a designated test environment, separated from the production
environment.
Version 2.0 - 20160712
  The supplier supports cXML with DTD Version 1.2.024.
o The supplier can define if the DTD should be sent in the message or not.

Connectivity
Fisher supports two protocols for E-Commerce information exchange: (1) HTTPS, which is the
preferred way to communicate and (2) AS2.

Security
The following security prerequisites need to be met:

 Client must be able to perform client authentication with SSL certificate at Fisher’s side.
o Self signed certificates are not allowed in Production.
 Sender and Receiver IDs need to be defined.
 Shared secret needs to be defined and checked (optional).

Fisher’s certificates are provided within the supplier package.

Purchase Order Mandatory

Purchase Order Confirmation Optional
Advance Shippment Notice Optional

Message specific information

The following sections describe the specifics of the individual transactions. Information on field level
can be found as comments in the Examples (References to the individual Examples in the supplier
package can be found in the outline table of the individual messages below).

Note: there is a difference between the nomenclature of the messages within cXML and the Fisher
Scientific EuropeERP-System. In the outline both message type names are given and usually the
Fisher Scientific Europe message type name is used in all communication.

Note: In the examples some fields have IDs in brackets (e.g. E1COPE, E2PIDE or E2ADR1). These IDs
are Fisher Scientific Europe internal ERP and are added to the Examples are reference for debugging
purposes.

A message using the cXML standard logically is separated into three parts: (1) a generic cXML header
similar across all messages, (2) a transaction specific header (such as a Order Request Header)
containing information only applicable for the specific transaction type and (3) the transaction lines
(such as order lines).

Examples with comments can be found in the XML folder of the supplier package. The generic cXML
Header will be explained in this section, whereas all message specific parts will be described in detail
in the Sections for the individual message types.

Table 1 describes the fields of the cXML Header in more detail.

Version 2.0 - 20160712
Table 1 - Description of cXML header fields

From From Credentials of the message. (Fisher for Purchase Orders,

Supplier for Order Response & Dispatch Advice). Contains one
Credentials element without shared secret.
Note: Header IDs have to be defined together with Fisher
Scientific Europe Ecommerce Team as these IDs need to be
unique for Business Partners in Europe.
To To Credentials of the message. (Supplier for Purchase Orders,
Fisher for Order Response & Dispatch Advice). Contains one
Credentials element without shared secret.
Note: Header IDs have to be defined together with Fisher
Scientific Europe Ecommerce Team as these IDs need to be
unique for Business Partners in Europe.
Sender Sender Credentials of the message. (Fisher for Purchase
Orders, Supplier for Order Response & Dispatch Advice).
Contains one Credentials element with optional shared secret.
Note: For Fisher the Sender ID will be different to the From ID
(as per ID list in the supplier package)
Note: Header IDs have to be defined together with Fisher
Scientific Europe Ecommerce Team as these IDs need to be
unique for Business Partners in Europe.
Credential Domain ID Domain – “Fisher”
Credential Identity ID (e.g. TMO_02, FisherDE) as per ID list in the supplier
package
Credential SharedSecret Secret passphrase to be included in messages between
suppliers. This phrase is defined per supplier and will be used
to verify the validity of the sender.
Sender UserAgent This field should be filled with a Software ID and Version from
which the message was generated.
Request The request element contains the message specific part as
described below
deploymentMode This attribute is used to identify If the message is a test
message or a production message. Messages that are sent to
the wrong environment (test message sent to production and
vice versa) must be stopped.

Purchase Order
This message is sent from Fisher Scientific Europe to the supplier with all necessary order data.
Fisher Message Type Name Purchase Order.xml
cXML Message Type Name OrderRequest.xml
Example file: Examples/01_PurchaseOrderExample.xml
Response example file: Examples/90_cXMLResponseExample.xml
Response error example file: Examples/91_cXMLErrorResponseExample.xml

Field Definitions
Field definitions consist of two parts: The first part describes the type, which can be alphanumeric (A)
or numeric (N). The second part describes the field length / number of characters. For numeric
Version 2.0 - 20160712
values the field length includes the total number of digits and the number of decimal places
separated by a dot character.

OrderRequestHeader Field
Def
orderID N 12 Fisher order number, must be stored and
included in subsequent messages. (E2ORNO
[N 12])
orderDate N8 Date of order in cXML date format (see FAQ)
(E2ODAT [N 8])

orderType Must be “regular”

type Must be “new”

Money

currency A4 Order currency (E1PCUR [A 4])

*body N 17.3 Total net order amount (E3ITIT [N 17.3])

ShipTo

Address

addressID A 17 Only present if Fisher’s ERP system has a ID

for the order’s ship to address. Can be used
to identify standard addresses. For further
information please contact ecommerce
support. (E2PIDE [A 17])

Name

xml:lang Can be configured, usually “EN”

*body A 30 Name field of the address (E2NAME [A 30])

PostalAddress

DeliverTo A 35 Deliver to can be present up to two times

and holds Adress line 1 and 2 of Fishers ERP
system. (E2ADR1 [A 35]), (E2ADR2 [A 35])

Street A 35 Street, address line 3 of Fishers ERP system.

(E2ADR3 [A 35])

City A 35 City, address line 4 of Fishers ERP system.

(E2ADR4 [A 35])
PostalCode A 16 Postal Code (E2POCD [A 16])

Country

Version 2.0 - 20160712

 isoCountryCode A4 ISO country code of the ship to address
(E2COUN [A 4])

BillTo Same like Ship To except that DeliverTo

fields are not present (address line 1 and 2)

Comments *body A 560 Comments on header level. If present, order

must be processed manually as per request
in the comment. (ETTX70 [A 560])

Extrinsic[name="GoodsMark"] A 30 Goods marking. The value needs to be

present on the Shipment Label and
Shipment Notes. (E1GDSM [A 30])

Extrinsic[name="CustomerReference"] A 20 End customer’s customer number in Fisher’s

ERP system if the order is direct ship. The
value needs to be present on the Shipment
Label and Shipment Notes. (E1COPE [A 20])

Extrinsic[name="CustomerOrderNumber] A 35 End customer’s order number in Fisher’s

ERP system if the order is direct ship. The
value needs to be present on the Shipment
Label and Shipment Notes. (E1CORN [A 35])

Extrinsic[name="CustomerNumber"] A 35 Your customer ID (E1CUID [A 35])

Extrinsic[name="SupplierNumber] A 35 Your supplier ID (E1SUID [A 35])

Extrinsic[name="ContactName] A 30 Name of contact at Fisher Scientific Europe

responsible for that order (E7Z7CONA [A
30])

ItemOut Each order line is represented by one

ItemOut element in the cXML

Quantity N 15.3 Ordered quantity (E3PQTY [N 15.3])

lineNumber N5 Order line number in Fisher’s ERP system,

must be present in all subsequent messages
related to the order. (E3LINE [N 5])

requestedDelivery N8 Requested delivery date of this order line

Date (YYYY-MM-DD) (E3DELB [N 8])

ItemID

SupplierPartID A 35 Supplier item number of the ordered item

(E3SPRC [A 35])

ItemDetail

Version 2.0 - 20160712

 UnitPrice N 17.4 Unit Price (E3SCPR [N 17.4])

Currency A4 Currency of the unit price (E1PCUR [A 4])

Description A 50 Description of the ordered item (E3DESC [A

50])

UnitOfMeasure A5 Unit of measure related to the quantity

(E3UNIT [A 5])

Extrinsic name="ProductCode" N 17.4 Thermo Fisher Scientific product code

(E3PRDC [A 35])

Extrinsic name="LineAmount" N 17.4 Total net amount of this order line (E3LAOC
[N 17.4])

Comments *body A 70 Comments on line level. If present, order

must be processed manually as per request
in the comment. (ETTX70 [A 70])

Order Response
This message is sent as a response to Fisher Scientific Europe to indicate the successful processing of
the order and contains expected shipping dates, etc.
Fisher Message Type Name Order Response
cXML Message Type Name ConfirmationRequest
Example file: Examples/02_OrderResponse.xml
Response example file: Examples/99_cXMLResponseExample.xml

ConfirmationHeader Field Message specific header

Definition
operation Must be “new”
Type Must be “detail”
(indicating that each line
is individually confirmed)
confirmID A 35 Unique ID of this
confirmation message
(E1OREF [A 35])
noticeDate Create date of this
confirmation message
(YYYY-MM-DD)
OrderReference
orderid A 35 Original Fisher order

Version 2.0 - 20160712

 number for this
confirmation message.
Each order needs to be
confirmed using a
separate message.
(E1CORN [A 35], E3CORN
[A 35])
orderDate N8 Original Fisher order date
(YYYY-MM-DD)
(E1ODAT [N 8])
DocumentReference
payloadID Should reference the
payload ID of the Fisher
order payloadID and is
optional. The value is
stored and can be used
for transparency
purposes.

ConfirmationItem The ConfirmationItem

holds the information
that should be
confirmed. There can be
multiple lines here for
one order line (e.g. if 40
pieces were order and 20
pieces are sent on the
first day and another 20
on the seconds day – this
would result in 2 lines
here)
Quantity N 15.3 Total confirmed quantity
(sum of all quantities for
a specific order line)
lineNumber N5 Line number as per
original Fisher order.
(E3LINE [N 5])
UnitOfMeasure A5 Unit of measure of the
line (see FAQ for allowed
values) (E3UNIT [A 5])
ConfirmationStatus This element holds the
confirmation data and
there can be multiple
elements for one order
line (as described above)
Type Must be “accept”.
Quantity N 15.3 Quantity that is
confirmed with this
element (E3CQTY [N
15.3]
shipmentDate N8 Confirmed shipping date
(YYYY-MM-DD) (E3DELT
Version 2.0 - 20160712
 [N 8])
UnitOfMeasure A5 Unit of measure of the
line (see FAQ for allowed
values) (E3UNIT [A 5])

ItemIn
SupplierPartID A 35 Supplier part ID of the
line item as an extrinsic
field. (E3SPRC [A 35])
ItemDetail
UnitPrice Money N 17.4 Unit price (E3PURP [N
17.4])
currency A4 Currency of transaction
(E1PCUR [A 4])
Description A 50 Item description (E3DESC
[A 50])
UnitOfMeasure A5 Unit of measure of the
line (see FAQ for allowed
values) (E3UNIT [A 5])
Extrinsic name="ProductCode" N 17.4 Thermo Fisher Scientific
product code (E3PRDC [N
A 35])

Dispatch Advice
This message is sent as a response to Fisher Scientific Europe to indicate that the goods where
shipped including the shipment date and additional batch information (if applicable).

IMPORTANT: ShipNoticeRequest may be sent per shipment containing one to ∞ related purchase
orders. Packaging information such as pallet or box numbers is not supported in V1.2.024 of the
ShipNoticeRequest and is therefore not required to be provided.
Fisher Message Type Name Dispatch Advice
cXML Message Type Name ShipNoticeRequest
Example file: Examples/03_DispatchAdvice.xml
Response example file: Examples/99_cXMLResponseExample.xml

ShipNoticeHeader Field Message specific header

Def
operation Must be “new”
shipmentDate N8 Date of shipment (YYYY-MM-DD)
deliveryDate N8 Estimated delivery date (YYYY-MM-DD)
noticeDate N8 Date of creation of shipment notice message
(YYYY-MM-DD)
shipmentID A 35 Unique ID of the shipment – should be identical
to the shipment ID on the paperwork which
comes with the goods
ShipNoticePortion
OrderReference
orderID A 35 Original Fisher order number for this ship notice

Version 2.0 - 20160712

 portion.
orderDate N8 Original Fisher order date (YYYY-MM-DD)
(optional)
DocumentReference
payloadID Should reference the payload ID of the Fisher
order payloadID and is optional. The value is
stored and can be used for transparency
purposes.

ShipNoticeItem
lineNumber N5 Line number as per original Fisher order
quantity N 15.3 Quantity that is confirmed with this element
UnitOfMeasure A5 Unit of measure of the line (see FAQ for allowed
values)
Extrinsic name=”SupplierPartID” A 35 Supplier part ID as per original order
Extrinsic name="ProductCode" A 35 Thermo Fisher Scientific product code (E3PRDC
[A 35])
AssetInfo OPTIONAL if batch information is available
Extrinsic name="BatchNumber" A Batch number, if item is batch controlled
(E7Z7BATC)
Extrinsic name="BatchOrderedQuantity N 15.3 Batch quantity, if item is batch controlled
(E7Z7OLQT)
Extrinsic name="BatchExpiryDate" N8 Batch Expiry date, if item is batch controlled and
date handled (YYYY-MM-DD) (E7Z7USBD)

Appendix
Appendix A: Reference Lists
Connectivity AS2
Environment URL
Test https://wmemeatest.fishersci.com:1443/invoke/wm.EDIINT/receive
Production https://wmemeaprod.fishersci.com:1443/invoke/wm.EDIINT/receive

Connectivity HTTPS
Environment URL
Test https://wmemeatest.fishersci.com:1443/invoke/FisherEU_RepositoryMIS.inbound/receiveXml
Production https://wmemeaprod.fishersci.com:1443/invoke/FisherEU_RepositoryMIS.inbound/receiveXml

Appendix B: Frequently Asked Questions

Which date and time format is used?
As stated in the cXML Specification the W3C Date and Time Formats Specification is used for date
and time formats. The timezone is fixed to GMT. The following two are used:

Complete date (used for plain dates):

YYYY-MM-DD (eg 1997-07-16)

Version 2.0 - 20160712

 Complete date plus hours, minutes and seconds (used for date and time):
YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00)

Which decimal format is used?

Number with a dot as a decimal mark and no thousands separator.

What das the field definition mean?

See: Field Definition

Which encoding is used?

UTF-8 encoding must be used for all in- and outgoing messages.

Which unit of measure codes are used?

The following codes are used:

Code Unit of Measure

EA Each
PK Pack
CS Case
PAL Pallet

Version 2.0 - 20160712