This page (revision-16) was last changed on 27-Apr-2022 10:34 by Lilia Urtan

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

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
16 27-Apr-2022 10:34 12 KB Lilia Urtan to previous
15 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
14 26-Nov-2021 10:22 12 KB Karen Parrott to previous | to last
13 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
12 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
11 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
10 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
9 26-Nov-2021 10:22 12 KB Kevin Higgs to previous | to last
8 26-Nov-2021 10:22 11 KB Kevin Higgs to previous | to last X_NEOGOV_TAX_PARMX ==> X_NEOGOV_TAX_PARM
7 26-Nov-2021 10:22 11 KB Kevin Higgs to previous | to last
6 26-Nov-2021 10:22 11 KB Kevin Higgs to previous | to last
5 26-Nov-2021 10:22 10 KB Karen Parrott to previous | to last
4 26-Nov-2021 10:22 10 KB Karen Parrott to previous | to last
3 26-Nov-2021 10:22 10 KB Kevin Higgs to previous | to last
2 26-Nov-2021 10:22 1 KB Kevin Higgs to previous | to last
1 26-Nov-2021 10:22 1 KB Kevin Higgs to last

Page References

Incoming links Outgoing links
UEINH
UEINH

Version management

Difference between version and

At line 6 changed 5 lines
import Employee Hire from NEOGOV Insight/Onboard into Personality. It will use
an IDIF interface format to extract employee hire data from the xml file exported
by Insight/Onboard. Extracted data will be loaded into HL conversion tables and
validated with HL standard conversion logic. Validated data will be stored into
the actual database tables to create employee hires.
import Employee Hire from NEOGOV Insight/Onboard into Personality. It will use an IDIF interface format to extract employee hire data from the xml file exported by Insight/Onboard. Extracted data will be loaded into HL conversion tables and validated with HL standard conversion logic. Validated data will be stored into the actual database tables to create employee hires.
At line 8 added 12 lines
!! Supported Business Areas
*REQUIRED
**Identitiy ([IEID])
**Personals ([IEPI])
**Employement ([IEEI])
**Work Assignment ([IEAS])
* OPTIONAL
**US Pay Rules / W4 ([IPRLUS])
**Payment Method ([IPPM])
**Contacts ([IECT])
At line 13 changed one line
1. After loading the seeddata, make a deep copy of IDIF "HL$NGV-HL-CV-EMP-XML", such as "__ABC$NGV-HL-CV-EMP-XML__".
1. After loading the seeddata, make a deep copy of IDIF "HL$NGV-HL-CV-EMP-XML", such as "__ABC$NGV-HL-CV-EMP-XML__".\\
At line 23 added one line
2. Add/update constant values for desire IDIF fields. The value in the constant field will be the value loaded when UEINH is launched.\\
At line 25 added 35 lines
3. Set up Preference "[DFLT PAYRULE|DFLT PAYRULE]" in IMST \\
\\
4. Launch the UEINH with "Set Up IDIF" set to Yes.
!!Additional Set Up Notes
Some values found in NEOGOV do not match those used in Personality. A series of lexicons have been created for mapping these differences. These are preloaded values, users should not need to update these lexicons
||Inbound Mapping||Corresponding Lexicon||
|[X_NEOGOV_ETHNIC]|[X_ETHNIC]
|[X_NEOGOV_MARITAL_STATUS]|[X_MARITAL_STATUS]
|[X_NEOGOV_TAX_PARM]|X_TAX_PARMX
|[X_NEOGOV_UFED_FILING_STATUS]|[X_UFED_FILING_STATUS]
|[X_NEOGOV_UST_FILING_STATUS]|[X_UST_FILING_STATUS]
The value in the MEANING field on the lexicon will be the value being imported from NEOGOV
The value in the Displayed field will be the mapped value as it is stored in the Personality system.
!! Report Parameters & Filters
|Directory Name|Name of the complete path and directory|
|XML File Name|Name of XML file to be extracted|
|Interface Code|Interface format for extracting data|
|Exception Level|Exception only, User Trace, Legislation, UserCalc Trace, Program Trace or Utility Trace
|Clear CV Tables|Purge data from conversion tables
|Set Up IDIF| This should be set to "Yes" when running the interface for the first time. All other instances this should be set to "No" or Null.
%%info
The column [Reference ID||REFERENCE_ID] on each interface definition (IDIF) is specific to each database which reference the id on IMCD column details tab. This field must be populated in order for the UEINH to function.\\
\\
The default [IDIF] will initially have this value set as null.To populate this field, the first time UEINH is run in each environment, the user must answer Yes to the prompt "Set Up IDIF".\\
\\
If this program is set up and tested in a TEST environment and then moved to Production be sure to run with Set Up IDIF = Yes for the first run in Production.   If this prompt is Yes for each run of UEINH, it will not cause issues but it will add processing time.%%
!!Sample IDIF Layout
At line 107 changed one line
|1|538|1|30|STATE Suppl Tax Method|Char|Detail Record| |IVPPRU.UST_SUPPL_TAX_METHOD| | |
|1|538|1|30|STATE Suppl Tax Method|Char|Detail Record| |IVPPRU.UST_SUPPL_TAX_METHOD| | |
|1|540|1|30|STATE Reciprocity Agreement|Char|Detail Record| |IVPPRU.UST_RECIPROCATION| |
At line 131 changed 19 lines
2. Add/update constant values for desire IDIF fields.
3. Set up Preference "DFLT PAYRULE" in IMST
!! Report Parameters & Filters
|Directory Name|Name of the complete path and directory|
|XML File Name|Name of XML file to be extracted|
|Interface Code|Interface format for extracting data|
|Exception Level|Exception only, User Trace, Legislation, UserCalc Trace, Program Trace or Utility Trace
|Clear CV Tables|Purge data from conversion tables
----
![Notes|Edit:Internal.UEINH]
[{InsertPage page='Internal.UEINH' default='Click to create a new notes page'}]
This page (revision-16) was last changed on 27-Apr-2022 10:34 by Lilia UrtanTop