The message describes delivery response message from a supplier to Extend Commerce Backend.

The supplier can with this message:

Purchase

Direct delivery from supplier to end customer. The purchase order is always triggered by a customer order.

Suborder

Delivery of goods from supplier to warehouse.

^{LxirEnvelope(1)}

^{LxirEnvelope/Header(1)}

Element	Data	Mand.	Description	Example
DateTime		Y	Date and time when message was created.	2011-12-05T13:43:24
DocumentNumber		Y	Document number/identifier
DocumentVersion		Y	Document version	1.0
DocumentName		Y	Document name	LxirSupplierOrderResponse
ToPartnerUser		Y	Shortname [Name] of the client the message integration relates to. Agreed with Lxir integration technicians. Must relate to the original supplier order once communicated to supplier
ToPartner		Y	[Name]	Ex. GBG
FromPartnerUser		Y	[Name]	Ex. GBG
FromPartner		Y	Fixed internal value	XOE

LxirEnvelope /Body(1)

LxirEnvelope /Body /LxirSupplierOrderResponse(n)

Element	Data	Mand.	Description	Example
OrderType	”Purchase”; ”Suborder”	Y	XML Attribute defining if the supplier order is of type purchase or suborder. Purchase used when shipping directly to customer (dropshipment), SubOrder used when shipping to warehouse (replenishment)
ConfirmType	”Confirmed”; ”InTransit”	Y	XML Attribute defining if the confirm message is a classic order response (“Confirmed”) or dispatch advice (“InTransit”)
Number		Y	Internal purchase number or suborder number – used as reference number to find which transaction to repond to.	RP-15 / PO-12
CreateDate		Y	Message creation date	Ex. 2011-12-05T13:43:24
DeliveryNote		N	Supplier’s delivery note (if any)
ExternalOrderNumber		N	External order number
SupplierOrderNumber		N	Supplier Order number

LxirSupplierOrder/Transport(1)

Element	Data	Mand.	Description	Example
TransportCondition		N	Transport condition	Incoterms 2010
DeliveryMethod		N	Method of delivery
ForwarderName		N	Forwarder name
ShipmentNumber		N	Tracking number at forwarder, if any

LxirSupplierOrder/Transport(1)/Packages(1)/Package(n)

LxirSupplierOrder/OrderRows(1)/Row(n)

Element	Data	Mand.	Description	Example
Position		Y	Original supplier order position (row number)	10
SubPosition		Y	Original supplier order sub position	0
Notes		N	Supplier’s note (if any)
SupplierProductNumber		N	Supplier’s product number
SupplierProductName		N	Supplier’s product name
ProductNumber		N	Lxir’s product number
ProductName		N	Lxirs product name
DeliveredQuantity		Y	Delivered quantity	Ex. 0.00
Unit		N	Unit for delivered quantity	Ex. PCS, must be same as communicated in supplier order message.
TotalGrossWeight		N	Gross weight per row in total (kg)
DeliveryDate		N	Confirmed delivery date	System will default to time of message processing

LxirSupplierOrder/OrderRows(1)/Row(n)/Packages(1)/Package(n)

LxirSupplierOrder/OrderRows(1)/Row(n)/PreAdvicedValues(1)/PreAdvicedValue(n)

Element	Mand.	Description	Example
Serialnumber	N	Serial number
Batchnumber	N	Batch number
BestBeforeDate	N	Best before date	2011-12-05T13:43:24
PackageInfo	N	Package info
PalletInfo	N	Pallet info
UUID	N	UUID
MAC	N	MAC
WLANMAC	N	WLANMAC
IMEI	N	IMEI
MSPKID	N	MSPKID
ANTITHEFTID	N	AntitheftId
IMEINumber2	N	IMEI number 2
ComputerName	N	Computer name
Asset	N	Asset
Quantity	N	Quantity	1

Example

<Body>

<Row>

</Row>

<Row>

</Row>

</OrderRows>

</LxirSupplierOrderResponse>

</Body>

</LxirEnvelope>

XSD LxirSupplierOrderResponse

SAMPLE Fi

Document version history

Version	Date	Author/change	Commenct
A	2013-05-31	Martin Hagman	Created document
B	2013-10-07	Martin Hagman	Added example data. Made ”Transport”- element mandatory.
C	2019-03-05	Johan Tempelman	Made Datetime, DocumentName and DocumentVersion in the header optional. Added ConfirmType-attribute in the LxirSupplierOrderResponse element Added/modified descriptions for OrderType and ConfirmType
D	2021-04-21	Josefin Kvillert	Changed wording to Extend Commerce Backend
E	2022-03-11	Zohaib Anees	Added ExternalOrderNumber SupplierOrderNumber Package nodes at Transport and Rows

Browser not supported