ETL9.2: Payable Time Already In TP (Taken By Payroll) Status Is Duplicated When Time Submitted From Rapid Time for Same DUR (Date Under Report) (Doc ID 3001434.1)

Last updated on JUNE 10, 2024

Applies to:

Symptoms

Submitting time from Rapid Time with a TRC (Time Reporting Code) that results in an exception, on a date for which previously submitted time was approved and taken by payroll, results in a duplication of the originally submitted and processed time.

Steps to replicate the issue:
Initial settings:
Both TRC’s used always require approval and approvals are based on Payable Time.
The first TRC is submitted, approved, and taken by payroll before submitting the second entry for the DUR.
The second TRC is submitted via Rapid Time and results in an exception.
Both TRC’s are submitted for the same date.
The TL Installation Table option to run Time Administration when time is submitted is selected (navigation: Set Up HCM > Install > Product Specific > Time and Labor Installation).

1. Navigate to Manager Self Service > Team Time > Enter Time and remove all entries from the timesheet for employee, submit.
2. Navigate to Main Menu > Time and Labor > Process Time > Request Time Administration and run TL_TIMEADMIN process.
3. Navigate to Set Up HCM > Product Related > Time and Labor >Time Reprting Codes-TRC
    Change TRC KUREG and TRC KUMLO to always require approval. For simplicity, I added a new row dated 12/1/2021.
4. Navigate to Setup HCM > Product Related > Time and Labor > Validation Criteria > Exception Definition and add a new exception that is "high" and "allowable".
5. Open Application Designer tool and add a new section/step/action in AE program TL_TR0012900 for the new exception so that it applies only for this test case.
6. Navigate to Set Up HCM > Product Related > Time and Labor > Validation Rule and create a Validation Rule for the new exception.
7. Navigate to Set Up HCM > Product Related > Time and Labor >Validation Set and include the new Validation Rule in the ST_ALL Validation Set.
8. Navigate to Set Up HCM > Install > Product Specific > Time and Labor Installation and change TL Installation Table setting to run Time Administration when time is submitted.
9. Log in as the manager. Navigate to Time and Labor > Report Time > Rapid Time and create a Rapid Time session with one row of data for the employee, with TRC = KUREG, 8 hours. Submit the session.
10. When the Rapid Time process completes, a row will have been created in PS_TL_RPTD_TIME with a REPORTED_STATUS = 'SB', a row in PS_TL_APP_PAY_XRF, and a row in PS_TL_PAYABLE_TIME with PAYABLE_STATUS = 'NA' (needs approval).
11. Log in as the manager and approve the time for KUREG for the employee. Approving all of the lines is also OK.
12. Load the approved time to payroll. 
13. Log in as the manager.  Navigate to Time and Labor > Report Time > Rapid Time and create a Rapid Time session with one row of data for the employee, with TRC = KUMLO, 1 hour.
     Submit the session. This will create the new high/allowable test exception created above. It will also cause PS_TL_PAYABLE_TIME.ORIG_SEQ_NBR to be set equal to SEQ_NBR on the KUREG line. Note, too, that a corresponding offset row is not produced.
14. Login as the manager and allow the test exception that was produced for TRC = 'KUMLO' in the previous step.
15. Navigate to Main Menu > Time and Labor > Process Time > Request Time Administration and run TL_TIMEADMIN for the employee. 
16. Review the results in PS_TL_PAYABLE_TIME. A new row, with a new SEQ_NBR, and ORIG_SEQ_NBR for KUREG is produced, along with a row for KUMLO, both with PAYABLE_STATUS = 'NA'.
17. Since the transaction for 8 hours of KUREG was already taken by payroll, this results in a duplicated payment if the second instance is approved.

Cause

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