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 setting types: Global settings, which affect all packages throughout the system, and package-specific settings.
This system-wide switch is activated as part of customizing. If this switch is deactivated, there is no package check at all. In general, one of the following three values can be selected:
OFF |
|
No package check. |
RESTRICTED |
|
Structure packages are not considered in the package check. The package check only takes place if the appropriate setting Package encapsulated is activated for the package.
|
R3ENTERPRISE |
|
The check considers structure packages on the client and server package side. This is similar to a RESTRICTED
package check but takes structure packages into account. That is, if the client and the provider are
stored in the same structure package, the check is limited to the RESTRICTED package check.
|
Package-specific settings are generally made when the package is created. You can change them later in the Package Builder (on the Properties tab).
Package encapsulated |
|
When this package property is activated, the package is referred to as encapsulated. This setting is especially relevant for a package in the role of a server package since it protects the package contents from unwanted use. Using this encapsulation property, you determine the sanctions imposed during package checks if the contents of the respective package are accessed. Development objects (contents of the package) must first be made available through server package interfaces before they can be accessed by a user through a use access.
|