Connect Oracle WMS: check inventory only — no order push

Fill in the IDCS Client ID, Client Secret, Token URL and your tenant instance address in the WMS connection, test the OAuth token exchange, and activate for inventory checks. Orders are not pushed to Oracle WMS by this connection.

The Oracle WMS connector connects this system to an Oracle WMS Cloud tenant for one job: checking inventory. It reads inventory quantities from the tenant instance for a SKU. It does not push orders to Oracle WMS — order push is not part of this connection, so orders must keep flowing through your existing route into Oracle WMS. This connection is configured in the WMS area, not through the channel wizard, and it signs in with an IDCS OAuth exchange using a Client ID, a Client Secret and a Token URL, plus the tenant instance address for the inventory calls.

Prerequisites#

• An Oracle WMS Cloud tenant instance, and its instance address. The address is set per tenant — there is no single default address that fits every tenant.
• An IDCS confidential application created for your WMS instance, with its Client ID and Client Secret ready to copy.
• The OAuth token endpoint of your IDCS domain, to use as the Token URL. It must be the endpoint of the same IDCS domain as the application above.
• Agreement inside your team that this connection is for inventory checks only. Orders still need their existing route into Oracle WMS.

Get your credentials#

1. From the Oracle WMS instance configuration, take the IDCS confidential application that was created for this WMS instance. Copy its Client ID.
2. Copy the Client Secret of that same application. The Client ID and the Client Secret must come from the same application — a secret from another application will not exchange for a token here.
3. Note the Token URL: the OAuth token endpoint of your IDCS domain.
4. Note the tenant instance address of your Oracle WMS instance as the baseUrl. Copy it from your own tenant information — do not borrow an address from another tenant or from an example.

Fill it into Integration#

This connection has no channel wizard field list. Open the WMS connection for Oracle WMS in Integration and fill in the values below on that WMS connection form. Do not look for Oracle WMS in the channel wizard field steps — the wizard has no fields for it.

1. Client ID — required: the Client ID of the IDCS confidential application created for your WMS instance.
2. Client Secret — required: the secret of that same IDCS application. It is a secret field and is used with the Client ID when the system exchanges for a token.
3. Token URL — required: the OAuth token endpoint of your IDCS domain. The token exchange is sent to exactly this address, so copy it in full.
4. Tenant instance address (baseUrl) — required for inventory calls: the address of your own Oracle WMS tenant instance. The connection test does not use this address, but every inventory check does, so fill it in now and fill it in exactly.

Test the connection#

Use the test on the WMS connection. It sends a client credentials exchange to the Token URL you filled in, authenticated with your Client ID and Client Secret, and it passes only when an access token comes back. If Client ID, Client Secret or Token URL is missing, the test stops with MISSING_CREDENTIALS. If the exchange returns no access token, it fails with AUTH_FAILED. Note what the test does not do: it does not call the tenant instance address, so a wrong baseUrl can still pass the test and only shows up later, at the first inventory check. There are two test entries you may come across: this WMS connection test is the real credential check described here, while a test shown in the channel wizard does not contact IDCS with these values — do not treat a pass there as proof that the IDCS values work. Judge the connection only by the WMS connection test, and then by one real inventory check.

Mapping / pick a template#

Pick the Oracle WMS inventory template. It covers inventory only: a SKU in this system is matched to the inventory record for that SKU on the tenant instance, and the quantity returned is the quantity the tenant reports. There is no order template to pick for this connection, because orders are not pushed. The inventory call uses the tenant entity interface, so confirm the SKU form your tenant uses — exact code, case and any prefix — on one known product first. After the test passes, run one inventory check for a SKU with known stock and compare the number with what the tenant shows, before activating.

Activate#

After activation, inventory checks from this system read the current quantities from your Oracle WMS tenant for the mapped SKUs. Watch the first checks in Runs / Logs and compare them with the tenant before leaving the connection unattended.

What this connection does not do: it does not push orders to Oracle WMS, and it does not bring shipment confirmations back from Oracle WMS. Keep sending orders through your existing route into Oracle WMS, and keep handling shipment confirmation in the system where it happens today.

FAQ#

An order push attempt fails with WMS_ENDPOINTS_PENDING

This connection does not push orders to Oracle WMS. Order entry into Oracle WMS depends on the tenant setup, and this connection only reads inventory, so the push stops with WMS_ENDPOINTS_PENDING instead of sending a request. It is not a credential problem and retrying will not change it.

Stop pushing orders through this connection. Send the order through your existing route into Oracle WMS, and use this connection for inventory checks only.

Test passes, but the inventory check fails with MISSING_BASE_URL

The test only exchanges for a token at the Token URL — it never calls the tenant instance address. The inventory check is the first step that needs baseUrl, so a missing or empty tenant address only appears there, as MISSING_BASE_URL.

Fill in the tenant instance address on the WMS connection with the exact address of your own Oracle WMS tenant, save, and run the inventory check again. The test result does not need to change — it was never checking this address.

WMS test fails with AUTH_FAILED

The exchange at the Token URL returned no access token. The Client ID and Client Secret pair was not accepted at that endpoint: the secret does not belong to the application of that Client ID, or the Token URL is the endpoint of a different IDCS domain.

Go back to the IDCS application created for your WMS instance and copy Client ID and Client Secret again from that same application, then confirm the Token URL is the OAuth token endpoint of the same IDCS domain, and test again.

Test stops with MISSING_CREDENTIALS

One of the three IDCS values is empty on the WMS connection: Client ID, Client Secret or Token URL. The exchange needs all three, so the test stops before contacting IDCS.

Fill in all three fields on the WMS connection form from the IDCS application and domain, save, and test again. Do not fill the tenant instance address into the Token URL field — they are different addresses with different jobs.

The channel wizard test passed, but the WMS test still fails

The two tests are not the same check. The channel wizard has no Oracle WMS fields and its test does not exchange a token with IDCS using your Client ID, Client Secret and Token URL, so a pass there says nothing about the IDCS values. Only the WMS connection test performs the real exchange.

Ignore the wizard result for this connection. Run the test on the WMS connection and work from its result, then run one real inventory check to prove the tenant address as well.

Inventory check returns nothing for a SKU that has stock in the tenant

The inventory check asks the tenant instance for the inventory record of the SKU sent. If the SKU form sent — exact code, case or prefix — does not match the form the tenant holds, or the tenant address points to a different tenant, the answer comes back empty even though stock exists.

First confirm the tenant instance address is your own tenant. Then take the exact SKU from the product record in the tenant, set that form in the mapping, and run the inventory check again.