Documentation of Comparison INstances
Cross Database Comparison
Documentation of Comparison Instance <Comparison Instance>
Table of Content
Relevant processes and interfaces 3
Variable (Instance Specific) Filters 4
Variable filters acting on both sources 4
This document provides background information on the Comparison Instance <Comparison Instance>.
<Explain within
this section what the overall purpose and background of the
Comparison Instance is and why it was created. Describe when this
Comparison Instance should be used.
Explain in business terms
what objects are compared between the two systems (e.g. sales orders,
business partners, materials, …) and which organizational
units should use this Comparison Instance>
Comparison Instance <Comparison Instance> is intended to verify the data consistency within the following business processes and interfaces.
Business Process / Interface Name |
System/Step Sender |
System/Step |
<Name of business process / interface according to Solution Manager documentation> |
<Name of business process step and system according to Solution Manager documentation> |
<Name of business process step and system according to Solution Manager documentation> |
|
|
|
Parameter |
Value |
Comparison Object |
<Name of Comparison Object> |
Comparison Block Size |
<Parameter value> |
Maximum number of errors |
<Parameter value> |
Maximum number of iterations |
<Parameter value> |
Exit condition (%) |
<Parameter value> |
Exit condition (total) |
<Parameter value> |
Parameter |
Value |
Source Type |
<ABAP/FIXS/FIXL/…> |
<Parameter Name> |
<Parameter Value> |
Parameter |
Value |
Source Type |
<ABAP/FIXS/FIXL/…> |
<Parameter Name> |
<Parameter Value> |
Instance Specific filters are defined on Comparison Object level, but the actual value is maintained on the Comparison Instance. Each Comparison Instance is utilizing its own set of values. These filters are used to allow a parallelization by defining ranges of objects (e.g. execute Comparison Runs for Open Orders and Closed Orders separately) or to restrict execution and access to data by organizational units (e.g. one Comparison Instance per company code). Use this section to document which options for variable filters have been defined and why.
Starting Solution Manager 7.1 SP9/SP10 variable filters are allowed for each source system and for mapped fields.
Mapping Name |
Value Low |
Value High |
Purpose |
<used mapping name> |
<value> |
<value >
|
<describe why this filter was created on instance level and how it should be used> |
|
|
|
|
Source |
Table Name |
Field Name |
Value Low |
Value High |
Purpose |
<Source no.> |
<table name> |
<field name> |
<value> |
<value >
|
<describe why this filter was created on instance level and how it should be used> |
|
|
|
|
|
|
Role |
Name |
Company |
Contact Data |
Requestor |
<Name> |
<Company name> |
<eMail / adress / phone number> |
Developer |
<Name> |
<Company name> |
<eMail / adress / phone number> |
Provider of filter values |
<Name> |
<Company name> |
<eMail / adress / phone number> |
No |
Description |
Changed at/by |
<No.> |
<Short description of change and reason> |
<date / name> |
<No.> |
<Short description of change and reason> |
<date / name> |
<No.> |
<Short description of change and reason> |
<date / name> |
37 Rectangle 3 Ministerio de Seguridad de la Nación
3RECTANGLE 1 PART SPECIFICATION TECHNICAL SUPPORT 8003456202 PART 1
5 INSIDE ART IRECTANGLE 2 NSIDE ART 2014 —
Tags: rectangle 10, name> rectangle, rectangle, cross, comparison, instances, documentation