Our customer (on EHP minus 1) decided on a multi country implementation of MSS Add-on 1.0 with the requirement that all UIBBs in ESS should have visibility control based on attributes of employee like Company Code, PA/PSA or EG/ESG.
The standard approach would be to use define multiple screens with required fields, use HRESS_C_PERSINFO_CONFIG to replace per combination and implement BAdI HRESS_PER_CONFIG_KEY for additional attributes. This definitely meets the requirement, however has following maintenance issues from a customer perspective.
- Any changes to screen for a specific combination defined by business will have wait till the monthly release cycle to be reflected in the portal ( only emergency transports can be moved to production environment between cycles)
- Most importantly, all changes require support organization involvement (configuration/transport). This should be avoided and had to be maintained by a power user using a custom table directly in Production.
This can be achieved with a post exit in method: GET_UIBBS_FOR_EVENT in Component Controller of FPM_OVP_COMPONENT.
- Get PERNR from Memory (PERNR_MEM_ID )
- Read all UIBBs.
- Remove UIBBs according to your customer requirements (used CONFIG_ID)