This content has been marked as final. Show 1 reply
I assume Oracle is doing this at the MONTHLY granularity for the BANDS. This allows a snapshot at the MONTHLY level to see the requisition age bands which helps from a performance standpoint. In your case, you can consider the following options:
- Manually create a report with the "Banding" that you need that reads the LOWEST grain requisition fact table. Depending on your data volumes, you may want to limit the ranges so that performance is not impaired. If you have a > 30 band, you may want to use the MONTHLY out of the box grain. Essentially, do not use the csv for this report banding.
- Customize the ETL process and add a separate table to represent your custom banding at a lower grain..this is a lot more work.
- Create a Materialized view on top of the lowest grain that has these custom bands..this will speed up performance. You will need to refresh this after each load.
If helpful pls mark correct or helpful