Skip to end of metadata
Go to start of metadata

Overview

Data Consistency Management in Solution Manager comprises the tools and procedures required to prevent, detect, investigate and correct inconsistencies in your solution landscape. This helps to ensure the successful execution of your core business processes and prevents costly business process downtimes.

Motivation

Today's business processes evolve in complex structures involving several systems of the overall landscape. As shown in the picture below it is important to ensure the data consistency between all involved systems.

Apart from user level errors like an incorrect manual entry in the system, there are possibilities of inconsistencies as well on application and technology level. The figure below presents potential causes of data inconsistency.

Why can Data Inconsistencies Occur?

User Level


User Level: Data inconsistencies due to

  • Real world operation System transaction

  • Incorrect manual entry of data

  • Completely missing entry of data

  • Wrong usage of transaction

Application Level

Application Level: Data inconsistencies within one system or between two systems due to

  • Absence of error handling

  • No clear leading system defined

  • Logical inconsistencies in application integration

  • Errors in application programs (transactional correctness)

Technology Level

Technology Level: Data inconsistencies due to

  • Data Loss

  • Initial Loads may have run into problems

  • One system crashes and is reset to an earlier state

  • Problems with Delta Loads

Examples

Benefits

Handling overview

The process of Data Consistency Management consists of 4 steps: Prevention, Detection, Correction and Investigation. In the picture below, these steps are displayed in a cycle expressing the continuity of the process.

 

Tools

Solution Manager includes several tools to cover the Data Consistency Management cycle and different technologies. The following figure presents those tools. Details for these tools are provided in the tool-specific section.

 


  • No labels