OIC SharePoint Integration Guide

Share

Introduction

Oracle Integration Cloud SharePoint integration is a critical capability in modern enterprise landscapes where organizations rely heavily on document collaboration platforms like Microsoft SharePoint alongside Oracle Fusion Cloud applications. In real-world implementations, consultants often face requirements to exchange files, automate document uploads, or trigger business processes based on SharePoint activities.

In Oracle Integration Cloud (OIC Gen 3), SharePoint integration enables seamless communication between Oracle SaaS applications and Microsoft ecosystems, ensuring automation, governance, and scalability. This blog provides a deep, implementation-focused guide on how to design, configure, and troubleshoot SharePoint integrations using OIC.

What is Oracle Integration Cloud SharePoint Integration?

Oracle Integration Cloud SharePoint integration refers to the process of connecting OIC with Microsoft SharePoint Online using REST APIs or Microsoft Graph APIs to perform operations such as:

  • Uploading files

  • Downloading documents

  • Creating folders

  • Listing files

  • Triggering workflows based on document events

Unlike legacy integrations, OIC Gen 3 supports secure, scalable, and API-driven interactions, making it ideal for enterprise-grade document automation.

Real-World Integration Use Cases

1. Employee Document Management (HCM Integration)

In a real Oracle Fusion HCM implementation:

  • Employee onboarding documents (ID proof, contracts) are uploaded via Oracle Fusion

  • OIC pushes these documents automatically into SharePoint document libraries

  • HR teams access documents centrally from SharePoint

Benefit: Eliminates manual uploads and ensures centralized document governance.

2. Invoice Archival from ERP to SharePoint

In Oracle Fusion ERP:

  • After invoice approval, documents are stored in SharePoint

  • OIC extracts invoice PDFs from ERP and uploads them to SharePoint

Benefit: External document storage reduces ERP storage load and improves accessibility.

3. Procurement Document Collaboration

In Oracle Fusion SCM:

  • Vendor documents (POs, contracts) are shared via SharePoint

  • OIC synchronizes documents between Fusion and SharePoint

Benefit: Enhances collaboration between internal teams and vendors.

Architecture / Technical Flow

A typical OIC SharePoint integration follows this architecture:

  1. Oracle Fusion / External System triggers integration

  2. OIC receives request (REST/Scheduled/ERP Event)

  3. OIC processes data and prepares payload

  4. OIC calls Microsoft Graph API

  5. SharePoint performs operation (upload/download)

  6. OIC logs response and updates source system

Key Components

  • OIC Gen 3 Integration Flow

  • REST Adapter

  • Microsoft Graph API

  • Azure App Registration (for authentication)

Prerequisites

Before building the integration, ensure the following:

1. Azure Setup

  • Register an application in Azure Portal

  • Generate:

    • Client ID

    • Client Secret

    • Tenant ID

  • Assign permissions:

    • Sites.ReadWrite.All

    • Files.ReadWrite.All

2. SharePoint Details

  • Site URL

  • Document Library Name

  • Folder Structure

3. Oracle Integration Cloud (Gen 3)

  • Active OIC instance

  • REST Adapter enabled

  • Access to Integration Designer

Step-by-Step Build Process

Step 1 – Create Azure App Registration

  1. Go to Azure Portal

  2. Navigate to: Azure Active Directory → App Registrations → New Registration

  3. Enter:

    • Name: OIC_SharePoint_Integration

    • Redirect URI: (optional)

  4. Save:

    • Application (Client) ID

    • Directory (Tenant) ID

Step 2 – Generate Client Secret

  1. Navigate to: Certificates & Secrets → New Client Secret

  2. Copy the secret value immediately

Step 3 – Assign API Permissions

  1. Go to: API Permissions → Add Permission → Microsoft Graph

  2. Add:

    • Files.ReadWrite.All

    • Sites.ReadWrite.All

  3. Click Grant Admin Consent

Step 4 – Create Connection in OIC

Navigation: Navigator → Integrations → Connections → Create

Configuration:

Field Value
Adapter REST Adapter
Connection Type Invoke
Base URL https://graph.microsoft.com/v1.0

Step 5 – Configure Security (OAuth 2.0)

  • Grant Type: Client Credentials

  • Token URL: https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token

  • Scope: https://graph.microsoft.com/.default

  • Client ID & Secret: From Azure

Test and save connection.

Step 6 – Create Integration

Navigation: Navigator → Integrations → Create → App Driven Orchestration

Step 7 – Upload File to SharePoint

Use Microsoft Graph API:

Endpoint:

PUT /sites/{site-id}/drive/root:/foldername/filename:/content

Configure REST Action:

  • Method: PUT

  • Headers:

    • Content-Type: application/octet-stream

Step 8 – Map Payload

In OIC mapper:

  • Map file content (Base64 or binary)

  • Map dynamic file name

  • Map folder path

Step 9 – Activate Integration

  • Save

  • Activate integration

  • Enable tracing for debugging

Testing the Technical Component

Test Scenario

Upload an employee document:

Input Payload Example:

{ “fileName”: “Employee_1001.pdf”, “content”: “Base64EncodedContent”, “folder”: “HRDocuments” }

Expected Output

  • HTTP Status: 201 Created

  • File appears in SharePoint folder

Validation Checks

  • File exists in correct folder

  • File size matches

  • Metadata is correct

Common Errors and Troubleshooting

1. 401 Unauthorized

Cause: Invalid token or expired secret

Solution:

  • Regenerate client secret

  • Verify OAuth configuration

2. 403 Forbidden

Cause: Missing API permissions

Solution:

  • Add Graph API permissions

  • Grant admin consent

3. File Upload Failure

Cause: Incorrect API endpoint or payload

Solution:

  • Verify site ID and folder path

  • Check binary content mapping

4. Large File Issues

Cause: Graph API size limitations

Solution:

  • Use chunk upload API

Best Practices

1. Use Secure Credential Storage

Avoid hardcoding secrets. Always use OIC connection security.

2. Implement Retry Mechanism

Handle transient failures using scope and fault handlers.

3. Logging and Tracking

  • Enable OIC tracking

  • Store response logs for audit

4. Dynamic Folder Handling

Use variables to dynamically create folder paths based on:

  • Employee ID

  • Invoice Number

  • Supplier Name

5. Use Scheduled Integrations for Bulk Upload

For large data transfers, avoid real-time APIs.

Real Consultant Tips

  • Always test Graph API in Postman before configuring OIC

  • Use smaller payloads during development

  • Maintain naming conventions for files

  • Document site ID retrieval process clearly

  • Monitor integration performance in OIC dashboard

Summary

Oracle Integration Cloud SharePoint integration is a powerful capability that enables seamless document management across enterprise systems. With OIC Gen 3 and Microsoft Graph APIs, organizations can automate file handling, improve collaboration, and reduce manual effort.

From employee onboarding documents to ERP invoice archival, SharePoint integrations are becoming a standard requirement in Oracle Cloud implementations. By following proper architecture, secure authentication, and best practices, consultants can build scalable and reliable integrations.

For more details, refer to official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. Can OIC directly connect to SharePoint without Azure setup?

No. SharePoint Online requires authentication via Azure AD and Microsoft Graph API.

2. What is the best method for uploading large files?

Use Microsoft Graph chunk upload API instead of single PUT request.

3. How do I get SharePoint Site ID?

Use Graph API:

GET /sites/{hostname}:/sites/{sitename}

Share

Leave a Reply

Your email address will not be published. Required fields are marked *