This page (revision-11) 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
11 26-Nov-2021 10:22 7 KB jmyers to previous LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
10 26-Nov-2021 10:22 7 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
9 26-Nov-2021 10:22 6 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
8 26-Nov-2021 10:22 6 KB JMyers to previous | to last
7 26-Nov-2021 10:22 6 KB JAiken to previous | to last
6 26-Nov-2021 10:22 6 KB RForbes 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 6 KB JEscott to last

Page References

Incoming links Outgoing links
LRCAPSI
LRCAPSI

Version management

Difference between version and

At line 3 changed one line
The Load Candidate Information (LRCAPSI) screen is another extension of the [LMTD] and was built specifically for a client and is the companion process to [XRAPPSI]. The purpose of these two processes is to extract candidate information to provide to a third party, in this case PSI. PSI performs a background check on the candidate and sends a file back to the client with an indicator of Pass or Fail. The client then loads this file via LRCAPSI into Personality. It is required that when an indicator of "Fail" is found that it set the Applicant Status to "Not Approved", which will also mark all applications to "Rejected".
The Load Candidate Information (LRCAPSI) screen is another extension of the [LMTD] and was built specifically for a client and is the companion process to [XRAPPSI]. The purpose of these two processes is to extract candidate information to provide to a third party, in this case PSI. PSI performs a background check on the candidate and sends a file back to the client with an indicator of Pass or Fail. The client then loads this file via LRCAPSI into eP. It is required that when an indicator of "Fail" is found that it set the Applicant Status to "Not Approved", which will also mark all applications to "Rejected".
At line 5 removed 2 lines
%%information We do not endorse ''PSI Background Check'' as a third-party background check vendor. There are many providers of such service. This functionality was built for a specific client who utilizes this vendor. The interface and programming is provided as-is and any modifications required to support a different vendor may need to be additionally developed. %%
At line 11 changed one line
** [Candidate Status|CANDIDATE_STATUS] = "08" (Approved) - New lexicon value
** RCA.Candidate_Status = "08" (Approved) - New lexicon value
At line 14 changed one line
** [Candidate Status|CANDIDATE_STATUS] = "07" (Not Approved)
** RCA.Candidate_Status = "07" (Not Approved)
At line 16 changed 2 lines
*** [Application Status|APPLICATION_STATUS] = "80" (rejected)
*** [Application Closed|APPLICATION_CLOSED] = date of processing
*** RAP.Application_Status = "80" (rejected)
*** RAP.Application_Closed = date of processing
At line 19 changed one line
** [Candidate Status|CANDIDATE_STATUS] = "05" (Flagged)
** RCA.Candidate_Status = "05" (Flagged)
At line 22 changed 2 lines
!Step 1 - Define Interface Format in [IDIF]
The source file layout needs to be defined as an interface format. The interface format is created and modified in the [IDIF] screen. Each line of the source file is read and divided into field values based on the field information table in this screen.
;Step 1 - Define Interface Format in [IDIF]
;:The source file layout needs to be defined as an interface format. The interface format is created and modified in the [IDIF] screen. Each line of the source file is read and divided into field values based on the field information table in this screen.
At line 25 removed 7 lines
||Field Name||Beg\\Pos||End\\Pos||Notes
|Storeno |1|4| In Personality this would be the Department Code
|SSN |5|15| xxx-xx-xxxx
|First Name| 16|50|
|Last Name| 51|85|
|Status| 86|120| One of three options (see above)
|Prime key| 121|130| Candidate Code
At line 34 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 37 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 39 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 LRCAPSI 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 LMTD must have Read/Write/Create access to this directory on the server.
At line 41 changed 2 lines
!Step 3 - Run LRCAPSI to load the file
Launch the LRCAPSI function specifying the appropriate parameters as indicated below.
;Step 3 - Run LRCAPSI to load the file
;:Launch the LRCAPSI function specifying the appropriate parameters as indicated below.
At line 45 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 48 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 50 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 52 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 54 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 56 changed 2 lines
!Step 5 - Verify Data has been loaded
If there are no exceptions in the report, you should navigate to the table(s) where the data was loaded and verify that the load was done correctly.
;Step 5 - Verify Data has been loaded
;:If there are no exceptions in the report, you should navigate to the table(s) where the data was loaded and verify that the load was done correctly.
At line 63 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 68 removed 5 lines
----
![Notes|Edit:Internal.LRCAPSI]
[{InsertPage page='Internal.LRCAPSI' default='Click to create a new notes page'}]
This page (revision-11) was last changed on 26-Nov-2021 10:22 by jmyersTop