SAP ABAP Data Element /BOBF/CONF_LIB_USAGE (Library Usage)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration
⤷
/BOBF/CONFIGURATION (Package) Business Object Processing Configuration

⤷

⤷

Basic Data
Data Element | /BOBF/CONF_LIB_USAGE |
Short Description | Library Usage |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /BOBF/CONF_LIB_USAGE | |
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 | Usage |
Medium | 15 | Usage |
Long | 20 | Usage |
Heading | 20 | Usage |
Documentation
Definition
The recommended usage of a library class.
Use
The usage of a library class defines if it is recommended to only use a library class for a prototype or in a productive environment.
Dependencies
Library classes that are only used for a prototype might not fulfill the performance requirements needed for these functions.
Example
Even though many generic things can also be used in a productive environment, the library classes that use prototypes help get functionality into a business object very fast and to focus on the specific logic of a business object at the beginning of the implementation.
If the performance requirements are not met, the library classes should be replaced by some specific implementation for the generic functionality
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |