Hierarchy
PI_BASIS (Software Component) Basis Plug-In⤷
CA (Application Component) Cross-Application Components⤷
POR4 (Package) Drag&Relate (Workplace Plug-in) with Rel. 4.0
Basic Data
| Data Element | DR_SUBASS |
| Short Description | Drag&Relate: Indicator: Subtype Is Assigned |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1_X | |
| 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 | Assigned |
| Medium | 15 | Assigned |
| Long | 30 | Subtype Is Assigned |
| Heading | 0 |
Documentation
Definition
When you are using Drag&Relate supertypes, you can use one data element for more than one object.
You do not have to assign all objects of the supertype to all data elements at the same time, instead, you must assign data elements more than once only if their semantics are not unique on the user interface.
This indicator specifies whether the object that is part of a supertype is assigned to the data element.
You should assign data elements only if their semantics are not unique, because if there is a unique assignment between the data element and the object type, the system can generate a link to the concrete object type. In addition to improved performance, the system can correctly determine the possible activities for a "real" link, in contrast to a link to a supertype.
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in |
