Prioritising orders in VL10B

[rafael_zaragatzky]

Dear colleagues,

My client uses background job VL10B in order to create deliveries for stock transport orders. Sometimes, the available stock cannot cover all the outstanding orders, so the job creates deliveries only for some orders.

We can't understand the logic how SAP picks the orders to create the deliveries for - it seems to be random. What my client wants is FIFO based on the requested delivery date.

Have you ever been confronted with such question? Do you know if this is possible to set up?

TIA

Raf

[Former Member · Accepted solution]

Hi,

The logic behind the delivery creation for order is purely based on the confirmed delivery dates which are store in the delivery due index file. If yo uwant delivery creation on FIFO basis please create a variant in SHD0 in this regard for VL10B. Thanking you

[rafael_zaragatzky · Accepted solution]

Thank you, Padmasri.

What do you mean when you write "creation for order is purely based on the confirmed delivery dates"? In our case the selection by the confirmed delivery date (actually it is the "delivery creation date" on the "Shipping" tab of the PO, which is also the date in the index file VETVG) can e.g. give orders for 100 pcs, but there are only 80 in stock. How will the system decide which orders to give the stock to?

If it selected by the oldest "confirmed delivery dates", this would satisfy us completely, since these dates follow the required delivery dates (always one day for transportation between them).

So the question is if VL10B shall prioritise based on these "confirmed delivery dates".

BR

Raf

[JL23 · Accepted solution]

do all your deliveries in VETVG table have the same priority (coming from ship-to partner sales org shipping data)?

[rafael_zaragatzky · Accepted solution]

Hi Jürgen,

Most of the orders have prio 2, but some don't have any priority. However, we couldn't observe that the priority affects the prioritisation of the orders in any way.

BR

Raf

[JL23]

have you seen OSS note 206985 VL10: Selection criteria for ordering index VETVG

[rafael_zaragatzky]

Thank you, Jürgen.

We don't use any additional selection criteria besides the date.

We are going to run a mass test in our test system now in an effort to reproduce the problem.

BR

Raf

[JL23]

I mentioned it because the OSS note explains that it cannot use the delivery date in case of STOs as it is the case with sales orders, because VETVG table does not have a delivery date, it just has an expected delivery creation date.

[rafael_zaragatzky]

Ah! Ok.

No, we don't select by the planned delivery date. We do use the delivery creation date and it would be fine for us if the system prioritised the orders with earlier "delivery creation date", since it is always one day before the planned delivery date - for all orders.

But unfortunately it doesn't. We will now do a full scale test with many orders, after having fixed the delivery priority for all the customers and also changed to package type 2. We have tested with this before, but now became unsure - maybe there were other disturbing factors at the same time when we ran the previous tests. So now it is time for a "clean" massive test.

BR

Raf