Oracle Fusion Forms Personalization using Sandbox

🧭 Introduction

Oracle Fusion Cloud supports no-code UI personalization using Sandbox and Structure tools. Known as Form Personalization, this method safely customizes navigational tiles, labels, and task names—without altering core application or upgrades. You can preview all changes in a sandbox locally before publishing them application wide.

 

📌 Common Use Cases

• Personalization & UI Tweaks: Change menus, tile labels, panels, and visibility of components while testing safely in sandbox.
• Testing New Functionality: Activate or disable Dynamic Flexfields, personalization, customized roles, and dashboards like Infolets or theme changes.
• Security Extensions: Build and test new CRM or custom business objects and configure data security before deploying.

 

 

✅ Use Case: Renaming a Tile and Task in Purchasing Screen in Fusion Application

 

Change	From	To
Tile	Negotiations	Negotiations / Solicitations
Task name	Create Negotiation	Create Negotiation / Solicitations

 

This change reflects corporate terminology, improves clarity for end‑users, and retains upgrade compatibility.

 

 

 

 

 

 

Before Change :	After Sandbox Changes

 

 

 

 

---

🔧 Step-by-Step Implementation

1. Create and Activate a Sandbox

• Navigate to Fusion Application → Navigator → Configuration → Sandboxes.
• Click Create Sandbox, assign a meaningful name and description.
• Select Structure as the personalization tool and activate it.

 

 

 

 

 

2. Launch the Structure Editor

• In the active sandbox, open Structure to view the UI component hierarchy.

 

• Navigate to Procurement → Negotiations.

                  

3. Rename at Page and Panel Levels

• Edit the Name property at the page level to "Negotiations / Solicitations".

                                   

• Under Panel Tabs or tasks, locate "Create Negotiation", update to "Create Negotiation / Solicitations".

 

4. Save, Preview, Publish

• Save and close the editor.
• Preview changes using sandbox’s preview mode to ensure accurate display.
• Publish the sandbox when confirmed, and have users sign out/sign in to refresh the UI.

                             

🧩 Best Practices & Tips

• Always create a separate test-only sandbox before moving to an integration/publish sandbox.
• After activating, log out/log in to prevent customization cache issues.
• Avoid publishing outdated sandbox before an Oracle patch or upgrade—stale sandboxes may conflict.
• Use labels for rollback or version control.
• Limit simultaneous multi-user editing in one sandbox—manage changes to reduce conflicts.

✅ Summary

Oracle Fusion’s sandbox framework is a powerful tool with wide range of capabilities to create secure, isolated environment to customize UI, security, and Oracle flexfield functionality—without impacting live fusion application. With support for versioning, rollback and conflict detection sandboxes streamline change management and ensure safe deployment to Production.

 

🌐 Oracle Integration Cloud (OIC) Gen3 – Key Features and Benefits

Oracle Integration Cloud (OIC) Generation 3 is Oracle’s latest evolution in application and process integration. It delivers a simplified and powerful low-code platform that enables seamless connectivity across Oracle and non-Oracle systems, with enhanced developer experience, modern monitoring, and better performance. Whether you are integrating cloud apps, building APIs, or automating business processes — OIC Gen3 simplifies it all.

Infographic: OIC Gen3 Architecture and Features

🔑 Key Features of OIC Gen3

• Unified Integration Platform: Combine Application Integration, Process Automation, and B2B messaging in one platform.
• Low-Code Development: Build integrations faster with visual design tools, guided wizards, and templates.
• Native Connectivity: Prebuilt adapters for Oracle SaaS (like ERP, HCM, CX) and 100+ other apps including SAP, Salesforce, Workday, etc.
• Advanced Observability: Real-time monitoring dashboards, automatic alerts, integration tracing, and intelligent analytics.
• GenAI Integration (NEW): Native integration capabilities with Generative AI APIs to enhance automation workflows.
• Zero Downtime Upgrades: Achieve continuous delivery with Oracle-managed seamless upgrades.
• Enterprise-Grade Security: Identity integration with OCI IAM, data encryption, secure keys, and policy-based access control.
• Built-in Process Automation: Automate multi-step approvals, service orchestration, and human task flows without code.
• Flex Deployment: Supports multi-cloud and hybrid architectures (cloud + on-premises).

📌 Common Use Cases

Here’s how organizations are using OIC Gen3 today:

1. Integrate Oracle ERP Cloud with third-party payroll and CRM systems.
2. Automate employee onboarding using Oracle HCM Cloud and DocuSign workflows.
3. Expose APIs for mobile and web apps using OIC's API gateway.
4. Build B2B transactions using EDI and AS2 standards.

🚀 Why Upgrade to OIC Gen3?

• Faster development and time-to-market for integrations.
• Reduced manual work and errors with automation.
• Better visibility into operations with AI-based monitoring.
• Flexible pricing and deployment options with OCI.

📝 Final Thoughts

OIC Gen3 is a game-changer for Oracle customers looking for fast, scalable, and intelligent integrations. With AI capabilities, low-code tools, and enterprise security, it helps businesses modernize and innovate — without complexity.

Ready to integrate smarter? Start exploring Oracle Integration Gen3 today!

📚 Suggested Reads:

• Top OIC Interview Questions
• Official Oracle Integration Cloud Page
• More Oracle EBS & OIC Tutorials

🚀 Oracle Integration Cloud (OIC) Gen3 – Best Practices for Implementation

Oracle Integration Cloud (OIC) Gen3 is Oracle's next-generation integration platform built for high scalability, modern user experience, and seamless connectivity. Whether you're integrating SaaS, on-premise, or third-party applications, following best practices is critical to ensure performance, reusability, and maintainability.

---

🎯 Why Gen3 Matters

• Completely redesigned web interface (Oracle Redwood look)
• Support for Process Automation & Visual Builder integration
• Lightweight, performant runtime engine
• Better lifecycle management & observability

---

📌 Top OIC Gen3 Best Practices

1. 🧩 Modular Integration Design
   Break complex flows into smaller, reusable integrations. Use Lookup and Global Variables for dynamic logic.
2. 🎨 Naming Conventions
   Use consistent prefixes like `APP-TO-ERP-XYZ-INTF` and meaningful names for connections, variables, and packages.
3. 🛡️ Secure Credentials via Vault
   Store sensitive details (usernames, passwords, tokens) in the **OIC Vault** instead of hardcoding them.
4. 📄 Use Error Handling Framework
   Implement global fault handlers or fault policies. Use **raiseError**, **terminate**, and **callback** strategically.
5. 🔄 Enable Tracing (Sparingly)
   Use **on-demand tracing** for troubleshooting. Avoid enabling in production for performance reasons.
6. 💾 Logging & Audit Logs
   Use `stageFile`, `assign`, and custom logs to track transactions. Clean up logs periodically.
7. ⏱️ Use Schedule Integrations Wisely
   For data synchronization, schedule integrations should be lean, time-boxed, and monitored.
8. 📥 Avoid Large Payloads in App-Driven Flows
   Split or paginate large data loads to avoid memory/timeout issues.
9. 🔁 Use FBDI & REST Adapters Where Possible
   For Oracle SaaS, prefer **FBDI bulk loads** or REST APIs to standard SOAP services.
10. 📚 Maintain Documentation
    Maintain a project wiki with connection details, business logic, version history, and issue tracking.

---

🧠 Developer Tips

• Use inline expressions instead of multiple `assign` blocks.
• Cache frequently used data (e.g., tokens, org values) where appropriate.
• Set up alert emails on failure using Notification Actions.
• Use Lookup tables for dynamic mappings.

---

⚙️ Deployment & Lifecycle Practices

• Use **version control**: Export integrations regularly and store in Git.
• Tag each deployment with a meaningful version and change note.
• Always **test in a staging environment** before moving to production.

---

🔍 Monitoring & Maintenance

• Use **Insight** dashboards to monitor business KPIs.
• Set retention policies to manage historical instance logs.
• Use Integration Agent for on-prem connectivity health monitoring.

---

📚 Useful Resources

• Oracle Integration Cloud Gen3 Documentation
• Oracle Integration Blog
• More posts on Oracle OIC & EBS

---

💬 Need Help or Want to Share Tips?

Have best practices to share or looking for help with your OIC integration? Drop a comment or reach us via our Contact Page.

🚚 Essential Setups in Oracle Fusion SCM for Implementation

Oracle Fusion Supply Chain Management (SCM) integrates key modules—Procurement, Inventory, Order Management, Logistics, and Manufacturing—to help implement a seamless enterprise process. These are the key setup tasks to complete in the Functional Setup Manager.

---

🔧 Core SCM Setup Tasks

1. Enterprise Structure Setup
   Define Legal Entities, Business Units, Inventory Organizations (Warehouses), and Chart of Accounts.
2. Inventory Management Setup
   Configure Organizations, Subinventories, Items, UOMs (Units of Measure), Transaction Defaults, and Receiving Parameters.
3. Product Information Management (PIM)
   Set up Item Classes, Catalogs, Attributes, Item Rules, and Lifecycle Phases.
4. Procurement Setup
   Register Suppliers, define Purchasing Categories, Approval Rules (BPM), and Document Preferences.
5. Order Management
   Configure Order Types, Fulfillment Lines, Pricing Strategies, ATP rules, and Event Triggers.
6. Shipping & Logistics
   Define Carrier options, Shipping parameters, Freight terms, and Delivery workflows.
7. Manufacturing Setup
   Establish Work Centers, Resources, Routings, Operations, and Bill of Materials (BOMs).

---

🌐 Cross-Module Configuration Essentials

• Value Sets – Used for Flexfields and validation logic.
• DFF / KFF (Descriptive & Key Flexfields) – To capture custom business data fields.
• Lookups – Custom dropdown options for wide-range data input.
• Approval Rules – Configured via Oracle BPM for workflow automation.
• Document Sequences – For invoice numbers, purchase orders, etc.

---

🔍 How to Access Setup Tasks

Navigate to Navigator → Setup and Maintenance
You must have the Application Implementation Consultant role to access task lists.

Select relevant SCM offerings (such as Inventory, Procurement, OM) and generate guided task lists that follow Oracle’s recommended implementation sequence.

---

📝 Best Practices for Smooth Implementation

1. Plan your enterprise structure (ledgers, business units, inventory orgs) in advance.
2. Complete foundational setup before configuring advanced modules.
3. Create standard item catalogs early to support functional processes.
4. Validate approval workflows and document routing in sandbox/UAT environments.
5. Use FBDI or REST API if you have bulk or ongoing data load requirements.
6. Document each configuration step along with screenshots and business context.
7. Review configurations regularly and plan for periodic audits.

---

📚 Trusted Resources

• Oracle SCM Cloud Official Documentation
• Oracle Functional Setup Manager (FSM) Setup Guide
• Visit our blog for more Oracle tutorials

---

💬 Feedback or Need Help?

Have implementation questions or need guidance? Please visit our Contact us page or leave a comment below.

how to transfer the bi or otbi report from one insance to other instance

🔁 How to Transfer OTBI/BI Reports Between Oracle Cloud Instances Using Archive & Unarchive

Migrating OTBI or BI reports from one Oracle Fusion Cloud instance (like DEV ➡️ TEST ➡️ PROD) can be done using the built-in Archive and Unarchive options. This ensures smooth portability of custom reports, dashboards, prompts, and folders without rebuilding them manually.

---

🟢 Step 1: Access Reports & Analytics in the Source Instance

Log in to the source Oracle Cloud instance (e.g., Development), then navigate to:

• Navigator >> Tools > Reports and Analytics
• Click on Browse Catalog

🟢 Step 2: Archive the Report or Folder

Locate the OTBI report or folder you want to migrate. Right-click on the item and select "Archive".

• This will download a .catalog archive file (e.g., SupplierReport.catalog)
• You can archive individual reports or entire folders for bulk migration

🟢 Step 3: Log in to the Target Instance

Now, switch to the target instance (e.g., TEST or PROD).
Again go to: Navigator >> Tools > Reports and Analytics > Browse Catalog

🟢 Step 4: Unarchive the Report

In the target instance, navigate to the folder where you want to upload the report.
Right-click in the empty space or folder, then choose "Unarchive".

• Select the .catalog file downloaded in Step 2
• Choose whether to overwrite existing content (optional)

🟢 Step 5: Validate & Run

After unarchiving, open the report to ensure it:

• Appears in the right location
• Uses valid subject areas and data sources
• Displays accurate results with no errors

💡 Pro Tips

• Use Archive for backup before editing live reports
• Always test the report in the target instance before releasing to users
• Retain folder structure and naming conventions for easier navigation

✅ Summary

The Archive and Unarchive features in Oracle OTBI make report transfers between environments fast, consistent, and error-free. Use them to streamline your deployment cycle and avoid rework.

👍 Was this helpful? Share your thoughts or let us know if you'd like a video walkthrough too!

Sample OTBi Report in Oracle Cloud

📊 How to Create Supplier Details OTBI Report in Oracle Cloud

Oracle Cloud provides a powerful feature known as OTBI (Oracle Transactional Business Intelligence), which enables real-time ad-hoc reporting. In this post, we will guide you through the steps to create a Supplier Details report using OTBI.

---

🟢 Step 1: Login to Oracle Cloud

Log in to your Oracle Cloud Application with appropriate credentials.

🟢 Step 2: Navigate to Reports and Analytics

Go to Navigator >> Tools > Reports and Analytics

🟢 Step 3: Choose How to Create Analysis

You can either:

• Click Reports >> Analysis
• OR go to Browse Catalog to create your analysis manually

🟢 Step 4: Browse to Desired Folder

Click on Browse Catalog and navigate to the folder where you want to save the report (e.g., Shared Folders > Custom > Reports).

🟢 Step 5: Click “Create > Analysis”

In the selected folder, click on Create and choose Analysis from the options.

📌 What’s Next?

After this, you’ll be prompted to select a subject area, such as Procurement – Suppliers Real Time. From there, you can drag and drop fields like Supplier Name, Supplier Number, Status, and more to design your OTBI report.

✅ Summary

• OTBI is a powerful tool for real-time reporting in Oracle Cloud.
• You can easily create a Supplier Details report by following the steps above.
• Use Subject Areas to pull in required supplier fields.

Have questions or want more sample reports? Let us know in the comments below!

OIC integration failing at connection level with message invalid security

---

🔐 Fixing the "Invalid Security" Error in Oracle Integration Cloud (OIC)

Published on: July 26, 2025
Author: [Aks]

---

🚨 Introduction: Struggling With "Invalid Security" in OIC?

Oracle Integration Cloud (OIC) is powerful—but nothing derails your integration flows faster than the dreaded:

⚠️ “InvalidSecurity: Error in processing the WS-Security security header”

This error is frustrating, vague, and often pops up during connection setup or runtime. But don’t worry—this post walks you through why it happens and how to fix it for good.

---

🧠 What Does "Invalid Security" Actually Mean?

This error generally signals a security mismatch between OIC and the external service you're connecting to. Common culprits include:

• ❌ Incorrect authentication (username/password or OAuth tokens)

• ❌ Mismatched security policies

• ❌ Missing or outdated certificates

• ❌ Connectivity agent or network/firewall issues

---

✅ The FIX That Worked: Refreshing Connection Metadata

After extensive troubleshooting, here’s what fixed the problem:

🔧 Steps:

1. Go to Connections in your OIC dashboard.

2. Find the failing connection.

3. Click on the three dots (⋮) on the right side.

4. Choose "Refresh Metadata".

🧹 Refreshing metadata ensures OIC re-reads the target system’s latest security headers, WSDL, and policy information.

---

🧪 Root Causes and How to Solve Them

Here’s a quick reference guide on what might be going wrong and how to fix it:

⚠️ Cause	🛠️ How to Fix It
Expired or invalid credentials	Double-check username/password or OAuth tokens. Avoid Basic Auth if MFA is enabled.
Security policy mismatch	Make sure OIC’s security policy matches what the target system expects.
Missing certificates	Upload needed SSL or intermediate certs (like msft.cer) to OIC’s trust store.
Connectivity agent config	Validate InstallerProfile.cfg and host resolution (/etc/hosts). Restart the agent.
Database adapter issues	Apply necessary DB patches (e.g., Patch 26482376) and confirm wallet configuration.
Network/firewall issues	Ensure no firewall or VCN rule is blocking your target URL.

---

🔎 Step-by-Step Troubleshooting Guide

Want to go deeper? Follow this order:

1. ✅ Verify credentials

2. 🔐 Match security policy

3. 📜 Import certificates

4. 🔌 Check agent config

5. 🧩 Resolve database issues

6. 🌐 Test endpoint accessibility

7. 📝 Enable and review trace logs

---

🛡️ Best Practices to Avoid This Error in the Future

• 🔄 Rotate credentials and update certs regularly

• 🔐 Use OAuth over Basic Auth where possible

• 🔍 Monitor error logs and set up alerts in the OIC console

• 🧪 Test in non-production before deployment

• 📦 Apply Oracle patches and keep adapters up-to-date

---

📘 References & Resources

• Oracle Troubleshoot Integration Runtime

• Known OIC Issues

• Managing Integration Errors

• Oracle Support Doc - Error Calling Fusion WebService

---

✅ Final Words

The "Invalid Security" error is solvable—and in many cases, it’s just outdated metadata causing the issue. Refresh the connection, validate your policies, and follow the checklist above for a smooth integration experience.

OIC interview questions and answers

• titled “Oracle Integration Cloud (OIC) – Interview Questions

  ---

  🌐 Oracle Integration Cloud (OIC) – Interview Questions & Answers

  🗓 Updated: March 11, 2025
  👨‍💼 Author: [Your Name or Company Name]

  ---

  💡 What is Oracle Integration Cloud (OIC)?

  Oracle Integration Cloud (OIC) is a powerful Platform as a Service (PaaS) that helps organizations connect applications, automate processes, and streamline data integration across cloud and on-premise systems.

  🧱 Key OIC Components:

  • 🔄 Integration Cloud Service (ICS): Build and run integrations

  • 🧰 Visual Builder Cloud Service (VBCS): Low-code app development

  • 🔁 Process Cloud Service (PCS): Automate workflows and business processes

  ---

  🔁 Common Integration Patterns in OIC

  Pattern	Description	Example
  Scheduled Orchestration	Triggers integration on a timed schedule	🕓 Run every 4 hours to import journal files via FTP
  App-Driven Orchestration	Starts via API or external event	🛒 REST endpoint receives order, pushes to ERP
  Basic Routing	Direct data flow with simple mapping	👥 Send HCM employee data to Fusion Apps
  File Transfer	Moves files across systems	💰 Upload payment files to bank FTP
  Publish to OIC	Sends messages to internal OIC topics	📣 Broadcast a payload to subscribers
  Subscribe to OIC	Listens to topic messages	📥 Inserts data into a DB when message arrives

  ---

  🔍 Key Differences: Basic Routing vs App-Driven Orchestration

  Feature	Basic Routing	App-Driven Orchestration
  Use Case	Simple 1:1 integration	Complex logic with conditions
  Components	Single mapping	Orchestration with loops, switches
  Example	Employee sync	Order processing workflow

  ---

  🧩 Essential OIC Components Explained

  🔌 Adapters:

  • File Adapter – Works via agent, supports files up to 10 MB.

  • FTP Adapter – Directly connects to FTP; supports 1 GB+ files.

  • Database Adapters (ATP/DBaaS) – Uses wallets/agents for secure connections.

  🌉 Connectivity Agent:

  • Secure bridge between OIC and on-prem systems (HTTPS, port 443).

  • Limits: 10 MB per payload (can segment large files).

  • Install via: java -jar connectivityagent.jar (after setting InstallerProfile.cfg)

  🧾 ERP Cloud Adapter:

  • Requires roles: Integration Specialist, SOAOperator.

  • Configure CSF Key for callback support.

  • Use metadata refresh if catalog sync lags (~30 mins wait time).

  ---

  🔬 When to Use ERP Adapter vs. Generic Adapters

  Use ERP Cloud Adapter	Use SOAP/REST Adapters
  ✔️ Pre-built catalog/API	✔️ Custom or unsupported APIs
  ✔️ Built-in callback support	❗ Manual XSD/JSON import required

  ---

  🚀 Advanced Features and Patterns

  📥 FBDI Integrations

  • Use for bulk file uploads into Fusion ERP

  • Supports callback status monitoring

  🧮 Global Variables & Data Stitching

  • Define reusable variables (primitive or complex types)

  • Use ASSIGN, APPEND, REMOVE in Stitch for payload manipulation

  🧯 Error Handling

  • Try-Catch per scope + Global fault handler

  • Use Throw for custom faults, Rethrow to escalate

  • Use “Parking Lot Pattern” for async error resubmission

  📊 Logging & Monitoring

  • Use short-term OIC logger or persist logs in DB/VBCS

  • Implement “heartbeat” checks for external endpoints

  ---

  🧪 Versioning, CI/CD & Feature Flags

  • Semantic versioning (v1.0.2, v2.3.1, etc.)

  • Automate deployments via OIC REST APIs

  • Integrate with GitHub/Jenkins for CI/CD

  • Feature flags progress from Internal → Controlled → GA (log SR for early access)

  ---

  🔐 Security & Certificates

  • OIC integrates with IDCS SSO

  • Use Service Accounts for system-to-system calls (bypass SSO)

  • Import 3rd-party SSL certificates via:
    Settings → Certificates → Import

  ---

  📦 Lookups & Packages

  • Lookups = Domain constants/value maps

  • Packages (.par) = Group and export integrations across environments

  ---

  🎯 Interview Tips & Focus Areas

  🎤 Topics to Highlight:

  • Real-world use cases: FTP → ERP file imports, retry patterns

  • Error handling strategies (sync vs async)

  • SOAP vs REST, XSDs, and when to use each

  • Queues vs Topics in Publish/Subscribe

  • REST verbs (GET, POST, PUT, DELETE)

  • CI/CD implementation with OIC APIs

  🧠 Troubleshooting Knowledge:

  • Metadata refresh for stale WSDLs

  • Dealing with agent connection failures

  • Handling locked or suspended integrations

  ---

  📚 Final Thoughts

  Oracle Integration Cloud (OIC) continues to be a cornerstone of enterprise cloud connectivity, and mastering it can unlock powerful automation and data orchestration capabilities. Preparing for an interview? Use this guide to solidify your fundamentals and demonstrate real-world knowledge with confidence.

  ---

  
  

OIC interview questions

---

🚀 Oracle Integration Cloud (OIC) Gen3 – Interview Q&A & Real-Time Insights

📅 Updated: July 26, 2025
✍️ By: Aks]

---

Oracle Integration Cloud (OIC) Gen3 is the latest evolution in Oracle’s cloud integration suite, bringing faster runtimes, enhanced observability, and a simplified development experience.

This blog addresses some frequently asked interview questions and real-time use case clarifications for professionals working with OIC Gen3.

---

🔁 1. What is the Difference Between FTP Adapter and File Adapter?

Feature	FTP Adapter	File Adapter
Use Case	Connects to FTP/SFTP servers	Accesses on-premise file systems
Deployment	Cloud-native	Requires OIC Connectivity Agent
Polling Support	✅ Yes	✅ Yes (via agent)
Transfer Type	Remote files over network	Local or network-shared files
Common Scenario	Download/upload files from a bank FTP	Reading data files from an on-premise legacy system

---

📦 2. What is FBDI Integration?

FBDI (File-Based Data Import) is Oracle Fusion’s standard method to load bulk data via interface tables using CSV/XML templates.

🔧 Typical FBDI Integration Steps:

1. Generate CSV file based on FBDI template (e.g., Suppliers, Journals).

2. Upload file to UCM (via ERP Cloud Adapter).

3. Invoke ERP Import job (e.g., Import Payables Invoices).

4. Monitor status and fetch results using callback or polling.

🧠 Tip: Always validate CSV structure and lookup codes before upload.

---

🔗 3. What Connections Are Required for FBDI Integration?

Connection	Purpose
ERP Cloud Adapter	Upload to UCM and run import jobs
FTP Adapter (Optional)	Retrieve CSV file from a remote location
SOAP Adapter	Callback/monitor import job status (if needed)
Email Adapter	Send notifications post import

---

📂 4. Does FTP Adapter Support Polling?

✅ Yes!

The FTP Adapter in OIC Gen3 supports file polling. You can configure:

• Directory path

• Polling frequency

• File patterns (e.g., *.csv)

• Archival/move after processing

👉 Use Cases: Fetching daily reports, invoices, or orders dropped by external systems.

---

🧮 5. How to Calculate the Top 2nd Salary (SQL)?

SELECT MAX(salary) AS second_highest_salary
FROM employees
WHERE salary < (
  SELECT MAX(salary) FROM employees
);

🔎 This query works by excluding the highest salary and fetching the next max value.

---

🔄 6. What is the Difference Between Synchronous and Asynchronous Integration?

Feature	Synchronous	Asynchronous
Client Waits?	✅ Yes	❌ No
Response Time	Immediate	Background / Delayed
Use Case	Real-time APIs	Bulk processing, FBDI, callbacks
Example	Get Employee Info by ID	Upload journal file, run job, send callback

---

🔃 7. Can We Convert Scheduled Integration to App-Driven?

🚫 No, this is not supported directly.

• Scheduled integrations are time-triggered and don’t accept external requests.

• You can recreate the flow logic in a new App-Driven integration.

🔧 Workaround: Copy artifacts and logic manually between integrations.

---

🔁 8. Can We Convert App-Driven to Scheduled Integration?

🚫 No, direct conversion is not supported.

• App-driven integrations are designed to be invoked by APIs or events.

• Scheduled integrations work on time-based triggers.

🛠 You must build a new scheduled integration with similar flow logic.

---

✨ Bonus Tip: Best Practices for OIC Gen3

• Use global fault handlers for robust error management.

• Group related integrations using lookup tables and packages.

• Schedule data purging for long-running integrations to keep performance optimal.

---

📌 Conclusion

OIC Gen3 offers robust capabilities for hybrid integrations, event-driven orchestration, and bulk data handling via FBDI. Understanding how adapters differ, how to design for sync/async patterns, and when to use scheduled vs app-driven flows is key for both developers and architects.

🔎 Whether you're preparing for an interview or implementing real-time use cases, mastering these patterns will give you a solid edge in working with Oracle Cloud integrations.

---

OTBi Reports Drill down Report

Here’s a visually enhanced blog post crafted for Blogspot or any modern CMS. It now includes screenshots to illustrate navigation and drilling behavior within OTBI.

---

📊 Creating Drill-Down Reports in OTBI (Oracle Fusion)

🗓 Updated: July 26, 2025
✍️ Author: [Aks]

---

🔍 What is OTBI Drill‑Down?

Oracle Transactional Business Intelligence (OTBI) offers interactive reporting within Oracle Fusion. With drill-down functionality, users can seamlessly transition from summary figures to detailed data—right from the same dashboard.

This guide shows you how to create interactive drill-downs using Action Links, transforming summary-level reporting into dynamic data discovery.

---

💼 Business Use Case: Supplier Invoices

Imagine a dashboard showing total invoice amounts by supplier. With a drill-down:

• Clicking a supplier name opens a detailed listing of invoices for that supplier.

• Enables self-service exploration without navigating multiple screens.

---

🛠 Step-by-Step: Build Drill‑Down in OTBI

Step 1: Summary Report (Summary Report)

• Select columns like:
  • Supplier Name
  • Invoice Count
  • Invoice Amount

• Save it as Summary Report

---

Step 2: Detail Report (Detail Report)

• Include granular fields:
  • Invoice Number
  • Invoice Date
  • Amount

• Add filter prompt:

  "Supplier"."Supplier Name" = @{SupplierName}
  

• Save as Detail Report

---

Step 3: Configure Action Link in Summary

In Summary Report:

1. Edit the Supplier Name column.

2. Go to Column Properties → Interaction.

3. Set Primary Interaction to Action Links.

4. Click Add Action Link:

   • Choose Navigate to BI Content

   • Select Detail Report

   • Map Supplier Name to @{SupplierName}

This creates the clickable link—from summary to detail.

---

✅ Test the Drill

• Run the Summary Report.

• Click on a Supplier Name—your Detail Report opens with filtered data.

• Ensure both reports are saved and reside in shared folders and use the same subject area.

---

🧯 Troubleshooting Tips

• Ensure the prompt variable in Detail matches the column name exactly.

• Both reports must use the same subject area.

• Confirm the Action Link mapping is correct.

• Use reports in dashboard view, not edit mode, for links to work properly.

---

📸 Visual Guide: Screens & Routing

1. Summary with action links on Supplier Name (Image 1)

2. Editing Action Link settings (Image 2)

3. Drilled detail report after click (Image 3)

4. Advanced drill via deep link configuration (Image 4)

These visual cues help navigate to the right settings and confirm linkage results.

---

📌 Tips & Extra Use Cases

• Extend drill-down to other fields like Business Unit, GL Period, Employee ID.

• For deeper analytics, create multi-level drill routines (e.g. invoice → payment status).

• Consider deep links to Fusion application pages for direct navigation—especially for expense reports or project cost details (docs.oracle.com, oracle.com, kaamilant.com, oracle-hub, tangenz.com, docs.oracle.com).

---

🚀 Why Drill‑Down Reports Deliver Value

• Enables self-service data exploration directly within OTBI.

• Eliminates manual extracts or duplicate report generation.

• Streamlines workflows by allowing navigational depth without leaving dashboards.

OIC GEN 3 ISSUES - Fixing NXSD Schema "No Data Found" or "No File to Process" Errors

🧠 Oracle Integration Cloud – Fixing NXSD Schema "No Data Found" or "No File to Process" Errors

📅 Updated: July 26, 2025
🔧 Category: Oracle Integration / File-Based Integrations
✍️ Author: Aks

---

⚠️ Problem Statement

You’ve built a file-based integration in OIC or SOA Suite using the NXSD schema (Native Format Builder). But during testing or runtime, you get errors like:

• “No data found or file is empty”

• “No file to process”

• “NXSD parser error – Data is not present in expected format”

---

🧪 Common Symptoms

• The integration completes with warning or faulted status.

• Logs or activity stream shows:

  JCA-11611: Failed to parse file.
  Reason: Data not present in expected format.
  

• No records are inserted or mapped.

• You receive a blank payload or <null> in the target node.

---

🔍 Root Cause

These issues almost always boil down to mismatch between your NXSD schema definition and the actual data in the file.

💡 NXSD (Native eXternal Schema Definition) is used in OIC/SOA to parse flat files (CSV, TXT, fixed-length, etc.). It acts like an XSD for non-XML data.

---

🛠️ Step-by-Step Fix Guide

✅ 1. Check File Format vs Schema

• Open your file and compare:

  • Delimiter used (comma, pipe, tab)

  • Number of fields per line

  • Presence of header rows

• Match these against the NXSD schema (.xsd with NXSD annotations).

📎 Example: If your NXSD expects 5 fields but the file contains 6, parsing will fail.

---

✅ 2. Validate NXSD Schema in JDeveloper or OIC

• If using JDeveloper:

  • Right-click NXSD file → Run Native Format Tester

  • Load sample data → See if parsing works

• In OIC, download and test file locally or review logs from the Activity Stream.

---

✅ 3. Set Correct Record Delimiter and Field Count

In NXSD definition:

• Check recordSeparator, e.g., \n, \r\n

• Ensure each <element> tag matches a field in the row

• If the file has blank lines or extra separators, parsing may break

<nsxsd:element name="Employee">
  <nsxsd:field name="EmpId"/>
  <nsxsd:field name="Name"/>
  <nsxsd:field name="Salary"/>
</nsxsd:element>

---

✅ 4. Use IgnoreEmptyLines="true" (Optional)

Add this attribute to <nxsd:format> if your file has blank lines:

<nxsd:format name="MyFormat" type="delimited" delimiter="|" ignoreEmptyLines="true" />

---

✅ 5. Watch for Header Rows

If your file contains headers, you must skip them:

<nxsd:format name="Header" skipLines="1" ... />

Alternatively, handle this in OIC using the file adapter configuration (uncheck “First row as header”).

---

✅ 6. Validate File Encoding

• Ensure your file is UTF-8 encoded (especially if created in Excel or external systems)

• Use Notepad++ or VS Code to confirm encoding

---

✅ 7. Use File Test Flow

If you're unsure, create a dummy integration that reads the file and logs its content. This helps isolate whether the error is with:

• File reading

• NXSD parsing

• Mapping logic

---

🔄 Example: Fix for a 3-Column CSV with Pipe Delimiter

✅ Input File

101|John Smith|65000
102|Lisa Wong|72000

❌ Common Mistake in NXSD

Using comma , instead of pipe |:

<nxsd:format delimiter="," />

✅ Corrected NXSD Snippet

<nxsd:format delimiter="|" recordSeparator="\n" />
<nxsd:element name="Employee">
  <nxsd:field name="EmpId"/>
  <nxsd:field name="Name"/>
  <nxsd:field name="Salary"/>
</nxsd:element>

---

📋 Summary Table

Issue	Possible Fix
File is blank	Check if file is being dropped correctly
File delimiter mismatch	Update NXSD with correct `delimiter="
Unexpected number of fields	Match schema elements with actual columns
Blank lines in file	Use ignoreEmptyLines="true"
File includes headers	Use skipLines="1" or handle via File Adapter UI
Encoding issues	Convert file to UTF-8

---

🎯 Conclusion

NXSD schema parsing issues can be frustrating but are often caused by small misconfigurations. By validating your file structure, NXSD definitions, and adapter settings, you can quickly isolate and fix the issue.

✅ Always test your schema with sample data and use logging and tracing to confirm what’s being parsed.