Performing a Package Check 

With the package check, you have the option of ensuring that the different relationships of the Repository objects are defined correctly in accordance with the package concept rules. The package check covers the static relationships between repository objects, in much the same way as the syntax of an ABAP program or the activation of a repository object is checked.

Note that package checks are always performed at the design time of the development object, not at compile time or runtime. This means that dynamic uses of the object (such as calling a function module) are not checked.

Procedure

The ABAP Workbench provides the option of performing a package check at different times in the development phase and for different object ranges. 

 

Performing a Package Check for All Objects in a Package

This package method includes in the package check all Repository objects of a selected package. The package check is initiated either from the Object Navigator or from the Package Builder (SE21). 

Prerequisites

Only the active version of an object is used for the check.

Call

       1.      Select the package to be checked in the Repository Browser of the Object Navigator.

       2.      In the tree display, open the context menu for the package node and choose the option Check → Package Check → Package Objects.

 

As an alternative to the last step, you can double-click the package node and start the Package Builder editor. There you can call the check function by selecting the corresponding icon .

The package check results are output in a detailed object list. Here you can choose between a simple list view and a hierarchical view.  

 

Performing a Package Check for Objects in a Package Hierarchy

The package check in this case affects the Repository objects within a hierarchical (sub)tree. This means that when you choose a package, not only its contents, but also the contents of its subpackages and their sub-hierarchy trees are included in the package check sequence. 

Prerequisites

Only the active version of an object is used for the check.

Call

...

       1.      Select the package to be checked in the Repository Browser of the Object Navigator.

       2.      In the tree display, open the context menu for the package node and choose the option Check → Package Check → Check Hierarchy Objects .

A hierarchical display of the objects is output on the screen.

       3.      In the object display, expand the subtree whose objects are to be included in the package check.

You have the option of including, in one single sequence of the package check, individual objects and sets of objects, as well as all objects that are contained in the package hierarchy.   

The results of the package check are output for each individual object node. 

 

Performing a Package Check for Individual Objects in a Package

Call from the Object Navigator

...

       1.      In the Repository Browser, choose the object to be checked.

       2.      In the tree display, open the context menu for the package node and choose the option Check → Package Check.   

The package check results are displayed in a list.

 

Call from the Extended Program Check (SLIN)

Remember that the extended program check can only be performed for active sources.

...

       1.      In the Repository Browser, choose the object to be checked.

       2.      In the tree display, open the context menu for the package node and choose the option Check → Extended Check.     

As an alternative to these two steps, you can call the check through the transaction SLIN or from the ABAP editor using the path Program → Check → Extended Program Check.

       3.      Set the Package Interface checkbox.

       4.      Start the program check. 

The extended program check also performs package checks and displays messages of the appropriate type (error, warning, information), where necessary. You can then navigate to the line in the source code where the problem occurred by double-clicking.

 

Call from the ABAP Dictionary (SE11)

Starting from the ABAP Dictionary tool, you can perform a package check on an active version of a Dictionary object (table, view, data element, domain, and so on). Inactive version is only checked when activating a Dictionary object.

...

       1.      Select the Dictionary object to be checked either in the Repository Browser or within the Dictionary tool.

       2.      From the menu, choose Check → Package Check.    

The package check results are displayed in a list.

When activating an inactive Dictionary object, the system performs the check automatically using the inactive version.

If an error occurs during a package check of one of SAP’s own Dictionary objects, this object is not activated. If the object has been created by a customer, however, a dialog box containing a warning is displayed.

 

Call of Package Checks During Transport Release

Checks are performed on some Dictionary object types when the relevant transport is released. The system administrator can specify whether or not the package check is switched on in the system.