Oracle Fusion BIP: Customizing Seeded Reports the Right Way

 Oracle Fusion BIP: Customizing Seeded Reports the Right Way

When a client asks to see only specific columns in a Standard/Seeded BIP Report, you have two main paths. 

Choosing the right one depends on whether you want to change the View 

or 

the Engine.

Option 1: Create a Custom Layout (Recommended)

This is the "cleanest" approach. You keep the standard logic but change the visual output

The Move: Create a new Layout (RTF/Excel/Online) using only the required columns from the existing Seeded Data Model.

Why it wins: It’s low maintenance. Since you’re still using the seeded Data Model, you benefit from any logic updates Oracle pushes during quarterly patches.

Best for: When the data is already there, you just want it to look tidier.


Option 2: Customize the Data Model

This is a deeper "under the hood" change.

The Move: Copy the seeded Data Model to the Custom folder, edit the SQL script to remove unwanted columns, and link it to a new report/layout.

Why it wins: Performance. If the seeded query is pulling massive amounts of unnecessary data that slows down the report, trimming the SQL can speed things up.

Best for: Complex reports where performance is a bottleneck or where you need to add custom logic/joins.

Comments

Popular posts from this blog

Importance of Incremental Data in Oracle Fusion

REST Web Service in Oracle Fusion to manage Banks