Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 43 Oracle Analytics and AI Sharing Center
- 19 Oracle Analytics and AI Lounge
- 283 Oracle Analytics and AI News
- 59 Oracle Analytics and AI Videos
- 16.3K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 108 Oracle Analytics and AI Trainings
- 20 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Enhancement Request: Full Historical Data Extraction for Payroll Balance/Costing Pipeline
The current implementation of the Payroll Balance Pipeline's full data load functionality limits data extraction to the three most recent years, regardless of an earlier date set in the "Initial Extract Date" parameter.
This behavior presents a significant operational challenge. Following mandatory Data Warehouse resets in our lower environments, we require the ability to reload the complete history of payroll and costing data from the HCM source to ensure data integrity. The current three-year limitation makes this impossible.
This functionality is also critical for addressing business needs that require older data, such as:
- Investigating and resolving historical payroll discrepancies that fall outside the three-year window.
- Fulfilling legal and compliance obligations that mandate access to a more extensive data history.
To resolve this, we propose that the pipeline be modified to honor the "Initial Extract Date" for all full data extractions. As an alternative, we suggest the addition of a new parameter that allows users to define the number of historical years to be imported.
Expect this functionality in both Non-PROD and PROD FDI environments.
Comments
-
Hi Anurag, thanks for bringing this up. In product development, every choice is a trade-off, and we want to ensure we’re making the right ones with you.
While a 3-year (12-quarter) window is the standard for high-performance analytics, we know that ‘standard’ doesn’t always cover every reality. To help us balance performance with depth, I’d love to dig deeper into the 'why' behind the need for longer history:
- Historical Discrepancies: Could you share a specific scenario where looking back beyond three years was critical?
- Legal Obligations: For those longer-tail mandates, what specific regulations are driving the timeline? We’re curious if granular data is a must, or if aggregates could meet the requirement.
Thanks & Hope all is well at your end
Manisha
1
