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_REMAKE |
| Short Description | Remake Name |
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 | Remake |
| Medium | 15 | Remake |
| Long | 20 | Remake Name |
| Heading | 30 | Remake |
Documentation
Definition
The name of a remake - actually, it's the name of a location declaring it a remake of another (original) location.
Use
You don't like how the original deals with the story? You ask yourself why the original's casting did not consider your favorite actor?
Well, why not just make your own remake?! Face the advantages: You define how much of the original your remake will take over, you might replace whatever you want to be different from the original, not only actors or the assignment of stylists or makeup sets to them.
Rules of remakes:
To raise the chances letting your remake be a success you should follow some basic rules and consider some essentials before even starting work, actually.
- First of all: A remake is just another location. Hence, you start creating a remake by simply adding it as a new location. Then you incorporate the additions or differences you wish your remake to have in comparison to its original. Even though you didn't define which original location you are about to remake, yet, you should of course at least keep in mind towards which goal you are "remaking".
- After finishing your remake you publish it to its original by adding it to the list of remakes and giving it a release.
- A remake will instandly and irresistibly influence the original forever. Wherever the original is playing, now your remake influences everything with all of its exchanges and enhancements.
- Before anything of your remake is taken into consideration all the original's setup such as casting or dialogs will be considered. That means, by just defining the name of a remake and letting it refer to the desired original, no change at all will affect the original.
- It is not possible to remove setups of the original by defining a remake, at least not in a direct way. You might enhance or change the casting of the original for instance, but removing an actor completely is not intended.
Dependencies
Although you are pretty free in what you do in your remake and how much you change in comparison to its original you refer to, be very careful when it comes to the design of your remake. Don't dare to much, keep in mind that the design of a location needs to meet expectations of all participating parties. You really don't want to face the original's director escalation when you exchange the design too radically! Developers would refer to those kind of escalations as "runtime-error" or "facing the dump of exceptions". Not choosing at least compatible designs can make your remake a flop.
But, if your production allows you to completely disconnect from the original in a way you even could introduce fresh and autonomous directors that run over the original's director's ignorance regarding your new design, you are really totally free. If your own director handles the new designs while still being aware of the original designs you could change the world. A bit.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 732 |
