My Oracle Support Banner

GPFRA: DSN Explanation of the Meta Sql DEL_RSLTM_FINALIZED - Why is Deleting the Extraction IDs for the Previous Runs from PS_GPFR_RSLT_TMP table? (Doc ID 2904672.1)

Last updated on OCTOBER 24, 2022

Applies to:

PeopleSoft Enterprise HCM Global Payroll France - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


When finalizing a DSN Monthly extraction, some tables are cleaned up.
In the case of table PS_GPFR_RSLT_TMP, the clean-up incorrectly deletes rows for any extraction id except the ones for the extract id that is being finalized.

Steps to replicate the issue:
Prerequisites for testing:
The Payroll process is run from: Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll > Calculate Absence and Payroll
The Monthly DSN is run from: Global Payroll & Absence Mgmt > Social Security/ Insurance > Run DSN Monthly Extraction FRA > DSN Monthly Run Page
1. Run Payroll for January 2022
2. Run Monthly DSN for January (do not finalize it)
3. Check the content of GPFR_RSLT_TMP
4. Run February 2022
5. Run Monthly DSN for February (do no finalize it)
6. Check the content of GPFR_RSLT_TMP
7. Now finalize execution of DSN for January
8. Verify the content of GPFR_RSLT_TMP

Expected result: the rows corresponding to February should not be deleted. For January, the table should have the rows corresponding to node S44.
Current result: System has deleted the rows corresponding to February (minus the ones for node S44). The rows for January are kept.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.