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
Basic Data
| Data Element | SCPL_DIALOG |
| Short Description | Dialog Subject (Unique Identifier, case-sensitive) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SCPL_DIALOG | |
| 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 | 6 | Dialog |
| Medium | 6 | Dialog |
| Long | 6 | Dialog |
| Heading | 6 | Dialog |
Documentation
Definition
Dialogs force actors to get in touch and contingently combine their texts.
Use
Some actors only do a good job when working together. Single actors might have too less text to make them interesting enough for a consideration by the stylist directly, or only the combined texts of several actors make sense at all. Well, just gather them into a dialog and point at one of the actors to be the most important. This actor then will be the only one really start acting when the director's "and action!" tells everybody to play.
Let's take a technical example, even if breaking the flair of big movies going on here with it:
An address is an awful monster of complexity when looking at it from an international point of view. But, of course we do have perfect tools here at SAP to tame that cuddly-at-heart beast. It's getting a bit worse if address data is not available in one single actor's character but spread out over several actors. This might happen due to constraints of the underlying data modelling tool or other restrictions you don't have under your own control.
Now, when saying "getting a bit worse" it means "not a problem at all". That is one of many reasons why Screenplay and its dialogs are existing. Breath, calm down. It's easy. First you group all entities, uhm - actors that contribute to the address' data into a dialog and select one of it to be the primary one. None of these actors but the primary one will reach your director in the list of acting actors, and the makeup of the address data applys the primary actor's makeup style.
When you set up a dialog you might specify a scene for it. This dialog is only taking place in that scene, evidently. Not specifying a scene for a dialog let that dialog be a location-wide dialog, occurring throughout all scenes.
Dependencies
Just to emphasize this: Actors that are involved in a dialog without being the primary actor for that dialog are not considered acting actors and hence will not be in the list of actors returned to your director. Nevertheless, you always have the possibility to access any actor and its text by looking up the screenplay actively. This is true for directors and stylists.
Additionally, you need to remember that currently only one actor can be set as primary actor per dialog. And, an actor can be assigned to only one single dialog of a location. An actor can participate in only one single location-wide dialog. The same is true in scene dialogs. However, the same actor can participate in a location-wide dialog and at the same time in multiple scene dialogs, each of different scenes.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 732 |
