Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-EUR (Application Component) European Monetary Union: Euro⤷
CNV_DMCM (Package) Data Mapping and Conversion: Maintenance
Basic Data
| Data Element | DMC_COPY_TYPE |
| Short Description | Type of Copy (With / Without Dependent Objects) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLEAN | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | CType |
| Medium | 15 | Copy Type |
| Long | 20 | Type of Copy |
| Heading | 10 | Copy Type |
Documentation
Definition
Here, you specify the objects you want to copy together with the selected object. The options you have here depend on the object type you selected:
For projects, it is not possible to copy dependent objects (subprojects, migration objects) as well.
For subprojects, the related conversion rules are always copied as well. If you specify here that you want to copy dependent objects as well, this refers to migration objects as well as any project-specific conversion rules that are used by these migration objects. These are then transferred from the source project to the target project.
If you copy a migration object, you need to decide if you want to copy the subproject- and project-specific rules used by this object. If you choose not to copy these rules, no rule calls are created for the receiver fields of the target migration object if the source migration object has subproject- and project-specific conversion rules assigned to these receiver fields.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20141029 |
| SAP Release Created in | 620 |
