The following problems occur if you print in WM:
- The system determines the incorrect printer
- The system prints with the incorrect print code
- The system prints with the incorrect spool code
- The system uses the incorrect form
- No print occurs
You make the settings for the print control in Warehouse Management in the IMG under the following path: 'Logistics Execution -> Warehouse Management -> Activities -> Define print control'.
1. Determination of the print code
The system determines the print code from the movement type used to generate the transfer order. If you print from multiple processing, the system copies the print code from the table for the collective print control. You find the settings in the print control under the items 'Assignments -> Print code -> Movement type' and 'Print control -> Multiple processing'.
2. Printer determination
You can influence the printer determination by means of numerous settings. First, the system searches for a printer in the table 'Assignments -> Printer -> Warehouse movements' in the print control. Here you can store a printer for different warehouse movements where both masked entries for the source and destination storage type and individual storage types are permitted. The system always selects the more specific entry. That is, for example, if a transfer order item has source storage type 001 and destination storage type 916, the system first searches for an entry with source storage type 001 and destination storage type 916. If this entry does not exist, the system searches for the entry with source storage type '***' and destination storage type '916'. If this entry does not exist as well, the system searches for the entry with source storage type 001 and destination storage type '***'. If it does not find an entry here, it uses the entry with source storage type '***' and destination storage type '***'. If the system finds a printer in this table, it terminates the printer determination here. You can also set the 'Printer src.st.type' flag. In this case, the system searches for a printer in tables 'Assignments -> Printer -> Picking area' and 'Assignments -> Printer -> Storage type'. If no printer has been determined, the system uses the default printer stored in the user master. If no printer is stored here as well, the system uses the printer LP01 by standard.
3. Spool code
The spool code is determined via the print code found. You can use the item 'Definitions -> Spool code' to assign the spool code to the print code. If, however, a different spool code is stored for the corresponding warehouse movement in table 'Assignments -> Printer -> Warehouse movement', the system uses the spool code from the warehouse movement and overwrites the spool code stored in the print code.
The forms are stored for the corresponding print code like the spool code, however, they can be overridden like the spool code by entries in 'Assignments -> Printer -> Warehouse movement'.
SAP provides the following forms (depending on the release):
- LVSBINPRINT Storage bin labels
- LVSETIKETT Picking labels
- LVSHULABEL Print HU label
- LVSKOMMIL1 Picking list for several TOs
- LVSKOMMIL2 Picking list for several TOs
- LVSLABELS Picking labels
- LVSLEINHALT SU Table of Contents
- LVSLESCHEIN SU slip
- LVSLETASCHEIN SU TO slip
- LVSPICKLIST Picking list with totals
- LVSSAMMELKANBAN Print Transfer Order List
- LVSTAEINZEL Print TO Individual Item
- LVSTALISTE Print Transfer Order List
- LVSTOSOLO Print TO Individual Item
- LVSTOSOLOKANBAN Print TO Individual Item
- LVSUMBUCHEN Posting change notice
5. Print of SU slips
You can store further forms for SU TO, SU slip and SU table of contents in the print control for storage units (IMG path 'Logistics Execution -> Warehouse Management -> Storage units -> Activities -> Define print control'). The items for 'Definitions -> Print code' and 'Assignments -> Printer -> Warehouse movement' contain further views for the additional SU slips. For each form, you can activate and deactivate the print here. In addition, you can store the spool data for each SU slip.
However, the print of the SU slips only occurs under clearly defined prerequisites. You can see from the following table whether an SU slip is printed. An 'x' in the column means that a slip is printed when the corresponding movement occurs.
Movement SU slip SU TO slip SU table of contents
Putaway x x x
new SU,, ,,
Stock tranfer,, x x x
and formation of new SU,, ,,
Complete x x
pick SU,, ,,
Pick partial,, ,,
quantity of SU,, ,,
Stock transfer x x
complete SU,, ,,
Stock transfer ,,
partial quantity SU,, ,,
6. Label printing
As of Release 4. 0, you can print labels in addition to the transfer order. You can issue the labels on a separate printer you can define under 'Printer pool/labels' in the print control, for example, since you want to use different paper. You can store the form of label in the print code. This can be overridden by entries in table 'Assignments -> Printer -> Warehouse movement' as well. In addition you can define that several labels should be printed for each transfer order item and you can store a separate label spool code.
7. Analysis of the print tables
You can use the 'Print control tables -> Analyze' pushbutton in the print control to simulate the print for a specified TO item. Based on the log issued, you can follow the accesses of Customizing tables and recognize a possible error cause during the print of the TO. Instead of the TO item, you can also specify different parameters like source storage type, destination storage type, picking area, print code, printer or spool code and simulate the print using these parameters. If the analysis returns a 'Do not print', the system does not print the TO item. Probably the 'No print' indicator is set in table 'Assignments -> Printer -> Warehouse movement'.
8. Printing using a separate print reports
If the above analysis of the print tables did not clarify the cause of the error, a further source of the error may be the use of a separate print report. Thus attempt to repeat the print using the corresponding SAP standard report. If the error no longer occurs then, the cause of the error is your print report. You can maintain the print reports under the items 'Print report -> Warehouse number' and 'Print control -> Multiple processing'. The SAP standard reports are RLVSDR40 for the TO single print and RLKOMM40 for the multiple processing. In releases <= 4.0, the standard reports are RLVSDR00 and RLKOMM00.