Purpose
The purpose of this page is to clarify the understanding of the system logic of VL10 transaction.
Overview
The following paragraphs and pictures will describe some characteristic (functionality and restriction) that are including in standard behavior of VL10.
Logic of selection date when delivering PO (stock transfer order or stock transfer scheduling agreement) in VL10:
To select a the PO, the delivery date must match two criteria:
(1) VETVG-LEDAT must fall in the range of selection date.
(2) There must be at least one schedule line, which's delivery creation date falls in the range of selection date.
For both point 1 and 2, the range of selection date means the from/to date of "Deliv.creation date" at the initial screen of VL10.
For point (1), you can check the VETVG-LEDAT in SE16. The VETVG-LEDAT usually is equal to the most early date among all the EKPV-LEDAT dates.
For point (2), system will calculate the delivery creation date for all the EKET entries and then compare it with the selection date. There are generally two situations:
- If EKET-MBDAT(material avaibable date) and EKET-TDDAT(transporation plan date) is set, system will use the earlier one as the delivery creation date.
- If MBDAT and TDDAT is blank for the schedule line, system will calculate the delivery creation date (EKET-EINDT minus EKPO-PLIFZ) ("delivery creation date" = "delivery date" -"Planned delivery time in days" )
So if you want to select certain schedulines, you may limit the selection by the from/to date. If you just enter a certain date in the "to date", system will select all the schedule lines, where the delivery creation date is earlier than that date.
As of the "delivery date"(LFDAT) and "delivery creation date"(LEDAT):
- LFDAT comes from EKET-EINDT. It means the request delivery date. Usually, in copy routine system fill LIKP-LFDAT with it when it is not earlier than the current date.
- LEDAT is calculated from schedule line, as mention above. LEDAT is the date that we compare with the range of selection date.
The setting in user role only works for background processing.
If you click the "background" button, only the selected item will be delivered. If you click the "dialog" button, system just work as VL01n, so it deliver the whole
order. This is standard logic and will not be changed.
VL10 or VL04?
Generally we recommend customer to user VL10* transaction instead of VL04.
VL10E(for sales order) or VL10F (for STO) transaction.
VL04 is an outdated transaction. VL10* is the new transaction, which is used for collective delivery creation.
Here are some basic points:
1. VL10* will have better performance than VL04.
2. VL10* provide more options to control the behavior of collective run.