SAP MDG: How to adjust UI or hide fields based on CR type and CR Step

[Former Member]

Hi,

I am new to the SAP MDG. I want to understand the process or steps to adjust UIs based on the CR type and workflow step number.

Consider, I need to adjust my UIs for material master and say I want to hide certain fields based on the CR Steps. As per my understanding, I need to perform below steps:

1. Configure the properties of Change request step
2. Select CR type and CR step and then based on it select Entity/Attribute which needs to be hidden
3. Set Field property to 'Not relevent' - This will make field grayed out at UI.

However, I am not able to hide the field for this CR type and CR Step. Can any one please let me know how can I achieve this?

SAP MDG version is 7.0 SP03.

[former_member190949]

Hello Vikas,

You can use Context based Adaption for this.

Both Material & BP have CR type & CR step as a predefined dimension in their respective schema BS_MAT and BP_ADAPTS respectively.

You can Hide the view by ticking the Hide UIBB checkbox as in the screenshot.

Thanks,

Kavita

cba.png

[Mark63]

Generally, for extensibility and UI adaptations, you can also see the how-to section at https://wiki.scn.sap.com/wiki/display/SAPMDM/Documentation%3A+Application+Framework+Including+Custom...

Best,

Markus

[loga201]

Hi ,

1. you use adaptations in MDG to change fields based on CR type and Workflow..
2. you can also implement BADI USMD_ACC_FLD_PROP_CUST_DEP_SET.
3. you also set properties in the get definition method of the feeder class.

Even though we have many option ,It is nice to use first one else 2nd one..

[former_member655347]

Hi Nathan,

I am using BADI USMD_ACC_FLD_PROP_CUST_DEP_SET to make the field mandatory, optional, hidden and gryed out at the step level of the workflow

But it is not working for every field properly . Like For eg . I am doing MEINS field to make it mandatory as 'relevant' at the requester level which is working fine , but when I making Cross -Material Plant Status(MSTAE) field also Relevant, at the requester level, it is not making it mandatory and also when moving to next approver level, I am making some of the fields mandatory and then also it is not working, Why there is an issue for some fields? Can you please help in this if something needs to be done at the config level?

[Former Member]

Hi Vikas,

Were you able to find the solution? If yes please share.

Thanks,

Swati