SAP ABAP IMG Activity SIMG_OKCMTRRESTART (Repetition of data transfers)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KC (Package) Cost Accounting Controlling EIS
IMG Activity
ID SIMG_OKCMTRRESTART Repetition of data transfers  
Transaction Code S_ALR_87000509   IMG Activity: SIMG_OKCMTRRESTART 
Created on 19981222    
Customizing Attributes SIMG_OKCMTRRESTART   Repetition of data transfers 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OKCMTRRESTART    

Tool for finding, analyzing and correcting errors

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.

Temporary saves during the data transfer

During a transfer, all records received are saved temporarily before being summarized. All sender and receiver records with errors are saved temporarily after summarization. The update is only started if no errors occurred. Before the update, all summarized receiver records are saved temporarily. 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 saved temporarily for each block. These records will, however, be summarized and updated at the same time.

Error analysis and repeat of transfer

This temporary saved 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 in the update, you can update the receiver records afterwards. You can also update all temporarily saved receiver records. 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 should be overwritten or not. 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 at least one key figure is not to overwritten, the system checks whether a record with the same record exists on the database. The record is then read.
  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 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 you wish.

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.

Note

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

Delete logs

The number of transfer logs that can be saved, depends on the quantity of the data. (The tables INDX and BAL_INDX are updated). Therefore, we recommend that you schedule a job that deletes the logs weekly.

Organization of data transfers and problems

Notes on organization

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/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/BP at period close. The following tools are available to help you organize data transfer:

  1. The version in EC-EIS/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.

Typical problems

  1. Data transfer using CPIC 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 program RKCCOMON under Import all sender records.
  2. 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 which are semantically incorrect were imported.

    For example, country key 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 which need to be derived from other characteristics using the 'Convert sender fields' rule. In this example, you could derive the country key 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.

Business Attributes
ASAP Roadmap ID 254   Transfer Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OKCMTRRESTART 0 HLA0009491 Data Collection 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19981222 
SAP Release Created in