Connect Oracle Fusion ERP: pull orders and invoices in

Fill in your Oracle Fusion instance URL in Integration and sign in with either a Fusion REST username and password or a pre-obtained OAuth bearer token, test, map, activate — sales orders and invoices come in.

The Oracle Fusion ERP connector pulls sales orders and invoices from your Oracle Fusion Cloud ERP into this system. That is the full scope of this connection: it does not pull customers, it does not check or pull inventory, and it does not push anything back to Oracle Fusion. Sign-in works one of two ways — a Fusion REST username and password, or an OAuth bearer token you obtain beforehand and paste in — and if a token is filled in, the token is used first. One connection per Oracle Fusion instance.

Prerequisites#

• An Oracle Fusion Cloud instance you can sign in to, and its instance URL, for example https://fa-xxx.oraclecloud.com.
• One complete sign-in set, chosen in advance: either a Fusion user with the integration roles, together with its password — or an OAuth2 access token obtained beforehand in your OCI / IDCS identity domain. Half a set does not connect.
• If you plan to use a token: a way to obtain a fresh token in your OCI / IDCS identity domain whenever the pasted one stops working, because this connection uses the token exactly as pasted and does not fetch a new one for you.

Get your credentials#

1. Note your instance URL, for example https://fa-xxx.oraclecloud.com. This is the only value every connection needs, whichever sign-in set you choose.
2. Option A — Basic sign-in: prepare a Fusion user with the integration roles, for example REST_USER, and keep its password ready. Username and password must be filled in together; one without the other does not count as a set.
3. Option B — Token sign-in: in your OCI / IDCS identity domain, obtain an OAuth2 access token beforehand and copy it. You paste the finished token in here — there is no sign-in jump and no token exchange inside this connection.
4. Pick one option as your working set. If you later fill in a token on a connection that was using username and password, the token takes over from then on.

Fill it into Integration#

1. Open Integration → Connector Marketplace → Oracle Fusion ERP → New connection.
2. base_url — required, Instance URL: your Oracle Fusion instance address, for example https://fa-xxx.oraclecloud.com.
3. api_version — optional, API version: leave it empty to use the built-in default 11.13.18.05. Fill it in only when your environment runs a different version.
4. username — for Basic sign-in, Username (Basic auth): the Fusion REST user with the integration roles, for example REST_USER. Fill it together with password, or leave both empty and use token instead.
5. password — for Basic sign-in, Password (Basic auth): the password of that same Fusion user. It is a password-type field and is stored as a secret.
6. token — optional alternative, OAuth bearer token: paste the OAuth2 access token you obtained beforehand in your OCI / IDCS identity domain. It is a password-type field and is stored as a secret. If token is filled in, it is used before username and password.

Test the connection#

Click Test connection. The test first checks the fill-in: if base_url is missing, or if neither sign-in set is complete — no username with its password, and no token — it stops with a missing-value message and sends nothing. It then makes one real, light, read-only request with the set you chose — the token as Bearer sign-in if a token is filled in, otherwise the username and password as Basic sign-in — asking the invoices resource for a single record. A 200 answer counts as a pass. A 401 or 403 answer means the sign-in set that was used was refused: check that set, not the other one. The test gives up after about 12 seconds if the instance does not answer.

Mapping / pick a template#

Pick the Oracle Fusion standard mapping. It covers the two kinds of data this connection pulls: sales orders from the salesOrdersForOrderHub resource, and invoices from the invoices resource. After the test passes, run one pull and check a real order and a real invoice side by side — numbers, customer reference, lines and amounts — before activating. There is no customer or inventory mapping in this connection, because this connection does not pull customers or inventory.

Activate#

After activation, the connection pulls sales orders and invoices from Oracle Fusion into this system on the schedule you set. Watch the first pulls in Runs / Logs and compare them with Oracle Fusion before leaving the connection unattended. If you sign in with a token, keep an eye on it: when the pasted token stops working, pulls will start failing until you paste a fresh one.

What this connection does not do: it does not pull customers from Oracle Fusion, it does not check or pull inventory, and it does not push inventory or anything else back to Oracle Fusion. Keep handling customers and inventory in Oracle Fusion itself, or through the other systems where that work actually happens.

FAQ#

Test fails with 401 or 403

Oracle Fusion refused the sign-in set that the test actually used. If a token is filled in, the token was used — so the token is what was refused, even if username and password are also filled in. With no token filled in, the username and password were refused, or that Fusion user does not carry the integration roles the REST resources need.

Work on the set that was used. Token in use: obtain a fresh OAuth2 access token in your OCI / IDCS identity domain and paste it in full into token. Basic in use: re-check username and password together, and confirm in Fusion that the user carries the integration roles. Then test again.

Test stops with a missing-value message before sending anything

The fill-in is incomplete: either base_url is empty, or neither sign-in set is complete. A username without its password is not a set, and a password without its username is not a set either — and with no token filled in, the test has no way to sign in at all.

Fill in base_url with the full instance URL, then complete exactly one set: username and password together, or a token pasted in full. Save, then test again.

It connected before, then pulls started failing on their own

If this connection signs in with a token, the pasted token has stopped working. This connection uses the token exactly as pasted and does not fetch a new one, so a token that worked at test time can stop working later while every other value stays correct.

Obtain a fresh OAuth2 access token in your OCI / IDCS identity domain, paste it in full into the token field, save and test. If failures continue with a fresh token, re-check the Basic set instead — or clear the token field to go back to username and password on purpose.

I filled in username and password, but sign-in behaves as if I had not

A token is also filled in on this connection, and a filled-in token is used before username and password. The Basic values are not broken — they are simply not the set being used while any token value is present.

Decide which set you want. To use the token, keep it fresh and ignore the Basic fields. To use username and password, clear the token field completely, save, then test again.

Connected, but customers or inventory never appear

That is the scope of this connection, not a failure: it pulls only sales orders and invoices. Customers and inventory are not pulled by this connection, so no mapping, schedule or credential change will make them appear here.

Keep handling customers and inventory in Oracle Fusion itself, or in the system where that data actually lives. Use this connection for orders and invoices, and check those two in Runs / Logs when you verify it.

Connected, but no orders or invoices are pulled in

The connection is working — the test read the invoices resource for real — but there is nothing new to pull: the instance has no new sales orders or invoices in the pull range. A wrong api_version value can cause the same empty result if your environment does not run that version.

Create or confirm one sales order and one invoice in Oracle Fusion, leave api_version empty unless you know your environment runs a different version than the built-in default, then run a manual pull and confirm both appear in the preview or in Runs / Logs.