Oracle Fusion Cloud and Workday
How to connect Oracle Fusion Cloud (ERP, SCM and HCM) and Workday. Both read, and both can also make changes once a SourceLace admin turns them on: Oracle Fusion creates and updates records, and Workday starts one business process, the business title change (see Making changes). Each person signs in with their own Oracle or Workday login, so Oracle and Workday show them only what their own roles and security groups allow. SourceLace never uses an administrator or integration system account, for reads or for changes.
Status: Available. Built on Oracle's and Workday's published REST APIs, and validated in your Oracle pod or Workday tenant during onboarding.
At a glance
| Connects through | Sign-in | Network | Status | First test question | |
|---|---|---|---|---|---|
| Oracle Fusion Cloud | Oracle Fusion Cloud REST APIs | Personal sign-in | Nothing to open | Available | "Show 5 unpaid Payables invoices from oracle_fusion:prod." |
| Workday | Workday REST API and Workday Query Language (WQL) | Personal sign-in | Nothing to open | Available | "Find workers named Lee in workday:prod." |
Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.
How this differs from other sources
There is no SourceLace-wide app for Oracle or Workday. Your Oracle or Workday admin registers an OAuth client for SourceLace inside your own system, and your SourceLace admin types its details into the source.
- The client secret is stored encrypted with your organization's own key. After saving, SourceLace only ever shows
(saved). To keep it when editing the source, leave the field empty; to change it, type the new one. - Type the secret on the web app's Connections page, not in a chat, so it never sits in a chat transcript.
- SourceLace sends a PKCE challenge with every sign-in. A public client (no secret) also works where your policy prefers it: leave the secret empty.
The redirect URL both systems ask for is:
https://mcp.sourcelace.ai/connect/callback
Oracle Fusion Cloud
What your admin does in Oracle
Once per Fusion environment (test and production each need their own). About 15 minutes.
Who: an Identity Domain Administrator of the identity domain your Fusion users sign in with (to register the application), and a Fusion IT Security Manager if people need roles (step 8).
- Sign in to the OCI Console (cloud.oracle.com). Open Identity & Security → Domains and click the identity domain your Fusion users sign in with. (Older pods call this Oracle Identity Cloud Service; the steps are the same.)
- On the domain's Overview, copy the Domain URL, such as
https://idcs-0123456789abcdef.identity.oraclecloud.com. This is theidcs_urloption. - Open Integrated applications → Add application → Confidential Application → Launch workflow. Name:
SourceLace. Click Next. - Under Client configuration, choose Configure this application as a client now:
- Allowed grant types: tick Authorization code and Refresh token, nothing else.
- Redirect URL: the redirect URL above.
- Client type: Confidential.
- Token issuance policy → Resources: tick Add resources, click Add scope, choose your pod's Fusion Applications resource, and add its scope (usually
urn:opc:resource:consumer::all). If the Fusion resource is not in the list, this identity domain is not the one your Fusion environment uses: go back to step 1 and pick the other domain. - Click Next, then Finish.
- Click Activate on the new application. Its page must show Active: an inactive application refuses every sign-in with "unauthorized_client".
- On its OAuth configuration tab, copy the Client ID, the Client secret (Show secret), and the scope shown next to the Fusion resource, exactly as shown with no added spaces, such as
urn:opc:resource:fa:instanceid=123456789urn:opc:resource:consumer::all. SourceLace addsoffline_accessitself, so people stay signed in. - Note the address people use for Fusion, such as
corvanta.fa.us2.oraclecloud.com. This is thehostoption. (An address copied from the browser, such ashttps://corvanta.fa.us2.oraclecloud.com/fscmUI/faces/..., also works: only the host is kept.) - Make sure people are Fusion users with the right roles. Each person signs in with an identity domain user that is also a Fusion user. Their Fusion duty roles and data security decide what they can read: an IT Security Manager checks them in Fusion's Security Console (for example, a Payables role to read invoices).
Check that it worked: after your SourceLace admin adds the source, one person clicks Connect, signs in with their Oracle login, and asks the first test question from At a glance.
Oracle's own guides: Oracle Fusion Cloud Applications documentation (search for "REST API for Oracle Fusion Cloud" and "Configure OAuth") and OCI Identity and Access Management documentation.
Add the source (SourceLace admin)
Kind: Oracle Fusion Cloud (ERP, SCM, HCM) (oracle_fusion).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
host |
Host name | (required) | corvanta.fa.us2.oraclecloud.com |
The Fusion address. Must end in .oraclecloud.com. |
idcs_url |
Host name | (required) | https://idcs-0123456789abcdef.identity.oraclecloud.com |
The identity domain URL from step 2. Must end in .identity.oraclecloud.com. |
client_id |
Text | (required) | 0a1b2c3d4e... |
From step 6. |
client_secret |
Secret | (none: public client) | From step 6. Stored encrypted; shown only as (saved). |
|
scope |
Text | (required) | urn:opc:resource:fa:instanceid=123456789urn:opc:resource:consumer::all |
The Fusion scope from step 6. |
resources |
List, separated by commas | (none) | receivablesCustomerAccountActivities, hcm/salaries |
Extra REST resources to list in search_schema. |
What people can do
search_schemalists common resources (Payables invoices, suppliers, purchase orders, requisitions, sales orders, items, projects, and HCM workers, absences, jobs and positions) plus any inresources. Any other Fusion REST resource can still be queried by name.describe_objectreads the resource's own description from Oracle: its attributes and child resources.query(languagefusion_rest) takes a resource with Oracle's REST options, such asinvoices?q=InvoiceAmount > 1000 and PaymentStatusFlag = 'N'&fields=InvoiceId,InvoiceNumber,InvoiceAmount&orderBy=InvoiceDate:desc&limit=50. HCM resources start withhcm/and CX ones withcrm/. The options allowed areq,fields,orderBy,finder,expand,limit(up to 500) andoffset; anything else is refused before Oracle is called. SourceLace pages through results itself.get_recordreads one record by its key, plus up to three child resources (such as an invoice'sinvoiceLines).propose_changeandapply_changecreate and update records, when changes are on (see Making changes).
Workday
What your admin does in Workday
Once per tenant (an implementation or sandbox tenant is the safest place for a first try). About 15 minutes.
Who: a Workday security administrator, or anyone whose security groups allow the Register API Client and View API Clients tasks.
-
Search for the task Register API Client (not "for Integrations": that one is for system accounts, and SourceLace signs each person in with their own login).
-
Fill it in:
- Client Name:
SourceLace. - Client Grant Type: Authorization Code Grant. Access Token Type: Bearer.
- Redirection URI: the redirect URL above.
- Refresh Token Timeout (in days): how long people stay connected, such as 30, or tick Non-Expiring Refresh Tokens if your policy allows.
- Support Proof Key for Code Exchange (PKCE): tick it if your tenant shows it.
- Leave Public Client unticked.
- Scope (Functional Areas): at least Staffing, Organizations and Roles, Time Off and Leave, Jobs and Positions, Contact Information and System (System holds Workday Query Language). Add others, such as Compensation or Benefits, for data people should read.
- Include Workday Owned Scope: tick it.
- Client Name:
-
Click OK. Workday shows the Client ID and Client Secret once: copy both now.
-
Search for View API Clients and open the API Clients tab. Copy:
- Workday REST API Endpoint, such as
https://wd2-impl-services1.workday.com/ccx/api/v1/corvanta_preview. Its host (wd2-impl-services1.workday.com) is thehostoption, and its last part (corvanta_preview) is thetenantoption. - Authorization Endpoint, such as
https://impl.workday.com/corvanta_preview/authorize. Its host (impl.workday.com, or such aswd5.myworkday.comin production) is theauth_hostoption. It is almost never the REST API host: hosts with-servicesin them are only for the API, and sign-in there fails on Workday's own page.
You can paste both endpoints whole into SourceLace: it takes the hosts and the tenant from them.
- Workday REST API Endpoint, such as
-
Make sure people can read the data. SourceLace shows each person what their own Workday security groups allow, through the functional areas in step 2. To use Workday Query Language, the client needs the System functional area, and people need access to the data sources they query.
Check that it worked: after your SourceLace admin adds the source, one person clicks Connect, signs in with their Workday login, and asks the first test question from At a glance.
Workday's own guide: Workday Community (sign in, and search for "Register API Client" and "Workday REST API").
Add the source (SourceLace admin)
Kind: Workday (workday).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
host |
Host name | (required) | wd2-impl-services1.workday.com |
The REST API host from step 4 (or the whole REST API Endpoint). Must end in .workday.com or .myworkday.com. |
tenant |
Text | taken from the pasted REST API Endpoint | corvanta_preview |
The tenant name from step 4. |
auth_host |
Host name | (required when host has -services in it) |
impl.workday.com |
The Authorization Endpoint's host from step 4 (or the whole endpoint). |
client_id |
Text | (required) | MzY4... |
From step 3. |
client_secret |
Secret | (none: public client) | From step 3. Stored encrypted; shown only as (saved). |
What people can do
search_schemalists the REST objects (workers, supervisory organizations, job profiles, job families, jobs) and the WQL data sources the person may use (such asallActiveWorkers).describe_objecton a WQL data source lists its fields; on a REST object it lists the fields of a sample record and the related listsget_recordcan add.querytakeswql, one Workday Query LanguageSELECT ... FROM ...such asSELECT workdayID, fullName, businessTitle FROM allActiveWorkers WHERE isManager = true(noLIMITneeded), orworkday_rest, a REST collection withsearch,limitandoffset, such asworkers?search=Lee&limit=20.get_recordreads one REST object by its Workday ID, plus related lists such as a worker'sdirectReports,supervisoryOrganizationsManagedortimeOffDetails.propose_changeandapply_changestart a business title change, when changes are on (see Making changes).
Making changes
Changes are off until a SourceLace admin turns on Allow changes for the source and lists the objects under Objects that can be changed (such as invoices for Oracle Fusion, or businessTitleChange for Workday). As everywhere in SourceLace, the person first sees a preview with the current and new values, and nothing is sent until they confirm. Each change runs as that person's own Oracle or Workday login, so their own roles decide whether it is allowed.
Oracle Fusion: create and update
- What can be changed: any top-level Fusion REST resource the admin lists, by the same name
queryuses (such asinvoices,suppliers,purchaseRequisitionsorhcm/workers). A create sends one new record to the resource; an update changes one record. - Checked before anything is sent: field names are checked against the resource's own description from Oracle. An unknown field, or one Oracle marks as not updatable, is refused in the preview. If Oracle says the resource does not allow create or update, that is refused too.
- The preview shows the record's current values of just the fields being changed.
- If someone else changed the record after the preview, the change is refused and the person is asked to propose it again. SourceLace uses Oracle's record version (ETag) when Oracle returns one; otherwise it compares the record's
LastUpdateDate(or, if the resource has none, the values themselves) just before writing. - Deletes are refused. Fusion records are closed or cancelled through their status (for example, cancel an invoice or close a purchase order), so ask for a status change instead.
- What each person's roles decide: whether they can create or change that kind of record at all (their Fusion duty roles and privileges, such as Manage Payables Invoices) and which records (their data security, such as business units). If Oracle refuses, SourceLace shows Oracle's own message.
- Setup: nothing new. The Fusion scope you already gave the OAuth client covers reads and changes; Fusion's roles are what limit changes. Make sure the people who should make changes have the right Fusion roles.
Workday: the business title change
Workday does not let outside apps edit records directly: every change runs a business process inside Workday, with its own approvals. SourceLace only offers changes that are a single, documented Workday REST call, so a change can never stop half way. Today that is one:
| Object to allow | What it does | Field |
|---|---|---|
businessTitleChange |
Starts a Business Title Change for one worker | proposedBusinessTitle (text, up to 255 characters) |
- It is proposed as an update, with object
businessTitleChangeand the worker's Workday ID as the record id. The preview shows the worker's current business title. - Approvals still apply. The preview says so: this starts Workday's own business process, so if your Workday setup requires a manager or HR partner to approve, the new title shows only after they do.
- Creates, deletes, any other field and any other Workday object are refused in the preview, before anything is sent. Just before starting the change, SourceLace reads the worker's current title again and refuses the change if it moved since the preview.
- Once changes are on,
search_schemalistsbusinessTitleChangeanddescribe_objectshows its field. - What each person's security groups decide: whether they may start a business title change for that worker, set by the business process security policy for Business Title Change in Workday (for example, workers for themselves, or managers for their team). If Workday refuses, SourceLace shows Workday's own message.
- Setup: the API client's scope must include Staffing, the functional area that holds the Business Title Change business process (already in the list in step 2 above). If your API client was registered without it, edit the client in View API Clients and add it. Then turn on changes for
businessTitleChangeon the source. - Not offered yet: contact information changes, job changes, time off and other business processes.
When something goes wrong
Each system has its own table: Oracle Fusion and Workday. For both:
| What you see | What to do |
|---|---|
| "... needs the option '...', such as ...." | Fill in that option. |
| "The option '...' of ... must be a host name ending in ..., such as ...." | Give the host from the steps above (a pasted address is fine). |
| "... needs the option 'client_id': the client id of the OAuth client your admin registered for SourceLace." | Fill in client_id. |
| "Sign-in was not completed: ... redirect_uri ..." | The redirect URL registered in Oracle or Workday is not exactly SourceLace's. Copy it again. |
| "Oracle answered with a web page instead of data (HTTP ...)." (or Workday) | The host option is probably wrong, or the system is down for maintenance. |
When something goes wrong with Oracle Fusion
| What you see | What it means | What to do |
|---|---|---|
| "... needs the option 'scope': the Fusion scope shown in your identity domain, such as ..." | scope is empty. |
Copy the scope (step 6), exactly. |
| "Sign-in was not completed: ... (error invalid_scope) ..." or "Oracle sign-in failed (invalid_scope): ..." | The scope is mistyped, or the application does not allow Refresh token. | Copy the scope again and tick Refresh token (steps 4 and 6). |
| "Sign-in was not completed: ... (error unauthorized_client) ..." or "Oracle sign-in failed (unauthorized_client): ..." | Authorization code is not ticked, or the application is not activated. | Steps 4 and 5. |
| "Oracle sign-in failed (invalid_client): ..." | The client ID or secret is wrong, or the application is inactive. | Copy both again (step 6), and check it shows Active. |
| "Oracle sign-in failed: ..." (another reason) | The identity domain's own reason follows. | Check steps 3 to 6. |
| "Oracle did not say which user signed in." | The identity domain's token did not name the user. | Contact support. |
| "Oracle Fusion did not accept your new sign-in (HTTP 401), so connecting again will not help ..." | The scope is for another Fusion environment (such as test instead of production), or the person is not a Fusion user. | Copy the scope shown for this environment's Fusion resource (step 6), and check the person (step 8). |
| "Oracle Fusion: ... Your Oracle roles do not allow this: ask your Oracle admin." or "Oracle Fusion: your roles do not allow this. ..." | The person's Fusion roles do not allow reading or changing these records. | An IT Security Manager checks their roles (step 8). |
| "Oracle Fusion: that resource or record does not exist, or your roles do not let you see it." | The resource name is wrong, or the roles do not allow it. | Check the name with search_schema, and the roles. |
| "Oracle Fusion: ..." (another message) | Oracle's own words, such as an unknown attribute in q. |
The AI usually fixes the query itself. |
| "Oracle Fusion does not allow ... on ... through its REST API." | That resource cannot be created or updated through Oracle's REST API. | Make the change in Fusion itself. |
| "This ... record changed in Oracle Fusion after the preview. Propose the change again." | Someone changed it after the preview. | Ask for a new preview. |
| "SourceLace does not delete Oracle Fusion records. ..." | Deletes are refused. | Change the record's status instead, such as cancelling an invoice. |
| "Your Oracle sign-in has expired." | The sign-in ended. | Connect again. |
| "The option 'resources' of ...: ..." | The list of resources in the source has an entry Oracle Fusion's REST API does not offer, or one that is not a valid name. | An admin corrects the list; the message names the entry. |
| "Oracle did not describe .... Check the resource name with search_schema." | The resource name is wrong or the REST API does not describe it. | Use a name from search_schema. |
| "Oracle sent back data in an unexpected shape.", "SourceLace refused to send an unexpected Oracle request." or "SourceLace refused to call an unexpected Oracle address." | Oracle's answer was not in the form SourceLace expects, or it pointed outside your Fusion host. | Try again. If it repeats, contact support. |
When something goes wrong with Workday
| What you see | What it means | What to do |
|---|---|---|
| "Enter the Authorization host of ...: the host of the Authorization Endpoint in Workday's View API Clients ..." | auth_host is empty and host is an API-only host. |
Copy the Authorization Endpoint (step 4). |
| "Workday sign-in failed (invalid_client): ..." | The client ID or secret is wrong. Workday shows the secret only once. | Generate a new secret in View API Clients and enter it again. |
| "Workday sign-in failed (invalid_grant): ..." | The sign-in code was refused, usually because the Redirection URI is not exactly SourceLace's. | Fix the Redirection URI (step 2), then connect again. |
| "Workday sign-in failed: ..." (another reason) | Workday's own reason follows. | Check steps 2 to 4. |
| "Workday did not say which worker signed in." | Workday's answer did not name the worker. | Contact support. |
| "Workday did not let you use WQL. Your Workday admin adds the System functional area ..." | The API client lacks the System functional area, or the person may not use WQL. | Add System to the client (step 2), and check the person's security groups. |
| "Workday: that does not exist, or your security groups do not let you see it." | The name or id is wrong, the security groups do not allow it, or the client lacks that functional area. | Check the name, the person's security groups, and the client's functional areas. |
| "Workday has no WQL data source '...' that you can use." | The data source name is wrong, or the person may not use it. | Check the name with search_schema. |
| "Workday: ..." (another message) | Workday's own words, such as a WQL syntax error. | The AI usually fixes the query itself. |
| "This worker changed in Workday after the preview. Propose the change again." | Someone changed it after the preview. | Ask for a new preview. |
| "SourceLace cannot change '...' in Workday. The changes it can propose are: ..." | Only businessTitleChange is offered. |
Propose that change, or make others in Workday. |
| "Workday changes go through business processes, so SourceLace can only start a business title change for one worker: ..." | The change was not an update of businessTitleChange. |
Propose an update of businessTitleChange with the worker's Workday ID. |
| "Your Workday sign-in has expired." | The sign-in ended after the client's refresh token timeout. | Connect again. |
| "Workday sent back data in an unexpected shape.", "SourceLace refused to send an unexpected Workday request." or "SourceLace refused to call an unexpected Workday address." | Workday's answer was not in the form SourceLace expects, or it pointed outside your Workday host. | Try again. If it repeats, contact support. |