System Settings (SAP Library - Package Builder)

System Settings

The following section outlines which system settings are connected with package checks and thus affect the flow of the package check.

There are two main types of setting: Global settings, which affect all packages throughout the system, and package-specific settings.

The global package check switch

This system-wide switch is activated as part of Customizing. If this switch is deactivated, there is no package check at all. Otherwise you can choose one of three values:

Pure Package Concept		Structure packages are not included in the package check. An interface must be defined in the provider package for each valid use. The user package must have access to this interface through a use access.
Restricted Package Check		Structure packages are not included in the package check. The package check only takes place if the appropriate Package check as client or Package check as server is assigned to the package.
R/3 Enterprise		The check includes structure packages. This is similar to a Restricted Package Check but takes structure packages into account. That is, if the user and the provider are stored in the same structure package, the check is limited to the Restricted Package Check. Otherwise, the system needs to check whether or not a use relationship between the two structure packages is allowed. If it is, the system performs the Restricted package check. Otherwise, an error message occurs.

Package attributes

Package-specific settings are generally made when the package is created. You can change them later in the Package Builder (on the Attributes tab).

Package Check as Server		You can assign the Package check as server attribute to any package. This attribute means that all users must comply with the pure package check (that is, this is a "strong" check). This package check is especially important for the provider package, since it protects the package from unwanted use. In particular, the provider can separate new developments. The use of new functions can then be controlled by the provider. That is, new development objects must first be made visible through the provider package interface, before they can be accessed by a user through a use access.
Package Check As Client		If the Package check as a client is assigned to a package, the package concept need only be complied with locally – that is, within this package. Globally, the pure package concept should only be complied with where possible. In particular, a user must always have a use access if the object it wants to use has been made visible in a provider package interface.

See also:

Structure Packages