Ansicht
Dokumentation
VC_MDC_ORD_RULES - Specify Order of Rules for Best Record Calculation
rdisp/max_wprun_time - Maximum work process run time Vendor Master (General Section)This documentation is copyright by SAP AG.
In this Customizing activity, you specify the order of rules for the best record calculation. You can specify the order of rules for fields and tables and you can specify the order in which the source systems are considered.
The process step best record calculation, calculates a record containing the cumulated, most valuable data for each match group that is identified by the process step matching. This calculation is based on certain rules.
In the Customizing activity Specify Process Template you specify whether and in what configuration you use the best record calculation as part of the consolidation process.
The process step matchinghas bundled records considered to be duplicates, the 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 recencycan 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 completenessis assigned to this field as highest priority, then the data is completed with data derived from the record with the next highest order.
- Choose New Entries.
- In the Config. IDfield,enter a configuration ID.
- In the Adapter Config. Descriptionfield, enter the corresponding description.
- 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.
- Tip: 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 Tablefield 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.
- Order of Rules for Tables
- On table level you can configure the order in which the rules SOURCE_SYSTEM, RECENCY, and BRFPLUS are applied to a specific table.
- Prerequisites: To run BRF+ checks in MDG, consolidation the Customizing activity Define Rules Using the Business Rule Framework plus is maintained.
- Tip: 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 Tablefield 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 rule.
- 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.
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 | Muphy |
| B22 | 10010010 | 32168000 | Murphy |
| 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.
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 | Murphy |
- Caution:
- Only if Order of Rules for Table contains an entry reffering 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.
BAL_S_LOG - Application Log: Log header data RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 8812 Date: 20240523 Time: 161723 sap01-206 ( 119 ms )
