This page (revision-14) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
14 26-Nov-2021 10:22 4 KB Kevin Higgs to previous
13 26-Nov-2021 10:22 4 KB jmyers to previous | to last LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
12 26-Nov-2021 10:22 4 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
11 26-Nov-2021 10:22 4 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
10 26-Nov-2021 10:22 4 KB JEscott to previous | to last
9 26-Nov-2021 10:22 4 KB JEscott to previous | to last
8 26-Nov-2021 10:22 4 KB JEscott to previous | to last
7 26-Nov-2021 10:22 4 KB JEscott to previous | to last
6 26-Nov-2021 10:22 4 KB JEscott to previous | to last
5 26-Nov-2021 10:22 4 KB JEscott to previous | to last
4 26-Nov-2021 10:22 4 KB JEscott to previous | to last
3 26-Nov-2021 10:22 4 KB JEscott to previous | to last
2 26-Nov-2021 10:22 3 KB JEscott to previous | to last
1 26-Nov-2021 10:22 3 KB JEscott to last

Page References

Incoming links Outgoing links
LTCE
LTCE

Version management

Difference between version and

At line 2 added 5 lines
%%label-info The LTCE is limited in the overall number of interfaces that it will process and will not allow local files to be loaded. \\
\\
It is recomended that [LMTD] should be used as a replacement as it allows more processing options.%%
At line 3 changed one line
The Load Time Clock Entries (LTCE) screen is a new function that is used to load Clock Entries; this was formally done using UTCIO. The entries are loaded based on a comma delimited source file. This source file must match an interface format specified in [IDIF]. The LTCE function will look for an interface code called LTCE.
The Load Time Clock Entries (LTCE) screen is a new function that is used to load Clock Entries; this was formally done using [UTCIO]. The entries are loaded based on a comma delimited source file. This source file must match an interface format specified in [IDIF]. The LTCE function will look for an interface code called LTCE.
At line 5 changed 2 lines
;Step 1 - Define Interface Format in [IDIF]
;:An interface format is needed for the LTCE to load time sheets with Start and End times. The specific interface format may be seen in the page [LTCE INTERFACE FORMAT].
Additional information pertaining to Clocking may be found in the [Clocking|CLOCK INFORMATION] page.
!Step 1 - Define Interface Format in [IDIF]
An interface format is needed for the LTCE to load time sheets with Start and End times. An example interface format may be seen in the page [LTCE INTERFACE FORMAT].
At line 14 added one line
The LTCE will look for an IDIF interface code “LTCE” for the file structure.
At line 9 changed 2 lines
;Step 2 - Define Site Preferences in [IMST]
;:Within the [IMST] screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system, which is convenient.
!Step 2 - Define Site Preferences in [IMST]
Within the [IMST] screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system, which is convenient.
At line 12 changed one line
;:The extract directory is defined using the [EXTRCT DATA FLDR] preference. The load directory is defined using the [LOAD DATA FLDR] preference. The [ATTACHMENTS FLDR] must be specified so the load functions know where to write the report exceptions log to.
The extract directory is defined using the [EXTRCT DATA FLDR|EXTRCT DATA FLDR(System_Preference)] preference. The load directory is defined using the [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)] preference. The [ATTACHMENTS FLDR|ATTACHMENTS FLDR(System_Preference)] must be specified so the load functions know where to write the report exceptions log to.
At line 14 changed one line
;:If the full path is not specified here, then the path used by the HL Application Directory will apply. The user who is running the LTCE must have Read/Write/Create access to this directory on the server.
If the full path is not specified here, then the path used by the HL Application Directory will apply. The user who is running the LTCE must have Read/Write/Create access to this directory on the server.
At line 16 changed 2 lines
;Step 3 - Run LTCE to load the file
;:Launch the LTCE function specifying the appropriate parameters as indicated below.
!Step 3 - Run LTCE to load the file
Launch the LTCE function specifying the appropriate parameters as indicated below.
At line 19 changed 2 lines
;Step 4 - Review Report and Exception File for Results
;:During the load process, all non-fatal exceptions as well as the number of insertions and updates (by table) are logged in the execution run logs. After the load process completes, a report is written to a text file indicating the number of records read, number of records bypassed, number of records processed, number of records that were bypassed because an identical one already existed in the table, and number of records updated/inserted by table. The report will display all non-fatal business exceptions encountered during the load with a record number indicating for which record the exception occurred. The report will also display the amount of time that was taken for the load process to complete.
!Step 4 - Review Report and Exception File for Results
During the load process, all non-fatal exceptions as well as the number of insertions and updates (by table) are logged in the execution run logs. After the load process completes, a report is written to a text file indicating the number of records read, number of records bypassed, number of records processed, number of records that were bypassed because an identical one already existed in the table, and number of records updated/inserted by table. The report will display all non-fatal business exceptions encountered during the load with a record number indicating for which record the exception occurred. The report will also display the amount of time that was taken for the load process to complete.
At line 22 changed one line
;:There are 2 tiers of exceptions that can be generated during the load process. The first tier involves extracting and building data from the source file and the second involves processing the extracted data. However, there will only be ONE exception for each failed load. Basically, if the record fails to build data correctly, the program will not bother loading it so you will never see 2 exceptions for a single failed record load.
There are 2 tiers of exceptions that can be generated during the load process. The first tier involves extracting and building data from the source file and the second involves processing the extracted data. However, there will only be ONE exception for each failed load. Basically, if the record fails to build data correctly, the program will not bother loading it so you will never see 2 exceptions for a single failed record load.
At line 24 changed one line
;:Exceptions generated while extracting and building data from the source file will indicate that the exception occurred while "reading data from file". Exceptions generated while processing the extracted data will indicate that the exception occurred while "loading data into the DB".
Exceptions generated while extracting and building data from the source file will indicate that the exception occurred while "reading data from file". Exceptions generated while processing the extracted data will indicate that the exception occurred while "loading data into the DB".
At line 26 changed one line
;:When a Null Pointer Exception (NPE) occurs during the load process, the entire stack trace to the NPE is captured and displayed as part of the exception message in the load report.
When a Null Pointer Exception (NPE) occurs during the load process, the entire stack trace to the NPE is captured and displayed as part of the exception message in the load report.
At line 28 changed one line
;:The report text file will be located in the directory which was specified in the [IMST] preference [LOAD DATA FLDR].
The report text file will be located in the directory which was specified in the [IMST] preference [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)].
At line 30 changed 2 lines
;Step 5 - Verify Loaded Data in [ITCE]
;:If there are no exceptions in the report, you should navigate to the [ITCE] where the data was loaded and verify that the load was done correctly.
!Step 5 - Verify Loaded Data in [ITCE]
If there are no exceptions in the report, you should navigate to the [ITCE] where the data was loaded and verify that the load was done correctly.
At line 40 added 3 lines
!Step 6 - Process Clock Punches
To process the clock punches the [UTCIO] should be run.
At line 37 changed one line
|File Name| This field holds the name of the file that has been placed on the \\server in the directory specified in the [IMST] record [LOAD DATA FLDR]. \\Mandatory
|File Name| This field holds the name of the file that has been placed on the \\server in the directory specified in the [IMST] record [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)]. \\Mandatory
At line 40 changed one line
|Interface Code| The Interface Code that was created in step 1 must be specified.
|Interface Code| The Interface Code 'LTCE' that was created in step 1 must be specified.
At line 52 added 5 lines
----
![Notes|Edit:Internal.LTCE]
[{InsertPage page='Internal.LTCE' default='Click to create a new notes page'}]
This page (revision-14) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop