.png)
Oracle SCM Cloud Integration Guide
Oracle SCM Cloud integrates with enterprise systems through Fusion Cloud REST APIs, SOAP services, selected business events, and file-based import and export processes.
Oracle SCM Cloud integration options at a glance
Oracle SCM Cloud provides REST APIs across multiple supply chain functional areas, including Items, Work Orders, Purchase Orders, Inventory, Transfer Orders, and Order Management objects. SOAP services remain available for selected business operations and established WSDL-based integrations. Oracle also supports selected business events, asynchronous processing, batch operations, and file-based imports such as FBDI for high-volume workloads. Martini can consume these interfaces, schedule incremental synchronization, receive supported event notifications, orchestrate import files, transform payloads, apply validation and business rules, and expose APIs for downstream applications. OAuth 2.0, Basic Authentication, and applicable SOAP security methods can be configured through secure environment settings.
| Integration point | Supported by Oracle SCM Cloud? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Read, create, update, and perform supported actions on SCM resources such as Items, Work Orders, Purchase Orders, Inventory, Transfer Orders, and Order Management objects. Coverage and write operations vary by resource and release. | Martini can consume Oracle REST APIs, follow pagination, apply filters, transform payloads, and orchestrate resource calls in workflows. |
| SOAP APIs | Yes | Use selected Oracle SCM business services when an operation is not available through REST, an existing WSDL integration must be retained, or a SOAP business operation is required. | Martini can consume Oracle SOAP services from their WSDLs and apply configured authentication, XML mapping, validation, retries, and error handling. |
| Business events and callbacks | Limited | Selected Oracle Fusion business events can initiate event-driven processes, but coverage depends on the SCM product area and event delivery architecture. They are not universal webhooks for every object. | Martini can receive supported notifications through an exposed API endpoint and then retrieve the authoritative Oracle resource when the event contains only an identifier. |
| Bulk, async, and batch processing | Yes | Use applicable REST batch operations, asynchronous processes, scheduled jobs, and high-volume import mechanisms for workloads that are unsuitable for individual transactional calls. | Martini can submit batches or asynchronous requests, persist process identifiers, poll status endpoints, and route failures for retry or review. |
| File import and export | Yes | FBDI and related file processes support selected high-volume loads such as Items, inventory transactions, Purchase Orders, Order Management data, and manufacturing data. | Martini can generate, validate, stage, transfer, and monitor documented import files while handling import-job sequencing, validation reports, and partial failures. |
| Attachment APIs | Limited | Attachments are available for selected Fusion business objects, with object-specific support for metadata and binary content. | Martini can make separate attachment calls where documented, transform metadata, transfer binary content, and apply size, content-type, and retry controls. |
| Authentication | Yes | Oracle environments may use OAuth 2.0, Basic Authentication, identity-domain configuration, application roles, data security policies, and applicable SOAP WS-Security methods. | Martini stores credentials and tokens in secure environment configuration and uses resource-specific authentication and authorization settings in API workflows. |
| Database and analytics access | Limited | Direct access to the underlying Oracle SCM Cloud SaaS database is not the normal integration method. Oracle reporting, extracts, or analytics services may support selected access patterns. | Martini can integrate with documented Oracle services or separate databases, but workflows should not depend on direct SQL access to the SaaS application database. |
How Oracle SCM Cloud exposes data and business events
Oracle SCM Cloud REST APIs
Oracle documents REST resources across multiple Fusion Cloud SCM product areas. REST is generally appropriate for supported transactional operations, resource reads, updates, actions, filtered retrieval, and lower-volume synchronization, although resource coverage and write support vary.
Martini implementation pattern
Martini implementation pattern: Martini workflows authenticate to the Oracle REST API, retrieve or submit resources, follow pagination links, map JSON payloads, apply business rules, and persist checkpoints, correlation identifiers, and processing status.
Implementation sequence
Oracle SCM Cloud SOAP services
Oracle provides SOAP web services for selected SCM operations and established enterprise service designs. SOAP is useful when a required business operation is not available through REST or an existing WSDL-based process must be maintained.
Martini implementation pattern
Martini implementation pattern: Martini consumes the Oracle WSDL service, configures the applicable authentication, maps XML request and response structures, invokes the operation, and classifies SOAP faults for retry or business review.
Implementation sequence
Oracle SCM Cloud business events
Oracle Fusion Applications supports selected business events and event-driven integration patterns. Availability, payload content, and delivery depend on the SCM product area and configured Oracle event infrastructure; there is no universal direct webhook for every object.
Martini implementation pattern
Martini implementation pattern: Martini exposes an API endpoint or consumes the configured event delivery path, validates the notification, and retrieves the authoritative Item, Work Order, Purchase Order, or other resource from Oracle REST APIs when the event contains only an identifier.
Implementation sequence
Oracle SCM Cloud file imports
Oracle FBDI and related file processes support selected high-volume inbound and outbound business processes. Templates, staging mechanisms, import jobs, validation, and reporting differ by object and must be confirmed for each process.
Martini implementation pattern
Martini implementation pattern: Martini workflows assemble and validate the required file, stage it through the documented Oracle file process, initiate the import job, and poll the resulting process or validation status before marking the batch complete.
Implementation sequence
Oracle SCM Cloud asynchronous processing
Oracle SCM Cloud may accept requests that complete through background jobs or asynchronous processes. Acceptance of an HTTP request does not necessarily mean that the business object or import has completed successfully.
Martini implementation pattern
Martini implementation pattern: Martini records the Oracle process or request identifier, separates transport acceptance from business completion, polls the documented status resource, and routes timeout, validation, and terminal failure states independently.
Implementation sequence
Common Oracle SCM Cloud integration patterns
Pattern 1: Synchronize Items to downstream applications
When to use this pattern
Use this pattern when Oracle SCM Cloud is the product master or an authoritative source for item attributes, revisions, and relationships. It is suitable for scheduled incremental synchronization with commerce, CRM, ERP, or analytics applications.
Integration direction
Example Mapping
| Oracle SCM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| ItemNumber | product.externalId | ProductCode |
| Description | product.name | Name |
| PrimaryUOMCode | product.unitOfMeasure | UnitOfMeasure |
| ItemStatusValue | product.status | Status |
Martini implementation pattern
A scheduled Martini workflow queries Items using documented change filters and pagination, transforms Oracle attributes and flexfields into a canonical product model, validates required fields, and upserts the target record using a stable external identifier. The workflow stores a checkpoint, logs rejected items, retries transient failures, and periodically reconciles missed changes.
Martini capabilities used
- workflows
- scheduled triggers
- API consumption
- data mapping
- business rules
- error handling
Pattern 2: Process Purchase Orders and supplier updates
When to use this pattern
Use this pattern when procurement data must move between Oracle SCM Cloud and a supplier, procurement, finance, or ERP application. The design must account for approval state, revisions, schedules, supplier sites, and line-level fulfillment.
Integration direction
Example Mapping
| Oracle SCM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| SupplierNumber | supplier.externalId | SupplierNumber |
| PurchaseOrderNumber | purchaseOrder.externalId | OrderNumber |
| DocumentStatus | purchaseOrder.status | Status |
| OrderedQuantity | purchaseOrder.lines[].quantity | Lines[].Quantity |
Martini implementation pattern
Martini validates supplier, supplier-site, business-unit, currency, line, schedule, and distribution data before submitting supported Oracle REST or SOAP operations. It uses an external correlation ID and deterministic lookup before creation, tracks approval or asynchronous import status, and sends confirmed status changes to the source application.
Martini capabilities used
- API consumption
- SOAP integration
- data mapping
- validation
- business rules
- correlation and idempotency
- error handling
Pattern 3: Synchronize inventory and transfer orders
When to use this pattern
Use this pattern when warehouse, commerce, order, or analytics applications require current Oracle balances and internal material movement status. It is appropriate for scheduled synchronization supplemented by events where available.
Integration direction
Example Mapping
| Oracle SCM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| ItemNumber | inventory.itemId | InventoryItem.sku |
| OrganizationCode | inventory.organization | InventoryLevel.location |
| OnHandQuantity | inventory.availableQuantity | InventoryLevel.quantity |
| TransferOrderNumber | transfer.externalId | TransferReference |
Martini implementation pattern
Martini retrieves paginated Inventory On-Hand Quantities and Transfer Orders, normalizes organization, subinventory, locator, lot, serial, and unit-of-measure values, and publishes the target update. It distinguishes balances from transactions, controls concurrency, records checkpoints, and runs reconciliation when event delivery or incremental filters are incomplete.
Martini capabilities used
- scheduled workflows
- REST API consumption
- pagination
- data transformation
- business rules
- checkpointing
- reconciliation
Pattern 4: Orchestrate manufacturing Work Orders
When to use this pattern
Use this pattern when a manufacturing execution, quality, maintenance, or production application must receive Oracle Work Orders and return execution information or exceptions.
Integration direction
Example Mapping
| Oracle SCM Cloud Field | Canonical Field | Target Field |
|---|---|---|
| WorkOrderNumber | workOrder.externalId | IssueKey |
| WorkOrderStatus | workOrder.status | Status |
| ItemNumber | workOrder.itemId | Summary |
| CompletionDate | workOrder.completedAt | ResolutionDate |
Martini implementation pattern
A Martini workflow consumes a supported Oracle event or polls Work Orders by status or timestamp, retrieves related operations and components, and maps actionable exceptions into the target application. Updates are sent back only for supported Oracle operations, with status tracking, duplicate detection, retry classification, and escalation for business validation failures.
Martini capabilities used
- event-driven workflows
- REST API consumption
- data mapping
- conditional routing
- business rules
- retry handling
- monitoring
Applications commonly integrated with Oracle SCM Cloud
Oracle SCM Cloud can be integrated with named enterprise applications when organizations need to coordinate supply chain, procurement, order, manufacturing, service, or commerce processes. The appropriate direction depends on the system-of-record model and the Oracle resources exposed in the target environment.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize products, customer orders, fulfillment status, and customer-facing supply information. | Oracle SCM Cloud → Martini → Salesforce | A Martini workflow retrieves changed Items, Sales Orders, or fulfillment data through Oracle REST APIs, maps it to Salesforce payloads, and applies correlation, validation, retry, and reconciliation rules. Selected demand or order data can flow in the reverse direction. |
| NetSuite | Coordinate product, inventory, procurement, and order data across Oracle SCM Cloud and NetSuite environments. | Oracle SCM Cloud → Martini → NetSuite | Martini orchestrates bidirectional REST API workflows, using explicit ownership rules for Items, Purchase Orders, inventory quantities, and orders. Checkpoints, deterministic lookups, and error queues help prevent duplicate transactions. |
| ServiceNow | Send supply, procurement, fulfillment, or operational exceptions into service-management workflows. | Oracle SCM Cloud → Martini → ServiceNow | Martini polls or receives supported Oracle event notifications, enriches exceptions with object and status data, and calls ServiceNow APIs to create or update incidents, cases, or work items. Status updates can be returned to Oracle where the process supports them. |
| Workday | Exchange supplier, worker-related procurement, or financial-process information where responsibilities span Workday and Oracle SCM Cloud. | Workday → Martini → Oracle SCM Cloud | Martini validates Workday-originated master data, transforms it into Oracle supplier or procurement structures where supported, and separately publishes Oracle status data to Workday using controlled workflows and audit records. |
| SAP S/4HANA | Coordinate products, inventory, procurement, manufacturing, and order data in a multi-ERP landscape. | SAP S/4HANA → Martini → Oracle SCM Cloud | Martini exposes reusable APIs and workflows for bidirectional synchronization, translates identifiers and units of measure, and applies object ownership, sequencing, idempotency, and reconciliation rules across the two platforms. |
| Jira | Create and update engineering, product, or supply-chain issue records from Oracle exceptions and work-order events. | Oracle SCM Cloud → Martini → Jira | A Martini workflow retrieves Work Orders or exception details, maps relevant context into Jira API requests, and stores Oracle identifiers and issue keys for subsequent status synchronization. |
| Shopify | Publish product availability and receive commerce orders for fulfillment through Oracle SCM Cloud. | Shopify → Martini → Oracle SCM Cloud | Martini consumes Shopify events or APIs, validates order and item identifiers, transforms orders into Oracle Order Management structures, and periodically publishes Oracle inventory or fulfillment status back to Shopify. |
| Coupa | Coordinate procurement requests, Purchase Orders, suppliers, and approval or fulfillment information. | Coupa → Martini → Oracle SCM Cloud | Martini maps Coupa procurement messages to Oracle Purchase Orders or supplier structures where supported, tracks approval and import status, and sends Oracle fulfillment updates back through the relevant Coupa API. |
How to build a Oracle SCM Cloud integration in Martini
Objective
Establish authenticated access to the Oracle SCM Cloud environment using the identity configuration and resource roles required by the integration.
Instructions in Martini
- Configure the Oracle base URL, OAuth 2.0 or permitted Basic Authentication details, and applicable SOAP credentials as environment secrets.
- Confirm application roles, duty roles, business-unit access, inventory-organization access, and other data security policies.
- Test access with the exact integration user and target resources.
Objective
Select a scheduling, event, API, or file trigger based on the Oracle resource and the required latency and volume.
Instructions in Martini
- Use a scheduled workflow for resources without a suitable event.
- Use supported Oracle business events as notifications, then retrieve authoritative resource data when necessary.
- Use an API or file-triggered workflow for inbound requests and FBDI-oriented processes.
Objective
Read Oracle resources or receive inbound data while handling pagination, filters, asynchronous status, and checkpoint state.
Instructions in Martini
- Follow Oracle pagination links and avoid assuming a fixed page size.
- Apply documented timestamps, status filters, or extraction options for incremental processing.
- Persist process identifiers and checkpoints for long-running or asynchronous operations.
Objective
Coordinate Oracle calls, target-system calls, enrichment, conditional routing, and process state in a maintainable Martini workflow.
Instructions in Martini
- Separate transport acceptance from business completion.
- Use reusable workflow logic for common authentication, lookup, correlation, and status handling.
- Route validation failures, transient failures, and terminal business errors differently.
Objective
Convert Oracle REST, SOAP, event, or file structures into canonical and target-specific models.
Instructions in Martini
- Map Items, Work Orders, Purchase Orders, Inventory, Orders, and related child objects explicitly.
- Normalize identifiers, units of measure, dates, status values, flexfields, and attachment metadata.
- Validate required fields before writing to the target system.
Objective
Enforce ownership, idempotency, sequencing, approval, and data-security rules before creating or updating business objects.
Instructions in Martini
- Use stable external identifiers or deterministic lookups before creating transactions.
- Do not retry non-recoverable validation or authorization failures as if they were transport errors.
- Handle Oracle approvals, revisions, import completion, and fulfillment status explicitly.
Common Oracle SCM Cloud data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Items | Synchronize product master data, attributes, revisions, and relationships. | Salesforce, NetSuite, Shopify, SAP S/4HANA, data platforms | Martini retrieves changed Items with documented filters and pagination, maps attributes and flexfields explicitly, validates required values, and performs idempotent upserts. |
| Item Structures | Exchange bills of material and component relationships for manufacturing and product processes. | SAP S/4HANA, manufacturing execution applications, engineering systems | Martini expands or retrieves child structures where supported, normalizes component quantities and identifiers, and applies sequencing and reconciliation rules. |
| Work Orders | Coordinate manufacturing orders, operations, components, and execution status. | Manufacturing execution systems, Jira, ServiceNow, analytics platforms | Martini can poll or process supported events, map status and operation details, submit updates where supported, and track asynchronous completion and failures. |
| Purchase Orders | Synchronize procurement orders, lines, schedules, suppliers, and fulfillment status. | Coupa, NetSuite, SAP S/4HANA, supplier collaboration applications | Martini validates supplier, business unit, currency, line, schedule, and distribution data, uses external correlation identifiers, and handles Oracle approval or import status. |
| Sales Orders | Process customer orders and order lines through Oracle Order Management. | Salesforce, Shopify, NetSuite, SAP S/4HANA | Martini maps external order structures to Oracle-supported resources, validates item and customer references, and prevents duplicate submissions through deterministic lookups. |
| Inventory On-Hand Quantities | Share inventory balances by item, organization, subinventory, locator, lot, or serial context. | Shopify, Salesforce, warehouse applications, analytics platforms | Martini retrieves paginated balances, converts units where required, distinguishes balances from movements, and runs reconciliation workflows when events or timestamps are incomplete. |
Authentication and security considerations
Authentication and authorization
Oracle SCM Cloud commonly uses OAuth 2.0 for REST access, although Basic Authentication may be permitted in some environments. Applicable SOAP services may use WS-Security or username-token-style authentication depending on Oracle configuration.
Successful authentication does not guarantee access to a resource. Oracle job roles, duty roles, privileges, business-unit access, inventory-organization access, procurement assignments, and data security policies determine the data an integration user can read or change.
- Store OAuth client details, secrets, tokens, and SOAP credentials in Martini environment secrets.
- Use least-privilege Oracle roles and test with the exact integration identity.
- Separate development, test, and production endpoints and credentials.
- Protect business data, attachments, and event endpoints with appropriate API security controls.
Operational considerations for Oracle SCM Cloud integrations
Design for Oracle SCM Cloud operational behavior
- Follow Oracle pagination links and persist checkpoints for long-running synchronizations.
- Use controlled concurrency, server-provided retry guidance, and backoff for throttling or transient failures.
- Make writes idempotent with stable external identifiers, deterministic lookups, and stored Oracle IDs.
- Distinguish HTTP acceptance from asynchronous business completion, import validation, and terminal failure.
- Confirm resource-specific event coverage, attachment support, REST write operations, and API version before implementation.
- Isolate flexfields, release-sensitive fields, and object-specific mappings so schema changes can be tested safely.
- For FBDI, manage templates, encoding, staging, import sequencing, validation reports, partial failures, and reprocessing.
- Use periodic reconciliation rather than relying exclusively on events or timestamps.
Why use Martini instead of scripts or point-to-point integrations?
Integration orchestration instead of isolated scripts
Oracle SCM Cloud integrations often combine REST resources, SOAP operations, business events, asynchronous jobs, and file-based imports. Martini provides a maintainable workflow layer for coordinating those mechanisms with downstream applications and internal APIs.
- Centralize authentication, pagination, checkpoints, mappings, validation, and correlation logic.
- Reuse workflows and services across Items, Work Orders, Purchase Orders, Inventory, and Orders.
- Apply explicit business rules for ownership, approvals, revisions, idempotency, and reconciliation.
- Handle transient failures, Oracle validation responses, asynchronous status, and rejected file rows consistently.
- Expose controlled APIs for downstream systems without coupling them directly to Oracle resource details.
- Use workflow logs, monitoring, testing, and deployment practices to support operational ownership.
Frequently asked questions
Oracle SCM Cloud supports Fusion Cloud REST APIs, selected SOAP web services, business events, asynchronous and batch processes, and file-based imports such as FBDI. Enterprise workflows can use REST for supported transactional resources, SOAP for selected business operations, events for supported processes, and scheduled or file-based synchronization for high-volume or non-event-driven workloads.
Yes. Martini can consume Oracle SCM Cloud REST APIs and SOAP services, receive supported event or callback notifications, orchestrate scheduled synchronization, transform SCM payloads, and manage documented file-based import and export processes. No native Martini Oracle SCM Cloud connector is documented in the supplied materials.
No. A dedicated Oracle SCM Cloud connector is not required. Martini can use Oracle's confirmed REST APIs, SOAP services, supported event delivery mechanisms, file processes, and authentication methods through workflows and APIs.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle SCM Cloud with Martini. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.
Use REST APIs for supported resource operations and modern transactional integrations. Use SOAP when the required operation is only available through a SOAP service, an existing WSDL design must be retained, or a SOAP business operation is required. Use FBDI or applicable asynchronous and batch mechanisms for high-volume processing.
Oracle supports selected business events and event-driven integration patterns, but event coverage is product- and process-specific. They should not be treated as universal webhooks for every SCM object. Martini can receive a supported notification and retrieve the authoritative Oracle resource when needed; polling remains appropriate where no event is available.
Martini can use documented timestamps, status filters, resource-specific extraction options, or selected business events to identify changes. Workflows persist checkpoints, follow pagination, map data to target schemas, and run periodic reconciliation so late, missed, or changed records are detected.
Martini can classify transport, throttling, authentication, authorization, validation, and business errors, retry only recoverable failures with controlled backoff, and route terminal failures for review. Stable external identifiers, deterministic lookups, stored Oracle IDs, and correlation IDs help prevent duplicate Purchase Orders, Work Orders, Inventory transactions, or Orders. Martini can also expose an API façade for downstream applications while centralizing these rules.
Related Martini documentation
Oracle APIs
Data processing
Build reliable Oracle SCM Cloud integrations with Martini
Use Martini to connect Oracle SCM Cloud APIs, services, events, and file processes with the applications and data platforms that support your supply chain. Design maintainable workflows for synchronization, orchestration, transformation, and operational control.