In HR Renewal, Action menu is present for objects in the landing page.
Currently Action Menu data is retrieved or determined from Launchpad(s) maintained in the PFCG role personalization object key. And also Action Menu actions are displayed based on type of object & other conditions.
For example in HR Professional,
–For Employees only the international + MOLGA to which the employee belons to only those actions appear in action menu.
–For Positions only position relevant actions appear in action menu.
–For Organization Units only relevant actions appear in action menu.
If the requirement is to have the different action menu for the objects, following is the approach you could follow to achieve the behavior:
Approach 1: By enhancing the odata for Action Menu (*This will only affect the landing page action menu’s):
1. PAO_ACTIONMENU oData service provides data to the Action Menu in landing page.
2. For HR Professional content or lanes, oData call might be as follows:
For ESS/MSS content or lanes, oData call might be as follows:
http<(s)>://<<host>:<port>/sap/opu/odata/sap/PAO_ACTIONMENU/HRActionMenuContents?$filter= OTYPE eq ‘P’ and OBJID eq ‘00000001’
The runtime class, which provides the data to this oData is CL_HRPAO_GW_RT_ACTIONMENU. In this class /IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_ENTITYSET method provides the data at runtime.
To achieve the requirement, you can do an Enhancement Implementation to this class’s method and implement the required code.
For example: based on the scenario like ESS/MSS filter parameters are passed to the GET_ENTITYSET method like otype and object id, based on these filter parameter code can be written to dynamically filter the content for the menu.
Another approach is to create different pfcg roles and associate different launchpad’s (with required actions). If this approach is used then all the action menu content can also be changed.
Example of the Action Menus in Landing Page: