Ellipse Gradient for Header

Oracle Procurement Integration Guide

Connect Oracle Procurement with enterprise applications through REST APIs, selected SOAP services, import files, and supported business-event notifications.

Oracle Procurement integration options at a glance

Oracle Procurement provides REST APIs for selected requisitions, purchase orders, suppliers, supplier sites, agreements, and receipts. Selected enterprise operations are also available through Oracle Fusion SOAP services. For event-driven designs, Oracle supports selected business events and notification patterns, although coverage and payloads vary by release and configuration. File-Based Data Import supports high-volume and batch-oriented loading for applicable objects. Martini can authenticate with OAuth 2.0 or permitted Basic Authentication configurations, orchestrate API and SOAP calls, generate import files, process notifications, paginate through collections, map data, and monitor asynchronous import jobs.

Integration pointSupported by Oracle Procurement?Common use casesHow Martini supports it
REST APIsYesQuery and manage selected Requisitions, Purchase Orders, Suppliers, Supplier Sites, Purchase Agreements, and Receipts, including child resources and supported actions. Availability is object- and release-specific.Martini can consume Oracle Procurement REST APIs, manage authentication, follow pagination, map responses, apply business rules, and persist checkpoints or correlation identifiers.
SOAP APIsYesInvoke selected Oracle Fusion enterprise operations when a required capability is exposed through a WSDL, an existing integration uses SOAP, or a service supports import, export, or scheduled processing.Martini can consume SOAP services, configure the applicable service endpoint and credentials, transform XML messages, and route SOAP faults through workflow error handling.
Webhooks / outbound callbacksLimitedUse selected Oracle business events and notification patterns for event-driven processing. Coverage, delivery mechanism, and payload completeness depend on the Oracle release and environment configuration.Martini can receive supported notifications or callbacks, treat compact event payloads as triggers, retrieve the authoritative Oracle resource, and process the result asynchronously.
Bulk / async / batch APIsYesUse File-Based Data Import and selected Oracle enterprise import processes for high-volume requisition, purchase-order, supplier, or other supported data loads.Martini can generate files, transfer them through the configured location, submit or invoke the available import process, monitor job status, and reconcile rejected rows.
File / attachment APIsLimitedUse file-oriented imports and object-specific attachment resources for migrations, scheduled loads, bulk corrections, or document synchronization. Supported templates, content types, and attachment behavior vary.Martini can create CSV or required import files and process supported attachment resources, while preserving metadata and applying content, size, and security checks.
Database / analytics accessLimitedUse Oracle reporting, extract, or analytics capabilities such as Oracle Transactional Business Intelligence when analytical extraction is required. Direct access to the Fusion SaaS database should not be assumed.Martini can consume supported reporting, extract, REST, or SOAP interfaces and route analytical data into target systems without relying on direct SaaS database connectivity.
AuthenticationYesAuthenticate with OAuth 2.0 where configured, or with permitted Basic Authentication configurations, using Oracle Cloud roles, privileges, scopes, and data-access assignments.Martini can store credentials and secrets securely, configure API authentication, and use a dedicated, least-privileged Oracle integration identity.

How Oracle Procurement exposes data and business events

Oracle Procurement REST APIs

Oracle provides REST resources for selected Procurement objects and operations, including Requisitions, Purchase Orders, Suppliers, Supplier Sites, Purchase Agreements, and Receipts. Resources, child collections, actions, fields, and versions vary by Oracle Fusion release and enabled offering.

Martini implementation pattern

Martini implementation pattern: Martini authenticates to the applicable Oracle REST endpoint, retrieves or submits resources, follows documented pagination, maps payloads to a canonical model, applies validation and business rules, and stores checkpoints or correlation identifiers for reliable synchronization.

Implementation sequence

Authenticate with the configured Oracle service identity
Retrieve the selected Procurement resource or receive workflow input
Follow pagination and retrieve required child collections
Validate release-specific fields and business rules
Map the Oracle payload to the target model
Write the result and store the synchronization checkpoint

Oracle Procurement SOAP services

Oracle Fusion Cloud Applications expose SOAP services for selected enterprise operations. SOAP is relevant when a required operation is not available through REST, an existing integration uses a WSDL, or an enterprise service supports import, export, or scheduled processing.

Martini implementation pattern

Martini implementation pattern: Martini consumes the applicable WSDL-based service, constructs the required XML request, transforms SOAP responses or faults, and coordinates subsequent REST, file, or target-system operations.

Implementation sequence

Configure the applicable Oracle SOAP service and authentication
Build the XML request from the canonical integration model
Invoke the selected SOAP operation
Parse the response or classify the SOAP fault
Apply business rules and map the result
Persist the outcome and route retryable failures

Oracle business events and notifications

Oracle supports selected business events and notification patterns, but event availability, delivery infrastructure, and payload completeness depend on the Procurement release and environment configuration. These mechanisms should not be treated as unrestricted webhooks for every object.

Martini implementation pattern

Martini implementation pattern: Martini receives a supported notification, validates its event type and identifier, retrieves the authoritative Procurement resource when the notification is compact, and processes the resulting object asynchronously.

Implementation sequence

Receive the supported Oracle event or notification
Validate the event type and resource identifier
Retrieve the authoritative Procurement object when required
Apply deduplication and business rules
Map and deliver the event to downstream systems
Record processing status and retry transient failures

Oracle File-Based Data Import

Oracle File-Based Data Import supports selected high-volume and batch-oriented data-loading scenarios. Templates, staging processes, import jobs, and supported objects vary by Procurement functional area.

Martini implementation pattern

Martini implementation pattern: Martini collects source data, validates and maps it to the Oracle import template, generates the required file, transfers it through the configured location, submits or monitors the Oracle import process, and reconciles rejected rows.

Implementation sequence

Collect and validate source procurement data
Map source fields to the Oracle import template
Generate the required import file
Transfer the file to the configured Oracle location
Submit or monitor the applicable import job
Reconcile completion status and rejected rows

Oracle attachments and documents

Oracle Fusion objects may expose attachment resources or document fields through REST or SOAP, but attachment support is object-specific. Content types, size limits, binary transfer behavior, and access controls must be confirmed for each resource.

Martini implementation pattern

Martini implementation pattern: Martini retrieves or receives supported document metadata and content, validates file properties, transfers the document to the target, and preserves the relationship to the Oracle object without exposing sensitive content in logs.

Implementation sequence

Confirm attachment support for the target Oracle object
Retrieve document metadata and supported content
Validate content type, size, and access rules
Transfer the document or metadata to the target system
Associate the document with the target business object
Record the correlation result without logging sensitive content

Common Oracle Procurement integration patterns

Pattern 1: Synchronize approved requisitions

When to use this pattern

Use this pattern when ServiceNow, Workday, or another enterprise application initiates purchasing demand and Oracle Procurement owns the formal Requisition. It supports scheduled retrieval or a supported event-driven trigger and prevents rejected, withdrawn, or duplicate requests from being propagated.

Integration direction
ServiceNow
Martini
Oracle Procurement
Example Mapping
Oracle Procurement FieldCanonical FieldTarget Field
requesterrequester.employeeIdRequisition requester
businessUnitprocurement.businessUnitCodeRequisition business unit
lines[].quantitylines[].quantityRequisition line quantity
approvalStatuslifecycle.approvalStatusRequisition approval status
Martini implementation pattern

Martini receives or retrieves approved requests, validates requester and business-unit references, maps lines, distributions, prices, currency, and delivery data, and creates or updates Oracle Requisitions through REST or an applicable import process. It uses source and Oracle identifiers for idempotency, routes validation failures to exceptions, and retries transient transport or throttling errors.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • validation
  • error handling
  • scheduled synchronization

Pattern 2: Distribute purchase orders to downstream systems

When to use this pattern

Use this pattern when Oracle Procurement is the purchasing system of record and suppliers, EDI gateways, SAP S/4HANA, NetSuite, or other applications require Purchase Orders and change-order updates.

Integration direction
Oracle Procurement
Martini
SAP S/4HANA
Example Mapping
Oracle Procurement FieldCanonical FieldTarget Field
PurchaseOrderNumberpurchaseOrder.numberPurchasingDocument.externalId
Supplier.SupplierNumbersupplier.numberVendor.externalId
Lines[].OrderedQuantitylines[].quantityItem.quantity
Schedules[].NeedByDatelines[].requestedDeliveryDateSchedule.deliveryDate
Martini implementation pattern

Martini retrieves newly created or changed Purchase Orders, expands required supplier, line, schedule, and distribution data, and transforms them into the downstream purchasing model. It checks purchase-order revision and cancellation state, preserves correlation identifiers, handles partial target failures independently, and retries only transient errors.

Martini capabilities used
  • API consumption
  • workflow orchestration
  • data mapping
  • conditional routing
  • idempotency
  • retry handling

Pattern 3: Synchronize supplier and supplier-site masters

When to use this pattern

Use this pattern when Oracle Procurement owns supplier data and Salesforce, SAP S/4HANA, NetSuite, Coupa, or a data platform needs approved Suppliers and Supplier Sites. It is suitable for scheduled incremental synchronization with controlled deactivation handling.

Integration direction
Oracle Procurement
Martini
Salesforce
Example Mapping
Oracle Procurement FieldCanonical FieldTarget Field
SupplierNumbersupplier.externalIdAccount.oracleSupplierNumber
SupplierNamesupplier.nameAccount.name
SupplierSiteCodesupplierSite.externalIdAccountSite.externalId
Statussupplier.lifecycleStatusAccount.status
Martini implementation pattern

Martini retrieves eligible Suppliers and Supplier Sites, filters by status and ownership rules, maps addresses and purchasing attributes, and upserts downstream records. It maintains supplier-to-target key mappings, distinguishes inactive sites from deleted data, and uses overlap windows or reconciliation runs to catch missed changes.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • business rules
  • checkpoint persistence
  • reconciliation

Pattern 4: Reconcile receipts against purchase orders

When to use this pattern

Use this pattern when warehouse, supplier, SAP S/4HANA, NetSuite, or accounts-payable processes need reliable receiving status. It identifies partial, over, short, or unmatched Receipts and creates exception work for manual resolution.

Integration direction
Oracle Procurement
Martini
NetSuite
Example Mapping
Oracle Procurement FieldCanonical FieldTarget Field
ReceiptNumberreceipt.externalIdItemReceipt.externalId
PurchaseOrderNumberpurchaseOrder.numberItemReceipt.purchaseOrderNumber
ReceiptLines[].ReceivedQuantitylines[].receivedQuantityItemReceipt.lines[].quantity
ReceiptLines[].ReceiptStatuslines[].statusItemReceipt.lines[].status
Martini implementation pattern

Martini retrieves incremental Receipts and related Purchase Order schedules, matches stable Oracle identifiers and line keys, calculates quantity variances, and sends valid results to the target system. It routes unmatched or over-received lines to an exception path, records reconciliation evidence, and retries transient API failures without duplicating receipt postings.

Martini capabilities used
  • scheduled synchronization
  • API consumption
  • data mapping
  • business rules
  • exception routing
  • idempotency
  • monitoring

Applications commonly integrated with Oracle Procurement

Oracle Procurement can be integrated with adjacent enterprise applications when organizations need to coordinate purchasing, supplier, workforce, service, finance, document, or exception-management processes. Martini can orchestrate these exchanges through Oracle APIs, selected SOAP services, files, events, and APIs exposed to participating systems.

Application Scenario Direction Martini Pattern
SAP S/4HANA Synchronize suppliers, purchasing documents, receipts, and related financial or material data across Oracle and SAP landscapes. Oracle Procurement → Martini → SAP S/4HANA Use scheduled or event-triggered Oracle retrieval, map Procurement objects to the SAP model, apply ownership and duplicate rules, and route failed transactions for retry or reconciliation.
Workday Provide worker, requester, cost-center, and organizational information for requisition and approval processes. Workday → Martini → Oracle Procurement Consume Workday data through its available enterprise interfaces, validate organizational references, transform them into Oracle-compatible values, and synchronize selected Procurement statuses back when required.
Salesforce Expose procurement status, supplier information, or purchase-order data to customer-facing and operational teams. Oracle Procurement → Martini → Salesforce Retrieve eligible Oracle Suppliers or Purchase Orders, normalize identifiers and statuses, upsert Salesforce objects through its APIs, and retain correlation identifiers for reconciliation.
ServiceNow Connect employee requests, procurement approvals, fulfillment activities, and exception workflows. ServiceNow → Martini → Oracle Procurement Receive ServiceNow requests or invoke its APIs, validate procurement attributes, create or update Oracle Requisitions, and return Oracle identifiers and status through a controlled workflow.
NetSuite Exchange suppliers, purchase orders, receipts, and purchasing or accounting data between Oracle Procurement and NetSuite. Oracle Procurement → Martini → NetSuite Use incremental Oracle REST retrieval and NetSuite API operations, map supplier and document keys, apply status and ownership rules, and handle partial failures independently.
Coupa Exchange supplier, requisition, purchase-order, invoice, or procurement reference data where Coupa and Oracle coexist. Coupa → Martini → Oracle Procurement Coordinate API or file exchanges between the platforms, transform procurement identifiers and statuses, validate required business-unit data, and reconcile asynchronous imports.
Jira Create work items for procurement exceptions, supplier onboarding tasks, or failed integration messages. Oracle Procurement → Martini → Jira Classify Oracle validation, import, or reconciliation failures, create Jira issues with safe diagnostic context, and update issue status when the workflow resolves the exception.
DocuSign Route procurement agreements or supplier documents for electronic signature and return completion status. Oracle Procurement → Martini → DocuSign Retrieve supported agreement or attachment content, submit a signature envelope through the DocuSign API, store envelope correlation data, and update Oracle or a downstream system with completion status.

How to build a Oracle Procurement integration in Martini

Objective

Establish the Oracle Procurement connection using the customer’s permitted authentication method and a dedicated least-privileged integration identity.

Instructions in Martini

  • Confirm the Oracle Fusion release, enabled Procurement offerings, endpoint coverage, and required roles.
  • Configure OAuth 2.0 where enabled, or the permitted Basic Authentication arrangement.
  • Store client credentials, passwords, tokens, and endpoint settings in secure environment configuration.
  • Validate access to the specific Procurement objects and business units required by the workflow.

Objective

Select an event, API, file, or schedule trigger based on Oracle’s coverage for the required object and transaction volume.

Instructions in Martini

  • Use a supported Oracle business event or notification when the event and delivery method are confirmed.
  • Use a scheduler for incremental REST retrieval when event coverage is unavailable or incomplete.
  • Use a file-based workflow for high-volume loads supported by FBDI or another Oracle import process.
  • Expose a Martini API when Oracle or an intermediary system needs to submit controlled integration requests.

Objective

Obtain the authoritative Oracle Procurement object and its required child collections, files, or status information.

Instructions in Martini

  • Call the relevant REST resource or SOAP service for the selected object.
  • Follow Oracle pagination links or documented limit and offset behavior.
  • Retrieve child resources such as lines, schedules, distributions, or attachments only when required.
  • Persist a checkpoint, page state, or source identifier for restartable processing.

Objective

Coordinate validation, enrichment, target calls, asynchronous import monitoring, and exception handling in a maintainable Martini workflow.

Instructions in Martini

  • Separate transport, transformation, business-rule, and target-write stages.
  • Use conditional routing for approved, rejected, cancelled, inactive, and exception states.
  • Queue or sequence large workloads to control concurrency and avoid throttling.
  • Track Oracle job identifiers and import status for asynchronous processes.

Objective

Convert Oracle Procurement payloads and files into a canonical model and the target application’s structure.

Instructions in Martini

  • Map actual Oracle objects such as Requisitions, Purchase Orders, Suppliers, Supplier Sites, and Receipts.
  • Normalize identifiers, statuses, dates, currencies, quantities, addresses, and child collections.
  • Generate Oracle import templates or target API payloads where required.
  • Use explicit, release-aware mappings rather than passing arbitrary fields through unchanged.

Objective

Enforce procurement ownership, approval, status, security, and duplicate-processing rules before writing data.

Instructions in Martini

  • Allow only eligible approval and lifecycle states to progress.
  • Use stable Oracle identifiers, revisions, source keys, or a Martini idempotency store.
  • Validate business units, supplier sites, requester references, and required line attributes.
  • Exclude sensitive pricing, banking, tax, or document content from ordinary logs.

Common Oracle Procurement data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
RequisitionsInternal requests for goods or services, including lines, distributions, delivery information, and approval data.ServiceNow, Workday, SAP S/4HANA, NetSuiteMartini retrieves or receives eligible Requisitions, validates approval and business-unit data, maps lines and distributions, and uses requisition identifiers for idempotency.
Purchase OrdersOrders issued to suppliers, including lines, schedules, distributions, pricing, fulfillment, and change-order information.SAP S/4HANA, NetSuite, Coupa, supplier portals, EDI gatewaysMartini retrieves new or changed Purchase Orders, transforms headers and lines into a canonical model, handles revisions, and routes delivery or acknowledgment failures for retry.
SuppliersSupplier master records used across purchasing and supplier-management processes.SAP S/4HANA, Salesforce, NetSuite, Coupa, data platformsMartini synchronizes approved or changed Suppliers, applies status and ownership rules, and correlates supplier numbers with downstream identifiers.
Supplier SitesSupplier locations and operating sites governing purchasing, invoicing, payment, and site-level controls.SAP S/4HANA, NetSuite, Coupa, finance applicationsMartini treats Supplier Sites as separately governed child data where required, validates site status and business-unit access, and preserves supplier-site composite keys.
Purchase AgreementsBlanket and contract purchase arrangements containing negotiated purchasing terms.DocuSign, SAP S/4HANA, Coupa, document repositoriesMartini retrieves supported agreement data and documents, maps terms and identifiers, and coordinates signature or downstream contract workflows where configured.
ReceiptsReceiving transactions that record goods or services received against Purchase Orders.SAP S/4HANA, NetSuite, warehouse systems, accounts-payable processesMartini matches Receipts to purchase-order lines and schedules, identifies partial or discrepant receipts, and produces reconciliation or exception records.

Authentication and security considerations

Authentication

Oracle Procurement API access depends on the Oracle Fusion security configuration, not only on successful authentication. OAuth 2.0 is supported where configured, and some environments permit Basic Authentication. API scopes, job roles, privileges, procurement agent assignments, business-unit access, and service permissions must all be aligned.

Secure integration identity

Use a dedicated Oracle integration user with narrowly scoped access. Martini can store OAuth client details, passwords, tokens, and endpoint configuration in secure environment settings rather than embedding secrets in workflows.

Data protection

Procurement integrations may process supplier, pricing, tax, banking, contract, and attachment information. Limit sensitive fields in logs, protect transferred files and documents, and apply appropriate encryption, access control, and segregation-of-duties practices.

Operational considerations for Oracle Procurement integrations

Release and schema management

Oracle Fusion releases can change available resources, fields, actions, and import behavior. Validate the customer’s release and enabled offerings, use explicit mappings, and regression-test integrations after quarterly updates.

Pagination and checkpoints

REST collection responses may be paginated. Martini workflows should follow documented pagination behavior, persist checkpoints, use stable identifiers, and apply overlap windows or reconciliation runs for long-running incremental synchronizations.

Throttling and retries

Control concurrency and use bounded exponential backoff for transient failures or throttling. Separate retryable transport conditions from authorization, validation, duplicate, and business-rule errors.

Idempotency and lifecycle states

Use requisition, purchase-order revision, supplier-site, and receipt identifiers rather than display names. Account for approvals, cancellations, change orders, inactive sites, partial receipts, and asynchronous import outcomes.

Testing and monitoring

Test representative child collections, attachments, import rejection cases, security boundaries, and release-specific behavior. Monitor workflow logs, Oracle job identifiers, rejected rows, and reconciliation results while excluding sensitive payload content.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate more than an API call

Oracle Procurement integrations commonly combine REST or SOAP calls, pagination, business rules, file imports, event notifications, target-system writes, and asynchronous job monitoring. Martini coordinates these steps in workflows instead of scattering logic across scripts.

Maintain explicit data contracts

Martini provides structured mapping, transformation, validation, and reusable integration assets for Procurement objects such as Requisitions, Purchase Orders, Suppliers, Supplier Sites, and Receipts.

Improve operational reliability

Centralized error routing, retries, checkpoints, idempotency, logging, and reconciliation make integrations easier to operate than isolated point-to-point code. Martini can also expose controlled APIs when Oracle or another application needs a stable façade.

Adapt to Oracle variation

Object availability and behavior vary by Oracle Fusion release and configuration. Martini allows endpoint, authentication, mapping, and workflow behavior to be configured for the customer’s environment without assuming direct database access or universal event coverage.

Frequently asked questions

How can Oracle Procurement be integrated with enterprise systems?

Oracle Procurement can be integrated through REST APIs for selected Procurement objects, selected Oracle Fusion SOAP services, File-Based Data Import and other batch processes, and supported business-event or notification patterns. The appropriate mechanism depends on the object, Oracle Fusion release, transaction volume, and event coverage.

Can Martini integrate with Oracle Procurement?

Yes. Martini can integrate with Oracle Procurement by consuming its REST APIs and selected SOAP services, generating and processing Oracle import files, receiving supported event or callback notifications, and orchestrating authentication, mapping, validation, synchronization, and error handling.

Do I need a connector to integrate Oracle Procurement with Martini?

No. A dedicated Oracle Procurement connector is not required. Martini can use Oracle’s confirmed native integration mechanisms, including REST APIs, selected SOAP services, import files, authentication methods, and supported event or notification endpoints.

Is there any extra Lonti cost to integrate Oracle Procurement with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle Procurement with Martini. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment model.

Which Oracle Procurement integration methods should be used for new integrations?

REST APIs are generally the primary choice for synchronous access to supported Procurement resources. Use SOAP when the required operation is service-specific or legacy, and use FBDI or another supported import process for high-volume or asynchronous loading. Confirm resource and release coverage before implementation.

Are Oracle Procurement events or webhooks available?

Oracle supports selected business events and notification patterns, but generic webhooks should not be assumed for every Procurement object. Martini can receive a supported notification and then retrieve the authoritative Oracle resource when the event contains only an identifier or compact payload.

How does synchronization and data mapping work with Oracle Procurement?

Martini can run scheduled or event-driven workflows that retrieve Oracle objects, follow pagination, map fields and child collections to a canonical model, apply status and ownership rules, and write to target applications. Checkpoints, stable Oracle identifiers, overlap windows, and reconciliation runs help manage incremental synchronization.

How are Oracle Procurement errors, retries, and duplicates handled?

Martini can distinguish authentication, authorization, validation, throttling, transport, duplicate, and asynchronous import errors. Workflows can retry transient failures with controlled backoff, route permanent failures to exceptions, monitor import job results, and use Oracle identifiers or correlation keys to prevent duplicate processing. Martini can also expose an API façade when a controlled intermediary endpoint is required.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Oracle Procurement with your enterprise systems

Use Martini to design maintainable Oracle Procurement integrations across APIs, SOAP services, import files, events, and downstream applications.

EXPLORE MARTINI
BOOK A DEMO