Contact person: Oracle cloud integration Developer -- 2

Phone:Show

Email:Show

Location: KOLKATA, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Role: OIC Developer (Fusion ERP ↔️ OTM Integration)
Location: Offshore – India (Remote)
Duration: 5–6 weeks (Contract, extendable)

⸻

About the Role

We’re looking for an experienced OIC Developer to help us integrate Oracle Fusion ERP with Oracle Transportation Management (OTM). The project involves building 3 simple master data interfaces and customizing a prebuilt shipment integration.

⸻

Key Responsibilities
• Build and deploy integrations in Oracle Integration Cloud (OIC).
• Develop Fusion ERP → OTM master data flows (Locations, Items, Carriers).
• Configure and extend OTM → Fusion ERP planned shipment flow.
• Handle mappings, transformations, and error handling in OIC.
• Support system integration testing and documentation.

⸻

Requirements
• 2+ years of hands-on OIC development experience.
• Strong knowledge of Fusion ERP & OTM adapters, SOAP/REST APIs.
• Experience with XSLT mappings and BI Publisher extracts.
• Prior experience with ERP ↔️ OTM integrations preferred.
• Good communication skills, ability to work independently from offshore.

⸻

Engagement Details
• Location: Offshore (India – remote)
• Duration: ~5 weeks (25 developer-days effort, extendable)
• Start Date: Immediate / within 2 weeks





Requirement

You’re essentially looking at setting up a set of OIC (Oracle Integration Cloud) integrations between Oracle Fusion ERP and OTM (Oracle Transportation Management). Let’s break this down orthogonally so it’s clear what’s involved:

⸻

Interfaces to Build

1. Master Data Interfaces (Fusion → OTM)

Typically, OTM requires some core master data from Fusion ERP to be in sync before transactional data can flow. The 3 simple ones you mentioned are likely:
• Location Master (sites, warehouses, customers, suppliers)
• Item/Product Master (goods being shipped, with attributes)
• Carrier/Service Provider Master (or sometimes Units of Measure / reference data, depending on scope)

These flows are usually outbound from Fusion ERP → OTM.
• Trigger: Fusion publishes events (or scheduled extracts).
• Transformation: OIC maps Fusion’s payload (SOAP/REST/BI Publisher extract) into OTM’s inbound XML/CSV structure.
• Delivery: Send to OTM via its web services (often TransmissionService API).

⸻

2. Planned Shipment (OTM → Fusion ERP)

This is the more critical/complex interface:
• OTM plans the shipments and generates the transportation plan.
• Fusion ERP (typically SCM Logistics or Purchasing/Order Management side) needs the shipment confirmation to update supply chain execution.
• Prebuilt flows exist in OIC under OTM-Fusion SCM adapters that handle:
• Listening for shipment events in OTM (via OTM’s OutboundTransmission or Integration layer).
• Mapping into Fusion ERP’s InboundShipment or ShipmentAdvice service.
• Usually needs some extension mapping (e.g., Fusion expects certain costing, organization, or UOM codes).

⸻

Integration Flow Setup in OIC
1. Source Connector (Adapter)
• Fusion ERP adapter (SOAP/REST/BI Publisher extract).
• OTM adapter (via web service / REST API / file if batch).
2. Mapping & Transformation
• Use OIC mapper to transform fields between Fusion ERP schemas and OTM inbound XML schemas.
• Handle code conversions (Org codes, UOM, currency, carrier IDs).
3. Error Handling & Logging
• Standard OIC fault handlers.
• Error notifications to functional team (email, OCI logging).
4. Scheduling / Triggers
• Master data flows: usually scheduled or event-driven from Fusion.
• Planned shipment flow: event-driven from OTM (real-time push).

⸻
Suggested Approach to Build
1. Start with the 3 master data flows since they’re simpler.
• Get payload structures from Fusion ERP.
• Align with OTM inbound service requirements.
• Test in sequence (Locations → Items → Carriers).
2. Then configure the OTM → Fusion planned shipment interface using the prebuilt integration:
• Deploy the prebuilt OIC integration for Shipment.
• Customize the mapping for your client’s org-specific fields.
• Test with an end-to-end order → shipment cycle.

⸻

End result: OTM will always have synchronized master data from Fusion, and Fusion ERP will receive planned shipments from OTM with minimal custom build." (client-provided description)