Re: Orderresponse and Backorder

[Tim McGrath <tim.mcgrath@documentengineeringservices.com>]

Your  question is best aimed at the ubl-dev mailing list as you may get a more detailed response.  I will copy them on this now.

Although in looking in more detail, i suspect it is an question to BII (as part of Peppol BIS 28 A).  Certainly UBL does not give any values for LineStatusCode so you can create your own mutually agreed code values for this if necessary. if you have a given set they are probably defined by BII. It may be that they have not engaged the backordering parts of UBL.  

In UBL the OrderResponse is used to confirm the Seller’s understanding of the current state of the Order. See section 2.6.3 in the specification...

2.6.3 Order Response

Proposed changes to an Order by the Seller are accomplished through the full Order Response document.

The Order Response proposes to replace the original Order. It reflects the entire new state of an order transaction.

It also is the means by which the Seller confirms or supplies Order-related details to the Buyer that were not available to, or specified by, the Buyer at the time of ordering. These may include:

• Delivery date, offered by the Seller if not specifically requested by the Buyer

• Prices

• Discounts

• Charges

• Item Classification codes

The Seller may advise on replacements, substitutes, or other necessary changes using the Order Response.

Each OrderResponse/OrderLine/LineItem allows for MinimumBackorderQuantity and MaximumBackorderQuantity. To address your first question then the LineItem/Quantity would be 10 and the LineItem/MaximumBackorderQuantity would be 4.  You may want to invoke the LineItem/PartialDeliveryIndicator (if you intend to deliver the first 6 before the remaining 4 are in stock) and perhaps the LineItem/BackOrderAllowedIndicator as well.

In looking at the second question i would have expected that delivery details are dealt with by a DespatchAdvice (or ReceiptAdvice).  So it may be that you are trying to use OrderResponse when it should be a DespatchAdvice?

DespatchAdvice/DespatchLine has BackorderQuantity and BackorderReason as well as DeliveredQuantity.

Am I on the right track here? Let me know if that is helpful.

On 29 Jun 2015, at 20:00, Thomas Pettersson <thomas.pettersson@psk-konsult.se> wrote:

Hi Tim,

 

We have a problem when we use UBL 2.1 OrderResponse that we need to solve. Hope you can help us out. I’ve googled and looked in the ubl-dev archives, but didn’t find the answer. You know that we at the moment are using Peppol BIS 28 A for ordering.

 

The situation is that in some  businesses (medical drug deliveries) it’s very common with back order. And they also need to confirm order and order lines after deliveries when the order line may be delivered at many times.

 

My first question – How  do you indicate that an order line is backordered fully or partially.

E.g. You get an order of 10 pcs. You confirm 6 and place 4 as backorder.

In “ubl-dev archives” they suggested the use of LineStatusCode, but there is no code for Back order.

Should we “create” new LineStatusCode – BO for Backorder?

 

My second question – How do you confirm order lines after a partial delivery?

E.g. After the delivery of 6, you need to confirm delivery of the 4 backordered pcs.

Note, of you only confirm 4, the buyer may note that 6 pcs is not accepted (if the buyer haven’t had time to register 6 as delivered).

A suggestion is that you always need to address all confirmed, back ordered and delivered quantities as long as the order line is not finished (closed).

Should we “create” new LineStatusCode - DE for Delivered?

 

 

Mvh

 

SFTI Tekniskt kansli
Thomas Pettersson
Consultant, expert e-business and integration
___________________________________
Mobile + 46 (0)70 532 82 02
thomas.pettersson@psk-konsult.se

 

-----------------

Regards 

Tim McGrath
tim.mcgrath@documentengineeringservices.com

Fremantle, Western Australia 6160

AUSTRALIA

Phone: +61438352228

Skype: t.mcgrath