Show TOC

 Definition of Variants Locate this document in the navigation structure

You can adapt the mass processing function and the order information system in a very flexible way, to meet the requirements of your company and its individual users. You can put together user-dependent report variants, report transactions, and variant transactions to provide every user with the exact range of functions required.

Techniques Used
  • Report variants

    With a report variant, (see Variant Maintenance ) you can specify default values for fields, hide fields or make them unavailable for input on the initial screen of a program. You can use report variants to schedule in the background or to define a report transaction. For technical reasons, only the display and input availability of the selection criteria can be influenced for the program. The display and input availability of other fields (for example, the parameters for mass processing or the list category) can only be controlled via a transaction variant. Conversely, the selection criteria cannot be influenced in the transaction variant.

    Note Note

    In the technical settings in variant maintenance of the report PPIO_ENTRY, you can specify defaults for the following values:

    • Order category (production or process order)

    • Transaction for which an authorization check should be carried out, if this variant is selected in a different transaction

    • Lists that can be selected (for example, components, operations, and so on)

    • Functions that can be selected (for example, exclude)

    • Mass processing active

    • Old ALV output

    Choose the variant maintenance function (transaction SE38). Enter the report PPIO_ENTRY, select Variant , and choose Change. Enter the desired variant and choose Change . Make the necessary settings in the Technical Settings area .

    End of the note.

    Note Note

    You can use the report PPIO_ENTRY_VARIANT_DISPLAY to display an overview of variants and their technical settings. The system issues information such as which output list, overall profile, and layout have been predefined.

    If no overall profile has been defined, the system uses the overall profile from the user specifications (in other words, from the SET/GET parameter IOC) or the last overall profile that was used.

    If no layout has been entered, the system automatically uses the default layout or the standard layout (if no default layout has been entered for this list).

    End of the note.
  • Report transactions

    A report transaction is used to call up a report variant of a program. You can insert a transaction in the menu or add it to the favorites list.

  • Transaction variants

    With a transaction variant (see Maintaining Transactions and Variant Transactions ) you can also hide fields or specify default values for them (for example, the parameters for mass processing, list category, production order selection, planned order selection or process order selection).

  • Variant transaction

    A variant transaction is used to call up a transaction variant (see Maintaining Transactions and Variant Transactions ). You can insert a transaction in the menu or add it to the favorites list. A variant transaction can, for example, be added to a user's favorites menu or role menu.

Example

The following example shows you how to create a customized transaction for reprinting time tickets.

  1. Defining a report variant

    Using transaction SE38, you define the report variant Z_LV01 for program PPIO_ENTRY. When you do this, you preset the following:

    • The operation list is the only list that can be selected.

    • The object Operations is predefined for the List field.

    • The Mass Processing Active indicator is set.

    • Selection fields that are not needed are hidden.

    • Print and Print mode , as mass processing functions, are preset for immediate execution. You define that these fields are blocked for entry.

  2. Defining a report transaction

    Using transaction SE93, you define the report transaction Z_LV01_T for report variant Z_LV01 of program PPIO_ENTRY.

  3. Defining a transaction variant

    Using transaction SHD0, you define the transaction variant Z_LV01_01 for report transaction Z_LV01_T. You hide the Production orders and Planned orders fields.

  4. Defining a variant transaction

    Using transaction SE93, you define the variant transaction ZLV01 for transaction variant Z_LV01_01 of report transaction Z_LV01_T. This variant transaction can be added to a user's favorites menu or role menu, for example.

Execution in the Order Information System and Mass Processing

The central program for mass processing and the order information system is PPIO_ENTRY. Examples have been set up in the standard system to demonstrate the use of the options described above:

Mass Processing

Variant transaction

Transaction for production order: COHV

  Logistics   Production   Shop Floor Control   Control   Mass Processing.  

Transaction for process order: COHVPI

  Logistics   Production – Process   Process Order   Tools   Mass Processing  

Report variant

Report : PPIO_ENTRY, V ariant : SAP&HVOM or SAP&HVOMPI

Order Information System

Report transaction

Transaction for production order: COOIS

  Logistics   Production   Shop Floor Control   Info System   Mass Order Information System.  

Transaction for process order: COOISPI

  Logistics   Production – Process   Process Order   Tools Mass Processing

Report variant

Report : PPIO_ENTRY, V ariant : SAP&COOIS or SAP&COOISPI

Collective Release

Variant transaction

Transaction : CO05N

  Logistics   Production   Shop Floor Control   Control   Collective Release.  

Transaction variant

Transaction : COHVOMRELEASE, T ransaction variant : CO05

Report transaction

COHVOMRELEASE

Report variant

Report : PPIO_ENTRY, V ariant : SAP&RELEASE

Print

Variant transaction

Transaction : CO04N

  Logistics   Production   Shop Floor Control   Control   Print.  

Variant transaction

Transaction : COHVOMPRINT, T ransaction variant : CO04

Report transaction

COHVOMPRINT

Report variant

Report : PPIO_ENTRY, V ariant : SAP&PRINT

Collective Availability Check

Variant transaction

Transaction : COMAC

  Logistics   Production   Shop Floor Control   Control   Collective Availability Check.  

Report variant

Report : PPIO_ENTRY, V ariant : SAP&AVAILCHK

Missing Parts List

Variant transaction

Transaction : CO04

  Logistics   Production   Shop Floor Control   Info System   Missing Parts Information System.  

Report variant

Report : PPIO_ENTRY, V ariant : SAP&PRINT

Pick List

Variant transaction

Transaction : CO27

  Logistics   Production   Shop Floor Control   Goods Movements   Material Staging   Pick  

Report variant

Report : PPIO_ENTRY, V ariant : SAP&PICK or SAP&PICKPI