SAP ABAP Data Element SCPL_SCENE (Scene Name (Unique Identifier, case-sensitive))
Hierarchy
☛
MDG_FND (Software Component) MDG Foundation
⤷ CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷ MDG_BS_BP_GENIL_NO_TRANSL (Package) Master Data Governance: GENIL
⤷ CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷ MDG_BS_BP_GENIL_NO_TRANSL (Package) Master Data Governance: GENIL
Basic Data
Data Element | SCPL_SCENE |
Short Description | Scene Name (Unique Identifier, case-sensitive) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SCPL_SCENE | |
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 | Scene |
Medium | 15 | Scene |
Long | 20 | Scene Name |
Heading | 5 | Scene |
Documentation
Definition
Some locations are of such a significance you have several scenes to catch it. Scenes might split the location into several meaningful views.
Use
The more imposing a location is the more reasonable it might be to split it in adequate scenes. With scenes a director can accentuate particular impressions, let it be more detailed makeup styles for a "close-up" scene (developers would say "detail views") or to embed dialogs into them.
Dependencies
Dialogs can be set up in a scene or for the location as such. For the latter just don't specfiy a scene at all while setting up the dialog. For that reason there can be only one dialog per location and a distinct one for each scene.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 732 |