Master Data Consistency Analyzer - MDCA

[grace_xin]

Introduction

MDCA tool (Master Data consistency Analyzer) was previously called as MICE (Master Data Inconsistency Evaluator).
It can be used to identify the data inconsistencies across applications. CVI (Customer vendor integration), BP (Business partner), Address etc that are configured to the MDCA framework. All the inconsistencies in an application can be identified in one go, or inconsistencies can be identified for specific objects based on the selection criteria. MDCA tool can be considered as a one stop solution to identify all data inconsistencies for an application which will eventually save a lot of time and effort and ensure seamless process flow.

Target audience

Functional expert

Release Status

This transaction MICE is in restricted release mode for exclusive use by SAP Support.

Results may not be accurate and may not reflect current state of data.

Do not execute this transaction without written guidance from SAP.       

MDCA Capabilities and Features

Transaction MICE is currently suitable for CVI and Business Partner applications to identify and repair inconsistencies. The tool also supports Address-related inconsistencies.

Key highlights include:

• Standard applications currently enabled: CVI, BP, and Address (additional applications such as DPP are planned).
• Support for customer-specific applications through framework extensibility.
• Execution in both foreground and background modes.
• Run History with execution metadata for traceability and analysis.
• Ability to exclude irreparable inconsistencies from result display.
• Application sub-keys/subcomponents to refine inconsistency analysis.
• Fully customizable selection criteria per application using MICEMVS and MICEMV.
• Display of total inconsistent records per master data object and per message type.
• Bulk repair functionality at master data level.
• Message classification (To Be Repaired, Repaired, Cannot Be Repaired).
• Criticality-based prioritization of inconsistencies (customizable).
• Display of message parameters and change logs (similar to BP transactions).
• Reuse of standard ALV functionalities.

Prerequisites

Before Implementing the notes in the sequence listed below, carefully review the SAP Note 3353957.

Important: Implement the SAP Notes listed below in strict sequence. In case any Note implementation status is incorrect or incomplete, stop and report back the issue to SAP Support. Do not proceed further with the implementation without resolving implementation issues from previous Notes.

MDCA Framework Notes :

1. SAP Note 2956974 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 1

This Note contains the package 'S_BUPA_TOOLS' in which the MDCA framework objects are developed.

    There will be activation issues for other objects in this Note, as the DDIC objects will be created from the next Notes below.

    Just make sure the package 'S_BUPA_TOOLS' is created sucessfully during the implementation of this Note.

2. SAP Note 3532897 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 2

3. SAP Note 3500434 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 3

    Once the above 3 notes are implemented, implement the first note again as mentiond below.

4. SAP Note 2956974 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 1

5. SAP Note 3232130 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 4

6. SAP Note 3362331 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 5

7. SAP Note 3384523 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 6

8. SAP Note 3472055 :- MDCA ( Master Data Consistency Analyzer ) - Framework Note 7

Post implementing above Notes, go to SE80 transaction, check and activate if there is any inactive objects in package 'S_BUPA_TOOLS'.

Business Partner ( BUPA ) Application Notes for MDCA Framework:

9. SAP Note 3396047 :- MDCA ( Master Data Consistency Analyzer ) - BP Application Note 1

10. SAP Note 3396036 :- MDCA ( Master Data Consistency Analyzer ) - BP Application Note 2

11. SAP Note 3485146 :- MDCA ( Master Data Consistency Analyzer ) - BP Application Note 3

12. SAP Note 3514136 :- MDCA ( Master Data Consistency Analyzer ) - BP Application Note 4

CVI Application Notes for MICE Framework :

13. SAP Note 3512942 :- MDCA ( Master Data Consistency Analyzer ) - CVI Application Note 1

14. SAP Note 3025283 :- MDCA ( Master Data Consistency Analyzer ) - CVI Application Note 2

Note: Currently, there is no change Logs functionality enabled. This will be automatically updated via the relevant SPs across relevant Releases.

Usage

MDCA tool can be launched using the transaction code MICE.

Active applications configured in MDCA framework will appear in the list and needs to be selected, which will enable the user to enter selection screen parameters for execution.

- Background Execution
The button ‘Execute in Background’ will help to run the tool in background which is advised when running for large number of inconsistencies.  The 'Find' option will find all the inconsistencies. All the inconsistency details along with their statuses will be stored in the spool and will be available in ‘Run History’ section post completion of the background job for display.

- Foreground execution
The foreground execution of MDCA tool will display an ALV with all the inconsistencies based on the selection parameters.

‘Run history’ section in the selection screen will store the details for each execution (Background and foreground) and can be used for analysis at a later point of time if required. Upon selecting an entry from run history, the details will be displayed in the ALV.

Steps to check the inconsistencies

step 1 & Step 2: run transaction code MICE and select the Application Objects

Step 3: Chose the Parameter to find the inconsistency

Step 4 & Step 5: Select Run Parameter and Selection Criteria

Step 6 & Step 7 & Step 8: Check result

The following is a screenshot for All Parameters for your reference.

Basic Tech info

Transaction code MICEMVS can be used to display the standard applications and other configurations delivered by SAP. Master data, table field, parameters and message nodes will be configured for each application which will help in execution of the MDCA tool. The application registered with active status will appear on the MDCA tool. 

Transaction MICEMV can be used to register custom applications. Master data, table field, parameters and message nodes must be configured as per the design. The custom class should refer to interface MICE_IF_WRAPPER for successful registration.
For more detais, please check 3353957 - MDCA ( Master Data Consistency Analyzer ) :- Functional Details

Successful configuration will generate the include programs MICE_GENERATE1 and MICE_GENERATE2 which will be used for dynamic generation of selection screen fields in MDCA tool.

Message node must be maintained with message class and message number details along with parameters to be displayed in the MDCA tool output. The criticality field is used to prioritize the inconsistencies while listing in the output.

MICE transaction is used to launch the MDCA tool. The selection screen will be displayed based on the configurations in MICEMV and MICEMVS.

The screen fields will be displayed based on the application selected. The tool can be executed, either by providing basic field values or by providing additional filters based on 'Specific' parameter option. Please refer attachments 'Initial screen' and 'Specific Parameters'.

After execution, all the inconsistencies will be displayed based on the selection criteria provided. Inconsistencies can be analysed further by checking the message text and additional parameters. Please refer attachment 'MICE -Output Screen'.

How to get SAP support for this tool

For issues related to the MDCA tool, please create an SAP Support incident with support component LO-MD-BP or AP-MD-BP-GEN.

Best Regards,

@Manoj_007  and Grace