Data model extension for Attribute in BP Reuse

 

Different Scenarios for Extension:


                                


Current Scenario:

We are going to add a new attribute into the entity BP_CENTRL of BP data model.



Implementation Steps for Each Scenario:

                      

Extend Field in Business Partner Level only

Implementation of Adding Field in BP only Consist following Steps:

Extension of Standard Tables and API Structure

·       As we are extending field in BUT000 table.

·       We need to add our field in the structure ‘CI_EEW_BUT000’ and ‘CI_EEW_BUT000_X’.

Extension of MDG Data Model

MDGIMG -> General Setting -> Data Modelling -> Edit Data Model -> BP -> BP_CENTRL.

Generate Data Model-Specific Structures

MDGIMG -> General Setting -> Data Modelling -> Generate Data Model-Specific Structures -> BP -> Structure -> BP_CENTRL.

 

Adjust Staging Area of Linked Change Requests

Or

Execute Program ‘USMD_ADJUST_STAGING’ with Parameter ‘BP’.

 

Define SMT Mapping

·       MDGIMG -> General Setting -> Data Modelling -> Generate Data Model-Specific Structures -> BP -> Mapping -> BP_CENTRL

·       MDGIMG -> General Setting -> Data Modelling -> Create and Edit Mappings -> Extend Mappings -> Extend Mappings.

·       Open the 2STA Mapping -> Select Mapping Step -> Details.

·       Edit -> Transformation tab -> Add new Transformation -> Select that Transformation -> Map field from Source Structure to Target Structure -> Save.

 

·       Open 2API Mapping -> Open Mapping Step -> Details.

·       Details -> Edit -> Transformation Tab -> Add New Transformation -> Select added Transformation -> Down Map Source field with Target field as below.

·       Go back to the Mapping Step page -> Select mapping step for X structure -> Details -> Edit -> Add new Transformation -> Map Source Field with Target Field.

 

Add field to UI

·       Open any Customer or Supplier on MDG UI -> Right Click -> Technical Help

·       Application Configuration

·       Open ‘BS_CU_OVP’

·       Customer Details Configuration

·       Open Configuration for BS_BP_DETAILS

·       Other Function from TAB -> Create Customization (Edit if already exist) -> Drag field from Repositories and Drop to the Preview Section.

·       Save the customization and Test Creation of Customer or Vendor.

Extend Field in Customer/Vendor Level Only

Extension of Standard Tables and API Structures

·       We need to add field in LFA1 table.

·       There is one Standard Include structure in LFA1 table as shown below.

·       We have added append structure into this structure and added our field.

·       For checking the API Structures for BP_VENGEN, we need to check the SMT Mapping

·       Open this mapping in SMT Interface.

·       As, this is from Active mapping the source structure will be API Structure.

·       Open the Source structure in SE11 t-code. Here the same Include structure is present inside this so we no need to add again.

·       Append X Structure.

·       In API mapping, we can get the X structure

·       Open structure in SE11 -> Search for the Standard Include if there or else create append structure and append the field into this.

 

Extension of MDG Data Model

·       MDGIMG -> General Setting -> Data Model -> Edit Data Model -> BP -> Entity -> BP_VENGEN -> Attributes -> Add new attribute -> Save -> Activate.

 

Generate Data Model-Specific Structures

·       MDGIMG -> General Setting -> Data Model -> Generate Data Model-Specific Structures -> BP -> BP_VENGEN -> Generate Selected Structures.

Define SMT Mapping

·       MDGIMG -> General Setting -> Data Model -> Extend Mappings -> Extend Mappings.

·       Select the mapping step and go to Details -> Transformation tab -> Add new Transformation

·       Select newly created transformation -> map the field as below.

·       Map the same for 2PP mappings for both main structure and X structure.

Add field to UI

·       Open any Supplier in display mode or Create any new CR.

·       Go into the ERP Vendor Section and open the details.

·       In Control Data UIBB -> Right Click on Screen -> Technical Help


                                                                                                                                  

·       Click on Web Dynpro Component

 

·       Create Enhancement or Customizing for this WD Component -> Add the Custom field into the Screen -> Save.


 

Extend Field in BP and Customer/Vendor Both

·       It is the combination of other 2 Extensions Scenario

·       We need to add one step that’s it.

CVI Mapping BADI Implementation

·       SE18 -> Enhancement Spot ‘CVI_CUSTOM_MAPPER’ -> BADI Definition ‘CVI_CUSTOM_MAPPER’ -> Create new Enhancement Implementation.

 

·       Create new BADI Definition -> We need to implement 2 methods as we are doing for Supplier.

·       Create Implementation for Methods ‘MAP_BP_TO_VENDOR’ and ‘MAP_VENDOR_TO_BP’.

·       ‘MAP_BP_TO_VENDOR’

·       ‘MAP_VENDOR_TO_BP’

 


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