Oracle Procurement

Oracle procurement PunchOut, from the supplier’s side

Oracle is the platform where suppliers most often build the wrong thing — because "Oracle" means two quite different systems, and the punchout requirements are not the same.

How Oracle Procurement PunchOut works

  1. Establish which Oracle your buyer runs. Fusion Procurement Cloud (Self Service Procurement) is the current cloud product. E-Business Suite iProcurement is the older on-premise line, still very much in use.
  2. Both support punchout, and both commonly use cXML for the handshake, but the buyer-side configuration, the fields they populate, and the way the returned cart is validated differ between them.
  3. The buyer selects your catalogue from their Oracle shopping interface, and Oracle sends a setup request to your endpoint.
  4. You authenticate and return a session URL; the buyer shops and checks out.
  5. Your site returns the cart to Oracle, where it becomes a requisition line subject to the buyer’s approval hierarchy.

What Oracle Procurement requires from you

Confirmation of which Oracle productAsk directly, in writing, whether the buyer is on Fusion Procurement Cloud or EBS iProcurement, and get the answer from someone technical rather than from the procurement contact.
Endpoint and credential configurationOracle-side setup happens in the buyer’s catalogue administration screens. You supply the endpoint and credentials; someone with the right access on their side configures it.
Category and UOM alignmentReturned lines must carry categories and units Oracle recognises, mapped to the buyer’s own category structure.
A named technical contact on the buyer sideOracle configuration is rarely self-service for the buyer. Without someone who has access to the right screens, testing stalls regardless of what you have built.

Where suppliers lose time on Oracle Procurement

The two Oracles get conflated constantlyA buyer saying "we use Oracle" tells you almost nothing. Building against the wrong assumption is the single most expensive mistake on this platform, and it is usually discovered during testing.
Older EBS instances are heavily customisedLong-lived on-premise deployments accumulate local modifications. What the documentation says and what a given instance does can differ, and the buyer’s own team may be the only source of truth.
Approval hierarchies delay the feedback loopA returned cart becomes a requisition that may pass through several approvers before anyone can confirm the integration worked end to end. Test cycles are slower as a result.
Oracle also runs its own supplier networkOracle Supplier Network is a distinct thing from punchout. Being registered there does not mean a punchout catalogue exists.

Timeline and price

Two to four weeks of supplier-side work once the product question is settled. Oracle engagements tend to have the widest spread of any of the four, driven almost entirely by how quickly the buyer’s technical contact can act.

A Oracle Procurement PunchOut catalogue is our Connect tier at $199/month for year one, stepping down to $129 from year two. If the buyer also wants purchase orders and invoices exchanged electronically, that is Order Loop at $349. You do not start paying until the connection is live in production.

The buyer's test queue, not the integration work, is what usually sets the date — see what actually controls the clock.

Oracle Procurement questions

How do we tell which Oracle system our buyer uses?

Ask for a screenshot of their shopping page, or ask the technical contact directly whether it is Fusion Procurement Cloud or E-Business Suite iProcurement. The URLs differ noticeably, and so does the interface. Do not infer it from the procurement contact’s description.

Does Oracle use cXML or OCI?

Oracle punchout is commonly implemented over cXML. OCI is SAP’s protocol and appears in SAP SRM environments rather than Oracle ones. The protocol should still be confirmed with the buyer rather than assumed.

We already punch out to a Coupa buyer. Does that help?

Considerably. The catalogue, the buyer-specific pricing logic and the session handling carry over — what changes is the platform-specific configuration and testing. That is why an additional buyer connection is a one-off fee rather than a fresh build.

Further reading

Working out what your Oracle Procurement buyer needs?

Send us the requirement they gave you. We will tell you what it means in Oracle Procurement terms, which tier covers it, and roughly how long it takes.

Start a conversation See pricing