These two processes are client-specific in the sense that the data provided in the source file must match the standards of PSI as this data is manipulated or used to derive column values that can be imported correctly into a system. Specifically, candidate codes less than 7 digits are left-padded with zeroes to ensure that candidate codes to be loaded are exactly 7 digits. This feature will be made more general in the near future so that other clients may use this.
Processing:
Field Name | Beg Pos | End Pos | Notes |
---|---|---|---|
Storeno | 1 | 4 | In Wiki 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 |
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.
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.
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.
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".
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.
The report text file will be located in the directory which was specified in the IMST preference LOAD DATA FLDR.
Report Parameters | |
---|---|
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 |
Interface Code | The Interface Code that was created in step 1 must be specified. |
Allow Update | The lexicon values of this field are YES or NO. Selecting "NO" disallows the updating of existing records in the database. If there are new records in the load file, the program will still perform an insertion of these records into the destination table. In short, selecting "NO" for Allow Update does not allow you to run the program in trial as it only prevents existing records in the database from being updated. Selecting "YES" will update existing records in the database with changes found in the load file. |
Allow Insert | The lexicon values of this field are YES or NO. By selecting "NO" LRCAPSI will not load any new records into the specified table. By selecting "YES" new records found in the load file will be inserted into the specified table. |
Exception Level | The lexicon values of this field are 0 to 9. Allows you to specify the level of trace you wish to see in the report. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation