/
ExternalBalance to Extend Commerce Backend

ExternalBalance to Extend Commerce Backend

Jan 18, 2024
Description

This integration is used to update the product balance by the external system. The specification is illustrated as the number 5 below.

The integration supports comparison of two different type of balance.

The default is physical balance comparison. Physical balance in external warehouse is compared to physical balance in Extend Commerce Backend. This works well when the warehouse does not have any other order sources affecting the available balance, or if balance is synchronized on a night schedule where no open orders are allowed to exist over night (which might be hard to guarantee)

If the warehouse receives orders from other systems, or by manual orders, excel files or a like, it might be better to compare available balance.

The available balance in Extend Commerce Backend is calculated as physical balance - the balance reserved against the warehouse currently being compared. Incoming orders (not yet reserved) are not affecting the available balance in this scenario, since the external warehouse does not yet know about these orders, and as a result they are not yet affecting the available balance in the external warehouse. 

Specification

Balance, LXIRExternalBalance

XMLstructure

LxirEnvelope \Header(1)

Element       

Code

Mand.

Explanation

FromPartner


Y

From system

FromPartnerUser


Y

User from system / Client

ToPartner


Y

To system

ToPartnerUser


Y

User of from system / Client

DocumentName


Y

Document name

DocumentVersion


N

Version of a document

DocumentNumber


N

Document number

DateTime


N

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

 

LxirEnvelope \Body\ItemBalance (1-999)

Element       

Code

Mand.

Explanation

ProductNumber


N

Product number handled in Extend Commerce Backend

Warehouse


Y

Warehouse short name

Balance


Y

New balance

Note


N

Notes 

LogDate


N

Date of update balance

CustomerProductNumber


N

Customer Product Number.

Can be used when external warehouse does not share the
same product identifier as the product 
number in Extend Commerce Backend.

BalanceType


N 

Supported values:
PhysicalBalance

AvailableBalance


Default if element BalanceType
is left out completely is PhysicalBalance 


XSD files


Example

 <?xml version="1.0" encoding="utf-8"?>

<LxirEnvelope>

  <Header FromPartner="anySimpleType" FromPartnerUser="anySimpleType" ToPartner="anySimpleType" ToPartnerUser="anySimpleType" DocumentName="LxirExternalBalance" DocumentVersion="DocumentVersion1" DocumentNumber="DocumentNumber1" DateTime="DateTime1" />

  <Body>

    <ItemBalance>

      <ProductNumber> 1511857</ProductNumber>

      <Warehouse> 2008200</Warehouse>

      <Balance>20</Balance>

      <Note>Note1</Note>

      <LogDate> 2016-08-08T12:12:12</LogDate>

     <CustomerProductNumber> 1511857</CustomerProductNumber>

     <BalanceType> PhysicalBalance</BalanceType>

    </ItemBalance>

    <ItemBalance>

      <ProductNumber> 1511858</ProductNumber>

      <Warehouse> 2008200</Warehouse>

      <Balance>25</Balance>

      <Note>Note1</Note>

      <LogDate> 2016-08-08T12:12:12</LogDate>

     <CustomerProductNumber> 1511857</CustomerProductNumber>

     <BalanceType> PhysicalBalance</BalanceType>

    </ItemBalance>

  </Body>

</LxirEnvelope>

Document version history

Version

Date

Author/change

Commenct

A

2016-09-19

Muhammad Jawad

Integration specification for LxirExternalBalance

1.0

2016-10-03

Martin Fransson


1.1

2017-08-14

Muhammad Jawad

Changed ProductNumber to non mandatory and also added the CustomerProductNumber field

 1.2

2020-06-02 

Martin Hagman 

Added information on BalanceType