Procurement ASL Rest Api Access through seeded/custom roles

Summary:

Hi,

I wanted to understand a oracle behavior we noticed while providing procurement ASL entries Rest Api access to a user in oracle fusion.

Ideally a user needs to be defined as procurement agent and have at least two privileges "PO_VIEW_ASL_REST_SERVICE_PRIV " and "PO_SEARCH_APPROVED_SUPPLIER_LIST_ENTRY_PRIV" to do a successful REST API call. These two privileges are inherited by some of the seeded roles like "ORA_PO_BUYER_JOB", "ORA_AP_ACCOUNTS_PAYABLE_INVOICE_SUPERVISOR_JOB", "ORA_AP_ACCOUNTS_PAYABLE_SPECIALIST_JOB", "ORA_FND_INTEGRATION_SPECIALIST_JOB", "ORA_PO_PROCUREMENT_INTEGRATION_SPECIALIST_JOB" etc.