Request for utility to identify BI Publisher reports referencing impacted tables after patching

Anu Kumari

Description:
After major quarterly updates (for example, the 26A update), certain seeded and custom BI Publisher reports may fail if underlying Oracle Fusion application tables are modified—such as when new columns are introduced or existing columns are changed.
Currently, there is no delivered feature that allows customers to easily identify which BI Publisher Data Models are querying a specific application table.

Due to large numbers of BI Publisher reports exist across environments. Manually opening each Data Model to search for table references (e.g., inv_transaction_lot_numbers) is not scalable and may cause delays in post‑update validation.

We request an Oracle-delivered feature that can:

• Search across all BI Publisher Data Models for SQL queries referencing a specific Fusion application table
• Provide a list of affected reports prior to or immediately after a quarterly update
• Help customers assess impact when patches introduce new fields or structure changes
• Reduce report failures and manual troubleshooting effort
• Improve readiness for quarterly updates by identifying dependent BIP reports in advance

Such a utility would greatly support proactive regression testing and reduce post‑update breakages, especially for customers with high report volume.