Ansicht
Dokumentation

ISM_PDEX_WORKLIST - Define Transaction Variants

ISM_PDEX_WORKLIST - Define Transaction Variants

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you can define transaction variants for the media issue worklist. Customer-specific transaction variants must begin with a letter.

A transaction variant in the media issue worklist uses a function group to group several transactions, which can be accessed from the worklist using the Other Functions menu option.

You define transaction codes for the maintenance and display transactions for each transaction variant.

You can specify the following for each transaction variant:

  • Which views are to be listed in the media issue worklist
    (You can hide plants and sales areas.)
  • The appearance of the selection screen for period selection
  • The layout

To create a selection screen for a specific transaction variant, proceed as follows:

  1. Create a module pool in the customer name range (for example, ZZRJKSDWORKLIST) using transaction SE38.
  2. Copy screen RJKSDWORKLIST/0310 to create a new screen (for example, ZZRJKSDWORKLIST/9310). Turn the existing modules PBO_310./PAI_310 into comments or delete them in the flow logic.
  • Flow logic of the screen copied:

PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
  1. Add a TABLES statement for RJKSDWORKLIST_CHANGEFIELDS to the module pool (for example, in ZZRJKSDWORKLIST).
  • Source code of module pool:

PROGRAM ZZRJKSDWORKLIST.
TABLES: RJKSDWORKLIST_CHANGEFIELDS.

To define the layout of a transaction variant, proceed as follows:

  1. You can specify whether each field is to be hidden or displayed in the transaction variant. The system uses the standard layout for fields that have not been entered in the Field Name column in this Customizing activity. You can choose the field status Display Only or Hidden for fields you list here.

You have already assigned functions Z0, Z1, and Z2 to function group ZZ.

Step 1:

You now assign function group ZZ to a transaction variant ZZ_JKSD13. When you access this transaction variant, you can navigate to the functions (transactions) assigned to the function group.

Step 2:

You create transaction ZZ_JKSD13 as a copy of the standard transaction JKSD13.

You can adjust the layout of the following fields:

Include RJKSDWORKLIST_MARA contains basic data fields (MARA). If you select a basic data field, choose the prefix 'MARA-' for the field name.

For example, you enter the field name MARA-FIELD1 for field RJKSDWORKLIST_MARA-FIELD1.

Include RJKSDWORKLIST_MARC contains plant data fields (MARC). If you select a plant data field, choose the prefix 'MARC-' for the field name.

For example, you enter the field name MARC-FIELD1 for field RJKSDWORKLIST_MARC-MARC_FIELD1.

Include RJKSDWORKLIST_MVKE contains sales area data fields (MVKE). If you select a sales area data field, choose the prefix 'MVKE-' for the field name.

For example, you enter the field name MVKE-FIELD1 for field RJKSDWORKLIST_MVKE-MVKE_FIELD1.






PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3668 Date: 20240329 Time: 130030     sap01-206 ( 51 ms )