banner human resources/position control release guide 8 · employee self-service release guide...

BannerHuman Resources/

Position Control Release Guide

Release 8.10October 2013

Banner®, Colleague®, PowerCampus™, and Luminis® are trademarks of Ellucian Company L.P. or its affiliates and are registered in the U.S. and other countries. Ellucian™, Ellucian Advance™, Ellucian Degree Works™, Ellucian Course Signals™, Ellucian SmartCall™, and Ellucian Recruiter™ are trademarks of Ellucian Company L.P. or its affiliates. Other names may be trademarks of their respective owners.

© 2013 Ellucian Company L.P. and its affiliates.

Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is limited to Ellucian licensees, and is subject to the terms and conditions of one or more written license agreements between Ellucian and the licensee in question

In preparing and providing this publication, Ellucian is not rendering legal, accounting, or other similar professional services. Ellucian makes no claims that an institution's use of this publication or the software for which it is provided will guarantee compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization's own choosing.

Prepared by: Ellucian4375 Fair Lakes CourtFairfax, Virginia 22033United States of America

Contents

HuPo

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Enhancements for 8.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Cumulative Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Electronic Approval Superuser Override- Functional. . . . . . . . . . . . . . . 8

New Administrator Proxy Rules form (NTRAPRX) - Functional. . . . . . . 9

Support for International Bank Account Number - Functional . . . . . . . 11

Banner General and Banner Finance Companion Release Information for IBAN 11

Banner General and HR updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Banner General updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

BANK_ROUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BANK_ACCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Banner HR updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Electronic Approval Superuser Override- Technical . . . . . . . . . . . . . . . 16

Changed packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

NOKEPAF (nokepa1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

NOKEPCR (nokepcr.sql/nokepc1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

NOKLIST (noklis1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Electronic Approval Summary (NOAAPSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Electronic Personnel Action (NOAEPAF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Changed processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Electronic Approvals Report (noraptr.pc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3man Resources/sition Control Release Guide | Contents

Contents

HuPo

Mass Salary Table Update (nbpmass.pc). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

New seed data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

New Administrator Proxy Rules form (NTRAPRX) - Technical . . . . . . . 19

Changed tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Proxy Rules Table (NTRPROX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Proxy Rules Table (NTRPRXY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

New scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

New Seed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Changed APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Proxy API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

ntkd_ntrprxy0.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20ntkb_proxy0.sql/ntkb_proxy1.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21ntkb_proxy_r0.sql/ntkb_proxy_r1.sql. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21ntkb_proxy_s0.sql/ntkb_proxy_s1.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Support for International Bank Account Number - Technical . . . . . . . . 22

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Document Number Repeating Table (PHRDOCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Document Number Repeating Table (PEBPAYM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Changed Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

PEKLIBS (peklibs.sql/peklib1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

NOKINST (nokinst.sql / nokinst1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

PEA1PAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

PHAADJT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23


Contents

HuPo

Changed Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

PHPCHEK/PHPCHKL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

PHRPREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Banner Integration for Ellucian Talent Management - Technical . . . . . . 25

Updated Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Resolutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Problem Resolutions - Technical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Advance queuing when using Oracle RAC (1-1CBHTLZ) . . . . . . . . . . . . . . . . . . . . 27

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27


HuPo

Introduction

This release guide provides an overview of the Banner® Human Resources/Position Control 8.10 release. Release 8.10 includes enhancements and problem resolutions.

System requirements

Install the following minimum releases to upgrade to Banner Position Control 8.10.

Install the following minimum product releases to upgrade to Banner Human Resources 8.10.

Enhancements for 8.10

This document describes the following enhancements that are new for the 8.10 release.

• Electronic Approval Superuser Override

• New Administrator Proxy Rules form (NTRAPRX)

• Support for International Bank Code and Account numbers for Payroll Processing

Banner General

Position Control

8.6 8.9

Banner General

Human Resources

Position Control

8.6 8.9 8.10

6man Resources/sition Control Release Guide | Introduction

HuPo

3

Cumulative Documentation

This document provides detailed information about the Banner Human Resources/Position Control 8.10 release only. Banner Human Resources/Position Control 8.10 is a cumulative release that also includes enhancements and problem resolutions delivered since the Banner Human Resources/Position Control 8.9 release.

* Release 8.8.2 was released after the 8.9 release. For more information about the initial release of the Banner Integration for Ellucian Talent Management Suite, you can refer to the Banner Integration for Ellucian Talent Management Suite Handbook, Banner Employee Self-Service Release Guide 8.8.2 and the Banner Human Resources Release Guide 8.8.2. There is also a Quick Summary Guide available in the Commons.

Release Number Contents Release Date

8.8.2* Initial release of Banner Integration for Ellucian Talent Management Suite

September 201

7man Resources/sition Control Release Guide | Introduction

HuPo

Electronic Approval Superuser Override- Functional

This section summarizes the functional changes made for enhancement 1-5WNHJF.

Previously, if an update to the Effective Date on an EPAF needed to be made by a Superuser, that person had to return the EPAF for correction to the originator. With Banner HR 8.10, a Superuser will be able to access the EPAF and update the Effective Date as needed.

This new functionality allows a Superuser to make final updates to an EPAF, without disturbing the original approver routing. Once a transaction is ready (Pending an Apply), the Superuser will now have the opportunity to update any field on the EPAF transaction, in order to ensure that it can successfully be applied. This allows for any last minute changes prior to updating the employee’s database records.

A new Transaction Status, Superuser Update Status (U), is introduced for this enhancement. Once the Superuser has changed one or more fields and saved the changes, the transaction will assume the Superuser Update Status (U). The Superuser will then need to submit the transaction once again in order to execute all edits against the transaction to assure completeness. Upon a successful submit, the transaction is ready to be applied.

For audit purposes, any Superuser changes will be recorded with a user note on the EPAF Comment table, detailing the date/time, user, and which portion of the transaction was changed. This enhancement is available for both Banner INB and Employee Self Service.

Processing steps for Superuser update

The following steps illustrate the processing that takes place with the new Superuser update.

• Superuser selects an Approved transaction (pending Apply).

• Transaction fields are enterable, so the Superuser makes changes and saves the changes.

• EPAF status changes to Superuser Update.

• Audit Comment is inserted.

• Superuser submits the EPAF for editing, and the transaction returns to Approved status.

• You can now perform an Apply online, or run NOPEAMA.

8man Resources/sition Control Release Guide | Electronic Approval Superuser Override- Functional

HuPo

New Administrator Proxy Rules form (NTRAPRX) - Functional

This section details the functional changes made for enhancement CMS-RPE 31893.

The purpose of this rule form is to allow an Administrator access to view and update an employee’s designated proxies. A proxy is an individual who is authorized to take action in a user’s absence. NTRAPRX reflects information the employee has created on the Electronic Approval Proxy Rule Form (NTRPROX) or in Self-Service.

The Administrator Proxy Rule Form (NTRAPRX) allows an Administrator to view or change Electronic Approval Proxy rules for an employee. Changes made on this form will affect records on the Electronic Approval Proxy Rule Form (NTRPROX).

The Administrator Proxy Rule Form consists of the following blocks and windows:

• Key block - Enter or search for any existing ID in the Enterprise Access Controls Form (GOAEACC)

• Electronic Approval window

• Other Modules window

9man Resources/sition Control Release Guide | New Administrator Proxy Rules form (NTRAPRX) - Functional

HuPo

The Administrator Proxy Rules form (NTRAPRX) has been added to two menus: The Electronic Approvals Rules menu and the Human Resources Administration Rules menu.

Refer to the help topic for NTRAPRX in the Banner Online Help system for more detailed information about this form.

10man Resources/sition Control Release Guide | New Administrator Proxy Rules form (NTRAPRX) - Functional

HuPo

Support for International Bank Account Number - Functional

This enhancement (1-1F0QEZZ) supports the changes that are needed to accommodate an expansion of the bank routing and account number fields in Banner for the International Bank Account Number (IBAN). This enhancement affects international clients who use IBAN, and it touches a number of Banner applications. For Banner Human Resources, it affects direct deposit processing of payroll funds.

Ellucian realizes that in the United States, Canada, and for international clients who choose not to use IBAN, it is imperative that the implementation of this IBAN enhancement does not disrupt existing direct deposit processing procedures. Special care has been taken to ensure that there is seamless processing for clients who do not use IBAN.

IBAN numbers can consist of the digits 0-9 and the upper case Latin letters A-Z. This is true even in countries where these characters are not part of the national language (i.e., Israel). To support IBAN in Banner requires expanding the bank identification code from 9 to 11 characters and the account number from 17 to 34 characters.

If your institution has licensed Banner HR and is in the US, you must ensure that the Nation code on the Installation Controls form (GUAINST) is populated with a nation code where the MMREF Code field on the Nation Code Validation form (STVNATN) = US.

If your institution has licensed Banner HR and is in Canada, you must ensure that the Location on the Position Control Installation Rules form is set to Canada.

Banner General and Banner Finance Companion Release Information for IBAN

For those international institutions who wish to implement IBAN and license either Banner Finance, Banner HR, or Banner Employee Self-Service, you must independently install the following version of Banner General.

• Banner General 8.6.1

You must also independently install these versions of the applications you have licensed.

• Banner Finance 8.6

• Banner Human Resources 8.10

• Banner Employee Self-Service 8.10

The full functionality of the IBAN enhancement will not be usable until you upgrade to these versions for each application that you license.

11man Resources/sition Control Release Guide | Support for International Bank Account Number - Functional

HuPo

Note: Refer to the release guides associated with each product for information about the changes required in each product.

Banner General and HR updates

There were a number of changes to Banner General for the IBAN enhancement, in addition to the changes to Banner HR. The following is a brief summary of the changes to both applications.

Banner General updates

New entries to control the editing and style of bank identification codes (international) and bank routing numbers (US and Canada), as well as bank account numbers have been created on the Crosswalk Validation form (GTVSDAX). You can refer to the GTVSDAX form in Banner Online Help for information about the settings you need to use on GTVSDAX to implement IBAN.

The following provides a summary of the two new rules on GTVSDAX that you will need to be aware of to implement the IBAN enhancement.

BANK_ROUT

Use the BANK_ROUT entry to establish the edit rules for the bank identification code (routing number).

According to international banking standards, bank identification code validation is defined as 6 LETTERS followed by 2 LETTERS or NUMBERS followed by an optional 3 LETTERS or NUMBERS. The length is always 8 or 11 since the last 3 are optional. According to US and Canadian banking standards, the bank routing number is a number, with a maximum of 9 digits. The default external code delivered via seed data is N09. Clients in the US and Canada should not change this value.

Leaving this value at the default of N09 prevents users from updating the ACH information (originating Bank routing Number) on the Bank Code Rules form (GXRBANK). It will also prevent users from entering an incorrect routing number in the following areas:

• the Bank Routing Number Validation form (GXVDIRD)

• the Direct Deposit Recipient form (GXADIRD)

• the Update Direct Deposit page in Employee Self-Service


HuPo

The rules are defined under Group=IBAN, Internal Code=BANK_ROUT, Sequence=1. The External Code may have one of the following values

BANK_ACCT

Use the BANK_ACCT entry to establish the edit rules for the bank account number.

According to US and Canadian banking standards, the bank account number is a maximum of 17 characters in the US and 12 characters in Canada. The default external code delivered via seed data is X17. Clients in the US and Canada should not change this value.

Leaving this value at the default of X17 will prevent users from updating ACH information on the Bank Code Rules form GXRBANK. It will also prevent users from entering an incorrect routing number in the following areas:

• the Bank Routing Number Validation form (GXVDIRD)

• the Direct Deposit Recipient form (GXADIRD)

• the Update Direct Deposit page in Employee Self-Service

The rules are defined under Group=IBAN, Internal Code=BANK_ACCT, Sequence=1. The External Code may have one of the following values:

0 Do not validate - The forms will be limited to the size of the data base field, but no other editing will be performed.

1 If ANY alpha characters exist, then generate WARNING if BIC validation fails (allows a mix of IBAN and non-IBAN bank numbers).

2 If ANY alpha characters exist, then generate ERROR if BIC validation fails (allows a mix of IBAN and non-IBAN bank numbers).

3 Force validation on all bank numbers and generate an ERROR if BIC validation fails

Xnn Generate an ERROR if the bank number exceeds nn characters in length.

Nnn Generate an ERROR if the account number exceeds nn in length or if there are any non-numeric characters (Default value is N09).

0 Do not validate - The forms will be limited to the size of the data base field, but no other editing will be performed.

1 If ANY alpha characters exist, then generate a WARNING if IBAN MOD 97 validation fails (allows a mix of IBAN and non-IBAN accounts).


HuPo

An IBAN is validated by converting it into an integer and performing a basic mod-97 operation (as described in ISO 7064) on the number. If the IBAN is valid, the remainder equals 1. The algorithm of IBAN validation is as follows:

1. Check that the total IBAN length is correct as per the country. If not, the IBAN is invalid. NOTE - Banner does not validate that the IBAN length is correct per country.

2. Move the four initial characters to the end of the string.

3. Replace each letter in the string with two digits, thereby expanding the string, where A = 10, B = 11....., Z = 35.

4. Interpret the string as a decimal integer and compute the remainder of that number on division by 97.

If the remainder is 1, the check digit test is passed and the IBAN might be valid.

Example (fictitious United Kingdom bank, sort code 12-34-56, account number 98765432):

Banner HR updates

In order to protect the integrity of the data in Banner HR for direct deposit records, new edits are in place during data entry of bank and direct deposit records for those clients who are in the US or Canada. For these clients, regardless of the GTVSDAX settings for the BANK_ROUT and BANK_ACCT entries, no routing numbers in excess of 9 digits or account numbers in excess of 17 characters will be permitted.

These edits are enforced for US clients when the nation code on the Installation Controls form (GUAINST) is set, and the value that is used has a corresponding entry on the Nation Code Validation form (STVNATN), where the MMREF Code is set to US.

These edits are enforced for Canadian clients when the Location on the Position Control Installation Rules form (NTRINST) is set to Canada.

2 If ANY alpha characters exist, then generate an ERROR if IBAN MOD 97 validation fails (allows a mix of IBAN and non-IBAN accounts).

3 Force validation on all accounts and generate an ERROR if IBAN MOD 97 validation fails.

Xnn Generate an ERROR if the account number exceeds nn characters in length (Default value is X17).

Nnn Generate an ERROR if the account number exceeds nn in length or if there are any non-numeric characters .

IBAN: GB82 WEST 1234 5698 7654 32

Rearrange: W E S T12345698765432 G B82

Convert to integer: 3214282912345698765432161182

Compute remainder: 3214282912345698765432161182 mod 97 =1


HuPo

Clients in the US and Canada should not change the external code default values on the Crosswalk Validation form GTVSDAX for the entries BANK_ROUT (N09) or BANK_ACCT (X17).

For international clients who use IBAN, only the last 16 characters of the account number, preceded by an asterisk, will be displayed on checks and direct deposit advices produced from the check print processes PHPCHEK and PHPCHKL, as well as the Payroll Register report, PHRPREG.


HuPo

Electronic Approval Superuser Override- Technical

This section details the technical changes made for enhancement 1-5WNHJF.

Changed packages

The following packages were changed for this enhancement.

NOKEPAF (nokepa1.sql)

Modified the procedure p_edit_ea_approver_action. The Superuser update access gets the Invalid action error when changes are made to the approval action.

Modified select_string in p_open_approval_rc procedure to handle sorting in case.

NOKEPCR (nokepcr.sql/nokepc1.sql)

Added procedure p_insert_superuser_comment to insert comments in the norcmnt database table.

Added procedure p_superuser_submit to insert comments and update transaction status to Approved if superuser Submits the EPAF transaction.

Modified procedures p_submit_epaf_initial_edit and p_submit_epaf to check the transaction status before calling p_superuser_submit procedure.

NOKLIST (noklis1.sql)

Added transaction type Superuser Update in the NOBTRAN_TRANS_STATUS_IND list and added action type Superuser Submit in NORROUT_ACTION_IND list.

Changed Forms

The following forms were modified for this enhancement.

16man Resources/sition Control Release Guide | Electronic Approval Superuser Override- Technical

HuPo

Electronic Approval Summary (NOAAPSM)

The list of transaction status in the TRANSACTION_STATUS key block item is modified to add the new status, Superuser Update. The GET_QUEUE_STATUS trigger is modified for the edit of valid queue status versus the new transaction status. The POST-CHANGE trigger of NOBTRAN_TRANS_STATUS_IND item is modified to add the new transaction status, Superuser Update.

Electronic Personnel Action (NOAEPAF)

Modified procedure POPULATE_NHQTRAN_RG to include the Transaction Status Superuser Update (U).

Modified form trigger CHECK_IF_UPDATEABLE to allow the superuser to update the transaction.

Modified form trigger ENABLE_BOTTOM_BUTTONS to display the options menu APPLY, SUBMIT for Superuser update transaction.

Modified the PRE-BLOCK trigger for NORROUT to disable the routing queue.

Added new procedure p_superuserupdate and p_superusersubmit to update the transaction status and insert comment for the superuser.

Modified the form trigger CHECK_FYI to navigate until the last record and allow different users for Approver Action FYI.

Modified the form trigger OPTM_SUBMIT to not make any updates to the routing queue for superuser update.

The procedure p_superusersubmit is called to change the transaction status to approved and insert a comment.

Modified the KEY-COMMIT trigger for the blocks NORTERN, NORTLBD to call the procedure p_superuserupdate.

Modified the PRE-UPDATE trigger for the blocks NORTRAN to call the procedure p_superuserupdate.

Modified CHECK_STATUS_IND function to include the Superuser Update and Approved transaction status so that key-next-item would move to the next data enterable field instead of approver action.

Modified the form trigger OPTM_SUBMIT to check for edits related to the routing queue for R and W transaction status.

Changed processes

The following processes were modified for this enhancement.


HuPo

Electronic Approvals Report (noraptr.pc)

Validate_trans_status and sel_nobtran routines of this process are modified to add the new Superuser Update transaction status.

Mass Salary Table Update (nbpmass.pc)

Sel_pending routine is modified to add the new Superuser Update transaction status into selection criteria.

New seed data

The following job submission has been added for this enhancement.

Script Reason

ngjbpdefu_081000.sql Modifies job submission help text for parameter 01 to GENERAL.GJBPDEF Jobs Parameter Definition table for the NORAPTR report.

ngjbpvali_081000.sql Adds job submission value for parameter 01 to GJBPVAL records for the new transaction type U for Position Control NORAPTR 8.10 process.


HuPo

New Administrator Proxy Rules form (NTRAPRX) - Technical

This section details the functional changes made for enhancement CMS-RPE 31893 and defect 1-QCRQL2.

Changed tables

The following tables were changed for this enhancement.

Proxy Rules Table (NTRPROX)

A new column has been added to this table.

Proxy Rules Table (NTRPRXY)

One new column has been added to this table.

New scripts

The following scripts are delivered for this enhancement.

Note: Unless otherwise noted, new scripts are run as part of the upgrade process for a release.

Column Data TypeNull / Not Null Comments

NTRPROX_ADMIN_ID VARCHAR2(30) Null PROXY ADMIN ID: The Oracle ID of theadministrator who changed the record.

Column Data TypeNull / Not Null Comments

NTRPRXY_ADMIN_ID VARCHAR2(30) Null PROXY ADMIN ID: The Oracle ID of theadministrator who changed the record.

19man Resources/sition Control Release Guide | New Administrator Proxy Rules form (NTRAPRX) - Technical

HuPo

.

New Seed Data

The following job submission data has been added for this enhancement.

Changed APIs

The following API was modified for this enhancement.

Proxy API

ntkd_ntrprxy0.sql

A new constant, M_NTRPRXY_ADMIN_ID is added to save the user ID of the administrator who changed the proxy records, other than the actual user.

Script Reason

ntrprox_081000_01.sql Adds a new column NTRPROX_ADMIN_ID.

ntrprox_081000_02.sql Adds column comments for the new column NTRPROX_ADMIN_ID.

ntrprxy_081000_01.sql Adds a new column NTRPRXY_ADMIN_ID.

ntrprxy_081000_02.sql Adds column comments for the new column NTRPRXY_ADMIN_ID.

Script Reason

ngubobjsi_081000.sql Adds the new NTRAPRX Administrator Proxy Rule form record to the GENERAL.GUBOBJS General Object Base table.

ngurmenui_081000.sql Add the new NTRAPRX Administrator Proxy Rule form record to the GENERAL.GURMENU General Menu Repeating table.

nguroptmi_081000.sql Adds new options menu records to GENERAL.GUROPTM table for the NTRPRXY form.


HuPo

ntkb_proxy0.sql/ntkb_proxy1.sql

A new column ntrprxy_admin_id is added to save the user ID of the administrator who changed the proxy records, other than the actual user. A new administrator user ID value is added into various routines and proxy_rec record type.

ntkb_proxy_r0.sql/ntkb_proxy_r1.sql

Administrator ID who changes proxy records other than the actual user is validated.

ntkb_proxy_s0.sql/ntkb_proxy_s1.sql

A new error message, “Admin ID for the nb_proxy is not valid,” for the new admin ID column is added. Few other messages are modified to follow API Standard.


HuPo

Support for International Bank Account Number - Technical

The following technical changes were made for the International Banking enhancement (1-1F0QEZZ).

Changed Tables

The following tables have been modified for this enhancement.

Document Number Repeating Table (PHRDOCM)

Column size of the PHRDOCM_BANK_CODE was increased from 9 to 11 and the column size of the PHRDOCM_BANK_ACCT_NO was increased from 17 to 34.

Document Number Repeating Table (PEBPAYM)

Column size of the PEBPAYM_BANK_ROUT_NUM was increased from 9 to 11 and the column size of the PEBPAYM_BANK_ACCT_NUM was increased from 17 to 34.

New Scripts

The following new scripts are delivered with this enhancement.

Note: Unless otherwise noted, new scripts are run as part of the upgrade.

Script Reason

phrdocm_081000_01.sql Increase the column size for two columns: PHRDOCM_BANK_CODE from 9 to 11 and PHRDOCM_BANK_ ACCT_NO from 17 to 34

pebpaym_081000_01.sql Increase the column size for two columns: PEBPAYM_BANK_ROUT_NUM from 9 to 11 and PEBPAYM_BANK_ACCT_NUM from 17 to 34

22man Resources/sition Control Release Guide | Support for International Bank Account Number - Technical

HuPo

Changed Packages

The following database packages have been modified for this enhancement.

PEKLIBS (peklibs.sql/peklib1.sql)

This package has been updated to include these new functions:

• peklibs.f_iban_acct_print_format

• peklibs.f_iban_installed_general

• peklibs.f_valid_format_bank_acct_num

• peklibs.f_valid_format_bank_rout_num

NOKINST (nokinst.sql / nokinst1.sql)

This package has been updated to include a new routine, f_check_nation, to check if an institution is US, Canada, or international. This function returns (Y)es for US/Canada and (N)o for others.

Changed Forms

The following Banner forms have been modified for this enhancement.

PEA1PAY

This form has been modified to change the Max size and the Width of the PEBPAYM_BANK_ROUT_NUM and PEBPAYM_BANK_ACCT_NUM fields to allow up to 11 characters for the Bank Routing Number and up to 34 characters for the Account Number to support IBAN data. The Post-Change trigger was updated to call the new peklibs functions to support the IBAN edits. New error messages have been added for US and Canada when Routing Number exceeds 9 characters and Account Number exceeds 17 characters.

PHAADJT

This form has been modified to change the Max size and the Width of the PHRDOCM_BANK_CODE and PHRDOCM_BANK_ACCT_NO fields to allow up to 11 characters for the Bank Routing Number and up to 34 characters for the Account Number to support IBAN data. The Check_bank_Info trigger was updated to call the new peklibs


HuPo

functions to support the IBAN edits. New error messages have been added for US and Canada when Routing Number exceeds 9 characters and Account Number exceeds 17 characters.

Changed Processes

The following processes were modified for this enhancement.

PHPCHEK/PHPCHKL

These two processes have been modified to add a new variable, bank_acct_num, to hold up to 34 characters for the bank account number. If the account number exceeds 17 characters, print the last 16 characters with a preceding asterisk.

PHRPREG

This report has been modified to add a new variable, rpt_bank_acct_no to hold up to 34 characters for the bank account number. If the account number exceeds 17 characters, print the last 16 characters with a preceding asterisk. The rpt_bank_code variable size was increased to hold up to 11 characters for the bank routing number.


HuPo

Banner Integration for Ellucian Talent Management - Technical

The following technical updates are included in this 8.10 release for the Banner Integration for Ellucian Talent Management Suite.

Updated Scripts

The following scripts were delivered previously and are re-delivered in this release. Depending on the order of installation of Banner Event Publisher, in combination with the upgrade of Banner Human Resources and Banner Employee Self-Services to 8.9 or 8.8.2, you may or may not need to apply these scripts. For specific details about the execution of these scripts, please see Article 000027950 in the Ellucian Support Center.

Script Reason

bemi_08090009.sql Insert new EVENTS.BUSINESS_EVENT_METADATA records for Banner Integration Talent Management enhancement

bemu_08090009.sql Disables the EVENTS.BUSINESS_EVENT_METADATA records

portmsbi_08090009.sql Inserts new records for Business Event Mappings

portmsed_08090009.sql Deletes the Custom Employee Class service event

portmsmd_08090009.sql Deletes all the SQL mapping records for Talent Management

The new SQL mappings will be re-inserted with correct information.

portmsmi_08090009.sql Inserts new SQL mapping records for Division, Position, Cost Center, Grade, Location, and User

25man Resources/sition Control Release Guide | Banner Integration for Ellucian Talent Management - Technical

HuPo

Resolutions

For details about the specific defects associated with the 8.10 Banner Human Resources and 8.10 Banner Position Control release, refer to the Banner Human Resources 8.10 Resolution Report and the Banner Position Control 8.10 Resolution Report. These Resolution Reports can be found in the Documentation Libraries under each product in the Ellucian Support Center.

Along with the Problem, Impact, and Resolution statements for each defect, you will find a Link. By copying and pasting the link into a web browser, you will be redirected to the Ellucian Support Center and the specific details of the change request.

26man Resources/sition Control Release Guide | Resolutions

HuPo

Problem Resolutions - Technical

This section provides the detail on technical changes for defect corrections that require further explanation than what is included in the Resolutions Report.

Advance queuing when using Oracle RAC (1-1CBHTLZ)

The following technical changes were made for this defect correction.

New Scripts

The following new scripts are delivered for this defect.

Note: Unless otherwise noted, new scripts are run as part of the upgrade.

Script Reason

pgtvsdaxi_08090002.sql Create rows in GTVSDAX table that will control the communication mechanism to be used in PXAW2CC form. Use Advanced Queuing or continue to use DBMS_PIPES. These rows are created set to N. This will indicate that core processing should continue to work as it always has and communicate using DBMS_PIPES.

pqueqtabc_08090002.sql Create queues and queue tables and start the created queues in support of an alternative for DBMS_PIPES. These queues can be used for publishing and consuming message content. Instead of the message content going over the PIPE, it will instead go through a message queue.

27man Resources/sition Control Release Guide | Problem Resolutions - Technical

banner human resources/position control release guide 8 · employee self-service release guide...

Documents