Ansicht
Dokumentation

EXIT_RLVSDR40_001 -

EXIT_RLVSDR40_001 -

Fill RESBD Structure from EBP Component Structure   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Two user exits are available for the printing of transfer orders:
1. in RLVSDR40 -> MWMD0001 : EXIT_RLVSDR40_001
Print transfer orders (TOs)
2. in RLKOMM40 -> MWMD0002 : EXIT_RLKOMM40_001
Print TOs using the multiple processing task

Both user exits allow you to control the process of printing transfer orders. The two user exits also have the same transfer parameters. If you want a modification to become effective in both print reports, you must activate both user exits and include the code you have written in a shared routine. This is possible since both user exit function modules are contained in the same function group.

The following examples show you some of the modifications that can be carried out:

  1. Changing the sorting and consequently the printing sequence. To do this, you must change the order of the entries in table XRLDRI. The corresponding header data will be added automatically.
  2. Adding additional data and printing them on the forms. To do this, you can add fields at the TO header level to table XRLDRH and fields at the TO item level to table XRLDRI. Before you can do this, however, you must extend the dictionary of structures RLDRH and RLDRI using the corresponding append structures (no modification) and customize the forms (copy the standard forms, change them and add them to the Customizing application).
  3. Printing transfer orders using customer-specific function modules. This means that RLVSDR40 and RLKOMM40 are only used for retrieving the data. For the printing process itself, other programs are used. In the items of XRLDRI, the following fields specify how the printing process is to be carried out:
    SINGL = Print single TO: one TO item per document
    MULTI = Print combined pick list : multiple processing printing or TO
    list using RLVSDR40
    POCHA = Posting change TOs: both TO items of the posting
    change per document
    SUSLI = Storage unit documents
    ETIKE = Print labels
    For example, if no storage unit document should be printed, as this is done through the user exit, changing parameter C_SU can be blanked out.

The transfer tables and parameters have the following meaning:
xrldrc Control printing for each TO item based on the Customizing
settings (forms, spool indicator, printer, and so on).
Be careful when changing these settings. If two successive
items have different print parameters, a new spool request
will be created.
xvblkk Shipping header data, if available and if desired
xvblkp Shipping item data
xsernr Serial numbers for TO items, if available
xrldrh TO header data, HR data and texts
xrldri TO item data and switch for print function modules
xrldrp Kanban data, if available
xrldru Hazardous material data and texts
xt329p Spool parameters
xresb Reservations for replenishment TOs for production
xrlvek Packaging recommendations submitted through the packaging
user exit. Only on header level for the time being, no
packed items.
xreftab Table of reference numbers for printing the log when using the
multiple processing task. Only relevant in this context. If you
delete it, no log will be printed.
c_t312s Sort profile. When you print transfer orders using the
multiple processing task, fields GRW00 to GRW14 determine
after which fields a control break will occur, that is,
when a new print page will be generated.
c_lesch SU document with multiple barcodes
c_letasch SU document with source and destination storage bin
c_leinh SU contents document
c_single = X means that printing is to be started after the user
exit is quit, blank means that printing is not to be
started. The same applies to the following fields:
c_po (posting changes), C_SU (storage units), c_label (labels),
c_multi (multiple processing printing), c_multi_ref (combined pick list printing using the multiple processing task)






General Material Data   General Material Data  
This documentation is copyright by SAP AG.

Length: 4268 Date: 20240419 Time: 230743     sap01-206 ( 72 ms )