Translate Function in OIC Guide

Introduction

In modern integrations, data transformation is one of the most critical steps, especially when working across multiple systems like ERP, HCM, and third-party applications. The Translate Function in Oracle Integration Cloud plays a key role in handling such transformations efficiently. Within Oracle Integration Cloud, the Translate function enables developers to convert payload formats—typically XML to JSON, JSON to XML, or even structured transformations using XSLT.

From a real project perspective, this function is heavily used when integrating Oracle Fusion applications with external systems like payroll vendors, banking APIs, or legacy systems.

What is Translate Function in Oracle Integration Cloud?

The Translate Function in OIC is a built-in action used to transform message payloads from one format to another using predefined or custom mapping logic.

It is commonly used for:

• XML to JSON conversion
• JSON to XML conversion
• Applying XSLT transformations
• Standardizing payload formats across integrations

Unlike simple field mapping, Translate is used when:

• Complex transformations are required
• External systems expect a different structure
• Schema mismatch exists between source and target

Key Features of Translate Function

1. Multi-format Transformation

Supports:

• XML ↔ JSON
• XML ↔ XML (using XSLT)
• JSON ↔ JSON

2. XSLT-Based Transformation

You can upload custom XSLT files for advanced transformations.

3. Schema-Driven Mapping

Uses source and target schemas defined in integrations.

4. Reusability

Reusable in multiple integrations, reducing duplication.

5. Supports Complex Logic

Handles:

• Conditional transformations
• Looping structures
• Nested mappings

Real-World Integration Use Cases

Use Case 1: Payroll Integration with Third-Party Vendor

In one HCM implementation:

• Oracle Fusion HCM generates payroll data in XML
• Vendor API expects JSON format

Solution:

• Use Translate function to convert XML → JSON
• Apply required field mapping

Use Case 2: Bank Payment File Transformation

ERP system generates payment file in XML format.

Bank requires:

• Custom flat file structure or JSON

Solution:

• Use XSLT within Translate function
• Transform XML into required bank format

Use Case 3: Legacy System Integration

A legacy system sends data in JSON but:

• Fusion ERP expects XML payload

Solution:

• Translate JSON → XML
• Map fields to Fusion-compatible structure

Architecture / Technical Flow

Here’s how the Translate function fits into OIC Gen 3 flow:

1. Source system sends payload (XML/JSON)
2. Integration receives payload
3. Translate function is invoked
4. Payload is transformed using:
   • Schema mapping OR
   • XSLT transformation
5. Transformed payload is sent to target system

Flow Summary:

Prerequisites

Before using Translate Function, ensure:

1. Defined Schemas

• Source schema (WSDL/JSON)
• Target schema

2. Integration Created

• App-driven or scheduled integration

3. Connections Configured

• REST Adapter
• SOAP Adapter

4. Optional: XSLT File

• For complex transformation logic

Step-by-Step Build Process

Let’s walk through a practical implementation scenario.

Step 1 – Create Integration

Navigation:

Navigator → Integrations → Create

• Choose:
  • App Driven Orchestration
  • Or Scheduled Integration

Step 2 – Configure Trigger

Example:

• Use REST Adapter
• Define input payload (JSON/XML)

Step 3 – Add Translate Action

In the integration canvas:

• Click “+” → Select Action → Choose Translate

Step 4 – Configure Translate Function

You will see:

Source Schema

• Input payload structure

Target Schema

• Output payload format

Transformation Type

Options:

• XML to JSON
• JSON to XML
• XML to XML (XSLT)

Step 5 – Upload XSLT (Optional)

For advanced transformations:

• Upload .xsl file
• Define transformation rules

Example:

Step 6 – Map Fields

Use OIC mapper:

• Drag source fields → target fields
• Apply transformations if needed

Step 7 – Save and Activate

• Validate integration
• Click Activate

Testing the Technical Component

Test Scenario

Input Payload (JSON):

Expected Output (XML):

Steps to Test

1. Go to Integration → Tracking
2. Submit test payload
3. Monitor instance

Validation Checks

• Ensure correct format conversion
• Validate field mapping
• Check for missing elements

Common Errors and Troubleshooting

1. Schema Mismatch

Issue:

• Source and target schemas don’t align

Solution:

• Validate schema structure
• Use proper namespace handling

2. XSLT Errors

Issue:

• Incorrect XPath expressions

Solution:

• Test XSLT independently
• Use proper XML structure

3. Null Value Handling

Issue:

• Missing fields in output

Solution:

• Add conditional logic in mapping

4. Namespace Issues

Issue:

• XML namespaces causing mapping failure

Solution:

• Properly define namespaces in XSLT

Best Practices

1. Always Use Schemas Properly

Define clean and structured schemas for transformation.

2. Use XSLT for Complex Logic

Avoid overcomplicating simple mappings.

3. Reuse Transformations

Design reusable integrations.

4. Validate Payloads Early

Perform validation before transformation.

5. Logging and Tracking

Enable tracking for debugging.

6. Keep Transformations Lightweight

Avoid heavy processing inside OIC when possible.

Real Consultant Tips

• In large enterprise projects, Translate function is often used in middleware standardization layers.
• Avoid mixing mapping and translation logic—keep them modular.
• Always maintain version control of XSLT files.
• For performance-critical integrations, minimize transformation steps.

Summary

The Translate Function in Oracle Integration Cloud is a powerful feature that enables seamless data transformation across systems. In real-world implementations, it becomes essential when dealing with heterogeneous systems that exchange data in different formats.

By understanding how to configure and use this function effectively, consultants can build scalable, efficient integrations in OIC Gen 3 environments.

For deeper reference, you can explore the official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. What is the main purpose of Translate function in OIC?

It is used to transform data formats (XML, JSON) and apply complex transformations using XSLT.

2. When should I use Translate instead of Mapper?

Use Translate when:

• Format conversion is required
• Complex transformation logic is needed

3. Can Translate function handle large payloads?

Yes, but performance depends on:

• Payload size
• Complexity of transformation
• XSLT efficiency