Collective process of VL10* is as follows
The transaction VL10 selects and processes orders and purchase orders due for delivery according to specific criteria. In addition the user can also select deliveries according to specific criteria. These can be:
A) deliveries that already exist for the sales orders and/or
B) in release 4.6C deliveries that were selected using other criteria. This is an independent transaction and can be executed without the sales order or purchase orders.
Integration
Delivery of documents (orders) via the delivery list is integrated in the following logistics supply chains:
Sales order - Delivery - Picking - Shipment - Billing document
Purchase order - Delivery - Picking - Shipment - Billing document/ Self-billing
Prerequisites for maintenance
Owing to the very user-specific nature of the settings of these transactions, it is essential for the processing of related problems to specify a selection variant with which the problem can be reconstructed. This can be generated in the menu on the selection screen for the extended delivery list under Goto > Display variant > Save as variant. Note that you must choose the variant in such a way that the reconstructing of the problem is not only possible for the day on which the variant was created. This means in particular that the considered document or documents must also appear in the delivery list at a later time.
The extended delivery processing in Transaction VL10 is delivered in the background up to and including Release 4.0B. Pilot customers for Transaction VL10 in release 3.1I or 4.0B are known to LE development and only they obtain the normal maintenance support.
Please look for note with the key word VL10 or VL10* to obtain the best result.
Functions
Differences between VL04 and VL10
As of Release 4.6, transactions VL10., VL10A, VL10B,.. replace transaction VL04.
With the transaction VL10 it is not only possible to create deliveries for complete documents, as it is with VL04, but for selected items or schedule lines.
There are more selection criteria with VL10*, for example: selection via partner criteria.
If you call up transaction VL04 in release 4.6, transaction VL10 will appear with the VL04 scenario (processing delivery list in upward compatibility mode for transaction VL04). For upward compatibility reasons, the standard system in Release 4.6 will still access the previous functions and report RV50SBT1 is started.
Difference between Dialog and Background
The creation of deliveries in dialog mode calls the transaction VL01N and each selected document is delivered completely. The system takes the at this moment available quantities into account. The user can deleted items that should not be delivered or change the quantities for each item.
The creation of deliveries in background mode processes document collectively.
(warning) After introducing the new transaction VL10, the dialog functionality from transaction VL04 was included because a lot of customers were used to use this function. Hence this function is also part of the collective delivery process but there were no changes made in this functionality for technical reasons. When we designed release 45B we had the possibilities either not to allow the creation in dialog from the Vl10 delivery due list or to provide a function which probably doesn't fit to the new functions of VL10. We decided to choose the latter.
When you create a delivery in dialog mode, the VL10 calls the transaction VL01N (single delivery) and the system is not able to distinguish between items and schedule lines and will therefore create the delivery for all items. The system will NOT recognize selected items and will create the delivery for all items regardless, leaving behind the items with varying data. It will work in background though.
List display
Display variants
The delivery due list is a ALV list (ABAP List Viewer). The user can choose which columns are displayed. The display can be save in a (user-specific) display variant (Settings > Layout > Save) and marked as default variant for this combination of List type, Display and selection (Settings > Layout > Manage).
Each user can save different user display variants. The criteria under which the independent variants are saved are:
List type (Index or Document list)
Layout (sequential or hierarchical))
Display with or without deliveries
header-item-assignment with hierarchical list display
While the list is build up or refreshed the values are taken from the user role and assigned to the (user-specific) default display variant.
In the SAP standard there are already default display variants assigned to user roles. The suffix of the variant name is a stringing together of the attributes list type, layout, with/without deliveries and header-item-assignment from the user role.
The transaction VL10 selects and processes orders and purchase orders due for delivery according to specific criteria. In addition the user can also select deliveries according to specific criteria. These can be:
A) deliveries that already exist for the sales orders and/or
B) in release 4.6C deliveries that were selected using other criteria. This is an independent transaction and can be executed without the sales order or purchase orders.
Integration
Delivery of documents (orders) via the delivery list is integrated in the following logistics supply chains:
Sales order - Delivery - Picking - Shipment - Billing document
Purchase order - Delivery - Picking - Shipment - Billing document/ Self-billing
Prerequisites for maintenance
Owing to the very user-specific nature of the settings of these transactions, it is essential for the processing of related problems to specify a selection variant with which the problem can be reconstructed. This can be generated in the menu on the selection screen for the extended delivery list under Goto > Display variant > Save as variant. Note that you must choose the variant in such a way that the reconstructing of the problem is not only possible for the day on which the variant was created. This means in particular that the considered document or documents must also appear in the delivery list at a later time.
The extended delivery processing in Transaction VL10 is delivered in the background up to and including Release 4.0B. Pilot customers for Transaction VL10 in release 3.1I or 4.0B are known to LE development and only they obtain the normal maintenance support.
Please look for note with the key word VL10 or VL10* to obtain the best result.
Transactions
Documents for selection
| |||||
|---|---|---|---|---|---|
Orders SD
|
Purchase Orders MM
|
SD + MM
|
Role
|
Szenario
| |
VL10
|
0001
|
VL10
| |||
VL10A
|
VL10B
|
VL10G
|
Index level
|
0001 / 0002 / 0003
|
0001 / 0002 / 0003
|
VL10C
|
VL10D
|
VL10H
|
Item level
|
0101 / 0102 / 0103
|
0101 / 0102 / 0103
|
VL10E
|
VL10F
|
VL10I
|
Schedule line level
|
0201 / 0202 / 0203
|
0201 / 0202 / 0203
|
VL10X: Choice of scenario, Technical collection of all transactions
VL10CU: Delivery scenario, table T186V
VL10CUV: Delivery scenario, table T186V
VL10CUA: List profiles (user role) for Shipping Due List
VL10CUA, table T186A
VL10CUC: Parameter per Profile in Delivery Process, table T186C
VL10CUE: Include/Exclude Function Codes, table T186E
VL10CUF: Functions in the Shipping Due List, T186F
VL10Batch: Batch job, RVV50R10C
VL10Batch_A: Batch job, RVV50R10A
VL10Batch_B: Batch job, RVV50R10B
Functions
Differences between VL04 and VL10
As of Release 4.6, transactions VL10., VL10A, VL10B,.. replace transaction VL04.
With the transaction VL10 it is not only possible to create deliveries for complete documents, as it is with VL04, but for selected items or schedule lines.
There are more selection criteria with VL10*, for example: selection via partner criteria.
If you call up transaction VL04 in release 4.6, transaction VL10 will appear with the VL04 scenario (processing delivery list in upward compatibility mode for transaction VL04). For upward compatibility reasons, the standard system in Release 4.6 will still access the previous functions and report RV50SBT1 is started.
Difference between Dialog and Background
The creation of deliveries in dialog mode calls the transaction VL01N and each selected document is delivered completely. The system takes the at this moment available quantities into account. The user can deleted items that should not be delivered or change the quantities for each item.
The creation of deliveries in background mode processes document collectively.
(warning) After introducing the new transaction VL10, the dialog functionality from transaction VL04 was included because a lot of customers were used to use this function. Hence this function is also part of the collective delivery process but there were no changes made in this functionality for technical reasons. When we designed release 45B we had the possibilities either not to allow the creation in dialog from the Vl10 delivery due list or to provide a function which probably doesn't fit to the new functions of VL10. We decided to choose the latter.
When you create a delivery in dialog mode, the VL10 calls the transaction VL01N (single delivery) and the system is not able to distinguish between items and schedule lines and will therefore create the delivery for all items. The system will NOT recognize selected items and will create the delivery for all items regardless, leaving behind the items with varying data. It will work in background though.
List display
Display variants
The delivery due list is a ALV list (ABAP List Viewer). The user can choose which columns are displayed. The display can be save in a (user-specific) display variant (Settings > Layout > Save) and marked as default variant for this combination of List type, Display and selection (Settings > Layout > Manage).
Each user can save different user display variants. The criteria under which the independent variants are saved are:
List type (Index or Document list)
Layout (sequential or hierarchical))
Display with or without deliveries
header-item-assignment with hierarchical list display
While the list is build up or refreshed the values are taken from the user role and assigned to the (user-specific) default display variant.
In the SAP standard there are already default display variants assigned to user roles. The suffix of the variant name is a stringing together of the attributes list type, layout, with/without deliveries and header-item-assignment from the user role.
No comments:
Post a Comment