OIC Integration steps for Item structures Conversion from One Inventory Org to Other Inv Org.

OIC Integration: BOM and Item Structure Conversion Between Inventory Organizations

In Oracle Fusion Cloud, when businesses expand or reorganize their manufacturing or inventory setups, it often becomes necessary to replicate or convert Item Structures (BOM) from one Inventory Organization to another. Doing this manually can be time-consuming and error-prone. Thankfully, using Oracle Integration Cloud (OIC), we can automate this process efficiently.

---

💡 Use Case Overview

We want to build an OIC integration that will:

• Extract BOM and Item Structure details from a Source Inventory Organization.
• Transform and prepare the data for a Target Inventory Organization.
• Load or create BOMs in the target org using Fusion REST APIs.

Example: Copy BOM structure for an item from INV_ORG_A (Manufacturing Plant A) to INV_ORG_B (Manufacturing Plant B).

---

🔧 Step-by-Step OIC Integration Flow

Step 1: Create a Scheduled Integration

• Open OIC → Integrations → Create → Choose Scheduled Integration.
• Name it: BOM_Structure_Conversion.
• This will allow automation to run periodically or on demand.

Step 2: Get BOM Details from Source Org

Use the Fusion REST API for Item Structures to fetch BOM details.

 GET /fscmRestApi/resources/11.13.18.05/itemStructures ?ItemNumber={itemNumber} &OrganizationCode={SourceOrg} 

Example Response:

{ "ItemNumber": "LAPTOP1001", "OrganizationCode": "INV_ORG_A", "Components": [ {"ComponentItem": "MOTHERBOARD", "Quantity": 1}, {"ComponentItem": "BATTERY", "Quantity": 1} ] }

Step 3: Map Source to Target Organization

Use a Data Mapper in OIC to change the organization context from INV_ORG_A to INV_ORG_B.

 TargetOrg = "INV_ORG_B" 

Also, apply transformations if the target org uses different item codes or UOMs.

Step 4: Create BOM in Target Org

Use the Fusion REST API to create or update BOMs in the target organization.

 POST /fscmRestApi/resources/11.13.18.05/itemStructures 

Sample Request Payload:

{ "ItemNumber": "LAPTOP1001", "OrganizationCode": "INV_ORG_B", "StructureTypeCode": "Primary", "Components": [ {"ComponentItem": "MOTHERBOARD", "Quantity": 1}, {"ComponentItem": "BATTERY", "Quantity": 1} ] }

In OIC, use the REST Adapter to invoke this endpoint, passing the transformed JSON payload.

Step 5: Add Logging and Error Handling

Implement structured logging for traceability:

• Log item number, source org, and target org.
• Log API response status codes and errors.

Add a Scope + Fault Handler in OIC for retries and fault notifications (email or Teams webhook).

Step 6: Validation and Reports

• Use GET API again for the target org to verify successful BOM creation.
• Generate a CSV report of successfully migrated BOMs.
• Send it as an email attachment from OIC.

---

🔗 Common Fusion APIs Used

API	Method	Description
/fscmRestApi/resources/11.13.18.05/itemStructures	GET	Fetch BOM/Structure details
/fscmRestApi/resources/11.13.18.05/itemStructures	POST	Create new BOM in target org
/fscmRestApi/resources/11.13.18.05/itemStructures/{StructureId}	PATCH	Update existing BOM

---

✅ Best Practices

• Use paging and filters while fetching BOM data for large item volumes.
• Maintain a mapping table (e.g., via lookup in OIC or database) for item number and org mapping.
• Implement idempotent logic — skip BOM creation if it already exists.
• Log integration run IDs for audit trail.

---

📊 Sample High-Level Integration Flow Diagram

 [SCHEDULE TRIGGER] ↓ [GET BOM from Source Org via REST Adapter] ↓ [Transform + Map Org Details] ↓ [POST BOM to Target Org via REST Adapter] ↓ [Validate + Log Results + Email Report] 

---

🧩 Summary

This integration helps Oracle Fusion Cloud users automate BOM and item structure replication between inventory organizations using OIC. It eliminates manual effort, ensures BOM consistency, and enables smooth manufacturing transfers across plants.

Using Oracle Integration Cloud’s REST Adapters, transformations, and fault handling, you can easily scale this to handle hundreds of items with audit tracking and notifications.

✨ Tip: You can extend this integration to migrate Work Definitions, Routing, and Cost Structures as well.