MDG: Data Quality

 We have some standard data quality solutions provided by SAP MDG framework as follows. 

1. Search applications

2. Duplicate check configuration

3. Validation and Derivation (BRF+ , BADI)

4. Data Quality Management rules

Search Applications:

·       For all the Out of the Box Standard Master Data Application, SAP provided Standard Search Application.

·       For MM, BP, AR, EAM, FI all having standard Search application.

·       For MM before S4/HANA use Enterprise search. After Introducing S4/HANA it uses HANA Search.

·       For Adding our Custom Attribute into the search criteria in Enterprise search it is complex, but in HANA search its very easy to bring.

·       In Fresh system, it’s not recommended to activate the standard search view provided by SAP.

·       It’s recommended to copy the standard search view and add our own attributes in that if we want custom one. We need to keep standard search view as it is for reference.

·       In HANA, by default Fuzziness will get set default.

·       Search Result is combined result of active area and staging area record.

·       When we add custom entity and custom table into data model scope and wants to bring that to search screen attribute criteria, then we need to do the configuration ‘Define join, Filed mapping, and Authorizations for Reuse tables’ under Search and Duplicate check.


      Access Class: Use to get the data from active area as well as staging area.

      Freeform: Use as a free search, like google. Regardless field it will give you result from any of the field. It is only relevant for Enterprise search.

      Fuzzy: Fuzzy search is relevant for Enterprise search and HANA search only. HANA search is fuzzy by default. 

     Dupliacte check

·       As General process, the customer will search for the object before creating new one in MDG.

·       But sometimes if the customer not searched for existing object and tried to create new object then this Duplicate check help customer to show the existing object present in system.

·       For this there is Match Profile in which standard out of the box match profiles given by SAP in which there are attributes by which we can determine the duplicate criteria.

·       Weight field can provide preference of the fields in Duplicate check.

·       Fuzziness gives you accuracy of Duplicate check. The default value is ‘1’. It means the complete pattern will match with exact result. The range start from ‘0’ to ‘1’. Giving value ‘0.5’ means if the value match 50% of criteria then it will show in Duplicate check.

·       If we want the attributes on Duplicate check popup but not in the Duplicate check configuration then we can check the checkbox ‘Ex. Attr’.

·       For one Data model we can have only one Match Profile in place.

·       In Low and High threshold, the range of weight of the match can be configured. 




    









Comments

Post a Comment

Popular posts from this blog

Extend the MDG Business Partner – Node Extension (Reuse Option)

Image
So, here we are going to add a new entity to the company code data level, as shown in the above figure. Steps:- Extension of S4 API Structures To get the API structures, we need to go to the standard BP handler class. In Below structure, we need to add our own API structure. Class ‘ CL_MDG_BS_ECC_HANDLER ’. Table Type ‘ MDG_BS_BP_TT_ECC_EXTERN ’. Data Dictionary Object Creation Structures For Genil model extensions: Creation of Table to store this Secret number data in backend active table Extension of BP data model with new Entity Generate Data Model specific structures Create and Implement BP Handler Class Below methods we need to re-define GET_OBJECT_DATA_BY_ENTITY SORT_ENTITIES MAP_DATA_2API MAP_DATA_2STA PREPARE_EI_HEADER_MAP_2API READ_OBJECT_DATA SAVE_ADDITIONAL_OBJECT_DATA CONSTRUCTOR Below methods we have created newly READ_VENDOR_BY_LIFNR READ_VENDOR MAP_BP_ZSECRET_N_2API MAP_BP_ZSECRET_N_2STA CONSTRUCTOR METHOD  constructor .    ...
Read more

SAP MDG Data Modelling

Image
·        Data model is to define the structure of the data storage. ·        During Master data processing, a change request is used to store the data which is in process of changing in staging area. ·        The data model can define reuse area that is used for data storage after completion of change request. ·        In this case the system moves the data from staging area to a storage location using access class of the reuse area. This storage location is called active area. ·        In case no reuse area is defined, the same database table which is used for staging area, are also used to store active data. ·        Then no access class is involved, the system does not move the data to other system or any other table then MDG generated tables which is used as active area. In simple term, Data Mode...
Read more

SAP Customer/Vendor Integration (CVI)

Image
Customer Vendor Integration       CVI is separated into 2 part. 1. CVI Configuration in S4/HANA system 2.   CVI Synchronization CVI Configuration In S4/HANA, If we want to make it Business Partner as a Leading Object to maintain Customer or Vendor then we must do CVI Configuration. Limitation of Customer/Vendor objects without CVI -> Only single address we can maintain for each customer or vendor.        ->  No relation supports between customer and vendor       -> No  time dependency data we can have       -> In  S4/HANA we have single business objects as ‘BP’.       -> BP  is capable of centrally managing master data of BP, Customer, Vendor Customer ·         Customer is a BP to which we sell our Goods or Services. ·         Some customer information is specific to a company (Company code data) or ...
Read more