Balance adjustment WMS

Description

Message sent between Extend Commerce WMS and Extend Commerce BACKEND to change balance of an item. This may occur e.g. due to many reasons, in the segment ItemLoadChangeCode you´ll find different codes for different type of adjustments of the item.

The message can also be used for blocking and deblocking of balance. this means that the warehouse system can mark a product as not available, but it's still physical in the warehouse

Specifications

1. Extend Commerce ItemChange, ITCHG

1.1 XML Structure

LXIRItemChange(1)

LXIRItemChange\Envelope (1)

Attribute	Code	Mand.	Explanation	Extend Commerce BACKEND	Extend Commerce WMS
FromPartner		Y	From system	X	X
FromPartnerUser		Y	User from system / Client	X	X
ToPartner		Y	To system	X	X
DateTime		N	Time for creation of message (YY-MM-DD hh:mm)	X	X
ReferensNumber		Y	Message reference number	X	X
InterchangeTest		N	Indicating testmessage	-	-

LXIRItemChange\Header (1)

LXIRItemChange\Header\HeaderInfo (1)

Attribut	Kod	Mand.	Explanation	Extend Commerce BACKEND	Extend Commerce WMS
CreationDate		N	Created date	X	X
DocumentName	ITECHG	Y	Name of message: ITECHG	X	X
DocumentNumber		Y	Message reference number	X	X

LXIRItemChange\Header\ItemChange (1-999)

LXIRItemChange\Header\ItemChange\ItemChangeInfo (1)

Attribute	Code	Mand.	Explanation	Extend Commerce BACKEND	Extend Commerce WMS
OperationCode	2	Y	2 = Change	X	X
Employee		Y	Identity of who registered the change. Always sent by WMS	X	X
UppdateTime		Y	Date and time. Always sent from LWS	X	Not existing in XSD
UpdateTime		Y	Date and time. Always sent from WMS		X
ItemLoadChangeCode	BL ST SK RI AU IS MI MR SI IF		Block/Unblock of balance Inventory. Balance: increase/decrease Scrapping. Balance: decrease Correction embedding. Balance: decrease Emergency withdrawl. Balance: decrease Internal damage. Balance: decrease Manual embedding. Balance: increase Manual correction of manual embedding. Balance: increase/decrease Balance inventory Balance: increase/decrease Internal change Balance: increase/decrease, no balance change on receieving side.	X X X X X X X X X -	X X X X X X X X X X
ChangeText		Y	Part change description. Always from MWS	X	X
DeliveryNumber		N	Purchaseordernumber. Note! Will only be saved if: ITECHGCODID = RI	X	-
PurchaseOrderNumber		N	Purchaseordernumber. Note! Will only be saved if: ITECHGCODID = RI MWS always sends purchaseordernumber i these cases.	-	X
OwnerNumber		N	Client affinity, i.e.NASE(VMI)		X
ArticleIdOld		Y	Article identity in WMS	X	X
QuantityOld		Y	Balance in stock location or article. Always from WMS	X	X
QuantityNew		Y	New balance in stock location or article.	X	X
BlockCodeOld	XX	Y	Blockcode. If ItemLoadChangeCode = BL, ST, XX = Block code	X	X
BlockCodeNew		Y	Blockcode. If ItemLoadChangeCode = BL, ST, XX = Blockcode	X	X
WarehouseOld		Y	Identification for the warehouse where message origin from	X	X
CustomerOrderNumber		Y	CustomerOrderNumber	X	X
BatchNumber		N	Batchnumber	X	X
SerialNumber		N	Serialnumber	?	X
IMEINumber		N		?	X	v9.11
MacAddress		N		?	X	v9.11
AntiTheftID		N		?	X	v9.11
UUID		N		?	X	v9.11
WLANMAC		N		?	X	v9.11
MSPKID		N		?	X	v9.11
BlockReason		N	BlockReason Repair Broken Damage Package Bad quality	?	X	v9.11

Blockcode

1.2 Structure

BlockCodeOld	BlockCodeNew	Rules	Extend Commerce BACKEND	Extend Commerce WMS
00 (nollnoll)	Filled	This means that the balance is to be blocked and the number to be blocked is QuantityNew	X	X
Filled	00 (nollnoll)	This means that the balance is to be blocked and the number to be locked is QuantityNew	X	X
Filled	Filled	Balance change of blocked number.	X	X

At BockCodeOld = XX and BlockCodeNew = XX; Number as the balance change means = QuantityNew (balance after) - QuantityOld (balance before) is based here on blocked balances.

Ex. QuantityNew = 10 and QuantityOld = 6 entails a balance change of +4, ie 4 units should be blocked.

QuantityNew / QuantityOld

Number as the balance change means = QuantityNew (balance after) - QuantityOld (balance before).
WMS never sends a sign of the change, ie it will never be a minus balance.

Triggering of message

WMS creates message after event by warehouse personnel.

Demand

The product must be existing in Extend Commerce BACKEND on the client

XSD file

Example

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

- <LXIRItemChange>

- <Header>

- <ItemChange>

</ItemChange>

- <ItemChange>

</ItemChange>

</Header>

</LXIRItemChange>

Document version history

Version.	Date	Author/change	Comment
A	2003-02-17	Joakim Petersson	Move the document to LXIRNG with new document no.
B	2004-02-13	Erik Sylvan	Changed the document to describe the flow between LXIR and LWS / EWS, added example messages
B1	2004-02-26	Erik Sylvan	Team to explain BlockBode BL (XX, XX)
PC	2008-03-18	Björn Johansson	Adjusted from LXIR3 and EWS
C	2008-03-31	Martin Fransson	Accepted
C1	2008-05-05	Lasse Sääf	Set ReferenceNumber to Mandatory
D	2010-09-21	Björn Johansson	Adjusted off lws and published on sharepoint and removed no longer valid product changes (RL, RO, RM and RF)
E	2012-02-27	Lasse Sääf	Added OwnerNumber
F	2014-06-04	Lasse Sääf	Added BatchNumber
F1	2014-06-04	Lasse Sääf	Added SerialNumber
G	2021-03-29	Josefin Kvillert	Changed wording from Extend to Extend Commerce BACKEND and Extend Commerce WMS
H	2022-03-18	Muhammad Jawad	Adjsuted the Node name from ExtendLXIRItemChange to LXIRItemChange