Oracle SCM SOAP API Guide

Introduction

Oracle Fusion SCM SOAP API plays a critical role in enterprise integrations where structured, secure, and reliable data exchange is required between Oracle Fusion Cloud and external systems. In real-world implementations, especially in supply chain environments, SOAP APIs are still widely used for transactional integrations like purchase orders, inventory updates, shipments, and supplier data synchronization.

From my experience working on Oracle Fusion SCM implementations, SOAP APIs are often preferred in scenarios where strict contracts (WSDL-based), high security, and guaranteed delivery are required—especially when integrating with legacy ERP systems or third-party logistics providers.

In this blog, we’ll go deep into how Oracle Fusion SCM SOAP APIs work, how to configure and use them, and practical implementation strategies using modern tools like Oracle Integration Cloud (OIC Gen 3).

What is Oracle Fusion SCM SOAP API?

Oracle Fusion SCM SOAP API is a web service interface provided by Oracle Fusion Cloud that allows external systems to interact with SCM modules using SOAP (Simple Object Access Protocol).

These APIs are:

• Based on WSDL (Web Services Description Language)
• Support XML-based request/response
• Secured via WS-Security or Basic Auth
• Typically used for transactional operations

Common SCM SOAP Services

Some commonly used SOAP services in SCM include:

• Procurement:
  • Purchase Order Service
  • Supplier Service
• Inventory:
  • Inventory Transaction Service
  • Item Service
• Order Management:
  • Order Import Service
• Shipping:
  • Shipment Service

Real-World Integration Use Cases

1. External Procurement System Integration

A manufacturing company uses a third-party procurement tool. Purchase orders created externally are sent to Oracle Fusion using SOAP API.

Flow:
External System → SOAP API → Fusion Procurement

2. Warehouse Management System (WMS) Integration

A WMS sends inventory transactions (receipts/issues) to Oracle Fusion Inventory via SOAP.

Scenario:

• Goods received in warehouse
• SOAP API updates inventory in Fusion

3. Supplier Data Synchronization

A vendor onboarding system pushes supplier details into Oracle Fusion using SOAP services.

Key Benefit:
Maintains a single source of truth across systems.

Architecture / Technical Flow

A typical Oracle Fusion SCM SOAP API integration looks like this:

1. External System / OIC sends SOAP request
2. SOAP request follows WSDL structure
3. Fusion validates request
4. Business logic executes
5. Response returned (Success/Error)

Integration Pattern with OIC Gen 3

• SOAP Adapter in OIC consumes Fusion WSDL
• Mapping transforms payload
• Security handled via credentials
• Response processed and logged

Prerequisites

Before working with Oracle Fusion SCM SOAP APIs, ensure:

1. Access to Fusion Instance

• Valid credentials
• Required roles (e.g., Integration Specialist)

2. WSDL URL

Example format:

3. Required Roles

Assign roles like:

• SOAOperator
• Integration Specialist
• SCM Application Roles

4. Oracle Integration Cloud (OIC Gen 3)

• Create connections
• Configure SOAP adapter
• Setup security policies

Step-by-Step Build Process

Let’s walk through a real implementation scenario:

Use Case: Create Purchase Order using SOAP API

Step 1 – Get WSDL

Navigate to:

Fusion URL:

Download WSDL file.

Step 2 – Create Connection in OIC Gen 3

1. Login to OIC
2. Go to Connections
3. Click Create

Select:

• Adapter: SOAP

Step 3 – Configure Connection

Enter:

• WSDL URL
• Security Policy:
  • Username Token

Provide:

• Username
• Password

Test connection → Should be successful

Step 4 – Create Integration

1. Go to Integrations → Create
2. Choose:
   • App Driven Orchestration

Step 5 – Add Trigger

• Use REST Adapter (if external system sends request)

Step 6 – Add SOAP Invoke

• Select SOAP connection
• Choose operation:
  • createPurchaseOrder

Step 7 – Data Mapping

Map:

Step 8 – Activate Integration

• Validate
• Activate
• Note endpoint URL

Sample SOAP Request (Simplified)

Testing the Technical Component

Test Using Postman

1. Select POST method
2. Enter endpoint URL
3. Add Headers:
   • Content-Type: text/xml
4. Add SOAP body
5. Send request

Expected Response

Success response includes:

• Purchase Order Number
• Status = SUCCESS

Validation Checks

• Check PO in Fusion:
  Navigator → Procurement → Purchase Orders
• Verify:
  • Supplier
  • Item
  • Quantity

Common Errors and Troubleshooting

1. Authentication Failure

Error:
Unauthorized

Solution:

• Verify credentials
• Check security policy

2. Invalid Payload Structure

Error:
SOAP Fault

Solution:

• Validate XML against WSDL
• Ensure correct namespaces

3. Missing Mandatory Fields

Error:
Validation Exception

Solution:

• Check required fields like:
  • Supplier
  • BU
  • Currency

4. Timeout Issues

Solution:

• Increase timeout in OIC
• Optimize payload

Best Practices

1. Always Use OIC as Middleware

Direct integration is possible but not recommended.

Why?

• Centralized error handling
• Transformation capability
• Monitoring

2. Validate Payload Before Sending

Use schema validation to avoid runtime errors.

3. Use Logging and Tracking

In OIC:

• Enable tracking fields
• Log request/response

4. Avoid Large Payloads

Split transactions when dealing with bulk data.

5. Use Proper Security Policies

Prefer:

• WS-Security
• OAuth (where supported)

6. Version Control WSDLs

Keep track of WSDL versions across environments.

Real Consultant Tips

From real project experience:

• Always test SOAP APIs in lower environments before production
• Use SOAP UI or Postman for quick testing
• Maintain error handling framework in OIC
• Keep mapping reusable
• Document all API endpoints and operations

Summary

Oracle Fusion SCM SOAP API remains a powerful and essential integration mechanism in enterprise environments. While REST APIs are gaining popularity, SOAP APIs still dominate in scenarios requiring strict contracts, security, and reliability.

By combining SOAP APIs with Oracle Integration Cloud (OIC Gen 3), organizations can build scalable, maintainable, and secure integrations across procurement, inventory, and order management systems.

If you are working in Oracle SCM projects, mastering SOAP APIs is not optional—it is a must-have skill for real-world implementations.

FAQs

1. When should I use SOAP API instead of REST in Oracle SCM?

Use SOAP when:

• You need strict WSDL contracts
• Security requirements are high
• Legacy systems are involved

2. Can I directly call SOAP APIs without OIC?

Yes, but not recommended. OIC provides:

• Transformation
• Monitoring
• Error handling

3. What tools can I use to test SOAP APIs?

Common tools:

• Postman
• SOAP UI
• OIC Test Console

Oracle Documentation Reference

For more details, refer to official Oracle documentation:

https://docs.oracle.com/en/cloud/saas/index.html