Ansicht
Dokumentation
RDSWP_BPM_GEN_COMP - Generic compare
CPI1466 during Backup Vendor Master (General Section)This documentation is copyright by SAP AG.
Purpose
Very often data (like master data) is exchanged between two systems. As the data is used for further processing in both systems consistency is crucial for correct business operation and any inconsistent states should be detected as early as possible requiring a regular consistency check of data between the involved systems by appropriate consistency check reports is needed.
The external compare is intended to be used for consistency checks between SAP-Systems whenever no standard check reports exist and to check between SAP and non-SAP system.
Public documentation regarding Business Process Monitoring in general and the Data Consistency Cockpit can be found in the SAP Service Marketplace under the ALIAS BPM: Go to help portal http://service.sap.com/bpm. The information available there is the best resource for self study, providing customers with comprehensive information, finding Release Notes, Best Practice Documents, Installation Guides.
Integration
Prerequisites
Release,,
ST-A/PI 01K,,First delivery of Generic External Compare
,,,,Solution Manager 4.0
Features
Selection
Standard Variants
Activities
Example
Create a comparison instance.
- Click on the create button. In the following dialog enter:
- The name of comparison instance. (mandatory)
- The name of system A
- The filename of system A if you choose the check box 'data via file upload'
- The RFC connection and the Generator if you choose the check box 'data via rfc connection'.
- Name of system B
- The filename of system B if you choose the check box 'data via file upload'
- The RFC connection and the Generator if you choose the check box 'data via rfc connection'.
- Note: the existing Generators are only than selectable, if you load the Generators via the 'Load Generators' button.
- The name of business object
- The maximum number of log entries
- The maximum number of log entries (errors) specifies a limit which aborts the comparison if more than x log entries were written. This limit prevents that largely differing extracts are compared until the end as it is impossible to analyze thousands of different log entries. The log entries are written up to the limit specified. Then the comparison stops and the log entries so far written can be inspected.
- The number of business object in memory
- Number of business objects in memory specifies how many business objects are simultaneously kept in memory for each file. This in important as XML files can be very large and so the number of objects that reside in memory has to be limited to ensure that memory consumption in on a reasonable level.
- The size of log entry buffer.
- Size of log entry buffer specifies how many log entries are kept in memory until they are flushed to the database.
Start a comparison instance
- Press the (Re)Start comp button and then several times the refresh button. The comparison should start after a while.
- If the status is green the comparison is finished.
Check the results
You can now check the results via the button 'Comp Detail' or via double-click on the line of the comparison instance. In the CRM Data Integrity Manager you have the possibility to analyse the inconsistencies which are occurred.
CPI1466 during Backup PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 4670 Date: 20240520 Time: 101708 sap01-206 ( 87 ms )