Versions Compared

Version Old Version 17 New Version 18
Changes made by

Lasse Sääf

Lasse Sääf

Saved on

Key

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

The flow describes the arrangement of new purchase order and return order, as well as change and cancellation.

Return orders are handled as a customer order type in LXIR and as a purchase order type in the EWS. Everything that is called the purchase order or row below also applies to return orders.

Purchase orders are called Call-off orders in LXIR.

Addition of new purchase order line / return order line cannot be done.

Change of purchase order / return order can be made. This occurs when changing the delivery date and or number. Cancellation can be made by full purchase order / return order but not line. However, cancellation of the purchase order line / return order line takes place during partial storage as the old line is replaced with a new one and this in order to reduce the risk of mis-storage. If DELVRY arrives at the ready-marked line, it must be rejected and alerted.

No feedback is made from the EWS in addition to the submission of registration.

A PURORD does not have to mean that there will be a DELVRY in response to all purchase order lines / return order lines, but the answer to these can come in several separate DELVRY messages. This happens when certain lines in a PURORD are answered but not all simultaneously. There should be no more answers with reference to the same POR and associated sequence number in different messages. If this happens, the answer must be rejected and an alarm added to the error log. On the other hand, there may be several answers to the same purchase order line / return order line and sequence number in the same message.

LXIR EWS only works with balances, not the term "be".

Panel
titleSimple flow chart

NEW PURCHASE ORDER

Image Modified

CHANGE PURCHASE ORDER

...

Panel
titleLXIRSubOrderResult, DELVRY

XML structure

LXIRSubOrderResult (1)

Envelope (1) LXIRSubOrderResult

Attribute

Code

Mand

Explanation

Lxir

EWS

Comment

FromPartner


Y

From system

X

X


FromPartnerUser


Y

Users from system / client

X

X


ToPartner


Y

To system

X

X


ToPartnerUser


Y

User System / Client

X

X


DateTime


N

Time to create the message (YY-MM-DD hh: mm)

X

X


ReferensNumber


Y

The reference number of the message

X

X


InterchangeTest


N

Indicates test message

X

X


Header (1)

HeaderInfo (1)

Attribute

Code

MAN

Explanation

Lxir

EWS

Comment

CreationDate


Y

Created date

X

X


DocumentNumber


Y

Call-off message reference number

X

X


DocumentName

DELVER

Y

Name of call-off message: DELVER

X

X


LXIRSubOrderResult \ t

SubOrderHeaderInfo (1) LXIRSubOrderResult

Attribute

Code

Mand

Explanation

Lxir

EWS

Comment

DeliveryNumber


N

Delivery identity. Not treated

-

X


WareHouseId


Y

Warehouse short name in EWS

X

X


ArrivalDate


Y

Time for start of delivery registration

X

X


SupplierId


N


X

X


OrderNumber


Y

Purchase order number / Return order number

X

X


ExternalOrderNumber
NExternal order numberX

SequenceNumber


Y

Purchase order / return order sequence number

X



OrderType


IN 
RV 
KR

Y

Purchase Order Type 
IN = Normal 
RV 
= Claim Order KR = Return Order

X

X

X

X

X

X

X

X


WarehouseSection


N

CAMPSITE

X



DeliveryNote


N

Comments from warehouse personnel regarding delivery note. No handling LXIR

X

X


ConsNote


N

Waybill number. No handling LXIR.

X

X


Employee



Employee who receives the delivery

-

X


CancelRemaining

0

1

NWill cancel all rows not received in this messageX

SubOrderRow (1-99999) LXIRSubOrderResult

SubOrderRowInfo (1) LXIRSubOrderResult SubOrderRowInfo

Attribute

Code

Mand

Explanation

Lxir

EWS

Comment

ArticleId


Y

Article

X

X


OwnerNumber


Y

Client name in EWS (Item owner)

X

X


PackageId


ST 
M

Y

Unit 
ST = Piece 
M = Meter

X

X

X

X

X

X


DeliveredQuantity


Y

Delivered amount. Total, included with possibly blocked in .. DeliveryBlocked BlockedQuantity

X

X


OrderPosition


Y

Line position

X

X


OrderSubPosition


Y

Row Subposition

X

X


OrderNumber


Y

Purchase order number / Return order number

X

X


RevisionCode


N

revision code

X

X


CustomerNumber


N

Customer number, not used

X

X


SupplierArticleId


N

The supplier's item number

X

X


AddressIdentity


N

Address identity, not used

X

X


ItemId


N

Vending Identity

-

-


Weight


N

Weight

X

X


CancelRemainingRow

0

1

NIf true, the remaining part of a partially received row will be cancelled. Default is false. Default behavior is to handle remaining part of a row as a new sub position to be handled later.X

IMEINumber
N

X

v9.10

MacAddress
N

Xv9.10
AntiTheftID
N

Xv9.10
UUID
N

Xv9.11
WLANMAC
N

Xv9.11
MSPKID
N

Xv9.11



DeliveryBlocked (0-1) LXIRSubOrderResult

Attribute

Code

Mand

Explanation

Lxir

EWS

Comment

BlockCode

XX

Y

However, different codes should be handled as a block regardless of code

X

-


PackageId

ST

Y

Unit

X

-


BlockedQuantity



Blocked number

X

-


BlockReason
NBlockReason
Repair
Broken
Damage Package
Bad quality
X
Panel
titleDeliveryBlocked

The element is optional. This can be seen as an ITECHG being sent with blocking of balance directly upon delivery.

...