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_ORIGINAL |
| Short Description | Original of a Remake |
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 | Original |
| Medium | 15 | Original |
| Long | 20 | Remake Of |
| Heading | 30 | Remake Of |
Documentation
Definition
Name of the original the remake is based on. This might be any location, including even another remake.
Use
Each remake has an original - some remakes are even better than their original. And if you don't like someone's remake you can remake this remake, as well. In this case that remake would be the original of your remake. Uh - confusing. Think of an original defining how the story goes. Someone enhances or deepens this story with a remake. You like that remake but wish to have your own additions to the story, so when you do a remake yourself you would consider the first remake your original.
Dependencies
All settings of this original will be valid for any remake of it. Designs, casting, dialogs - all of these will stay unchanged, as long as the remake is not actively redefining them. See the rules of remaking to learn how to let a remake do such kind of redefinitions and enhancemenrts, respectively.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 732 |
