SAP ABAP Data Element TYP_PLUGINREAD (Plug-In for Database Read)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-FS-ARE (Application Component) Archiving Engine
⤷ ARFA_ARCHIVING_METADATA (Package) Archiving Metadata
⤷ CA-FS-ARE (Application Component) Archiving Engine
⤷ ARFA_ARCHIVING_METADATA (Package) Archiving Metadata
Basic Data
Data Element | TYP_PLUGINREAD |
Short Description | Plug-In for Database Read |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Plug-In |
Medium | 18 | Plug-In: DB Read |
Long | 20 | Plug-In: DB Read |
Heading | 18 | Plug-In: DB Read |
Documentation
Definition
Grouping term for read modules. A read plug-in is used to structure the retrieve method for a business object.
A read plug-in can be reused by multiple archiving objects. In this case, a read plug-in replicates the functions of an archiving class.
You need to check whether the read plug-in is a better option for shared data than the usual archiving classes:
- Read plug-ins enable the business display of archived data (business view). Archiving classes do not.
- Archiving objects with archiving classes cannot function as pure deletion objects. Archiving objects with read plug-ins can also be used as pure deletion objects in principle.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 30 |