Document toolboxDocument toolbox

Copying a Query

The chapter starts with a simple case, describing the copying process of Queries. A new Query is created on the same InfoProvider. More complex cases are explained in the next chapter Application Scenarios.

First of all, the Type “Query” (first checkbox), as well as a specific Query on the left sub-screen of an SAP system, needs to be selected. As soon as a Query has been picked it will appear together with its corresponding InfoProvider below the left table.

Source Element area with selection of the system, object type and Reporting Object

The next step includes choosing an SAP BW-System (Field “SAP System”), one or more InfoProvider-Types (Checkboxes “Type”) and a Target-InfoProvider on the right sub-screen. The chosen InfoProvider is shown below the right table. Tap “Next” to confirm the selection. 

Target element area with selection for the system, InfoProvider type and InfoProvider

Now technical names of Reporting Elements and the included Objects can be changed manually. The “Execute consistency checks” button initiates the validation of the “new” Query. For example, it is important that technical names are correct and necessary Objects are part of the target system.

List of all elements contained in the Query with current and new technical name and consistency check button

In a new window, the technical names of elements from the Source-Query (“Tech. Name (Target)”) and the Target-Query “(Tech. Name (Source)”) will be displayed.

Element

Display in Tool

possible Renaming

Mapping

New set up when copying

Query

yes

mandatory

-----------------

yes

Global Structure

yes

mandatory, if Mapping of underlying InfoObjects has been changed

automatized

yes, if underlying InfoObject has been changed

Key Figure

yes

no

automatized or manually

no

Characteristics

yes

no

automatized or manually

no

Variable

yes

mandatory, if Mapping of underlying InfoObjects has been changed

automatized

yes, if underlying InfoObject has been changed

Calculated Key Figure

yes

mandatory, if Mapping of underlying InfoObjects has been changed

automatized

yes, if underlying InfoObject has been changed

Restricted Key Figure

yes

mandatory, if Mapping of underlying InfoObjects has been changed

automatized

yes, if underlying InfoObject has been changed

Local Structure

no

no

automatized

yes

Element of local Structure

no

no

automatized

yes

Condition

no

no

automatized

yes

Exception

no

no

automatized

yes

Cell definition

no

no

automatized

yes

Selection

no

no

automatized

yes

Formula

no

no

automatized

yes

Using the “Mass Edit” function, Reporting Elements of different types in one Query can be renamed simultaneously.

Mass edit area with settings for the prefix and replacement of first letters

The “Apply target values” button starts the final process of generating a new Query. A dialog window appears with the information that all replacements have been successful and the Elements can now be created.

Successful Consistency check and Apply target values button now activated

With “Start creation” the Query can be created. Afterward, a pop-up shows the Query’s Returncode.

Returncode 0 indicating that the creation was succesful

In general, the Docu Performer writes all Reporting Elements after copying to the package $TMP. In some cases, this is not possible. This could be related to the settings (RSA1 > Transport Connection, Menu Edit > Transport) in your SAP system. If it is not possible to write the entities to the package you get the message below. That means copying was possible but writing to package not.

Return code 0 with warning, that no TADIR entries were created

 Changing an InfoObject to Field manually does NOT adjust the respective Base Object for Variables. That means you also have to manually adjust Base Objects from Variables.

© 2023 bluetelligence GmbH. All rights reserved.
Impressum – Legal Notice: https://bluetelligence.de/en/imprint
Privacy policy: https://performersuite.de/en/privacy-policy
Atlassian privacy policy: https://www.atlassian.com/legal/privacy-policy