- What is writing behaviour?
- How many kinds of written behaviour and what are they?
Environment
SAP Landscape Transformation replication server
Resolution
The write behavior determines how changes to the target system database occur.
You can specify the following write behaviors:
- Array Insert
With array insert, all transferred data records from the source system table that belong to a data portion are written to the target database in one insert operation.
If a duplicate entry for a key field is found, no records from the relevant portion are written to the target database (the changes are rolled back). The system sets the status of the portion to Failed, and an error message is written to the application log. Note that you view that status of the portion in transaction LTRC (tab page Load Statistics).
- Single Insert
With single insert, each transferred record from the source system table is written to the target database using a separate insert operation.
If a duplicate entry for a key field is found, the relevant record is not written to the target database. All other records are written to the target database. Regardless of whether any duplicate entries for key fields occur, the system sets the status of the portion to Finished once the target database operation is complete. The system creates an entry in the application log for any duplicate entries found.
- Array Modify
With array modify, all transferred data records are written to the target database in one operation.
If a duplicate entry for a key field is found, the relevant record is written to the target database (the existing record is overwritten). All other records are written to the target database. Regardless of whether any duplicate entries for key fields occur, the system sets the status of the portion to Finished once the target database operations are complete.
This write behavior can be advantageous if you expect duplicate entries for key fields to occur, and you want to overwrite the target system database records with those from the source system.
- Array Insert with Duplicate List
The system first uses the write behavior Array Insert. If no duplicate entries for key fields are found, no further action is taken. That is, all transferred data records from the source system table that are written to the target database in one insert operation.
However, if a duplicate entry for a key field is found, the system executes a second insert operation by using the write behavior Single Insert. This is done in order to identify the duplicate entries. However, the relevant record is not written to the target database (the changes are rolled back).
If duplicate entries for key fields occur, the system sets the status of the portion to Error. The system creates an entry in the application log for any duplicate entries found.
This write behavior can be advantageous if you expect duplicate entries for key fields to occur, and you want to analyze these entries. You can view the duplicate entries for the key fields in the application log, and decide how they should be handled.
- Sum Up
Each transferred record from the source system table is written to the target database using a separate insert operation. If a duplicate entry for a field of type Currency or Quantity is found, the system performs a SUM operation. That is, the system increases the amount in the target system record by the amount in the record to be inserted
- Dynamic Single Insert
The system uses the write behavior Array Insert. If no duplicate entries for key fields are found, no further action is taken. That is, all transferred data records from the source system table that are written to the target database in one insert operation.
However, if a duplicate entry for a key field is found, then the system uses the write behaviour Single Insert. This is done in order to identify duplicate entries. The relevant record is not written to the target database.
If duplicate entries for key fields occur, the system sets the status of the portion to Finished. The system creates an entry in the application logs for any duplicate entries found.
This write behavior can be advantageous if you expect duplicate entries for key fields to occur, and you want to retain the target system database records.
- Update Set
You can use this write behaviour to change specific field values for the target system table.
If you want to change such values, we recommend contacting SAP in order to engage the services of SAP consulting.
- Delete
You can use this write behaviour to delete data records from the target system database. Note that this means that if the target system already contains these records, they will be deleted.
If you want to restrict the set of data to be deleted, we recommend contacting SAP in order to engage the services of SAP consulting.