MDG Derivation (BADI)

In this blog, we will see how to derive MDG attributes using BADI.

Derivations can be divided into two types. 

  • Single-entity derivation: Automatically populating some attribute value in one entity based on an attribute value from same entity. For this, we use 'USMD_RULE_SERVICE' BADI definition.
  • Cross-entity derivation: Automatically populating some attribute value in one entity based on an attribute value from another entity. For this, we use 'USMD_RULE_SERVICE_CROSS_ET' BADI definition.
First, we will see a single entity derivation.
Scenario: We are going to make language English as the default if the user gives the country as India.

Steps:
1. Go to SE18.


2. In 'USMD_RULE_SERVICE' BADI defination, create BADI Implementation. 


3. For creating BADI Implementation, first we need to create Enhancement Implementation. 


4. Give the properties as below.


5. Now, create BADI Implmentation and give following properties.


6. Maintain the filter values. Here, we are going to perform derivation on the address entity, so we maintained the entity as AD_POSTAL and the data model as BP. (Note: To get the technical entity and attribute name, we can put debugger in empty method implementation and trigger it by opening MDG UI and there you can get the technical names, which we can use in our code)


7.  Now, implement method DERIVE_ENTITY.


8. Write code as follows. 


9. Finally, test this derivation on Customer or Supplier Governance UI.





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