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

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 6 KB khiggs to previous
13 26-Nov-2021 10:22 6 KB khiggs to previous | to last
12 26-Nov-2021 10:22 6 KB jmyers to previous | to last LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
11 26-Nov-2021 10:22 6 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
10 26-Nov-2021 10:22 6 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
9 26-Nov-2021 10:22 6 KB RForbes to previous | to last
8 26-Nov-2021 10:22 6 KB RForbes to previous | to last LMTD INTERFACE FORMAT ==> DATA LOADER IDIF FORMAT
7 26-Nov-2021 10:22 6 KB JMyers to previous | to last
6 26-Nov-2021 10:22 6 KB JEscott to previous | to last
5 26-Nov-2021 10:22 6 KB JEscott to previous | to last
4 26-Nov-2021 10:22 6 KB JEscott to previous | to last
3 26-Nov-2021 10:22 6 KB JEscott to previous | to last
2 26-Nov-2021 10:22 6 KB JEscott to previous | to last
1 26-Nov-2021 10:22 5 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 4 changed one line
The Load Benefit Elections (LBEN) screen is an extension of the technology used by [LMTD]. LBEN has the same functionality of the [LMTD] with the exceptions that an [IDIF] interface code must be defined and the process is strictly used to update Benefit Elections. The LBEN has been designed to call the special benefit election logic which checks the schedule to ensure the employees are eligible for the benefit plans/coverages.
The Load Benefit Elections (LBEN) screen is an extension of the technology used by [LMTD]. It was originally built for a particular client and thus was very customized. However, it has recently undergone some changes to make the LBEN more generic and powerful, like that of the [LMTD]. LBEN will now respect derivation expressions where as previous versions of the function did not.
At line 6 added 2 lines
The original LBEN still exists and is now known as LBEN_407. The new LBEN has the same functionality of the [LMTD] with the only exception that it is strictly used to update Benefit Elections. The LBEN has been designed to call the special benefit election logic which checks the schedule to ensure the employees are eligible for the benefit plans/coverages.
At line 13 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|ATTACHMENTS FLDR(System_Preference)] must be specified so the load functions know where to write the report exceptions log to.
At line 27 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)]. These exceptions will not be reported in the PDF report for LBEN so it is important for users to have access to this folder to review when loads fail. The file name will be the original file name prefixed with "LOAD REPORT -" and the mex id and suffixed with "via IDIF 'NAME_OF_IDIF_USED'.txt", for example "LOAD REPORT - 9916_OPTIONAL_LIFE.csv via IDIF HL$OPT_LIFE.txt". This file will be stored in the [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)] folder on the server.
;:The report text file will be located in the directory which was specified in the [IMST] preference [LOAD DATA FLDR].
At line 29 changed one line
;:If records are not loaded due to errors, these bypassed records will be copied to a separate file which can be loaded once the records have been corrected. This allows you to load in just the bypassed records without having to manipulate the original file. The file name will be the original file name prefixed with the mex id and suffixed with _BYPASSED.txt, for example "9916_OPTIONAL_LIFE.csv_BYPASSED.txt". This file will be stored in the [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)] folder on the server.
;:If records are not loaded due to errors, these bypassed records will be copied to a separate file which can be loaded once the records have been corrected. This allows you to load in just the bypassed records without having to manipulate the original file. The file name will be the original file name prefixed with the mex id and suffixed with _BYPASSED.txt, for example 9916_iptl.csv_BYPASSED.txt. This file will be stored in the [LOAD DATA FLDR] folder on the server. This file will only be created for the Dif Data Loader processes, it will not be created if using the Table Data Loader.
At line 37 changed 2 lines
|Server File| This field provides 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)].
|Local File| This field allows you to upload a local source file for loading into the database\\ (similar to that of WW Reports in Personality). To do this, you must populate the\\ 'Local File' field by selecting the local source file using the file chooser. When \\selecting a local source file to load, the 'Server File' field MUST be blank.
|Server File| This field provides the name of the file that has been placed on the server\\ in the directory specified in the [IMST] record [LOAD DATA FLDR].
|Local File| This field allows you to upload a local source file for loading into the database\\ (similar to that of WW Reports in [{$applicationname}]). To do this, you must populate the\\ 'Local File' field by selecting the local source file using the file chooser. When \\selecting a local source file to load, the 'Server File' field MUST be blank.