Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-CIC (Application Component) Interaction Center WinClient⤷
CO (Package) R/3 Application development: PP Production orders
Basic Data
| Data Element | CO_SCRDBERN |
| Short Description | Area Name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SCRPCHA30 | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Name |
| Medium | 15 | Area Name |
| Long | 20 | Area Name |
| Heading | 12 | Area Name |
Documentation
Definition
Identification of a screen area, in which dynamic subscreens are included in the procedure. Each area of the screen must have a unique name of up to 10 characters. In the flow logic, an area in PBO is addressed by the command
CALL SUBSCREEN area name INCLUDING program screen.
Specify the area name directly. You can enter the subscreen in variables or directly as literals in ''. At the point specified in the flow logic, the PBO parts of the subscreen expire. The procedure of the PAI parts of the subscreen is initiated at the requested point in the PAI of the flow logic in the superior screen by the
CALL SUBSCREEN area name
A normal screen can include several areas for several subscreens. The subscreen itself is indicated by an attribute as a subscreen. A subscreen can not call another subscreen itself.
History
| Last changed by/on | SAP | 20020520 |
| SAP Release Created in | 470 |
