Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 34 Next »



1. Description

This is a description of the flow regarding creating a purchaseorder from XTND Backend to external warehouse.

XTND Backend creates a purchase order which the opposite system will receive and update in their system. Then opposite system will reply so that XTND Backend can update the balance and status for the purchase order.



Purchase order

2.1 LXIRSubOrder, GenericPURORD 

2.1.1 XMLstructure 

Attribute

Code

Mand.

Description

Notes

FromPartner


Y

From system

You will get the data from Extend Commerce

FromPartnerUser


Y

User from system / Client

You will get the data from Extend Commerce

ToPartner


Y

To system

You will get the data from Extend Commerce

ToPartnerUser


Y

User of from system / Client

You will get the data from Extend Commerce

DateTime


N

Document create date (YY-MM-DD hh:mm)


ReferensNumber


Y

Unique message reference number


InterchangeTest


N




LXIRSubOrder\Header (1-999)

LXIRSubOrder\Header\HeaderInfo (1)

Attribute

Code

Mand.

Description

DocumentNumber


Y

File message reference number

DocumentName

GenericWarehousePURORD

Y

File message name: GenericWarehousePURORD

CreationDate


N



LXIRSubOrder\Header\SubOrderHeader (1)

LXIRSubOrder\Header\SubOrderHeader\SubOrderHeaderInfo (1)

Attribute

Code

Mand.

Description

Notes

OrderNumber


Y

Purchase order number, Return order number. See note below.


ExternalOrderNumber


Y

External order number for the sub order /return order


OrderType

IN

Y

Purchase order type


SupplierId


Y

Supplier Number.


SupplierName


N

Name of supplier


WarehouseId


Y

Warehouse name in /GenericWarehouse

You will get data from Extend Commerce

ArrivalDate


Y

Expected delivery date (YY-MM-DD hh:mm)


SupplierOrderNumber


N

Order number of supplier


Reference


N

Reference


Notes


N

Public notes


InternalNotes


N

Internal notes



LXIRSubOrder\Header\SubOrderHeader\HeaderAdditions (1)

Attribute

Code

Mand.

Description

OperationCode


1

2

3

0

Y

Type

1=A purchase order / return order

2=Change purchase order / return order

3=Cancel the purchase order / return order

0=No handling for head. Used when the purchase order / return order row be changed


LXIRSubOrder\Header\SubOrderHeader\SubOrderRow (1-99999)

LXIRSubOrder\Header\SubOrderHeader\SubOrderRow\SubOrderRowInfo (1)

Attribute

Code

Mand.

Description

OrderPosition


Y

Purchase order row. Return order row

OrderSubPosition


Y

Sub position of purchase order / return order row

OwnerNumber


Y

Client affiliated filed like (VMI), fixed value you will get data from Extend Commerce

ArticleId


Y

Product number

PackageId


PCS

M

Y

Unit
PCS = Pieces

M = Meter

Additional list can be ordered from Extend Commerce

OrderQuantity


Y

Ordered quantity, always in stocked keeped unit

SupplierArticleId


N

Supplier product number, not used for return order

ArrivalDate


Y

Expected delivery date (YY-MM-DD hh:mm)

ReceivingRowStatus


N

Sub order / return order row status id

CustomerProductNumber


N

Customer product number information


LXIRSubOrder\Header\SubOrderHeader\SubOrderRow\SubOrderRowAdditions (1)

Attribute

Code

Mand.

Description

OperationCode


1

2

3

Y

Type

1 = New, In cases of new purchase order

2 = Update, Changing the purchase order

3 = Cancel the purchase order



ExternalOrderNumber

First we are using the ExternalOrderNumber to identify the purchase order if not found then using the OrderNumber to identify the suborder for the receiving. External Order number range can be dedicated per warehouse.

Identification of order rows

We are identifying the rows by two ways

  1. By position and sub position

If the position and sub positions are given in the external message, then we are using them to identify the row, to handle backorders for order row level this is needed

      2.By product number

If position and sub positions are not available, then we are using the product number to identify the row.


Receiving at warehouse

3.1 LXIRSubOrderResult, GenericWarehouseDELVRY

3.1.1 XMLstructure

LXIRSubOrderResult (1)

LXIRSubOrderResult\Envelope (1)

Attribute 

Code 

Mand. 

Description 

Notes 

FromPartner 

  

Y 

From system 

Will be provided by Extend Commerce

FromPartnerUser 

  

Y 

User from system / Client 

Will be provided by Extend Commerce

ToPartner 

  

Y 

To system 

Will be provided by Extend Commerce

ToPartnerUser 

  

Y 

User of from system / Client 

Will be provided by Extend Commerce

DateTime 

  

N 

Document create date (YY-MM-DD hh:mm) 

  

ReferensNumber 

  

Y 

Message reference number 

  

LXIRSubOrderResult\Header (1) 

LXIRSubOrderResult\Header\HeaderInfo (1) 


Attribute 

Code 

Mand. 

Description 

CreationDate 

  

Y 

Create date 

DocumentNumber 

  

Y 

Message reference number 

DocumentName 

GenericWarehouseDELVRY 

Y 

Suborder result message name: GenericWarehouseDELVRY 


  

LXIRSubOrderResult\Header\SubOrderHeader (1-999) 

LXIRSubOrderResult\Header\SubOrderHeader\SubOrderHeaderInfo (1) 


Attribute 

Code 

Mand. 

Description 

Kommentar 

DeliveryNumber 

  

N 

Delivery Identity.  

  

WareHouseId 

  

Y 

Warehouse name in GenericWarehouse 

  

ArrivalDate 

  

Y 

Time for the start of the registration incoming deliveries 

  

SupplierId 

  

N 

  

  

OrderNumber 

  

Y/N 

Purchase order number 

Not mandatory if ExternalOrdernumber is used 

ExternalOrderNumber 

  

N 

External order number 

Using external order number if order number is not specified 

SequenceNumber 

  

Y 

Sequence 

  

OrderType 

IN 
  

Y 

Purchase order type 
IN = Normal 

  


  

  

 

LXIRSubOrderResult\Header\SubOrderHeader\SubOrderRow (1-99999) 

LXIRSubOrderResult\Header\SubOrderHeader\SubOrderRow\SubOrderRowInfo (1) 


Attribute 

Code 

Mand. 

Description 

ArticleId 

  

Y 

Product number 

OwnerNumber 

  

Y 

Client name in GenericWarehouse, data provided by Extend Commerce

PackageId 

  
  

N 

Unit, same as we sent in the Purchase Order 

DeliveredQuantity 

  

Y 

Delivered quantity. Total, included with any blocked in the .. \ Delivery Blocked \ Blocked Quantity 

OrderPosition 

  

Y 

Row position 

OrderSubPosition 

  

Y 

Row sub position 

OrderNumber 

  

Y 

Purchase order number 


  

LXIRSubOrderResult\Header\SubOrderHeader\SubOrderRow\DeliveryBlocked (0-1) 


Attribut 

Kod 

Mand. 

Description 

Lxir 

GenericWarehouse 

Kommentar 

BlockCode 

XX 

Y 

Different codes shall be treated as a block whatever code 

X 

- 

  

PackageId 

  

Y 

Unit 

X 

- 

  

BlockedQuantity 

  

  

Blocked quantity 

X 

- 

 


Delivery blocked

The element is optional.  

Receiving

In order to check the response to a purchase order is made reference to the row with Order Number + Order Position + OrderSubPosition. 

Over delivery

Over Delivery is normally not permissible, XTND must be updated and changed rows sent before the entry into warehouse done. 

Example

  1. Purchase order, LXIR SubOrder 

EXEMPEL 

  1. Receiving, LXIR SubOrderResult 

  

  <?xml version=”1.0” encoding=”ISO-8859-1” ?>  

 - <LXIRSubOrderResult> 

  <Envelope FromPartner=”GenericWarehouse” FromPartnerUser=” SOLARSE” ToPartner=”XOE” ToPartnerUser=” SOLARSE” DateTime=”2008-03-12 15:32” ReferensNumber=”0010000080” InterchangeTest=”” />  

 - <Header> 

  <HeaderInfo CreationDate=”2008-03-12 15:32” DocumentName=”DELVRY” DocumentNumber=”0010000080” />  

 - <SubOrderHeader> 

  <SubOrderHeaderInfo DeliveryNumber=”29” WarehouseId=”CLJO” ArrivalDate=”2008-03-12 15:27:21” SupplierId=”0” OrderNumber=”RP-28” ExternalOrderNumber ="01" SequenceNumber=”” OrderType=”IN” WarehouseSection=”” DeliveryNote=”” ConsNote=”” Employee=”Plockare 1” />  

 - <SubOrderRow> 

  <SubOrderRowInfo ArticleId=”01046” OwnerNumber=”541” PackageId=”SÄCK” DeliveredQuantity=”126” OrderPosition=”10” OrderSubPosition=”1” OrderNumber=”RP-28” RevisionCode=”” CustomerNumber=”” SupplierArticleId=”01046” AddressIdentity=”” ItemId=”” Weight=”25000” />  

  </SubOrderRow> 

  </SubOrderHeader> 

  </Header> 

  </LXIRSubOrderResult> 




  1. Purchase order, LXIR SubOrder 

EXEMPEL 

  1. Receiving, LXIR SubOrderResult 

  

  <?xml version=”1.0” encoding=”ISO-8859-1” ?>  

 - <LXIRSubOrderResult> 

  <Envelope FromPartner=”GenericWarehouse” FromPartnerUser=” SOLARSE” ToPartner=”XOE” ToPartnerUser=” SOLARSE” DateTime=”2008-03-12 15:32” ReferensNumber=”0010000080” InterchangeTest=”” />  

 - <Header> 

  <HeaderInfo CreationDate=”2008-03-12 15:32” DocumentName=”DELVRY” DocumentNumber=”0010000080” />  

 - <SubOrderHeader> 

  <SubOrderHeaderInfo DeliveryNumber=”29” WarehouseId=”CLJO” ArrivalDate=”2008-03-12 15:27:21” SupplierId=”0” OrderNumber=”RP-28” ExternalOrderNumber ="01" SequenceNumber=”” OrderType=”IN” WarehouseSection=”” DeliveryNote=”” ConsNote=”” Employee=”Plockare 1” />  

 - <SubOrderRow> 

  <SubOrderRowInfo ArticleId=”01046” OwnerNumber=”541” PackageId=”SÄCK” DeliveredQuantity=”126” OrderPosition=”10” OrderSubPosition=”1” OrderNumber=”RP-28” RevisionCode=”” CustomerNumber=”” SupplierArticleId=”01046” AddressIdentity=”” ItemId=”” Weight=”25000” />  

  </SubOrderRow> 

  </SubOrderHeader> 

  </Header> 

  </LXIRSubOrderResult> 


  • No labels