LXIR BALANCE ANSWER

Description

The flow describes how the balance comparison (physical balance) takes place between the EWS and LXIR. EWS sends a message every night and comparison takes place in LXIR. No feedback is returned to the EWS.

Balances are compared as follows:

LXIR	SUStaus in LXIR	EWS	Lxir	EWS
Physical balance minus bar coded quantity	Received (16) + Reserved (32) + WareHouseNotified (64) WareHouseNotifiedWithErrors (128)	Stock balance + balance to be picked	X	X
Reserved quantity	Reserved (32)	Balance to be picked	X	X
Blocked quantity	Blocked (2048)	Barring Aldo	X	X

Physical balance in LXIR is everything that is in place on the warehouse, regardless of the blocked or unblocked quantity.

The physical balance in the EWS is the total balance in stock that does not have a reservation and is entered.

Balance to be picked up in EWS is order-placed balance that has not been acknowledged (no order result sent back to LXIR)

The three balances are compared and if different, this is logged by e-mail, and / or in a file. If the article is not found in LXIR, this is marked with 'M' (missing). Only deviations are shown; these may then be handled manually after assessment.

Balance of all active items for the client is sent from the EWS, (also items with inventory balance 0).

Simple flow chart

LXIR EWS

Message triggering

Trigger is started in the EWS. EWS sends the message at specific times, once a day, at night

Specifications

Element	Code	Mand.	Explanation	Lxir	EWS
DocumentName		J	Name of this document = BalanceAnswer	X	X
FromSystem		N	Dispatch system. If the message is sent from LXIR this is LXIR	X	X
FromParty		J	Identity of the sending party (company, client etc)	X	X
FromPartyQualifier		N	Identifiers for the identity ie whether it is an organization number, name or other.	X	X
ToSystem		N	Receiving system. LXIR if the message is to LXIR	X	X
ToParty		J	Identity of the receiving party (company, client etc)	X	X
ToPartyQualifier		N	Identifiers for the identity ie whether it is an organization number, name or other.	X	X
InterchangeDate		N	Date and time when the message was created	X	X
InterchangeNumber		J	Sequence number for all messages in a flow between two parties. Used to check that all messages arrive.	X	X
InterchangeTest	"" 0 1	N	Flag for whether it is a test message "" Or not specified and 0 are messages in operation 1 are test messages.	X	X

Body / LXIRBalanceAnswer / Balance Answer

Element	Code	Mand.	Explanation	Lxir	EWS
ProductNumber		J	Unique product number	X	X
OwnerNumber		N	Client affiliation, ex.NASE (WMI)		X
WarehouseId		J	Unique identifier on the stock that the balance statement applies.	X	X
AnswerDateTime		J	Date and time when the balance statement was created	X	X
PhysicalBalanceOK		J	Physical balance completely	X	X
BlockedBalanceOK		J	Completely blocked balance	X	X
ReservedBalanceOK		J	Balance on orders reserved against total stock balance	X	X

Example

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

- <LXIREnvelope>

<Header DocumentName="BalanceAnswer" FromSystem="EWS" FromParty="KERAKOLL" FromPartyQualifier="" ToSystem="XOE"

ToParty="KERAKOLL" ToPartyQualifier="" InterchangeDate="2008-03-18 23:52" InterchangeNumber="114" InterchangeTest="" />

- <Body>

- <LXIRBalanceAnswer>

</LXIRBalanceAnswer>

</Body>

</LXIREnvelope>

XSD

Document version history

Version.	Date	Author/change	Comment
A	2004-01-29	Erik Sylvan	The document created
	2004-02-02	Erik Sylvan	Added SU statuses and ReservedBalanceOK
PD	2008-03-18	Björn Johansson	Adjusted from LXIR3 & EWS
B	2008-03-31	Martin Fransson	Accepted
B1	2008-05-05	Lasse Sääf	Set InterchangeNumber to Mandatory
C	2010-09-22	Björn Johansson	Adjusted off LWS relations, published on sharepoint
D	2012-05-03	Lasse Sääf	Added OwnerNumber, deleted field not used

Manual & Kunskapscenter

LXIR BALANCE ANSWER

Related content