Hierarchy
⤷ BC-DWB-TOO-PAK (Application Component) Package Tools
⤷ SPAK_TOOL (Package) Package Builder: Tools
Basic Data
Data Element | PACKNAM2 |
Short Description | Package Name |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEVCLASS | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table | TDEVC |
Further Characteristics
Search Help: Name | PB_PACKAGE_NAME | |
Search Help: Parameters | DEVCLASS | |
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 | Package |
Medium | 20 | Package |
Long | 30 | Package |
Heading | 30 | Package |
Documentation
Definition
Packages are an enhancement of development classes for concepte that allow for better modularization, encapsulation, and decoupling of the SAP R/3 System.
So far, thedevelopment classes have been provided with a transport layer as simple containers for development objects. This layer defines the transport route. As an enhancement of development classes, packages are characterized by the basic properties of nesting, interfaces, and visibility as well as use accesses.
Nesting is the ability of packages to embed other packages into themselves within the package hierarchy.
The visibility describes a property of package elements. A development element can be visible outside of its package. (As a rule, it is visible within its package, but never visible in all packages embedded in this package.) A development element is then visible to the outside whenever it is within a package interfacee.
With use access, you have in a package a one-sided right to use the development elements of a package interface of another package.
Definition
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in | 46D |