Versions Compared

Old Version 21

changes.mady.by.user mikael.resare

Saved on

compared with

New Version 22

changes.mady.by.user mikael.resare

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

 

Panel
title1. Description

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.

...

 

Panel
titlePurchase order

  1. LXIRSubOrder

(1)LXIRSubOrder\Envelope (1)

  1. , GenericPURORD 

  1. XMLstructure 

 

 

 

 

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


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

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


PCS

M

Y

Unit
PCS = Pieces

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


1

2

3

Y

Type

1 = New, In cases of new purchase order

2 = Update, Changing the purchase order

3 = Cancel the purchase order

...

Panel
titleExternalOrderNumber

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 

Man 

Description 

Notes 

FromPartner 

  

Y 

From system 

Will be provided from Extend 

FromPartnerUser 

  

Y 

User from system / Client 

Will be provided from Extend 

ToPartner 

  

Y 

To system 

Will be provided from Extend 

ToPartnerUser 

  

Y 

User of from system / Client 

Will be provided from Extend 

DateTime 

  

N 

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

  

ReferensNumber 

  

Y 

Message reference number 

  

LXIRSubOrderResult\Header (1) 

LXIRSubOrderResult\Header\HeaderInfo (1) 

 

Attribute 

Code 

Man 

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 

Man 

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 

Man 

Description 

ArticleId 

  

Y 

Product number 

OwnerNumber 

  

Y 

Client name in GenericWarehouse, data provided from Extend 

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 

Man 

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 

- 

  

 

  1. DeliveryBlocked 

The element is optional.  

  1. Receiving 

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

  

The response on one row may be divided. That is, a row that is sent with the expected incoming deliveries of example 300 pcs then come back with three rows of 100 pcs on each. The response to a row will always be grouped in a single message. In this case, the split has all row the same order position + OrderSubPosition, that these are not listed in the response. 

  1. Over delivery: 

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


Panel
titleExample

  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>