Subject: | TNA File fail to Process |
Summary: | Danam Fiji has upgraded Linksoft from V9 to V13. They use the following TNA Method:
- Device:
- TI001 - HP IIngersoll Rand HP3000e (File)
- The locations of the respective folder are:
- FileWatchLocation: D:\Timesheet\Watch
- FileProcessingLocation: D:\Timesheet\Processing
- FileCompletedLocation: D:\Timesheet\Completed
- Process: ESS021 is set to run every 10 minutes
- TNA Setup - the below Rules are Running
- A001 – Timesheet processing rules
- A002 – Use a "Time Buffer" when calculating "timesheet" hours
- R003 – Change multiple clock type "IN" to clock type "BREAK IN" for entries in a day. Shift "Start Time", "Buffer" settings are used to determine a day.
For Example: 1. Shift A starts at 8am, "Time Buffer" has 15 minutes before start and "New Entry Hours Buffer" is 19 hours, then a day is from 7:45am to 3:00am (next day) 2. Shift B starts at 8pm and "Time Buffer" has 60 minutes before start and "New Entry Hours Buffer" is 19 hours, then a day is from 7:00pm to 3:00pm (next day) - R004 – Approve time entries submitted from "Timesheet"
- R008 – Do not import timesheet entries for "Non-Timesheet" employees into payroll
- R009 – Mark entries exceeding maximum hours configuration as invalid
Issue: - The TNA file was placed in the Watch folder
- Process ESS021 was executed successfully
- The file moved from the Watch to the Processing folder
- The file was stuck in the Processing folder
- Upon verifying the event log – 2 errors were noted:
- Module: LT_ESS_TimesheetImport_Compute
Error: Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them. - Module: LBS_POS_Customer_All_Update
Error: Cannot insert the value NULL into column 'Code', table 'LINKSOFT.dbo.LBS_POS_Customer_all'; column does not allow nulls. INSERT fails.
Notes: - These errors were not found in the training database in UAT
- There was a patch executed as part of Case: T13988, Subject: Submitting a days TNA Record Times Out – after that several files were imported and they were imported successfully
Environment Details: - LinkQA8
- Version: 13.40.0621.GA
- URL: http://10.0.0.18/LinkWEB-Danam
- Login: standard "admin" login
- Files in Watch Folder
- Moved to Process Folder
- Upon verifying the event log – 2 errors were noted:
- Module: LT_ESS_TimesheetImport_Compute - Error: Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
- Module: LBS_POS_Customer_All_Update - Error: Cannot insert the value NULL into column 'Code', table 'LINKSOFT.dbo.LBS_POS_Customer_all'; column does not allow nulls. INSERT fails.
|
Audit Notes: | Edited by sanjay on 22/07/22 09:51. Edited by sanjay on 13/07/22 08:54. Edited by sanjay on 12/07/22 14:37. Edited by aarti on 11/07/22 17:07. |
12 Jul 2022 | 02:37PM Comment 1 by Sanjay (Link Technologies) Case L12754 added to project 14.00 |
12 Jul 2022 | 02:44PM Comment 2 by Aarti Pooja Gayaneshwar (Link Business Solutions) Assigned To: Aarti Pooja Gayaneshwar (Link Business Solutions) Followup Date: 12-07-2022 08:39 PM Time Taken: 2.00 |
| Meeting with Sanjay and Aarti
Error 1: Module: LT_ESS_TimesheetImport_Compute Error: Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them. Discussed: Sanjay has taken a trace of this error. He advised that he would rectify this and update
Error 2: Module: LBS_POS_Customer_All_Update Error: Cannot insert the value NULL into column 'Code', table 'LINKSOFT.dbo.LBS_POS_Customer_all'; column does not allow nulls. INSERT fails. Discussed: The customer table for POS and ESS are the same. Sanjay is looking at how best to handle this. |
|
12 Jul 2022 | 02:47PM Comment 3 by Aarti Pooja Gayaneshwar (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 12-07-2022 08:46 PM |
| Assigning case to Sanjay |
|
12 Jul 2022 | 07:13PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 13-07-2022 01:13 AM Time Taken: 5.00 |
| Hi Aarti, as a workaround, you can use SQL Server 2017 compatibility. I will investigate the issue further in SQL2019. |
|
13 Jul 2022 | 08:54AM Comment 5 by Sanjay (Link Technologies) ETC was changed from 12/07/2022 to 22/07/2022 |
19 Jul 2022 | 08:55AM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 19-07-2022 02:54 PM Time Taken: 1.00 |
| Same issue as case L12756. |
|