The flow describes a message flow of new customer order messages sent from LXIR to / EWS. Only new customer order messages are sent. Changing and canceling customer orders is not possible.

The answer to a CUSORD sent to the EWS is always a CORRES and it is always seen as a final delivery. If a customer order line cannot be picked for any reason, a CORRES message will nevertheless be sent in response and a change of the customer order line can be made at a later time and when is dependent on the reason for the picking deviation.

If several customer order lines are sent in the same CUSORD then a common reply message is always sent for these lines, CORRES from the EWS. This happens when the pick is ready for all sent lines.

LXIR - EWS only works with balances, not the concept of "be".

No information is sent back today regarding the chosen mode of transport from the EWS.

All triggerings are created by event in LXIR

New: Customer order placed against EWS-controlled warehouse for the client. When picking dates are sent, CUSORD is sent to the EWS if the other terms on the customer order are met in LXIR (Crossdocking and part delivery). Transmission may occur depending on the answer. A sold customer order is counted as new.

Change: Not allowed 

Cancellation: Not allowed

• Manual routines are required each time a payment customer of transport is placed in LXIR, which is to be handled by the EWS. (Set up in party table - agreement - customer number, etc.).

• The article must be made available to the client.

• Packing for the article must be made available.

• In the case of delivery methods that require postgironr and bank giro, this is sent in the intended CUSORD-ADR field.

LXIROrderResult (1)

Envelope (1) LXIROrderResult

Header (1-999)

Header (1) LXIROrderResult

LXIROrderResult \ header \ Order Head (1)

LXIROrderResult \ header \ InternalDeliveryInfo (0-1)

LXIROrderResult \ header \ Shipment (0-1)

LXIROrderResult \ header \ Shipment \ Packages (0-1)

LXIROrderResult \ header \ Shipment \ Package (1-99999)

LXIROrderResult \ header \ OrderRows (1-99999)

LXIROrderResult\Header\OrderRows\PackageInfo\Package(0-99999)

Balance available, can not be picked. Reservation attempts are postponed for 1 working day until picking takes place. Sales order will be resent from Extend Commerce BACKEND the next picking day until picking has taken place. Otherwise, the same information is sent as the original order. Extend Commerce WMS handles this as a new order. Now the same message as the original order is sent again but now with the following information In the element LXIROrder \ Header \ OrderHeader:

In Extend Commerce BACKEND, the order lines will continue to be reserved. An N-receipt does not release the reservation. This means that for an N receipt, the order will go towards the same shipment. If in one and the same message two lines are normally acknowledged and one with N, these lines will still be on the same shipment. The two normal rows will be sent when the remaining row is acknowledged to eg External system.

N-receipt is thus a temporary code that should only be used for one and the same day.

Out of stock. For Extend Commerce BACKEND, acknowledgment with 0 (zero) in the field \ OrderRows \ PickedQuantity may occur, but it is often the case that some are delivered. Wait for an ITECHG message with inventory code ST on the product. Recalculation takes place on a confirmed date thereafter. In Extend Commerce BACKEND, what is not delivered will be reserved and moved forward one day.

Code S should not normally occur. It should be noted that in Extend Commerce BACKEND you can choose that partial delivery is not allowed and this can then lead to a partial delivery despite the choice.

Agreed overdelivery i.e. an agreement with the customer. If the number picked exceeds the ordered number, a new row with a new subposition and status picked must be created on the part that is handed over.

Agreed subcontracting, i.e. an agreement with the customer that results in cancellation of the deviating number.

A check is made that \ OrderRows \ PickedQuantity + \ OrderRows \ DiscrepancyQuantity = ordered quantity. If this is not the case, an error logging will take place.

The code M stands for Manual Handling. Not supported in Extend Commerce WMS, but external storage systems such as Ongoing can in some cases set this code which then indicates that the system will require the line to be handled manually in Extend Commerce Backend. De-reservation is made of a reserved balance. Shipdate and NextReservationAttempt are set for the far future. The order line is blocked for reservation with the flag "WaitReservation".

Balance available, can not be picked. Reservation attempts are possible immediately. This is the same logic as the N-receipt, i.e. a de-reservation is made. However, expectedDeliveryDate and Shipdate do not change on the order line, unlike the N acknowledgment which postpones the dates one working day.

Here comes the shipping number in some cases and it depends on the delivery method and settings in the EWS. If a shipping number is created per order, it can be sent but not if it is the same shipping number for several different orders.