Package Creation and first steps

Updated 1 week ago by Stephanie Krenz

Description

The Package Editor is a very wide-ranging area and we will explain all the available options and functions in the next few articles. In the article Examples you will finally find two possible applications that will take you step by step from theory to practice. And before you know it, you'll be able to get started yourself!

Note
From version 1.16, some functions have been changed or extended. New or changed features are identified in the following sections.

Package Creation

To create a new package, click Package Studio at the top, then click + Package at the top right.

Enter a name, description (optional) and tags (optional) in the pop-up window. Click Create Package to proceed to the next section.


SAP System

The first important step in creating a package is to select an SAP System. Up to and including version 1.14.1, this step is mandatory. From version 1.16, you can close the selection window by clicking on the X in the top right-hand corner. This will return you to the package overview.

You will see a list of all the SAP systems registered in dab Nexus and you can select the system from which you want to extract the tables and their contents. From version 1.16 you can also see whether the connection test to this SAP system was successful or not by a green tick or a red X.

Beachte
If you select an SAP system that cannot be reached at the moment (no connection, not registered, incorrect logon data, etc.), an error message is displayed after the selection. In this case, either use another SAP system or try to find out the reason why the system cannot be reached. Contact your IT or SAP team.

Once you have successfully selected an SAP System, you will be taken to the Package Editor.


Toolbar from version 1.16

On the far left of the screen there are 3 lines that open the sub-functions. There you will find the following functions:

  • Import Package: import an existing package
  • Export Package: export a created package
  • Change SAP System: change the selected SAP System
  • Clear Table cache: all SAP tables stored in the package are reloaded - this is mainly required when moving from an R3 to an S/4HANA system or when Z fields occur in the tables.
  • Clear Report chache: all SAP reports stored in the package are reloaded - this is mainly required when moving from an R3 to an S/4HANA system or when Z fields occur e.g. in a Z report.
  • Reset to Analytic Group Package: if the package was created using an Analytic Group and then edited using the Package Studio, you can use this feature to reset all subsequent customisations.

To the right of these functions is the Packages button. This will take you back to the package overview. Next to it is the package name. Clicking on it will bring up a pop-up window where you can edit the package name, description and tags.

At the top in the middle you will see the Undo and Redo buttons - Undo the last change and Redo the last change respectively.

In the top right hand corner is the Permissions button. Here you can select which teams or individual users can see and use the package. If you select NO Teams/Users, ALL Teams/Users registered in Nexus will have access to the Package.

Click Save Package to save your changes.

Toolbar up to version 1.14
  • File
    • Save: save the Package
    • Import: import a Package
    • Export: export a Package
    • Quit: exit Package Editor
  • SAP System
    • Clear Table Cache (Version 1.11 or lower - Clear Cache and resolve all tables): is required if, for example, a Z field has been inserted in a table in an SAP system, but this does not exist in another SAP system - the structure of the tables is read again from the SAP system
    • Clear Report Cache (new from Version 1.12): is required if an integrated report has been changed in the SAP-system in order to transfer these changes to dab Nexus
    • Change SAP System (Version 1.11 or lower - Switch to): change the SAP-system
  • Diagram
    • Re-Draw: restore the diagram in the center if nodes have been moved
  • Help
    • Shortcuts: overview of the available keyboard shortcuts
  • Package-Name: if there is an asterisk * next to the name, the current changes have not yet been saved
  • Pen: change the name of the Package, the Description and Tags
  • Undo (arror to the left): undo last change
  • Redo (arror to the right): reverse last undo
  • Floppy disk: save the Package

Variants

These allow you to manage similar evaluations in one package and yet separate them using the variants. This eliminates the need to create a new package and gives you a better overview of the existing evaluations.

This allows you to use the same tables as in the standard version, but you can create new repositories and virtual tables.

From version 1.16

You will now find the variants at the bottom left of the screen. The standard variant is called Default. You can add more variants using the +.

In the following pop-up you can give the new variant a name and specify which of the existing variants you want to create a copy of. You can create it using Create Variant. By right-clicking on a variant, you can rename or delete it. Deleting only works if there is more than one variant.

Up to version 1.14

The standard variant is called Default -> You can add more variants via + Variant. By right-clicking on the variant name, you can rename the variant (Rename) or, if more than one variant exists, delete it (Delete).

How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)