Common Types of Timecard Data Corruptions
(Doc ID 2335722.1)
Last updated on JUNE 21, 2023
Applies to:
Oracle Time and Labor - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : All version, Oracle Time and Labor Rules
Frequently it is reported that the data as it appears on the timecard is not correct and does not correspond to what has been retrieved by the recipient application.
Further investigation using the OTL Analyzer may show the following types of data corruption :
1. Active Detail / Inactive Day
Time_Building_Block_Id Object_Version_Number Det_Date_To Day_Date_To
xxxxxxxx 1 31-DEC-4712 00:00 14-NOV-2017 14:49
yyyyyyyy 1 31-DEC-4712 00:00 14-NOV-2017 14:49
2 Rows Selected
Error: You have data corruption issue in this timecard.
Please log a service request with Oracle Support showing them this section in the output to ask a data fix from development.
2.Duplicate Translation display keys
Translation_Display_Key - Duplicates
Active Detail / Inactive Day
and potentially due to the above errors also see:
These Expenditure Item Ids are linked to an Object Version Number of a Time
Building Block ID that do not exist in the original OTL Timecard
3.Translation display keys for the wrong line
Translation_Display_Key - Wrong Line
Time_Building_Block_Id Translation_Display_Key Detail_Row Attribute_Category
Attribute1 Attribute2 Attribute3 Attribute4 Attribute5 Attribute6 Attribute7
xxxxxxxx aaaaaaa|1|5 1 PROJECTS 134 358016 Time GB ST N
yyyyyyyy aaaaaaa|1|1 1 PROJECTS 152 6632 Lunch GB ST N
zzzzzzzz aaaaaaa|1|3 1 PROJECTS 152 6632 Lunch GB ST N
...
Error: You have data corruption issue in this timecard. Please refer to the following notes:
- Note: 1547463.1 Profile OTL: Debug Check Enabled
- Note: 1462822.1 After Editing Timecard by Nulling Out Hours, Timecard Gets Corrupted
And we strongly recommend that you log a service request with Oracle Support showing them this section in the output.
4.Translation_Display_Key - Wrong Day
TIMECARD_ID RESOURCE_ID START_TIME TIME_BUILDING_BLOCK_ID DAY DAY_TDK DET_TDK
CORRECT_SEGMENT3
aaaaaaa 8087 10-SEP-2017 00:00 20313399 16-SEP-2017 00:00 13822|0|3
13822|2|3 6
aaaaaaa 8087 10-SEP-2017 00:00 20313400 15-SEP-2017 00:00 13822|0|2
13822|1|2 5
aaaaaaa 8087 10-SEP-2017 00:00 20313401 14-SEP-2017 00:00 13822|0|1
13822|1|1 4
aaaaaaa 8087 10-SEP-2017 00:00 20313398 13-SEP-2017 00:00 13822|0|0
13822|1|0 3
Error: You have data corruption issue in this timecard.
Findings and Recommendations:
Please log a service request with Oracle Support showing them this section in the output to ask a data fix from development.
5. Duplicate Time Entries Displayed on the Recent Timecards Page
Please refer to Note Duplicate Time Entries Displayed on the Recent Timecards Page (Doc ID 2261992.1)
for more details
Datafixes are usually required to fix the problem.
To avoid data corruption, user should set the profile OTL: Debug Check Enabled to yes, as this will cut down on these types of corruptions as well.
In more recent code versions <Patch 27876829:R12.HXT.C> / <Patch 27876829:R12.HXT.B> can help to prevent some types of corruptions like duplicate timecards being shown on Recent Timecards Page
STEPS
The issue can be reproduced at will with the following steps:
1. Run OTL Analyzer
2. Check the output
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |