HR/CORE-CT data is retrieved using the HRISWebAPI and the HRISAPI and HRINTRECRUIT Database.
| UC_ |
|---|
...
| CURRENT_TREE |
|---|
...
| java field |
|---|
...
| Page-Up field | |
|---|---|
| ROWID |
...
| rowid | ||
| DT_ |
...
| ID | dtId | |
| DT_J_DEPT_ |
...
| ID | deptId | used in BusinessUnitLevel1ID |
...
| used in BusinessUnitLevel12D |
...
| used in BusinessUnitLevel3ID | ||
| DT_DEPT_ |
...
| DESC | description | Name |
| DT_DEPT_PARENT_NODE_ |
...
| ID | parentNodeId | |
| DT_DEPT_NODE_ |
...
| ID | nodeID | |
| DT_NODE_ |
...
| LEVEL | nodeLevelNumber | |
| DT_TREE_LEVEL_ |
...
| NUM | treeLevelNumber |
...
DataBase ViewTable – taken from PSTREENODE-VWVW (Also known as OrgHierarchy.)
| UC_ |
|---|
...
| CURRENT_TREE |
|---|
...
| DT_J_DEPT_ID |
...
| Department Number | |
| DT_DEPT_DESC |
...
| Department Description | |
| DT_PARENT_NODE_ID | |
| DT_DEPT_NODE_ID | |
| DT_NODE_LEVEL | |
| DT_TREE_LEVEL_NUM |
...
| Level |
...
Summary
- The Business Unit files must have a header record followed by all the detail records. The delimiter used to separate the fields is the pipe(|). All three Business Unit files will be created with one job, multiple steps.
- Create a hierarchy tree for each department from the lowest level to the highest level, where the highest level is 4 and the lowest level is 10. This hierarchy is used to create all three Business Unit Files. Do not include any departments where the department description is blank.
Business Unit 1 file is a file containing the highest level department. In the case of UConn, the highest level is 4, which are the President of the University, the Provost of Academic Affairs, and the Executive Vice President and CFO.
- Business Unit File 1 contains only the level 4 records (hierarchy tree size = 4). Levels 1, 2, and 3 are ignored.
- The BusinessUnitLevel1ID will be the department number. This is the key to the file, therefore must be unique.
- The Name is the department description.
Sample Business Unit 1 file:
...
Business Unit 2 file is a file containing levels mainly 5, 6, and 7. Highest level is 5 and lowest level is 7.
Remove any level with a department description stating with INA-. These are UConn inactive accounts. HR uses the INA- prefix in the description because Core-CT will not allow them to delete any department numbers.
Combinations:
Levels:
All three levels (5, 6, 7)
...
No Level 5, Level 6, or Level 7
- Remove any level with a department description stating with INA-. These are UConn inactive accounts. HR uses the INA- prefix in the description because Core-CT will not allow them to delete any department numbers.
- If there is no level 5, 6 or 7, determine if level 8, 9, or 10 exists. If level 8, 9, or 10 exists use levels 8, 9, and 10 in place of levels 5, 6, and 7 to create the BusinessUnitLevel2ID and Name. If only a level 4 exists, use the level 4 department id for both the BusinessUnitLevel2ID and the BusinessUnitLevel1ID and use the department description for level 4, as the Name.
- Levels 1, 2, and 3 are ignored.
- BusinessUnitLevel2ID is the key to the file, therefore must be unique.
...
- If only one of these levels exist the BusinessUnitLevel2ID is the department number of the level. If multiple levels exist, the BusinessUnitLevel2ID is the department number of the highest level followed by a dash followed by the next highest level number and if needed (followed by a dash followed by the lowest level).
Examples:
UOC01151
UOC01179-UOC01895
UOC01179-UOC01895-UOC01161
6. The Name is the department description. In the case of multiple departments the second and third descriptions are entered into parenthesis. Remove entire record if the department description is blank. These are invalid organizations.
Examples:
Agriculture,Health,Natural Rcs
Business(Business Undergrad Programs)
Business(Business Undergrad Programs)(Research)
7. The BusinessUnitLevel1ID is the level 4 department for the particular hierarchy. This should point back to an entry in the Business Unit 1 file.
8. The entries in Business Unit 1 file must also appear in the Business Unit 2 file. Page-Up needs this to create a waterfall effect.
...
UOC01928|University Compliance|UOC01000
Business Unit 3 file is a file containing all departments. Highest level is 4 and lowest level is 10. The BusinessUnitLevel3ID is to be created using level 8, 9, and 10 in reverse order unless levels 8, 9, an 10, do not exist in the departments hierarchy. Levels 1, 2, and 3 are ignored.Remove any level with a department description stating with INA-. These are UConn inactive accounts. HR uses the INA- prefix in the description because Core-CT will not allow them to delete any department numbers.
Combinations:
Levels:
All three levels (8, 9, 10)
...
No Level 5, Level 6, or Level 7
- Remove any level with a department description stating with INA-. These are UConn inactive accounts. HR uses the INA- prefix in the description because Core-CT will not allow them to delete any department numbers.
- If there is no level 8, 9, or 10, determine if level 5, 6, or 7 exists. If level 5, 6, or 7 exists use Levels 5, 6, and 7 in place of levels 8, 9, and 10 to create the BusinessUnitLevel3ID and Name. If only a level 4 exists, use the level 4 department id for both the BusinessUnitLevel3ID and the BusinessUnitLevel2ID and use the department description for level 4, as the name.
- BusinessUnitLevel3ID is the key to the file, therefore must be unique.
- If only one of these levels exist the BusinessUnitLevel3ID is the department number of the level. If multiple levels exist, the BusinessUnitLevel3ID is the department number of the highest level followed by a dash followed by the next highest level number and if needed (followed by a dash followed by the lowest level). Note that this is in the reverse order of how the keys are created in Business Unit 2 file.
...
Examples:
UOC01151
UOC01895-UOC01179
UOC01161-UOC01895-UOC01179
5. The Name is the department description. In the case of multiple departments the second and third descriptions are entered into parenthesis. Note that the department descriptions are also reversed from the way they are created in the Business Unit 2 file. Remove entire record if the department description is blank. Organizations with blank descriptions are invalid organizations.
Examples:
Agriculture,Health,Natural Rcs
Business Undergrad Programs(Business)
Research(Business Undergrad Programs)(Business)
6. The BusinessUnitLevel2ID is the level 5, 6, and/or 7 created similar to the BusinessUnitLevel2ID from the Business Unit 2 file.
7. The entries in Business Unit 2 file must also appear in the Business Unit 3 file. Page-Up needs this to create a waterfall effect.
...
Name
BusinessUnitLevel2ID
Link to Page-up site
| https://uconn.dc4.pageuppeople.com/dashboard? | use netid and password to authenticate |
Press the icon with three horizontal lines in the upper right-hand corner.
Navigate - System Settings+Integration+Import Logs(files into Page-Up)
Type = Generic Importer, Status = unarchived, pressing Search button will display files that have not yet been processed.
Type = Generic Importer, Status = archived, pressing Search button will display files that have been processed.
Names of the
...
output files
| uconn_configs/webapi/rpm/batch |
|---|
| business-unit-1-page-up.txt |
| business-unit-2-page-up.txt |
| business-unit-3-page-up.txt |
Execution
...
Command
| /createBusinessUnitFilesJob.html |
Control-M Schedule and Job
| UAT | UAT_AEWEB_SCHEDULE | UAT_RPM_BUSINESS_UNITS_TO_PAGEUP | Ad-Hoc |
| PRD | PRD_AEWEB_RPM_SCHEDULE1 | PRD_RPM_BUSINESS_UNITS_TO_PAGEUP1 | Runs daily at 6:45am |
UAT - UAT_AEWEB_SCHEDULE/UAT_RPM_BUSINESS_UNITS_TO_PAGEUP
PRD - PRD_AEWEB_RPM_SCHEDULE1/PRD_RPM_BUSINESS_UNITS_TO_PAGEUP1