EnjoySAP - Ergonomic Improvements in Delivery Processing
Scope of Functions
Dialog processing of inbound and outbound deliveries was completely revised during SAP's Enjoy initiative.
- The delivery data is now organized in process-oriented groups, making it easier for the user to find.
- Foreground navigation is easier thanks to buttons and tabstrip controls.
- A status overview gives you a summary of the delivery document's processing status at a glance.
- You can switch from display to change mode without having to exit the application.
New processing transactions have the following new transaction codes:
- Outbound deliveries
- VL01N Create outbound delivery with order reference
- VL01NO Create oubound delivery without order reference
- VL02N Change outbound delivery
- VL03N Display outbound delivery
- Inbound deliveries
- VL31N Create inbound delivery
- VL32N Change inbound delivery
- VL33N Display inbound delivery
You can also reach the above transactions by way of the SAP Easy Access navigational menu. These transactions have the same range of functions as the previous delivery processing transactions.
Effects on Existing Data
The new transactions do not require any dataset conversion, transfer or change in any way.
Effects on System Administration
Continuation of the previous delivery processing transactions
In order to make the conversion to the new dialog transactions easier for you, the previous transactions for foreground processing of inbound and outbound deliveries (transactions VL01, VL02 and VL03 or VL31, VL32 and VL33) are still fully functional in Release 4.6. However, the old transactions are only accessible via transaction code and not by using the SAP menu.
Transactions VL01 through VL03 and VL31 through VL33 will not be supported in future releases. Before you upgrade to a release following 4.6, you should therefore convert your processes to the new transactions. This also applies to calling up the transactions within your own batch inputs or reports.
Incompletion processing
In the new delivery dialog, new internal function codes are used to navigate through the various detail screens. This also affects Customizing of the delivery's incompletion log, since function codes are necessary for navigation of the data fields recorded in the incompleteness procedure.
Basically, you can process the incompletion log in the old delivery dialog and in the new one. However, you can only maintain the function codes for one dialog or the other in Customizing for the incompletion log.
To make the conversion to the new dialog easier for you, the SAP standard error procedure for incomplete groups G (delivery header) and H (delivery item) are already converted to the new function codes.
Effects on Customizing
As described above, this switch to new internal function codes makes it necessary to adjust the incompletion control.
See: 
Define incompletion procedures .
No other Customizing activities are necessary.