Limit “Add” action on Personal Payment Method in Oracle HCM

Summary:

Hi everyone,

I would like to understand if it is possible to restrict the Add action for Personal Payment Methods in Oracle HCM.

Our requirement is to prevent employees from adding new Personal Payment Methods, while still allowing them to view or possibly update existing ones.

We are evaluating different options such as:

• Role security (privileges related to Personal Payment Methods)
• Transaction Design Studio
• Page personalization / VBS

Has anyone implemented a similar restriction?
Which is the recommended approach to disable or hide the Add button for Personal Payment Methods in self-service?

Any guidance or best practices would be appreciated.