Based on various business requirements it is possible to use VL10X transaction for delivery note creation. As an example...
Contents Introduction .................................................................................................................................................. 2 Delivery Scenario ...................................................................................................................................... 2 List Profile (Role) ....................................................................................................................................... 3 Configuration Steps....................................................................................................................................... 3 Configure List Profile ................................................................................................................................. 3 F Code Profile .......................................................................................................................................... 10 Allowed F Codes ...................................................................................................................................... 12 Delivery creation profile ......................................................................................................................... 12 Assign list profile to delivery scenario .................................................................................................... 12 Program VL10C as a background job .......................................................................................................... 14
Introduction Based on various business requirements it is possible to use VL10X transaction for delivery note creation. As an example we use VL10C for sales order line item delivery document creation, VL10E can be used to create delivery documents for schedule lines, etc. Therefore it is necessary understand how to configure this transaction based on your business requirement. SAP has given a provision to configure this transaction via a functionality called "Delivery Scenario" and "List profile (Role)". These fields can be seen under the "User Role" tab of the VL10X transactions.
Delivery Scenario “Delivery Scenario” is used to demonstrate business process of delivery documents that are ready for shipping. Based on the transaction you called for delivery document creation, relevant scenario will come in to play. Transaction VL10A VL10B VL10G VL10C VL10D VL10H VL10E VL10F VL10I VL10
Delivery Scenario 0001 0002 0003 0101 0102 0103 0201 0202 0203 VL10
Description Sales orders Purchase orders Sales orders and purchase orders Sales orders items Purchase order items Sales orders and purchase orders (items) Sales order schedule lines Purchase order schedule lines Sales orders and purchase orders (schedule lines) User-specific delivery scenario
As mentioned in the above table, transaction “VL10” can be freely defined for a user specific delivery scenario. In order to do that, you have to set the user parameter “LE_VL10_SZENARIO” under the transaction SU3.
List Profile (Role) This is a user role which contains fine-tuning controls for processing delivery lists. You can use user parameters to determine list profiles (Roles). Below user parameters are defined in the system for this purpose.
LE_0001_PROFIL -> Default User Role for Scenario 0001 -> VL10A LE_0002_PROFIL -> Default User Role for Scenario 0002 -> VL10B LE_0003_PROFIL -> Default User Role for Scenario 0003 -> VL10G LE_0101_PROFIL -> Default User Role for Scenario 0101 -> VL10C LE_0102_PROFIL -> Default User Role for Scenario 0102 -> VL10D LE_0103_PROFIL -> Default User Role for Scenario 0103 -> VL10H LE_0201_PROFIL -> Default User Role for Scenario 0201 -> VL10E LE_0202_PROFIL -> Default User Role for Scenario 0202 -> VL10F LE_0203_PROFIL -> Default User Role for Scenario 0203 -> VL10I LE_VL10_PROFIL -> Default List Profile for Creating Deliveries (TA VL10) -> VL10
Configuration Steps Configure List Profile Under this IMG node you can define control settings which can be used to fine tune the delivery due list. These settings can be mainly categorized as below;
Rule to setup default values for the delivery creation date Selection screen variants Attributes which can only influence to the layout of the delivery list output screen Which kind of documents can be selected for delivery processing
IMG Path:
Take a copy of standard list profile to implement custom requirements.
Eg: To change the VL10C transaction, I have to take list profile "0101"
Highlight the line and press the button copy Maintain your own profile ID and name for it (Starting with "Z")
Eg:
The description you specify here will be shown in the VL10C transaction Eg:
If you mark "Change Attribute" flag in the List Profile", system will allow user to change any value in the data that comes out of "List Profile" Customizing.
Important: But this field functions together with the "Allow Assignment" field in the "Delivery Scenario". If you want to do any changes in the transaction VL10 "User Role" tab, then you need to mark both tick boxes. This field can be found in the “Delivery Scenario” customizing.
If both fields are marked in customizing, then in the VL10C transaction, you should be able to change the list profile and individual values that determined from the list profile.
In order to change the individual values determined from the list profile, please un-tick the “Use List Profile”.
Under "Selection Criteria" field, select the document types which can be used for delivery (Eg: Sales Documents)
Mark "Open Deliveries" tick box. This setting will make sure only open delivery due sales orders get selected in VL10C transaction
Based on the setting you make under "List Type" field, the output screen will differ.
Eg: o
When Output -> Only the line details displayed
o
When Output -> Schedule line level data displayed
Field controls the default delivery creation dates appear in the VL10C transaction. Eg: o VL10C -> Take one month advance date
o VL10C -> Take today's date
o VL10C -> takes today and tomorrow date
You can go through the "F1" help of each field to understand how it controls the VL10C transaction and the output screen.
If you want to use the transaction VL10, you can even create your own selection variants and assign them under user parameter “LE_VL10_USER_VARIANT”. This variant will be set automatically when you call the transaction VL10.
F Code Profile This profile contains list of functions that needs to be carried out when the delivery due list is processed. This F code profile is assigned to your list profile in customizing.
Can create new function code profile under transaction “VL10CUF”. But this is a modification and not as Customizing or a user exit.
Allowed F Codes This is used to hide online functions in the delivery list to the list profile currently being used. For example we use this to avoid getting the delivery list output and create deliveries in background.
Delivery creation profile This contains the detail control profiles for creating and processing deliveries.
Assign list profile to delivery scenario Under this IMG node you have to assign the above created "List Profile" to your delivery scenario IMG Path:
Eg:
With this assignment, you can see the list profile "AW01" automatically comes to the transaction VL10C under "User Role" tab
Therefore based on the settings you have maintained under "List Profile" the transaction "VL10C" will behave.
Program VL10C as a background job Please also note, if you want to use the transaction VL10C (Program - RVV50R10C) as a batch job to create delivery notes, then you need to below changes;
Add “F Code Profile” as 5001
Add below function code under the tab “User Role” in to your variants.
Please check the collective note – 113411 on various VL10 corrections.
Author: Anupa Wijesinghe E-Mail:
[email protected] /
[email protected] Website: www.learnsaptips.com View my profile in LinkedIn Follow me on Twitter
Disclaimer This article is done based on my research and readings, unless otherwise stated. The views expressed are my own and not of anyone else. Author accepts no liability for the content of the articles in this website or for the consequences of any actions taken on the basis of the information provided. Using this information is at the users own discretion and responsibility.
