This is a description of the flow regarding creating a purchaseorder from Extend Backend to external warehouse.
Extend creates a purchase order which the opposite system will receieve and update their system. Then opposite system will reply so
that Extend can update the balance and status for the purchase order.
LXIRSubOrder (1)
LXIRSubOrder\Envelope (1)
Attribute | Code | Man | Description | Notes |
FromPartner |
| Y | From system | You will get the data from Extend |
FromPartnerUser |
| Y | User from system / Client | You will get the data from Extend |
ToPartner |
| Y | To system | You will get the data from Extend |
ToPartnerUser |
| Y | User of from system / Client | You will get the data from Extend |
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 | Man | 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 | Man | 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 |
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 | Man | Description |
OperationCode |
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 | Man | 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 |
ArticleId |
| Y | Product number |
PackageId |
M | Y | Unit M = Meter Additional list can be ordered from Extend |
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 | Man | Description |
OperationCode |
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
- 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.