Configuring custom GRC NWBC Launch Screens restricted via PFCG roles

Challenge: Standard SAP GRC roles for NetWeaver Business Client (NWBC) grant excessive access privileges that exceed users’ actual job requirements. This over-provisioning creates security risks and poor user experience, as users encounter numerous irrelevant hyperlinks and folders they don’t need for their daily tasks.

Implementation Approach: The solution leverages transaction LPD_CUST (Configure Launchpad for Menus) to design custom NWBC landing pages. This involves copying standard Webdynpro application configuration, component configuration and UIBB component in which LPD_CUST role is linked.

In this blog, the detailed steps for configuring LPD_CUST, Web Dynpro Configuration and PFCG mapping is highlighted.

Environment: GRC Access Control 12.0

 

​ Challenge: Standard SAP GRC roles for NetWeaver Business Client (NWBC) grant excessive access privileges that exceed users’ actual job requirements. This over-provisioning creates security risks and poor user experience, as users encounter numerous irrelevant hyperlinks and folders they don’t need for their daily tasks.Implementation Approach: The solution leverages transaction LPD_CUST (Configure Launchpad for Menus) to design custom NWBC landing pages. This involves copying standard Webdynpro application configuration, component configuration and UIBB component in which LPD_CUST role is linked.In this blog, the detailed steps for configuring LPD_CUST, Web Dynpro Configuration and PFCG mapping is highlighted.Environment: GRC Access Control 12.0   Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog

You May Also Like

More From Author