SAP ABAP Data Element JDYNMUSS (Indicator: Is screen concerned a required screen ?)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
Basic Data
| Data Element | JDYNMUSS |
| Short Description | Indicator: Is screen concerned a required screen ? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | JANE | |
| 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 | Req.screen |
| Medium | 15 | Required scr. |
| Long | 20 | Required screen |
| Heading | 3 | Req |
Documentation
Definition
The indicator is set if the corresponding screen has to be accessed and displayed. This means, in the application, that the plausibility checks have to be executed at all costs.
System-defined mandatory screens may not be deleted in customizing.
History
| Last changed by/on | SAP | 19990827 |
| SAP Release Created in |
