This page (revision-9) was last changed on 26-Nov-2021 10:22 by jmyers

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
9 26-Nov-2021 10:22 6 KB jmyers to previous LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
8 26-Nov-2021 10:22 6 KB jmyers to previous | to last INPT DATE FORMAT ==> INPT DATE FORMAT(System_Preference)
7 26-Nov-2021 10:22 6 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
6 26-Nov-2021 10:22 6 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
5 26-Nov-2021 10:22 6 KB JEscott to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
LPTS
LPTS

Version management

Difference between version and

At line 6 added one line
LPTS will not create time sheets, just time sheet entries so clients should ensure there are exiting time sheets for the period to be loaded. If a time sheet cannot be located, the LPTS will fail to load that record.
At line 7 removed 4 lines
LPTS may create time sheets depending on how the interface format is defined in [IDIF]. In order to have LPTS create new time sheets, there must be an entry in [IDIF] for: PTSE.ACT_DIF_PRE_INSERT_CREATE_TS. This will force the system to call the new logic to create a new time sheet, if necessary.
If the PTSE.ACT_DIF_PRE_INSERT_CREATE_TS line is missing from [IDIF] LPTS will not create time sheets, just time sheet entries so clients should ensure there are exiting time sheets for the period to be loaded. If a time sheet cannot be located, the LPTS will fail to load that record.
At line 13 changed one line
LPTS will respect any date formats that are set up in the [INPT DATE FORMAT|INPT DATE FORMAT(System_Preference)] preference in [IMST]. If no format has been defined, then the LPTS will respect any ddmm type formats i.e.:ddmmyyyy, ddmmmyyyy, dd-mmm-yyyy
LPTS will respect any date formats that are set up in the [INPT DATE FORMAT] preference in [IMST]. If no format has been defined, then the LPTS will respect any ddmm type formats i.e.:ddmmyyyy, ddmmmyyyy, dd-mmm-yyyy
At line 18 changed one line
An interface format is needed for the LPTS to load time sheets.
;:An interface format is needed for the LPTS to load time sheets with Start and End times.
At line 20 removed 4 lines
The [Times Based Interface for LPTS|TIMES BASED INTERFACE FOR LPTS] page shows an example of an interface format for loading time sheets with Start and End times.
The [Hours Based Interface for LPTS|HOURS BASED INTERFACE FOR LPTS] shows an example of an interface format for loading time sheets that are hours based.
At line 25 changed one line
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.
;: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 27 changed one line
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.
;: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.
At line 29 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 LPTS 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 LPTS must have Read/Write/Create access to this directory on the server.
At line 32 changed one line
Launch the LPTS function specifying the appropriate parameters as indicated below.
;:Launch the LPTS function specifying the appropriate parameters as indicated below.
At line 35 changed one line
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.
;: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 37 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 39 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 41 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 43 changed one line
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)].
;:The report text file will be located in the directory which was specified in the [IMST] preference [LOAD DATA FLDR].
At line 46 changed one line
If there are no exceptions in the report, you should navigate to the [IPTS] where the data was loaded and verify that the load was done correctly.
;:If there are no exceptions in the report, you should navigate to the [IPTS] where the data was loaded and verify that the load was done correctly.
At line 52 changed one line
|File Name| This field is 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
|File Name| This field is the name of the file that has been placed on the server \\in the directory specified in the [IMST] record [LOAD DATA FLDR]. \\Mandatory
At line 57 removed 5 lines
----
![Notes|Edit:Internal.LPTS]
[{InsertPage page='Internal.LPTS' default='Click to create a new notes page'}]
This page (revision-9) was last changed on 26-Nov-2021 10:22 by jmyersTop