Ansicht
Dokumentation

SIMG_OKCMTRRESTART - Repetition of data transfers

Addresses (Business Address Services)   General Data in Customer Master  
This documentation is copyright by SAP AG.

Under Transaction data -> Transfer -> Transfer log. in the application menu or with ABAP report program RKCDLMON you can determine whether data transfers have run without errors, or whether errors occurred.

1. Enter a sender structure or a transfer path and highlight 'Display'. Select 'Execute'.
2. Limit the period accordingly and, where necessary, enter other selection criteria. Select 'Execute'.
   A list of the logs is displayed.
3. Position the cursor on a line and choose 'Goto -> Display message' in order to read the log messages.
4. Position the cursor on the external number of the log and select 'Goto -> Detail' in order to analyze and edit the errors.

During a data transfer, all records received are saved temporarily before being summarized. All sender and receiver records with errors are buffered after summarization. The update is only started if no errors occurred during summarization. Before the update, all generated receiver records are buffered. If a sender program used the same logical unit several times during a transfer using CPIC and the data is transferred in a block, the transferred records will be buffered for each block. These records will, however, be summarized and updated at the same time.

This buffered data enables you to import the sender records or summarized receiver records again and analyze the errors. Depending on the type of the error, it may be useful to work with the sender or summarized records.

If a problem occurs during the update, you can update the receiver records afterwards. There may already be records on the database with the same key as the receiver records to be updated. For this reason, you can specify for each key figure whether the values on the database are to be overwritten. You do this when you are maintaining the rules for the data transfer. The system carries out the following steps:

1. When processing the data transfer rules, the key of the receiver record is formed from the sender record.
2. If you have defined the transfer rules such that the value of at least one key figure is not to be overwritten, the system checks whether a record with the same key exists in the database. This record is then read from the database.
3. If the key figure values of a record are not to be overwritten, this is taken into account in the total operation. If the total operation for a key figure is SUM and the key figure is not to be overwritten, the key figure value from the database is taken as the start value.
4. The appropriate key figure values from all sender records summarized on the same key are totaled using this start value. The procedure for other total operations is similar.
5. If you have defined summarization levels, you must delete these summarization levels and build them again.

This procedure ensures that the receiver records from the last transfer can be posted to as often as desired.

You can import sender records with errors again. This is useful if the transfer rules had been maintained incorrectly, for example. You can, however, import all sender records again. If you wish to cumulate the key figure values, however, you should only import the sender records once.

If you wish to update or import a larger volume of data records after the error analysis, you must carry out the function in the background processing. To do so, select 'Functions for background processing'. The ABAP report program RKCCOMON is called. The log number is automatically controlled in the corresponding field. You can create a variant before you update or import the data records in background processing.

The number of transfer logs that can be saved, depends on the volume of the data. (The tables INDX and BAL_INDX are updated). It is therefore recommended that you schedule a job that deletes the logs weekly.

Data transfer to an Executive Information System or a Business Planning system must be organized differently to data transfer to an information system in an operative system. An EIS is unlike an operative information system in that data is not written to EC-EIS or EC-BP every time a posting takes place, nor can a flag be set in the sender system that data has already been read. For this reason, it is important to limit the data in any one transfer and to make sure that a reversal is possible. In addition, data from many sources is usually transferred to EC-EIS or EC-BP at period close. The following tools are available to help you organize data transfer:

1. The version in EC-EIS or EC-BP can be used to separate datasets from one another. Set up your own version for data transfers.
2. Using limited datasets, create test reports with which you can check the completeness and correctness of the data transfers.
3. Use aspect summarization to copy the data into the productive version.

1. Data transfer using a CPIC connection terminated for technical reasons.

Summarization and an update will not yet have taken place. If the data was collected in one queue, it will not have been deleted from the queue. The data can be transferred again. This is activated automatically. If data was collected in several queues, the blocks of data which were transferred without errors have been saved in the receiver system and can be imported with the function Transaction data -> Transfer -> Transfer log in the application menu or directly using the ABAP program RKCDLMON under Import all sender records.

1. The summarization or update was unsuccessful.

This is probably due to the fact that a characteristic value was not contained in the master data. Correct the master data or the sender records and import them again.

1. Valid keys that are semantically incorrect were imported.

For example, the country/region FRA (France) and town MUN (Munich) were entered for a plant. In order to find such errors, you should set up test reports for the data imported. In addition, you should keep the sender records as small as possible and derive characteristics that need to be derived from other characteristics using the 'Convert sender fields' rule. In this example, you could derive the country/region and town for the plant from the plant number. The problem of deleting records written to the database also occurs here. You can only do this if the records in a data transfer can be separated from other records using selection conditions.

General Data in Customer Master   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 7087 Date: 20240523 Time: 201819     sap01-206 ( 150 ms )