OIC Accelerator Upgrade: Reviewing Merge Reports and Resolving Unmerged Extensions

Working...

When upgrading an Oracle Integration Cloud (OIC) Accelerator, Oracle automatically merges the latest accelerator changes with your customized extensions. While most changes are merged successfully, some extensions may require manual intervention due to conflicts or customizations.

The Merge Report provides a consolidated view of all merged and unmerged extensions, allowing developers to quickly identify and resolve any outstanding issues before completing the upgrade.

This blog explains how to access the Merge Report from the Integration Palette and review each unmerged extension.

Why Review the Merge Report?

After an accelerator upgrade, reviewing the Merge Report helps you:

• Verify which extensions were merged successfully.
• Identify extensions that require manual review.
• Understand the reason behind merge conflicts.
• Ensure all customizations are retained after the upgrade.
• Validate the integration before deployment.

Steps to Review the Merge Report

Step 1: Open the Upgraded Integration

Open the upgraded integration in the OIC Designer.

Step 2: Open the Integration Palette

From the left-side panel, open the Integration Palette.

Navigate to the Extensions section.

Step 3: View the Merge Report

Select Merge Report from the Integration Palette.

The report displays:

Successfully merged extensions

Partially merged extensions

Unmerged extensions requiring manual resolution

This provides an overview of the upgrade status for all extensions.

Step 4: Review Each Unmerged Extension

Expand each unmerged extension listed in the report.

For every extension, review:

• The affected integration component
• The merge status
• The reason for the conflict
• Any customizations that were not merged automatically

This helps determine the manual changes required.

Step 5: Resolve the Unmerged Changes

Open the corresponding extension and compare it with the original implementation.

Review components such as:

Mappings (XSLT)

Variables

Assign actions

Switch conditions

Invoke activities

Fault handlers

Connections and adapter configurations

Apply the required changes manually while preserving both the accelerator updates and your customizations.

Step 6: Validate and Test

Once all unmerged extensions have been reviewed and resolved:

• Validate the integration.
• Resolve any validation or mapping errors.
• Perform functional testing.
• Activate the integration after successful validation.

Best Practices

• Always review the Merge Report immediately after an accelerator upgrade.
• Resolve all unmerged extensions before deployment.
• Compare customizations carefully to avoid losing business logic.
• Validate the integration after every manual update.
• Test all impacted integration flows before promoting to higher environments.

Conclusion

The Merge Report is an essential tool during OIC Accelerator upgrades. It provides a centralized view of merged and unmerged extensions, enabling developers to quickly identify areas requiring manual attention. By reviewing each unmerged extension and validating the integration thoroughly, you can ensure a smooth upgrade while preserving existing customizations and minimizing deployment risks.

OIC - Oracle Integration Cloud (OIC) – Upload File to UCM, Submit ESS Job, and Monitor Job Status

A common Oracle ERP Cloud integration pattern is to upload a file to UCM, submit an ESS job, and then poll the ESS job status until it completes successfully. This pattern is widely used for payment processing, FBDI imports, bank acknowledgements, and other batch integrations.

Business Requirement

Suppose an external system generates a file (CSV/XML/TXT) that needs to be processed by Oracle ERP Cloud.

The integration should:

1. Upload the file into Oracle ERP Cloud UCM.
2. Submit the required ESS job.
3. Wait for the job to finish.
4. Check the ESS job status.
5. Continue processing only when the job completes successfully.

Integration Flow

External System

      │

      ▼

Receive File

      │

      ▼

Upload File to UCM

      │

      ▼

Receive Content ID

      │

      ▼

Submit ESS Job

      │

      ▼

Receive Request ID

      │

      ▼

Loop Until Completion

      │

      ▼

Get ESS Job Status

      │

      ▼

Success / Error Handling

Step 1 – Upload File to UCM

Configure the Oracle ERP Cloud Adapter and select:

Operation: File Upload to WebCenter (UCM)

Example values:

Account: FAFusionImportExport

UCM Folder: fin$/payments$/import$

After upload, Oracle returns a Content ID, which is required by many ESS jobs.

Step 2 – Submit ESS Job

Invoke another ERP Cloud Adapter.

Choose: Submit ESS Job

Provide:

Job Package Name: /oracle/apps/ess/financials/payments/fundsDisbursement/payments/

Job Definition Name: FDAckProcessing

Parameters: <referenceNumber>

Example ESS Job Path:

/oracle/apps/ess/financials/payments/fundsDisbursement/payments/FDAckProcessing

The adapter returns an ESS Request ID.

Example:

Request ID : 300000458912345

Step 3 – Wait Before Polling

Instead of checking immediately, add a Wait activity.

Example:

Wait 20–30 seconds

This avoids unnecessary API calls while Oracle begins processing the job.

Step 4 – Check ESS Job Status

Use a While scope.

Pseudo logic: While Status != SUCCEEDED

   Wait 20 Seconds

   Get ESS Job Status : Pass the Request ID returned during job submission.

End While

If the status becomes:

SUCCEEDED → Continue integration.

ERROR → Raise fault.

WARNING → Handle based on business requirement.

Typical statuses include:

Status Meaning

WAIT Waiting to start

READY Ready for execution

RUNNING Currently executing

SUCCEEDED Completed successfully

ERROR Failed

WARNING Completed with warnings

When to use Upload File to UCM:

You are uploading a payment file or bank file.

You need to run a specific ESS job yourself after the upload.

The file is not a standard Oracle FBDI import.

You need full control over the sequence (Upload → ESS Job → Poll Status).

Example:

Upload payment acknowledgment file.

Upload HSBC bank file.

Upload custom XML/CSV.

Upload a file and then run FDAckProcessing ESS job.

When to use Bulk Import:

You are importing Oracle ERP business data using FBDI.

Oracle ERP supports that object through the Bulk Import operation.

You want Oracle to manage the import process for that business object.

Examples:

Supplier Import

Customer Import

GL Journal Import

AP Invoice Import

Asset Import

Item Import

Conclusion

Uploading a file to UCM, submitting an ESS job, and continuously monitoring the job status is one of the most common Oracle Integration Cloud design patterns. By combining the ERP Cloud Adapter, Wait, and While activities, you can build a robust integration that ensures downstream processing starts only after the ERP job has successfully completed.

OIC - Oracle Integration Cloud (OIC): Configuring BI Publisher Data Model to Return DATA_DS, Empty XML Tags, and CSV Output

When integrating Oracle ERP Cloud reports with Oracle Integration Cloud (OIC), you may encounter situations where BI Publisher omits empty XML elements. This can create issues in OIC because expected XML nodes are missing, making mappings and XPath expressions fail.

This blog explains how to configure your BI Publisher Data Model so that:

The response contains the <DATA_DS> root tag instead of only column headers.

Blank fields are returned as empty XML tags (for example, <STATUS/>) instead of being omitted.

CSV output is enabled if required.

Problem Statement

While calling a BI Publisher report from OIC:

The XML response may contain only headers or omit the <DATA_DS> section when no data is returned.

Columns with NULL values are not included in the XML payload.

Missing XML elements can cause integration mappings, stage file processing, or downstream applications to fail.

Solution

Open the BI Publisher Data Model and configure the following properties.

1. Enable CSV Output

Check:

✅ Enable CSV Output

This allows the report to generate CSV output when required by downstream integrations.

2. Include Empty XML Tags

Under XML Output Options, enable:

✅ Include Empty Tags for Null Elements

✅ Include Open & Close Tags

These settings ensure that if a database column contains a NULL value, BI Publisher still generates the XML element.

Before

<DATA_DS>

   <G_1>

      <REQUEST_ID>12345</REQUEST_ID>

   </G_1>

</DATA_DS>

After

<DATA_DS>

   <G_1>

      <REQUEST_ID>12345</REQUEST_ID>

      <STATUS/>

      <ERROR_MESSAGE/>

   </G_1>

</DATA_DS>

This makes XML parsing in OIC much more reliable.

Why This Is Important

Using these options provides several benefits:

Ensures a consistent XML structure.

Prevents XPath and mapper failures in OIC.

Simplifies Stage File and XML parsing.

Guarantees expected tags exist even when values are NULL.

Improves compatibility with downstream systems expecting fixed XML schemas.

Configuration Screenshot

The following BI Publisher Data Model settings should be enabled:

Enable CSV Output

Include Empty Tags for Null Elements

Include Open & Close Tags

These options are available under the Properties page of the Data Model, as shown in your screenshot.

Conclusion

If your OIC integration depends on consistent XML elements, configuring the BI Publisher Data Model correctly is essential. By enabling CSV Output and selecting Include Empty Tags for Null Elements along with Include Open & Close Tags, BI Publisher always returns a predictable XML payload with the <DATA_DS> structure and empty tags for NULL values. This greatly improves integration stability and reduces mapping errors in Oracle Integration Cloud.