SAP ABAP Data Element PAK_ENCAPSULATION_LEVEL (A package's level of protection)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-ABA-LA (Application Component) Syntax, Compiler, Runtime
⤷
SPAK_API_KERNEL_TABLES (Package) Package check tables accessed by C++ coding (kernel)

⤷

⤷

Basic Data
Data Element | PAK_ENCAPSULATION_LEVEL |
Short Description | A package's level of protection |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PAK_ENCAPSULATION_LEVEL | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Kapselung |
Medium | 15 | Kapselung |
Long | 20 | Kapselungsstufe |
Heading | 10 | Kapselung |
Documentation
Definition
Defines the sanctions if contents of a package is accessed that is not published through interfaces
Use
Actual levels are
- Not encapsulated: the contents of the package can be accessed without any restrictions, that is, the package only works for grouping objects together. The package cannot have an explicit default interface
- Weakly encapsulated: accessing non-published contents raises warnings. If the package has an explicite default interface, only access to the interface defined as default interface is possible. This level is meant as a transitional level towards an encapsulated package.
- Encapsulated: accessing non-published contents raises error messages. The package can still have an explicit default interface. Additional, object-type specific restrictions (e.g. interdiction of obsolete constructs) may take effect for objects in an encapsulated package
Note
If you use PAK_ENCAPSULATION_LEVEL in ABAP programs, class CL_PAK_DOMAINS provides constants for the individual values.
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 710 |