SAP Note

Header Data

Symptom

Problem: Entering and transporting variants for queries

Temporary reports are generated from queries.The variants are entered for these reports and are therefore sub-objects of these reports. Since temporary objects cannot be transported, certain measures are required to transport variants for queries because report variants do not have any TADIR entries.

Other Terms

Query, report, variant, transport, AQQV

Reason and Prerequisites

While entering and transporting a query and its variants, you must distinguish between queries defined in the standard area (client-specific) or in the global area (cross-client).

Solution

Entering variants

You can always enter variants using the 'Goto  Variant maintenance' function on the initial screen of transaction SQ01 or when you execute a selection screen.

1. Query from the standard area (client-specific) No system variants can be created for these queries.

2. Query from the global area (cross-client) System variants may exist for these queries(starting with SAP& or CUS&). In the customer system, you can only create system variants starting with CUS&.System variants starting with SAP& are delivered by SAP and cannot be modified in the customer system.You should always enter system variants via the 'Goto  Variant maintenance' function on the initial screen of transaction SQ01, otherwise, the connection to the Workbench Organizer will not work. You can enter other variants as desired.

Transporting queries

A detailed description of the procedure for transporting queries, including variants, is provided in the section 'Transport query objects' of the query guide.

1. Query from the standard area (client-specific) These queries are transported in three steps with the aid of a special transport utility('Environment -> Transports' function on the initial screen of Transaction SQ02).

a) Generate a transport dataset in the source system (export, during which a transport request is created for the transport dataset)

b) Transport the transport dataset with the help of the Workbench organizer

c) Transfer the transport dataset to a client of the destination system (import)

You can transport all variants of a query with this transport (no selection is possible).However, a variant is never imported if a variant with the same name already exists in the relevant client of the destination system.An import in this case is not possible, even if you select the 'Overwriting permitted' option.This option refers to the variants as well as the query.

2. Query from the global area (cross-client) In the global area, only the transport of system variants is supported.Other variants cannot be transported. System variants for queries' must (as already described) always be maintained using the 'Goto -> Variant maintenance' function on the initial screen of Transaction SQ01.With this type of maintenance, you ensure that the variant is entered in a transport request with the help of the Workbench organizer if the query is a not temporary object (see above, transport object R3TR AQQV).You can then distribute the system variant with the usual transport mechanisms. In addition, system variants of queries can also be transported by manually writing the

    412054 - SAP query: How do I transport variants for queries  

Version   6     Validity: 13.08.2001 - active   Language   English

Released On 13.08.2001

Release Status Released for Customer

Component BC-SRV-QUE SAP Query

Priority Recommendations / Additional Info

Category Consulting

corresponding entries into a transport request. R3TR AQQV <Reportname of the Query><10 Space><Variant name> You will find the name of the generated query report via the 'Goto Other functions -> Display report name' function on the initial screen of transaction SQ01. Example: You want to transport the system variant SAP&MEPOAN of the query MEPO of user group /SAPQUERY/ME.To do this, make the following entry in the object catalog of a transport request: R3TR AQQV AQZZ/SAPQUERY/MEMEPO========== SAP&MEPOAN

Validity

This document is not restricted to a software component or software component version

Support Packages & Patches

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (1)

Support Packages

Software Component Release Support Package

ECC-DIMP 500 SAPKIPMH04

617179   ME81N: F4 help doesn't work for selection field 'Material'

617179   ME81N: F4 help doesn't work for selection field 'Material'