Oracle Fusion Access for Data Foundation
Data Foundation brings data from every ERP system and instance you connect into one Common Finance Model, and Oracle Fusion Cloud ERP is one of the ERPs it reads directly. The Oracle Fusion connection uses OAuth 2.0 client credentials, a read-only integration user, and a small set of BI Publisher reports. This page is for the Oracle Fusion administrator who sets that up, and for the PlaidCloud user who asks them to.
PlaidCloud only reads data. Nobody sends a password or a client secret by email.
Send the Access Request
Section titled “Send the Access Request”On the project’s Foundation tab, choose Create a new connection under Oracle Fusion connection. The form shows the full request. Click Copy request to paste it into your own message, or Email request to open it in your mail program with the subject “Read-only Oracle Fusion Cloud ERP access for PlaidCloud (OAuth 2.0 client credentials).”
What the Oracle Fusion Administrator Sets Up
Section titled “What the Oracle Fusion Administrator Sets Up”-
Create an integration user and give it a job role that can view, for every ledger you report on:
- General Ledger: ledgers, accounting calendars and period statuses, journal batches, journals and account balances (for example “General Accountant” with data access to those ledgers)
- Currency conversion rates (daily rates)
- Key flexfield segment labels, value sets and their account hierarchy (trees)
- Receivables: invoices and their distributions, and customer accounts
- Inventory items
- Run access to the BI Publisher reports in step 3 and the ERP Integration Service (ESS jobs)
-
Register a confidential application in the identity domain (IAM) with the client credentials grant and the scope of the Fusion Applications REST API. Copy its client ID and secret.
-
Deploy nine BI Publisher reports under
/Custom/PlaidCloud/DataFoundation. Each one runs as an ESS job, with the report name as the job definition, and returns a CSV with the columns listed in the request:Report What it returns PlaidCloudKeyFlexLabelsOne row per segment of each General Ledger chart of accounts: its position, its label and its value set PlaidCloudSegmentValuesEvery value of those value sets, with the natural account type and the value hierarchy PlaidCloudCalendarThe accounting periods of every ledger, with the ledger’s period-average and period-end rate types PlaidCloudCodeCombinationsThe code combinations and their segments PlaidCloudBalancesThe opening balances of every ledger PlaidCloudJournalLinesThe journal lines, read one ledger, period and balancing segment value at a time PlaidCloudCustomersThe customer accounts and their party names PlaidCloudItemsThe items of the master inventory organization PlaidCloudSalesLinesOne row per Receivables invoice line The exact columns of each report are in the request text on the Foundation tab. Give the report names exactly as shown.
What to Send Back
Section titled “What to Send Back”| The administrator sends | Entered in PlaidCloud as |
|---|---|
The host of your Fusion Applications URL, without https:// |
Pod host |
| The token URL of the identity domain | Token URL |
| The scope of the REST API application | Scope |
| The client ID from step 2 | Client ID |
| The client secret from step 2 | Client secret |
| The balancing segment values PlaidCloud may read | Under Balancing segment values, which Fusion can’t list: enter one value under Name, or leave it blank to load every one |
The request’s closing list asks for these values together. Share the client secret through your password manager, not by email. The PlaidCloud user’s team pastes it into PlaidCloud themselves.
Check the Access
Section titled “Check the Access”Back in PlaidCloud, enter the values and click Test connection. Each dataset shows as Readable, Missing permission or Error:
| Dataset | Read from |
|---|---|
| Entities, Fiscal calendar, Chart of accounts, Departments | The ledgers, plus the key flexfield labels, segment values and calendar reports |
| Currency rates | Daily conversion rates |
| General ledger | Journal batches and the journal lines report |
| Trial balance | The balances and code combinations reports |
| Customers, Products, Sales lines | The customers, items and sales lines reports (optional) |
When a dataset is missing, the test says which permission to add. Ask the administrator to add it to the job role and test again. Customers, Products and Sales lines are optional: a Fusion pod that doesn’t hold them still loads everything else.