MDG – Technical Customization and Configuration of the screens Based on User role

Thanks for sharing.

If possible, Can You explain the things, Configuration/Changes required in Classes and its relevant Methods(Point 1 to 15), Implementing Standard BAdi/Code Changes in Method INITIALIZE(Point 16) little detail with screenshots ?

My understandings from blog are given below, correct me if wrong, kindly add Your notes wherever You feel to explain.

(Points 1 to 16 are in same order as blog)

1. The Badi BADI_MDG_BS_MAT is enhanced to read the values from the above table and modify the properties.
   • We need to enhance the BAdi Implementation ‘BADI_MDG_BS_MAT’ to read values from ‘required table(As in blog)’ and we need to modify Properties
2. Copy the enhancement implementation MDG_BS_MAT_GEN from package MDG_BS_MAT_MODEL_GEN into ‘Z_IM_MDG_BS_MAT_GEN’.
   • Copy Enhancement Implementation ‘MDG_BS_MAT_GEN’ via SE19
   • 
   • Via SE18, BAdi Definition ‘USMD_UI_EVENT2’, After Copying
   • 
   • when copying ‘Enhancement Implementation’, its belongings(Enh. Imple. Elements) are getting copied,
     • BAdi Implementation
     • Implementing Class (it belongings)
     • Class-Methods
     • Methods-Code
     • Filter Values
     • 
     • 
     • 
3. Copy the class CL_MDG_BS_MAT_UI_BADI into ZCL_IM_MDG_BS_MAT_UI_BADI.
   • As Class ‘CL_MDG_BS_MAT_UI_BADI’ also get copied while copying Enhancement Implementation ‘Z_IM_MDG_BS_MAT_GEN’, we need to change the Class with ‘ZCL_IM_MDG_BS_MAT_UI_BADI’.
   • Via SE24, copying 
   • 
   • 
   • 
   • Changing the Class in ‘Enhancement Implementation’ to ‘Z_IM_MDG_BS_MAT_GEN’ 
   • 
   • 
4. Set the filter value UICONFIGURATION = Z_MM_MATGEN_ALL__SG_01_1 (Configuration that needs to be used ,If it is custom set as custom)
   • Deleting ‘FilterValues’  that are get copied while copying Enhancement Implementation ‘Z_IM_MDG_BS_MAT_GEN’ 
   • 
   • Adding ‘Filter Combination’ ‘UICONFIGURATION = Z_MM_MATGEN_ALL__SG_01_1’
   • 
5. In the attributes tab Change the value of GC_USUAL_UI_CONFIG to ‘Z_MM_MATGEN_ALL__SG_01_1’.
   • Changing Attribute Value 
   • 
6. The code has been implemented in three methods
   • From 7, 8 & 9th points
     • IF_EX_USMD_UI_EVENT2~MODIFY_DEFINITION
     • IF_EX_USMD_UI_EVENT2~PROCESS_VALUE_HELP
     • IF_EX_USMD_UI_EVENT2~MODIFY_VIEW
   • Method listed in ‘Requirement Detailing Table’
     • IF_EX_USMD_UI_EVENT2~MODIFY_DEFINITION
     • IF_EX_USMD_UI_EVENT2~MODIFY_VIEW
     • IF_EX_USMD_UI_EVENT2~GET_ATTR_VALUE_SET
7. IF_EX_USMD_UI_EVENT2~MODIFY_DEFINITION used to hide the Main view and subview and the event buttons
   • To Adjust Definition of Attributes/Add Attributes ::: Used to Hide Main View, Sub View & Event Buttons
8. IF_EX_USMD_UI_EVENT2~PROCESS_VALUE_HELP used to filter the F4 value based on the custom table entries
   • To Restrict Selection for Input Help ::: Used to Filter F4 Value, based on Custom Table Entries
9. IF_EX_USMD_UI_EVENT2~MODIFY_VIEW  to set the filed level attributes.
   • To Dynamically Adjust User Interface ::: Used to Set Field Level Attributes
10. The custom table zmmdguibadi has been created to maintain the different combination of data.Based on the user , retrieve the roles from table agr_users.  Based on the Model,CREQ type , roles and entity retrieve the information from zmmdguibadi which will be used in all the METHODS.
    • Custom Table ‘zmmdguibadi’ created to maintain different combination of Data
      • Based on User, Retrieve the Roles from Table ‘agr_users’ with ‘AGR_NAME’
      • Based on Model, CREQ Type, Roles and Entity; Retrieve information from ‘zmmdguibadi’ which is used in Methods
11. IF_EX_USMD_UI_EVENT2~MODIFY_DEFINITION—Based on zmmdguibadi-action eq ‘02’ ,zmmdguibadi -usmd_mview_id, zmmdguibadi -usmd_visible      hide main view
    • Method ‘IF_EX_USMD_UI_EVENT2~MODIFY_DEFINITION’; will Hide Main View, Based on ‘zmmdguibadi’ when
      • ‘Action’ Equals to ‘02’,
        • ‘zmmdguibadi’ – ‘usmd_mview_id’
        • ‘zmmdguibadi’ – ‘usmd_visible’
12. Based on zmmdguibadi-action eq ‘03’ , zmmdguibadi–usmd_sview_id and ls_zmmdguibadi–usmd_visible hide subview.
    • Method ‘IF_EX_USMD_UI_EVENT2~MODIFY_DEFINITION’; will Hide SubView, Based on ‘zmmdguibadi’ when
      • ‘Action’ Equals to ‘03’,
        • ‘zmmdguibadi’ – ‘usmd_sview_id’
        • ‘zmmdguibadi’ – ‘usmd_visible’
13. IF_EX_USMD_UI_EVENT2~PROCESS_VALUE_HELP – Based on the zmmdguibadi-action eq ‘01’ ,zmmdguibadi—usmd_attribute1 and the value of zmmdguibadi–usmd_attribute , Retrieve the corresponding entries to be populated into F4 help of other fields.
    • Method ‘IF_EX_USMD_UI_EVENT2~PROCESS_VALUE_HELP’, will Retrieve corresponding entries to be populated into F4 help. Based on ‘zmmdguibadi’ when
      • ‘Action’ Equals to ‘01’,
        • ‘zmmdguibadi’ – ‘usmd_attribute1’
        • ‘zmmdguibadi’ – ‘usmd_attribute’
14. IF_EX_USMD_UI_EVENT2~MODIFY_VIEW — Based on the value of zmmdguibadi-action eq ‘04’ , zmmdguibadi—usmd_attribute , set            zmmdguibadi–usmd_attribute1 required ,read_only  or visible.
    • Method ‘IF_EX_USMD_UI_EVENT2~MODIFY_VIEW’, will make the field ‘ReadOnly’ or ‘Visible’, Based on ‘zmmdguibadi’ when
      • ‘Action’ Equals to ‘04’,
        • ‘zmmdguibadi’ – ‘usmd_attribute1’
        • ‘zmmdguibadi’ – ‘usmd_attribute’
15. IF_EX_USMD_UI_EVENT2~MODIFY_VIEW — Based on the value of zmmdguibadi-action eq ‘05’ , zmmdguibadi— fpm_event_id, set event invisible.
    • Method ‘IF_EX_USMD_UI_EVENT2~MODIFY_VIEW’, will set event ‘Invisible’, Based on ‘zmmdguibadi’ when
      • ‘Action’ Equals to ‘05’,
        • ‘zmmdguibadi’ – ‘fpm_event_id’
16. The standard BADI USMD_CREQUEST_UI is  implemented ZMMD_USMD_CREQUEST_UI. The code changes are done in the method INITIALIZE to make the reason field mandatory
    • Kindly elaborate.