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_RTO_BEHAVIOUR |
| Short Description | MWB: Transfer Behaviour of Conversion |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DMC_RTO_BEHAVIOUR | |
| Data Type | NUMC | Character string with only digits |
| 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 | Behavior |
| Medium | 18 | Transfer Behavior |
| Long | 32 | Transfer Behavior of Conversion |
| Heading | 32 | Transfer Behavior of Conversion |
Documentation
Definition
Control of the migration behavior regarding database changes in the target system.
Use
The write behavior determines how database changes are carried out in the target system.
- Write Behavior 1: Array-Insert
With array-insert, all data records in a receiver structure are written to the target database in one insert operation.
If a duplicate key is found, the complete portion is rejected (all receiver structures), and an error message is written to the application log.
- Write Behavior 2: Single-Insert
With single-insert, each record of a receiver structure is written to the database in a separate insert operation.
If a duplicate key is found, only the affected data record is rejected, while all non-duplicate records are inserted. The keys of the duplicate records are written to the application log. The data portion is set to "completed" even if duplicates occurred and the corresponding error messages were written to the application log.
- Write Behavior 3: Array-Modify
With array-modify, all transferred data records are written to the target database. If a record with the corresponding key already existed, it is overwritten.
- Write Behavior 4: Array-Insert mit Duplikatliste
This write behavior first tries an array-insert with the same write behavior as described under 1. If a duplicate key is found, single-inserts are tried as described for write behavior 2 for the affected receiver structure(s) to determine the duplicate keys. After that, all changes are rolled back for the complete portion, so you will never see any records added to the DB table(s) in case of write behavior 4!
The duplicate keys are either written to the application log or (for background processing) written to the spool list of the job.
In case of duplicates the data portion is set to error state.
- Write Behavior 5: Sum-Up
A single-insert with the same write behavior as described under 1 is made.
For tables containing amount fields, the function changes to a totaling mode if it finds a duplicate key. The field values in the amount fields of the existing records are increased by the amounts from the record to be inserted.
- Write Behavior 6: Dynamic Single-Insert
This write behavior first tries an array-insert with the same write behavior as described under 1. If a duplicate key is found, single-inserts are tried as described for write behavior 2 for the affected receiver structure(s).
All duplicate keys are written either to the application log (for dialog start) or to the spool list of the job (for background processing).
So this write behavior is similar to write behavior 4, the differences being:
1) Whatever can be inserted will really be inserted, there is no rollback.
2) The data portion is set to loaded state even if duplicates occurred.
- Write Behavior 7: Update Set
With this write behavior it is possible to change specific field values of existing data records.
The corresponding settings can be defined in the receiver structure maintenance screen of transaction MWB (button "Define Update Set") - Write Behavior 8: Delete
Rather than writing data in the receiver system, existing data with the corresponding key values are deleted. To restrict the set of data to be deleted, selections can be defined in the receiver structure maintenance screen of transaction MWB (button "Define Delete")
Dependencies
Example
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in | 50A |
