OTBI custom report missing new order fields after patch deployment

ERP Oracle Fusion Cloud
, , , , , , , ,
1

After applying the latest patch in ofc-23c, our custom OTBI reports are missing several new order fields that were added through Application Composer. During QA regression testing, we discovered that reports which previously showed custom fields like ‘Customer Priority Level’ and ‘Expedite Reason’ now display blank columns.

The fields are visible in the Order Management UI and data is being captured correctly in the database. However, when we run OTBI reports using the ‘Sales Orders - Order Details’ subject area, these custom attributes don’t appear in the available fields list, and existing reports that reference them show null values.

We’ve tried refreshing the subject area metadata and clearing the OTBI cache, but the fields still don’t show up. The Application Composer configuration shows these fields as ‘Enabled for Reporting’, but something in the metadata synchronization seems broken. This is causing incomplete regression test results because we can’t validate that order data is being properly captured and reported. Anyone dealt with OTBI subject area refresh issues after patching?

system 2

I can provide a complete solution based on extensive experience with OTBI subject area issues after ofc-23c patches. The problem involves all three focus areas: subject area refresh, Application Composer settings, and metadata synchronization timing.

First, address the OTBI subject area refresh properly. The standard cache clear isn’t sufficient after patches that modify the underlying data model. Navigate to BI Administration > Manage BI Presentation Catalog > Subject Areas, select ‘Sales Orders - Order Details’, and perform a ‘Reload Files and Metadata’ operation. This is different from a simple cache refresh - it forces OTBI to rebuild the entire subject area structure from the current database schema.

Second, verify and correct Application Composer attribute settings. The patch may have reset the analytics integration flags. Go to Application Composer > Order Management > Orders > Custom Fields. For each missing field, check these specific settings: ‘Enable for Analytics’ must be checked, ‘Analytics Label’ must be populated (not blank), and critically, verify the ‘Subject Area Association’ field shows ‘Sales Orders - Order Details’. The ofc-23c patch sometimes clears this association even when the Enable flag remains checked. Re-save each field definition even if settings appear correct - this triggers a metadata update event.

Third, handle metadata synchronization properly with correct timing. After making Application Composer changes, you must wait for the scheduled ‘Analytics Metadata Sync’ job to complete before OTBI will recognize the changes. This job runs every 4 hours by default. To force immediate synchronization, navigate to Scheduled Processes > Schedule New Process > Analytics Metadata Synchronization, and run it manually. Monitor the process log to ensure it completes without errors - look specifically for messages about ‘Extended attributes synchronized’ and ‘Subject area metadata updated’.

The critical sequence is: (1) Verify Application Composer settings and re-save, (2) Run manual metadata sync job and wait for completion, (3) Perform OTBI subject area reload, (4) Clear browser cache and OTBI session cache, (5) Verify fields appear in the subject area field list before running reports.

For your specific issue with blank columns in existing reports, you need to edit each report and re-add the affected fields from the field picker. The patch changed the internal field identifiers, so old references no longer resolve correctly. Create new calculated fields in OTBI that reference the refreshed custom attributes, rather than trying to reuse the old field references.

One additional consideration for ofc-23c: Oracle changed how flexfield contexts are exposed in OTBI. If your custom fields use context-sensitive flexfields, you may need to modify the context value rules to ensure they’re included in the default context that OTBI queries. Check Oracle Support Note 2847392.1 for the specific flexfield context mapping changes introduced in 23c patches.

This draft is based on general Oracle Fusion Cloud knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

This usually happens when the OTBI metadata refresh doesn’t complete successfully after Application Composer changes. Check the BI Server logs for any errors during the subject area deployment. Also verify that the custom fields have the correct ‘Reporting Flag’ set in Application Composer - sometimes patches reset these settings.

4

Marcus, I checked the BI Server logs and found warnings about ‘unable to synchronize extended attributes’ during the last metadata refresh. The reporting flags in Application Composer are still set correctly though. Could the patch have changed how custom fields are mapped to the OTBI data model?

5

We saw similar issues in ofc-23c where patches modified the subject area structure without properly migrating custom field mappings. You need to manually republish the Application Composer sandbox and then perform a full OTBI metadata refresh, not just a cache clear. Also check if the custom fields are in a flexfield structure that needs to be explicitly added to the OTBI subject area through the BI Administration interface.

timothy_tech 6

Tested this on OFC-23C patch environment: the ‘Reload Files and Metadata’ on Sales Orders - Order Details subject area immediately surfaced the missing order fields in OTBI.

7

The problem might be that your custom fields are defined in a descriptive flexfield context that isn’t automatically included in the standard subject area. After patches, Oracle sometimes changes which flexfield contexts are exposed by default in OTBI. You’ll need to extend the subject area to include your specific flexfield context, or modify the field definitions to use a context that’s already exposed. Check the ‘Sales Orders Real Time’ subject area as well - sometimes custom fields show up there instead of the standard subject area after patches.

8

I’ve dealt with this exact scenario multiple times. The issue is that ofc-23c introduced changes to how Application Composer attributes are synchronized with OTBI subject areas. After patches, the metadata layer needs explicit refresh with proper sequencing. First, verify in Application Composer that your custom fields still have ‘Enable for Analytics’ checked. Then go to the sandbox and click ‘Publish Sandbox’ even if it shows no pending changes - this forces a metadata resync. Wait 15-20 minutes for the backend synchronization job to complete before attempting any OTBI operations.