cancel
Showing results for 
Search instead for 
Did you mean: 

Hiding/Removing Fields from SRM UI Add-On Screens

ryan_seko
Explorer
0 Kudos

We are upgrading from SRM 5.0 to 7.0 and using the new UI Add-On.  I'm not very familiar with the UI5 interface or javascript and I haven't been able to figure out how to hide or remove fields from the UI add-on screens.  I've read through the Extensibility Customer Cookbook, but that mainly talks about adding fields to screens.  One of the fields I'm trying to hide is on the Can't Find?/Describe Requirement screen.  In SE80, I opened the /SRMNXP/SHOPPINGCART BSP application and "shoppingcart/FreeTextItem/FreeTextitem.view.js" page and fiddled around with the javascript code and reactivated everything, but that didn't work.  Am I on the right track or is there some other way to modify sap-delivered screens?

Thanks,

Ryan

Accepted Solutions (1)

Accepted Solutions (1)

Matt_Fraser
Active Contributor
0 Kudos

, have you done this sort of thing, by chance?

(FYI, Ryan and I work together)

laurent_burtaire
Active Contributor
0 Kudos

Hello,

i did not yet work on this point...

I checked cookbook for extensibility from OSS note 1830075 - User-defined fields: Preparation and use

Some explainations are not clear...

Nevertheless, check blog Extensibility in SAP SRM User Interface Addon 1.0

Default customizing is available on client 000.

Maybe it could help to have a look at it !

Regards.

Laurent.

Matt_Fraser
Active Contributor
0 Kudos

Thanks Laurent. Most of the documentation still seems to point towards adding custom fields rather than hiding delivered ones, but there might be a few hints in the blog you linked about a way to do it, so we'll try exploring that further, and perhaps reach out to for additional guidance.

ryan_seko
Explorer
0 Kudos

Thanks Laurent.  Sorry for the late reply.  In the end, the screen modifications required a combination of using the CUSTOM_PRE_EXIT method referenced in the Extensibility Cookbook and directly modifying the JavaScript in the shopping cart application.  The extensibility framework couldn't handle some of the modifications because the application was using dynamically-generated field names.

Answers (0)