Configure Best Record Calculation

Within the process step Best Record Calculation, for each match group a best record is calculated. This calculation follows a well defined process based on certain rules.

Activities

To configure the Best Record Calculation for MDG, consolidation, run the Customizing activities under Start of the navigation path Master Data Governance Next navigation step Consolidation and Mass Processing Configure Best Record Calculation End of the navigation path .

For an overview on the rules for the Best Record Calculation run the Customizing activity Specify Rules for Best Record Calculation.
The standard delivery contains the following rules to determine the best record:
- COMPLETENESS: Determines that on field level completely maintained record win.
- RECENCY: Determines that on table level the most recent record wins.
- SOURCE_SYSTEM: Determines that on table level the record from a specified source system wins.
- BRF+: Best record calculation is up to the Business Rule Framework (BRFplus).
  For more information, see Define Rules Using the Business Rule Framework plus.
  Note
  To set up a table for best record calculation using BRFplus proceed as described:
  Run the Customizing activity Configure Process Models.
  Select a business object type.
  On the Tables view set the BRF+ indicator for the corresponding table.
  End of the note.
To specify the order of rules and the parallelization for the best record calculation run the Customizing activity Specify Order of Rules for Best Record Calculation. Adapting the number of parallel processes can improve the performance of the consolidation process.
Note
To use parallelization in SAP MDG, consolidation you have to set up an RFC destination:
- To create the bgRFC inbound destination manually, the authorization object S_BGRFC with activity 02 and type 07 has to be assigned to you.
  Run transaction SBGRFCCONF.
  On the Define Inbound Dest. tab choose Create.
  Enter a name in the Destination field.
  Enter MDC_QUEUE_ in the Prefixes field.
  If you use a queue prefix other than MDC_QUEUE_ this has to be entered in the corresponding field as described below.
  
  On the Scheduler: Destination tab select the destination by double clicking on it.
  If the destination does not exists, proceed as described:
  
  Choose Create and on the bgRFC Configuration dialog box select Inbound.
  Enter the destination name into the Destination field and leave all other values as defaulted.
  
  In the Open Connections field enter the number of allowed parallel processes or queues you wish to be managed by this destination. This number also specifies the maximum of parallel processes to be configured during the step configuration.
- If you do not create the bgRFC inbound destination manually the very first consolidation process will trigger the automatic creation of the inbound destination under prerequisite that the authorization object S_BGRFC with full authorization is assigned to workflow system user.
For more information see http://help.sap.com/saphelp_nw70ehp2/helpdata/de/f0/225c3c60065627e10000000a114084/content.htm

End of the note.
The process step matching has bundled records considered to be duplicates, the so called match groups.

In a first step, the records of a match group are compared on table level. For a specific table the source system or the recency can be considered to have higher priority. Depending on this setting the corresponding data is taken into account for the best record. The information, what source system has a certain priority for a specific table is maintained in the Order of Source Systems view.

In a second step the preliminary best record is processed on field level. If a field does not contain data but completeness is assigned to this field as highest priority, then the data is completed with data derived from the record with the next highest order.
1. Choose New Entries
2. In the BO Type field, enter a business object type using the entry help.
3. In the Config. ID field, enter a configuration ID.
4. In the Adapter Config. Description field, enter the corresponding description.
5. In the Number of Processes field enter the number of processes you want to be processed in parallel.
6. If required enter the Prefix for Queue Name.
  
  Note
  If you use queue prefixes other than MDC_QUEUE_ these have to be entered in the Prefix for Queue Name field.
  
  End of the note.
7. Mark your entry and configure the order of rules:
  - Order of Source Systems
    If you use the rule SOURCE_SYSTEM you have to specify the order of source systems for specific tables. For tables not explicitly mentioned all source systems have the same order.
    
    Note
    You can reduce maintenance effort, in case you want to apply the same order of source systems to all tables: To do so, create an entry with Space in the Table field and assign it to a source system. This order of source systems now is valid for all tables, except tables that are explicitly assigned to another order of source systems.
    
    End of the note.
  - Order of Rules for Tables
    On table level you can configure the order in which the rules SOURCE_SYSTEM and RECENCY are applied to a specific table.
    
    Note
    You can reduce maintenance effort, in case you want to apply the same order of rules to all tables: To do so, create an entry with Space in the Table field and assign it to a rule. This order of rules now is valid for all tables, except tables that are explicitly assigned to another order rules.
    
    End of the note.
  - Order of Rules for Fields
    On field level you can specify if the rule COMPLETENESS is applied to a specific field.
    
    To do so select the corresponding table and field name.

Example

Your source systems show the following entries in table BUT0BK (BP: Bank Details) for the fields BANKL (Bank Key), BANKN (Bank Account Number) and, KOINH (Account Holder Name).

System	BANKL	BANKN	KOINH
A11	10010010	32168000	Rosy
B22	10010010	32168000	Rosi
C33	10010010	32168000

The Customizing activity is configured in the following way:

Order of Source Systems:

Table

Seq. No.

Business System

1

C33

2

B22

3

A11

As the table field does not contain any entry the order of source system is taken into account for all tables.
Order of Rules for Tables:

Table

Seq.No.

Rule ID

BUT0BK

1

SOURCE_SYSTEM

The rule SOURCE_SYSTEM is taken into account for the table BUT0BK.
Order of Rules for Fields:

Table

Field Name

Seq.No.

Rule ID

BUT0BK

KOINH

1

COMPLETENESS

The rule COMPLETENESS is taken into account for the field KOINH in table BUT0BK.

Table	Seq. No.	Business System
	1	C33
	2	B22
	3	A11

Table	Seq.No.	Rule ID
BUT0BK	1	SOURCE_SYSTEM

Table	Field Name	Seq.No.	Rule ID
BUT0BK	KOINH	1	COMPLETENESS

The rules are applied as follows:

On table level the rule SOURCE_SYSTEM selects system C33 as system with the highest priority. Therefore in the first step the following set of data is selected for the preliminary best record:

BANKL

BANKN

KOINH

10010010

32168000
On field level the rule COMPLETENESS is applied. The field KOINH remained empty in the first step. Now the set of data is completed with data from system B22 as this is the highest rated system that contains data in the KOINH field.

BANKL

BANKN

KOINH

10010010

32168000

Rosi

Note
Only if Order of Rules for Table contains an entry referring to the rule SOURCE_SYSTEM, either specific for table BUT0BK or generic for all tables, the KOINH field is completed in the described way. If the Order for Rules for Table settings do not contain a corresponding entry, the source system is not taken into account and it is not to be predicted what data is used to complete the KOINH field.

End of the note.