Structure
packages were introduced to apply rules, within the development and
correction process, for using objects from different packages.
One of the
fundamental goals of this concept is to ensure that the two software
components SAP_HR and SAP_APPL remain technically independent. This means that objects contained in the structure
package HR cannot use any objects that belong to the structure package
APPL.
Initially, each structure package is completely
independent of each other structure package. In such cases, the use of objects from other
structure packages would lead to an error if a package check was
performed.
The table below
summarizes examples of how object visibility is implemented in different
structure packages and of the dependencies between them, within the Core
Applications of SAP ERP. Thus, it shows exactly how the structure package
concept has been implemented in SAP ERP.
Structure package |
Visible... |
Can use objects from ... |
BASIS |
in all other packages |
BASIS
|
ABA |
in all other packages except BASIS
|
BASIS or ABA |
HR |
only in HR
|
BASIS, ABA, APPL_TOOLS, and HR |
APPL |
only in APPL
|
BASIS, ABA, APPL_TOOLS, and APPL |
APPL_NU |
only in APPL_NU
|
BASIS, ABA, APPL_TOOLS, APPL_NU, and APPL |
APPL_TOOLS |
in all other packages except BASIS
|
BASIS, ABA, and APPL_TOOLS |
The reciprocal dependencies of the structure packages are a result of the use accesses of the user structure packages to the package interfaces of the provider structure packages.
See also:
Applying Filters in Structure Packages
Accessing Content from Another Package Hierarchy