We are building an APEX integration against Oracle Fusion Receivables for the following use case: an existing standard receipt already exists in Fusion, we identify it via REST, identify the target invoice via REST, derive the Bill To Site Use Id, and then attempt to create the receipt application against that invoice.
We can successfully:
- GET the receipt from
/standardReceipts
- GET the invoice from
/receivablesInvoices
- GET the bill-to site from
/receivablesInvoices/{CustomerTransactionId}/lov/billToSites
- GET existing records from
/receivablesCustomerAccountSiteActivities/{SiteUseId}/child/standardReceiptApplications
However, when we POST to /receivablesCustomerAccountSiteActivities/{SiteUseId}/child/standardReceiptApplications, Oracle returns 403 Forbidden.
The user already has Accounts Receivable roles and relevant security context roles and value access, so I am trying to understand what specific privilege, duty role, data security policy, or REST entitlement is typically required to create standard receipt applications via REST for this use case.
Has anyone successfully posted to standardReceiptApplications for applying an existing receipt to a specific invoice, and if so, what role/privilege/security setup was required?