Tag: Oracle BI

  • Why OTBI Isn’t Showing Your CoA (And How to Fix It Fast)

    Why OTBI Isn’t Showing Your CoA (And How to Fix It Fast)

    Introduction

    One of the most common frustrations in Oracle Fusion OTBI reporting occurs when Chart of Accounts segments fail to appear correctly within subject areas. Organizations often expect all configured segments to appear automatically, only to discover that OTBI displays only limited dimensions or incomplete hierarchy information.

    Fortunately, this issue is usually caused by missing configuration steps related to hierarchy flattening, BI-enabled segments, flexfield deployment, or BI metadata synchronization.

    This guide walks through the key Oracle Fusion OTBI configuration steps required to correctly expose Chart of Accounts segments and hierarchies within OTBI subject areas.

    Watch the Webinar

    Understanding OTBI Subject Areas

    Out of the box, Oracle Fusion OTBI subject areas typically display three mandatory Chart of Accounts segments:

    • Balancing Segment
    • Cost Center Segment
    • Natural Account Segment

    These dimensions are required within Oracle General Ledger.

    Additional Chart of Accounts segments may appear automatically if organizations used Rapid Implementation during initial setup. However, manually configured environments often require additional OTBI configuration steps before custom segments become visible.

    Step 1: Flatten Your Account Hierarchies

    One of the most important configuration steps is hierarchy flattening.

    For each Chart of Accounts segment:

    1. Ensure one hierarchy version is active
    2. Navigate to Actions
    3. Select Flatten
    4. Select Column Flattening

    This process denormalizes hierarchy relationships so OTBI can query parent-child relationships more efficiently.

    Hierarchy flattening should be rerun whenever hierarchy maintenance occurs.

    Without flattening:

    • hierarchy rollups may fail
    • reporting structures may appear incomplete
    • OTBI performance may degrade

    Step 2: Publish Account Hierarchies

    After flattening hierarchies, organizations must publish hierarchy data.

    Publishing makes hierarchy metadata available to Oracle reporting tools including:

    • OTBI
    • SmartView
    • Financial Reporting Studio

    Failing to publish hierarchies often prevents reporting dimensions from appearing correctly.

    Step 3: Create Segment Labels

    For non-qualified Chart of Accounts segments, organizations must create segment labels.

    This configuration step maps Oracle flexfield segments into BI reporting structures.

    A critical requirement is the BI Object Name format.

    For General Ledger segments, BI Object Names must follow this exact naming convention:

    • Dim – GL Segment1
    • Dim – GL Segment2 through Dim – GL Segment10

    This naming syntax is extremely sensitive.

    One common issue occurs when Microsoft Word or PowerPoint automatically converts:

    • en dash (-)

    into:

    • em dash (—)

    Oracle requires the standard en dash format.

    Incorrect character formatting can prevent OTBI configurations from functioning correctly.

    Budgetary Control Differences

    Budgetary Control configurations differ from General Ledger configurations.

    Unlike General Ledger:

    • Budgetary Control has no mandatory segments
    • only 10 BI dimensions are available
    • naming conventions use XCC instead of GL

    Budgetary Control BI Object Names must use:

    • Dim – XCC Segment1
    • through
    • Dim – XCC Segment10

    Organizations should carefully plan Budgetary Control segment usage because only 10 dimensions are available.

    Step 4: Assign Labels to CoA Segments

    Once labels are created:

    1. Navigate to Manage Structures
    2. Edit the Chart of Accounts structure
    3. Assign newly created labels to the appropriate segments

    This connects Oracle flexfield structures to BI reporting metadata.

    Step 5: Enable BI and Attach Hierarchies

    Next, organizations must verify that each segment is:

    • BI Enabled
    • associated with a hierarchy

    Navigate to:

    Manage Structure Instances

    Then:

    1. Edit the structure instance
    2. Verify BI Enabled is checked
    3. Attach the appropriate hierarchy

    Without these settings, segments may fail to appear inside OTBI subject areas.

    Step 6: Deploy the Flexfield

    After configuration changes are completed:

    1. Navigate to Manage Chart of Accounts Structures
    2. Select Deploy Flexfield

    Deploying the flexfield pushes configuration changes into Oracle Fusion metadata structures.

    Organizations frequently miss this step, causing reporting configurations to remain unavailable.

    Step 7: Run Required Scheduled Processes

    Two critical scheduled processes must be executed after configuration changes.

    Create Rules XML File for BI Extender Automation

    Navigate to:

    Scheduled Processes → Schedule New Process

    Run:

    Create Rules XML File for BI Extender Automation

    Parameter:

    • Essbase Application = your Chart of Accounts

    Wait for this process to complete fully before proceeding.

    Import Oracle Fusion Data Extensions for Transactional Business Intelligence

    Next run:

    Import Oracle Fusion Data Extensions for Transactional Business Intelligence

    Parameter:

    • ERP

    This process may take significant time to complete depending on environment size.

    Even empty environments may require approximately one hour.

    Subject Areas Affected

    Once configurations are completed successfully, additional segments become available across multiple Oracle Fusion subject areas.

    Affected Financials subject areas include:

    • General Ledger – Journals Real Time
    • General Ledger – Transactional Balances Real Time
    • Payables Invoices – Transactions Real Time
    • Receivables – Transactions Real Time
    • Receivables – Receipts Details Real Time

    Additional Procurement and Projects subject areas may also expose new dimensions.

    Fixed Assets Configuration Differences

    Fixed Assets configurations behave differently from General Ledger configurations.

    Key Asset Flexfields include:

    • CAT# for Asset Category
    • LOC# for Asset Location
    • KEY# for Asset Key

    Unlike General Ledger:

    • hierarchy flattening is not required
    • hierarchy publishing is not required

    Organizations should understand these differences before attempting to troubleshoot Fixed Assets OTBI issues.

    Common OTBI Configuration Mistakes

    Common OTBI configuration issues include:

    • hierarchy flattening not completed
    • hierarchy publishing skipped
    • BI Enabled not checked
    • incorrect BI Object Name formatting
    • flexfields not deployed
    • scheduled processes not executed
    • incorrect segment label assignment

    Most OTBI reporting visibility issues trace back to one or more of these configuration gaps.

    Final Thoughts

    Oracle Fusion OTBI reporting relies heavily on proper Chart of Accounts configuration, hierarchy management, flexfield deployment, and BI synchronization.

    When configurations are performed correctly, organizations gain significantly improved reporting flexibility across:

    • General Ledger
    • Payables
    • Receivables
    • Procurement
    • Projects
    • Budgetary Control

    Understanding the relationship between Oracle flexfields, hierarchies, BI metadata, and scheduled processes is critical for building scalable Oracle Fusion reporting environments.

    Related Oracle Topic Hubs

    About Afternoons With ACEs

    Afternoons With ACEs provides practical Oracle Fusion implementation expertise from Oracle ACE Professionals Lee Briggs and Thomas Simkiss.

    Sessions focus on:

    • enterprise ERP best practices
    • Oracle Fusion implementation strategy
    • reporting and analytics
    • SmartView
    • OTBI
    • testing and governance