Extend Data model with Entity in Material(Reuse)

 

Extend Master Data Governance for Material (MDG-M) by a New Reuse Entity Type

 

Scenario:

We are going to add the new Entity as follows.

Entity

Data Element

SU Type

Attributes

Relation

ZBUPA01

NA

4

ZNICKNAME

Leading from MATERIAL

Qualifying from ZBUPA

ZBUPA

NICKNAME

3

NA

Qualifying to ZBUPA01

Note: We replaced ‘YBUPA01’ and ‘YBUPA’ with ‘ZBUPA01’ and ‘ZBUPA’ in our Extension.

Data model with Custom Reuse Entity Type contain following steps:

Creation of Custom Active Table

·       Created below Table ZIN_T_MAT_BUT

Creation of API Structures

 

·       Created Structure ZIN_S_MAT_BUT and Included the table ZIN_T_MAT_BUT as follows.

·       Created X structure for updating of Material

·       Creating Table Type for above both Structures.



                                

  
                        

·       Create Table Type for X structure same like above.

 

Extending API Structures in Standard Data Structure ‘MDG_BS_MAT_S_MAT_DATA’

·       Extension of API Structure into Standard Data Structure

·       Create Append Structure and add respective table types into it. ZIN_BS_MAT_DATA_EXT_BP

·       Naming convention is <Table Name>_TAB and <Table Name>_X_TAB.

BADI Extension Implementation in ‘MDG_BS_MAT_API_SEGMENTS_EXT’

·       SE18 -> BADI Name ‘MDG_BS_MAT_API_SEGMENTS_EXT’ -> Create new Implementation

Or

·       MDGIMG -> Central Governance for Material -> Business Add-Ins -> BAdI: Extension of the API with Customer-Specific Segments.

·       Filter Value as API Structure Name. ZIN_S_MAT_BUT

 

 

 

 

 

 

·       In Implantation class, implement ‘READ’ Method as follows.

·       Implement ‘CHECK_AND_SAVE’ method as below.

 

 

Data model Extension with Custom Entity

·       MDGIMG -> General Settings -> Data Modeling -> Edit Data Model -> Select MM -> Entity -> Create New Entities as below.

·       Create Type 4 Entity

·       Add Attributes into type 4 Entity

·       Create Type 3 Entity and mention Data model into it

 

 

 

·       Define Relations as below

·       Save The Data Model and Activate it.

·       Now we need to generate data model specific structure.

·       MDGIMG -> General Settings -> Data Modelling -> Generate Data Model-Specific Structures -> Select MM data models -> Create Structures as follows -> Click on button ‘Generate Selected Structures’.

·       In SE11 check the structures generated.

 

Creation of SMT Mapping

·       MDGIMG -> General Settings -> Data Modelling -> Generate Data Model-Specific Structures -> Select MM data models -> Mapping -> Create mappings as below.

·       MDGIMG -> General Settings -> Data Modelling -> Create and Edit Mappings -> Create and Edit Mappings

·       Create new mapping for Active to Staging and give the name as configured before.

·       Give mapping steps as below and click on ‘Details’

·       In Transformation, Create new Transformation as below.

·       Select the Transformation and map the fields as shown below.

·       Map all the fields from Source Structure to Target Structure one by one.

·       Now again create new Mapping for Staging to Active and give respective name as configured before.

 

 

·       Click on ‘Change Structure Keys’ and add values as below.

·       Details -> Transformation -> Add new Transformation -> Map the fields same like we did for to Staging structure mapping

Extension of UI with new UIBB

·       Open any CR or Create new one -> Right click on screen -> Technical Help -> Application Configuration

·       Open main OVP Configuration

·       Screen like below will open. Now we need to Create new UIBB inside Section ‘MAT_SECTION’

·       For this we need to create new Enhancement or Customization. For this

·       Other function -> Enhance/Create Customization (Edit customization if already created)

 

 

·       In Enhancement -> Click on UIBB and Select ‘List Component’.

·       The new row will be added in last.

·       Give the name under ‘Config ID’ and click on ‘Configure UIBB’.

·       Give feeder class and parameter as below.

·       Add the columns by clicking on ‘+Column’ button. Select required column and add into UIBB.

·       Now go to the main page -> open ‘Wire Schema’ -> Add new Wire by clicking ‘+Wire’.

·       Under below Transaction we need to add Wiring for our custom UIBB

 

 

 

 

·       Mention details as below

Component

FPM_LIST_UIBB_ATS

Config ID

ZIN_BS_MAT_BUPA01 (Give Configuration ID created for custom UIBB)

Connector Class

/PLMU/CL_FRW_W_CONN_DEFAULT

Port Identifier

MARA

Port Type

Lead Selection

Source Component

FPM_FORM_UIBB_GL2

Source Config Name

MDG_BS_MAT_MATERIAL_FORM_04

 

·       Test CR by Creating New Material

·       Here we changed the properties of UI to add selection.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

               

 

 

 

 

 



Comments

Post a Comment

Popular posts from this blog

SAP MDG Process Modelling

Image
Overview In SAP MDG, every change to master data is initiated using a change request. After a change request is initiated, it needs to be processed before activation or rollback by applying governance rules and collaborations. The process model provides the required input (metadata) for change request creation and processing, e.g., workflow, CR steps, and objects that can be processes. Submit and activate/rollback are mandatory steps in a change request. MDG reuses the SAP Business Workflow component of an underlying SAP business suite. SAP MDG workflow is an instance of SAP Business Object BUS2250. If the request has parallel processing, then each parallel step of the change request will have one BUS2250 instance. Define Governance Scope: Here we can define governance scope on the entity as well as the attribute level. For example, we have kept ‘NO’ to the below custom entity. As a result of MDG UI, the UIBB for this entity will only be in read-only mode. Business Object An ...
Read more

MDG Derivation (BADI)

Image
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. H...
Read more

MDG Validation (Using BADI)

Image
In this blog, we will see how to validate the MDG attributes using the BADI implementation. So, we are taking the example of the 'BP Grouping' field to make it mandatory on the UI. For this, we should know the technical attribute name for the respective field. In our case, 'BU_GROUP' is the technical name for the BP grouping field. Steps for the Implementation of Validation BADI. 1.   Open T-code ‘MDGIMG’ –> General Setting -> Data Quality and Search -> Business Add-Ins -> Execute BADI: Define Validation/Derivation OR SE18 -> BADI name: 'USMD_RULE_SERVICE' -> Create BADI Implementation.  2. After execution, the following screen will appear. Go down, and there you will find the option to create enhancement implementation. Click on that button. 3. Provide the name and short description of the implementation, as follows:   4.  After that, we have to create the BADI Implementation and Implementation class. 5.  You will be directed to the Enha...
Read more