Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Description

The message describes a external system creating a supplier order, and a expected receiving at warehouse in Extend. (called LXIRSUBORDER) 

Only new orders can be sent. No update or delete events.

Specifications

XML structure

LxirEnvelope(1)

LxirEnvelope/Header(1)

Element       

Code

Mand.

Explanation

DateTime YDate and time when message was created.
DocumentName YDocument name
DocumentNumber YDocument number/identifier
DocumentVersion YDocument version
FromPartner YFixed internal value
FromPartnerUser YFixed value that you will get from Extend
ToPartner YFixed value that you will get from Extend
ToPartnerUser YShortname [Name] of the client the message integration relates to. Agreed with Extend.

LxirEnvelope /Body(1)

LxirEnvelope /Body /SubOrders/LxirSubOrder(n)

LxirEnvelope /Body /SubOrders/LxirSubOrder/SubOrderHeader

Element       

Code

Mand.

Explanation

OperationCode1YFixed value of “1”
SupplierNumber YThe Supplier number as registred in Extend.
WarehouseShortName YShortname of the warehouse where the receiving of goods are to be expected
SupplierAgreementNumber YThe number (id) of the supplier agreement
SupplierAgreementName YName on the supplier agreement.
ExternalOrderNumber YA reference number that will identify the order. This must be unique, Extend will have a control of that the number has not been used before.

LxirEnvelope /Body /SubOrders/LxirSubOrder/SubOrderHeader/SubOrderRows(n)

Element       

Code

Mand.

Explanation

OperationCode1YFixed value of “1”
SupplierProductNumber YSuppliers product number, This number on the product must be registred in Extend Masterdata on product/supplier agreement
SupplierProductName NPhone number
OrderQuantity YQuantity that are expected to be received
ProductUnit N 
PurchaseUnitFactor N 
ExpectedDeliveryDate YDate when products are expected to be received at warehouse
Example

 <Header FromPartner="NAMEFromPartnerUser="NAMEToPartner="XOEToPartnerUser="NAMEDocumentName="LXIRSUBORDERDocumentVersion="1.0DocumentNumber="132456789DateTime="2018-08-16T08:30:00" />

      <Body>

        <SubOrders>

          <LxirSubOrder>

            <SubOrderHeader>

              <OperationCode>1</OperationCode>

              <SupplierNumber>123456</SupplierNumber>

              <WarehouseShortName>WH1</WarehouseShortName>

              <SupplierAgreementNumber>90001</SupplierAgreementNumber>

              <SupplierAgreementName>TestSupplieragreeement 1</SupplierAgreementName>

              <ExternalOrderNumber>132456789</ExternalOrderNumber>

            </SubOrderHeader>

            <SubOrderRows>

              <Row>

                <OperationCode>1</OperationCode>

                <SupplierProductNumber>900001</SupplierProductNumber>

                <SupplierProductName>EUR-pall</SupplierProductName>

                <OrderQuantity>2</OrderQuantity>

                <ProductUnit></ProductUnit>

                <PurchaseUnitFactor></PurchaseUnitFactor>

                <ExpectedDeliveryDate>2018-08-16</ExpectedDeliveryDate>

              </Row>

               <Row>

                <OperationCode>1</OperationCode>

                <SupplierProductNumber>20005550</SupplierProductNumber>

                <SupplierProductName>DemoProduct Large</SupplierProductName>

                <OrderQuantity>64</OrderQuantity>

                <ProductUnit></ProductUnit>

                <PurchaseUnitFactor></PurchaseUnitFactor>

                <ExpectedDeliveryDate>2018-08-16</ExpectedDeliveryDate>

              </Row>

            </SubOrderRows>

          </LxirSubOrder>

        </SubOrders>

      </Body>

    </LxirEnvelope>

Document version history

ersion

Date

Author/change

Commenct

A

2013-05-27

Martin Hagman

Document created

 

2016-06-08

 Martin HagmanAdded DeliveryWarehouse and additional data like more row data
 2018-02-24Pontus CarmeReviewed and updated names on specification
  • No labels