Hierarchy
FINBASIS (Software Component) Fin. Basis⤷
FIN-FB (Application Component) Financials Basis⤷
UGWB (Package) FI General: Workbench
Basic Data
| Data Element | UG_MD_TR_UPD_MODE_OVERWRITE |
| Short Description | Overwrite |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | UG_FLG | |
| 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 | Overwrite |
| Medium | 20 | Overwrite |
| Long | 30 | Overwrite |
| Heading | 10 | Overwrite |
Documentation
Definition
Use
Choose this option to replace individual database records only when importing the transport request. The system evaluates which database records will be transported when creating the transport request.
Note:
Since Customizing from the source and target system for a value is mixed and no checks are carried out for this option, this can easily lead to invalid master data or Customizing. So choose this option carefully. (See also the example below).
For this reason, this option is not activated for all Customizing objects. As a precaution, this option is deactivated in those Customizing areas or master data in which invalid table entries would impair Customizing.
However, this option only refers to the Customizing object to be transported. If the Customizing object itself contains subordinate Customizing objects (for example, selection conditions) in the SAP Consolidation component SEM-BCS, the system always uses the update mode Delete Imported Ones for these lower-level Customizing objects. This is also true for Customizing objects that are included in the transport request due to the option Reusable Lower-Level Objects.
Dependencies
Example
You want to transport all values of a characteristic. The values A and G exist for the characteristic in the source system at the creation time of the transport request. There are entries for sequence numbers 1, 2, and 3 for A. There are entries for sequence numbers 1 and 2 for G.
A new value C is created after creating the transport request and before exporting it. A new entry for sequence number 5 is generated for A.
The values A, G, and H exist in the target system. A has entries for sequence numbers 1, 2, 3, and 4; G has entries for sequence numbers 1 and 3.
The system behaves as follows when you select this option:
- Value C is not simultaneously transported as it did not exist when the transport request was created.
- Value H is not changed in the target system.
- The entries for sequence numbers 1, 2, and 3 are replaced for A. The entry for sequence number 5 is not transported from the source system, the entry for sequence number 4 is not deleted from the target system. As a result, A has entries for sequence number 1, 2, 3, and 4 after the import which partly come from the source system and partly from the target system.
- For G, the entry for sequence number 1 is replaced, the entry for sequence number 2 created and the entry for sequence number 3 not changed. As a result, B has entries for sequence number 1, 2, and 3 after the import which partly come from the source system and partly from the target system.
Using this option means that through the transport, individual data rows of the database tables from the source system are copied between the system. As the examples with A and G show, Customizing from the source and target system is mixed for a value. No checks are carried out here. This can easily lead to invalid master data or Customizing.
History
| Last changed by/on | SAP | 20041006 |
| SAP Release Created in | 300 |
