Hierarchy
⤷
⤷
Basic Data
| Data Element | TYP_ACTION04 |
| Short Description | Read Plug-In |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | 04 |
| Medium | 15 | 04 |
| Long | 20 | 04 |
| Heading | 2 | 04 |
Documentation
Read Plug-In
A read plug-in is a group of read modules and is primarily used as a structuring aid when many tables are involved.
A read plug-in can be used by multiple archiving and deletion objects (reuse, read plug-in sharing, central definition of read modules and reuse in multiple archiving scenarios). This should usually be avoided.
One read plug-in is preferable for lightweight scenarios. It can have the same name as the scenario itself (standard naming convention).
A read plug-in is therefore a 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 scenarios. In this case, a read plug-in replicates the functions of a class.
Check whether the read plug-in is a better option for shared data than the usual classes:
- Read plug-ins enable the business display of archived data (business view). Classes do not.
- Archiving scenarios 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.
- Archiving scenarios with read plug-ins are optimized for performance. Archiving scenarios with archiving classes are in many cases suboptimal with regard to performance.
- Unlike archiving classes, a read plug-in enables flexible enhancement (additional tables to be included).
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 40 |