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_LOCATION_ID |
| Short Description | Unique ID of a Location (case-sensitive) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SCPL_LOCATION_ID | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | SCPLT_LOCATION |
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 | Location |
| Medium | 15 | Location |
| Long | 20 | Location |
| Heading | 30 | Location |
Documentation
Definition
A location ID is a case-sensitive identifier of a location that is globally unique throughout Screenplay.
Use
Since the identifier of a location is allowed to be case-sensitive it's easy to consider it a name of a location. Actually, it's recommended to choose an identifier that preferably is kind of self-explanatory which adds weight to that argument.
But, what does "location" mean at all in surroundings of Screenplay? It most probably simplifies comprehension of it when you take it literally. Think of what a screenplay is and how important excellent locations are in film business and you are pretty close already. Technically spoken, a location in "our" Screenplay is more or less just an arrangement of runtime surroundings in which we try to visualize data of arbitrary complexity - let's call it data landscape to stay in film makers vocabulary. In the same way a camera shot of an overwhelming landscape in real movies always will just show a humble cutout of the actual view the camera man holding the camera would have, within Screenplay locations intentionally aim to bring simplified representation of vastly too complex information.
While locations themselves do not influence complexitiy of data or landscapes respectively they do give a good impression of the environment they reside in. For instance when bringing the unapparent complexity of address data to a mobile device it's good advice to represent it as condensed and yet well-arranged as possible. Otherwise a user might miss the point, or the audience will be left behind the "story" that is told.
So, a location delimits the scenario in which the visualization of data needs to take place. Give it a name that considers that and at the same time provides at least the first gut feeling what it is all about. And put more profound details into the location's desctription.
Dependencies
Another paralism to film business is that for telling a story you need actors. Without a location there are no actors - a location for itself just tells its own, un-touching story.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 732 |
