cancel
Showing results for 
Search instead for 
Did you mean: 

Info on VL06

Former Member

Hello Gurus,

VL06 transaction lists the deliveries which are due for

Checking, Distribution, Confiramtion, Loading, Goods Issue and Transportation Planning.

Could you please explain what each of these signify and what exactly when you delivery through each of these phases. What settings or fields are updated.

all apt answers are rewarded....

Regards,

Pavan P.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Before final billing is done, it should be checked that the prior processes have occured successfully, so that the customer is billed for the delivered material only and that too at the fixed price as per in quotation or order.

for what exactly does the following process signify:

Material Checking: This process actually checks the material availability in our stock so that a confirmed delivery date to the customer can be allotted.

Distribution link: This link signifies by which link the product is going to reach customer.

like sales organization, distribution channel and division.

Confirmtion: The confirmation of the available goods and their requested delivery date.

Loading:The product to be delived has to be loaded in the transportation vehicles e.g. truck, train, etc.

Goods Issue :The confirmation that goods have left our factory to be delivered to the customer.

Transportation Planning The channel / route through which the transportation of goods from plant to customer would be reaching.

e.g. half of the transportation would be through train, remaining through truck,etc.

regards,

Siddharth.

ranjeetrajendra_jain
Active Contributor
0 Kudos

Simplified Delivery Processing Using the Delivery Monitor

Description

As of Release 4.5A, there is a new function called the "Delivery Monitor" which is used to display and process open and completed deliveries. In addition to expanded selection options for calling up the worklist, this new function provides a number of follow-on functions for further processing of deliveries and for calling up information in the delivery environment.

The delivery monitor will, in future, replace the transactions for 'Deliveries in Process' and the 'Delivery List for Partner and Material'. These include:

VL15 Deliveries to be confirmed

VL16 Deliveries to be picked

VL17 Deliveries to be loaded

VL18 Deliveries for transportation planning

VL19 Goods issue to be posted for deliveries

VL05 Deliveries for partner and material

The above transactions are no longer available in Releases 4.5A and 4.5B via the menu, but can now only be called up using the respective transaction code. In future releases, we plan to drop these functions altogether.

Change system parameters in customizing

The delivery monitor no longer needs a link to Customizing. You can maintain the display variants of the various lists within the delivery monitor itself, either on a user-specific or company-wide basis.

The required Customizing settings for the display variants of transactions VL05 and VL15 up through VL19 can no longer be configured using IMG. You can, however, call up the respective Customizing transactions to maintain these display variants:

Transaction VOL0 for maintaining display variants of VL05

Transaction VOL6 for maintaining display variants of VL15 - VL19

The functions for including user-specific fields into the display variant have been simplified to a large degree. In most cases, it is sufficient if you extend the respective dictionary structure in order to display fields at header or item level of the delivery. Programming of user exits will, for the most part, no longer be necessary.

For special requirements, you have the customer exit V50Q0001 at your disposal. For more information on how to set up your own special display variants (Transaction SMOD), refer to the documentation of the customer exit.

The user exits that existed up to now for transactions VL05 and VL15 through VL19 are not called up by the delivery monitor.

Effect on batch input

The transactions for deliveries in process are not suitable for background processing (batch input) for technical reasons.

Using the delivery monitor, you canh execute certain collective processing runs for deliveries in background processing. You will find more information on this also in the documentation.

Regards

Lakshmipathi
Active Contributor
0 Kudos

Dear pavan

the link is self explanatory

[Working with the Delivery Monitor |http://help.sap.com/saphelp_46c/helpdata/en/fe/51f5d2fc6511d1850b0000e81ddea0/frameset.htm]

In the above link, on your left screen, three more additional links are there. Go through the same.

thanks

G. Lakshmipathi