OTL: Post Upgrade To 12.2.12 Hours Becoming Null When Timecard Is Updated From A Custom Application Using Standard API HXC_TIMESTORE_DEPOSIT
(Doc ID 3061426.1)
Last updated on DECEMBER 04, 2024
Applies to:
Oracle Time and Labor - Version 12.2.12 and laterInformation in this document applies to any platform.
Symptoms
A custom web services SOA application is used to create or update timecards and it uses the standard hxc_timestore_deposit API.
Post upgrade from 12.2.4 to 12.2.12, when a timecard is updated from the custom Web Services application, it is making the hours null.
Example:
======
Before Timecard Update:
------------------------
Recent Timecards:
Status Transferred To Period Starting Period Ending Recorded Hours Submission Date
Approved None 08-Jul-2024 14-Jul-2024 16 18-Jul-2024
Timecard Details:
Project Task Type 08-Jul 09-Jul 10-Jul 11-Jul 12-Jul 13-Jul 14-Jul Total
xxxxx xxx xx 4 4 8
xxxxx xxx xx 4 4 8
++ In the custom application, hours for 12-Jul changed from 4 to 6 and submitted.
After Timecard Update:
-------------------------------
Recent Timecards:
Status Transferred To Period Starting Period Ending Recorded Hours Submission Date
Approved None 08-Jul-2024 14-Jul-2024 16 23-Jul-2024
Timecard Details:
Project Task Type 08-Jul 09-Jul 10-Jul 11-Jul 12-Jul 13-Jul 14-Jul Total
xxxxx xxx xx 4 Null 8
xxxxx xxx xx 4 Null 8
++ When timecard update is submitted, the call is made to hxc_timestore_deposit.update_building_block.
++ However, there is no issue using the standalone API.
STEPS:
--------
1) Responsibility: Self Service Time
2) Enter and submit a timecard
3) From custom application, edit or update the timecard and submit triggering hxc_timestore_deposit.update_building_block
4) Check the timecard data in Self Service responsibility
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |