System Design Specification

System Design Specification for HRS0080

Version: 1.1

Implementation

Plan

for

Project Title: Capture Staff Levels in Oracle HR & Payroll

Project Code: HRS080

Version: 1.0

Date: 19/05/14

Project: HRS080

Contents

1Document Management2

1.1Contributors2

1.2Version Control2

2OVERVIEW3

3Implementation Stages4

3.1. Addition of the Levels field to HRMS Application4

4Procedure to populate the new field9

4.1Table changes:9

4.2New Procedure9

4.3Renew Existing Code10

5Run initial data update10

Document Management

Contributors

Role

Unit

Name

Systems Analyst Designer (Owner)

Pamela Smulski

Business Analyst

Project Manager

Nikki Stuart

Project Sponsor

Susan McLaren

Business Area Manager

Other document contributors

Version Control

Date

Version

Author

Section

Amendment

19/05/14

1.0

P.Smulski

Initial version

OVERVIEW

The Level field held in relation to every assignment in HR has previously been allocated and recorded only during the extract to produce reports for HESA. The HR department has requested a permanent record of this value to be added to the HR system.

The field will initially be calculated using existing grade levels and some records updated by the HR team themselves. After implementation the data will be records in HR by the interface from the Successful applicants system. Queries of the Level data will be available through the PPIPMI Business Objects universe.

This document covers the implementation of the changes required for this project including changes within the HRMS system, a new pl/sql procedure and changes to existing ones.

Changes to the PPIPMI Buxiness Objects universe are not covered by this document.

Implementation Stages

3.1. Addition of the Levels field to HRMS Application

Create List of Values

Create a new list of values within the HR application called VS_UOE_LEVEL:

In the HR application, navigate System Administrator > Application > Validation > Set

And populate fields as show below.

Click on the yellow save icon.

Populate List of Values

Then navigate to System Administrator > Application > Validation > Values

In the name box type VS_UOE_LEVEL% and click on Find. This should open up the screen for input of the valid values:

Enter the values shown here as the Value and Description providing an enabled from date as 26-FEB-1995 for each level code.

Values for the Level field:

Value

Description

A0

Vice-Chancellor/Principal/Head of Institution

B1

UCEA level 2A

B2

UCEA level 2B

C1

UCEA level 3A

C2

UCEA level 3B

D1

UCEA level 3/4A1

D2

UCEA level 3/4A2

D3

UCEA level 3/4A3

E1

UCEA level 4A

E2

UCEA level 4B

F1

UCEA level 5A

F2

UCEA level 5B

I0

XpertHR level I

J0

XpertHR level J

K0

XpertHR level K

L0

XpertHR level L

M0

XpertHR level M

N0

XpertHR level N

O0

XpertHR level O

P0

XpertHR level P

Click on the yellow save icon.

Create Flexfield

From the HR application menu, select System Administrator > Application > Flexfield > Descriptive > Segments and then press F11.

Enter Additional Assignment Details in the title box and press F11

Uncheck the Freeze Flexfield Definition to ‘unfreeze’ and click on the OK to confirm.

Click on Global Data Elements in the ‘context field values’ area.

Click on the Segments button.

Click on the last field currently in the table and then the New button, A separate screen will appear – cancel out of this screen.

Click on the ‘Column’ field and then the available options option in the field.

Make sure that you deselect the Required check box on this page.

ASS_ATTRIBUTE8, 9 and 28 are currently available, select ASS_ATTRIBUTE8 to use for the LEVEL field.

Enter UOE_Level for Name and Level for Window Prompt, then click on the muti-select from the Value set field.

On the new window, enter VS_UOE_Level% and click the Find button. Select VS_UOE_Level and click OK (See screen shot below)

Now save with the yellow save icon on the menu bar.

NOTE: Click the Freeze Flexfield definition option on the front screen and save again before leaving this section.

Procedure to populate the new fieldTable changes:

The following code will create a new logging table and modify existing eRecruitment tables by adding new columns.

K:\ISAPPS\dsg\Projects\HRS080 - Levels\Code_for_TEST\ erecruit_table_changes.sql

· K:\ISAPPS\dsg\Projects\HRS080 - Levels\Code_for_TEST\ new_log_table.sql

New Procedure

Create a New procedure called UOE_LEVEL_UPDATE in the APPS schema of HRTEST.

The code is located here

· K:\ISAPPS\dsg\Projects\HRS080 - Levels\Code_for_TEST\UOE_LEVEL_UPDATE_header.sql

· K:\ISAPPS\dsg\Projects\HRS080 - Levels\Code_for_TEST\UOE_LEVEL_UPDATE_body.sql

Renew Existing Code

Update existing eRecruitment code by running the following 2 scripts in the APPS schema on HRTEST

· K:\ISAPPS\dsg\Projects\HRS080 - Levels\Code_for_TEST\ uoe_erecruit_appoint_pkg_header.sql

· K:\ISAPPS\dsg\Projects\HRS080 - Levels\Code_for_TEST\ uoe_erecruit_appoint_pkg_body.sql

Run initial data update

Inform John Chan or appropriate other Support team member that there could be over 13,000 change flags being raised on the TEST HR system. This is part of what this process will do.

Connect to the apps user on HRTEST

Run the following command:

· exec UOE_LEVEL_UPDATE_PKG.update_level;

This code takes an hour in Dev so I expect it to take up to 20 minutes in Live.

After completion run the following sql and forward the result to Susan McLaren and Pamela Smulski. This will provide information on records that could not be provided with LEVEL field data.

SELECT assignment_number, grade, employee_number, employee_name

FROM APPS.UOE_LEVEL_ERROR_LOG;

----- End of implementation ----

Page 4 of 10