Banner Human Resources/Position Control Release Guide 8

Transcription

BannerHuman Resources/Position Control Release GuideRelease 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 EllucianRecruiter 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 issubject to the terms and conditions of one or more written license agreements between Ellucian and the licensee in questionIn preparing and providing this publication, Ellucian is not rendering legal, accounting, or other similar professional services. Ellucian makes noclaims that an institution's use of this publication or the software for which it is provided will guarantee compliance with applicable federal or statelaws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers ofthe organization's own choosing.Prepared by: Ellucian4375 Fair Lakes CourtFairfax, Virginia 22033United States of America

ContentsIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Enhancements for 8.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Cumulative Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Electronic Approval Superuser Override- Functional. . . . . . . . . . . . . . . 8New Administrator Proxy Rules form (NTRAPRX) - Functional. . . . . . . 9Support for International Bank Account Number - Functional . . . . . . . 11Banner General and Banner Finance Companion Release Information for IBAN 11Banner General and HR updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Banner General updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BANK ROUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BANK ACCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Banner HR updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Electronic Approval Superuser Override- Technical . . . . . . . . . . . . . . . 16Changed packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16NOKEPAF (nokepa1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16NOKEPCR (nokepcr.sql/nokepc1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16NOKLIST (noklis1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Electronic Approval Summary (NOAAPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Electronic Personnel Action (NOAEPAF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Changed processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Electronic Approvals Report (noraptr.pc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Human Resources/Position Control Release Guide Contents3

ContentsMass Salary Table Update (nbpmass.pc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18New seed data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18New Administrator Proxy Rules form (NTRAPRX) - Technical . . . . . . . 19Changed tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Proxy Rules Table (NTRPROX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Proxy Rules Table (NTRPRXY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19New scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19New Seed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Changed APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Proxy API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20ntkd ntrprxy0.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ntkb proxy0.sql/ntkb proxy1.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ntkb proxy r0.sql/ntkb proxy r1.sql. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ntkb proxy s0.sql/ntkb proxy s1.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20212121Support for International Bank Account Number - Technical . . . . . . . . 22Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Document Number Repeating Table (PHRDOCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Document Number Repeating Table (PEBPAYM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Changed Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23PEKLIBS (peklibs.sql/peklib1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23NOKINST (nokinst.sql / nokinst1.sql) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23PEA1PAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23PHAADJT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Human Resources/Position Control Release Guide Contents4

ContentsChanged Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24PHPCHEK/PHPCHKL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24PHRPREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Banner Integration for Ellucian Talent Management - Technical . . . . . . 25Updated Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Problem Resolutions - Technical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Advance queuing when using Oracle RAC (1-1CBHTLZ) . . . . . . . . . . . . . . . . . . . . 27New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Human Resources/Position Control Release Guide Contents5

IntroductionThis release guide provides an overview of the Banner Human Resources/PositionControl 8.10 release. Release 8.10 includes enhancements and problem resolutions.System requirementsInstall the following minimum releases to upgrade to Banner Position Control 8.10.BannerGeneralPositionControl8.68.9Install the following minimum product releases to upgrade to Banner Human ontrol8.68.98.10Enhancements for 8.10This 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 ProcessingHuman Resources/Position Control Release Guide Introduction6

Cumulative DocumentationThis document provides detailed information about the Banner Human Resources/Position Control 8.10 release only. Banner Human Resources/Position Control 8.10 is acumulative release that also includes enhancements and problem resolutions deliveredsince the Banner Human Resources/Position Control 8.9 release.ReleaseNumber8.8.2*ContentsRelease DateInitial release of Banner Integration for EllucianTalent Management SuiteSeptember 2013* Release 8.8.2 was released after the 8.9 release. For more information about the initialrelease of the Banner Integration for Ellucian Talent Management Suite, you can refer tothe Banner Integration for Ellucian Talent Management Suite Handbook, BannerEmployee Self-Service Release Guide 8.8.2 and the Banner Human Resources ReleaseGuide 8.8.2. There is also a Quick Summary Guide available in the Commons.Human Resources/Position Control Release Guide Introduction7

Electronic Approval SuperuserOverride- FunctionalThis 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 aSuperuser, that person had to return the EPAF for correction to the originator. With BannerHR 8.10, a Superuser will be able to access the EPAF and update the Effective Date asneeded.This new functionality allows a Superuser to make final updates to an EPAF, withoutdisturbing 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 minutechanges prior to updating the employee’s database records.A new Transaction Status, Superuser Update Status (U), is introduced for thisenhancement. Once the Superuser has changed one or more fields and saved thechanges, the transaction will assume the Superuser Update Status (U). The Superuserwill then need to submit the transaction once again in order to execute all edits against thetransaction to assure completeness. Upon a successful submit, the transaction is ready tobe applied.For audit purposes, any Superuser changes will be recorded with a user note on the EPAFComment table, detailing the date/time, user, and which portion of the transaction waschanged. This enhancement is available for both Banner INB and Employee Self Service.Processing steps for Superuser updateThe following steps illustrate the processing that takes place with the new Superuserupdate. Superuser selects an Approved transaction (pending Apply). Transaction fields are enterable, so the Superuser makes changes and saves thechanges. 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.Human Resources/Position Control Release Guide Electronic Approval Superuser Override- Functional8

New Administrator Proxy Rules form(NTRAPRX) - FunctionalThis 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 anemployee’s designated proxies. A proxy is an individual who is authorized to take action ina user’s absence. NTRAPRX reflects information the employee has created on theElectronic Approval Proxy Rule Form (NTRPROX) or in Self-Service.The Administrator Proxy Rule Form (NTRAPRX) allows an Administrator to view orchange Electronic Approval Proxy rules for an employee. Changes made on this form willaffect 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 windowHuman Resources/Position Control Release Guide New Administrator Proxy Rules form (NTRAPRX) - Functional9

The Administrator Proxy Rules form (NTRAPRX) has been added to two menus: TheElectronic 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 detailedinformation about this form.Human Resources/Position Control Release Guide New Administrator Proxy Rules form (NTRAPRX) - Functional10

Support for International BankAccount Number - FunctionalThis enhancement (1-1F0QEZZ) supports the changes that are needed to accommodatean expansion of the bank routing and account number fields in Banner for the InternationalBank Account Number (IBAN). This enhancement affects international clients who useIBAN, and it touches a number of Banner applications. For Banner Human Resources, itaffects direct deposit processing of payroll funds.Ellucian realizes that in the United States, Canada, and for international clients whochoose not to use IBAN, it is imperative that the implementation of this IBAN enhancementdoes not disrupt existing direct deposit processing procedures. Special care has beentaken 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 istrue 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 9to 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 theNation code on the Installation Controls form (GUAINST) is populated with a nation codewhere 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 theLocation on the Position Control Installation Rules form is set to Canada.Banner General and Banner Finance CompanionRelease Information for IBANFor those international institutions who wish to implement IBAN and license either BannerFinance, Banner HR, or Banner Employee Self-Service, you must independently installthe following version of Banner General. Banner General 8.6.1You 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.10The full functionality of the IBAN enhancement will not be usable until you upgrade tothese versions for each application that you license.Human Resources/Position Control Release Guide Support for International Bank Account Number - Functional11

Note: Refer to the release guides associated with each product forinformation about the changes required in each product.Banner General and HR updatesThere were a number of changes to Banner General for the IBAN enhancement, inaddition to the changes to Banner HR. The following is a brief summary of the changes toboth applications.Banner General updatesNew entries to control the editing and style of bank identification codes (international) andbank routing numbers (US and Canada), as well as bank account numbers have beencreated on the Crosswalk Validation form (GTVSDAX). You can refer to the GTVSDAXform in Banner Online Help for information about the settings you need to use onGTVSDAX to implement IBAN.The following provides a summary of the two new rules on GTVSDAX that you will need tobe aware of to implement the IBAN enhancement.BANK ROUTUse 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 definedas 6 LETTERS followed by 2 LETTERS or NUMBERS followed by an optional 3LETTERS 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 alsoprevent 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-ServiceHuman Resources/Position Control Release Guide Support for International Bank Account Number - Functional12

The rules are defined under Group IBAN, Internal Code BANK ROUT, Sequence 1.The External Code may have one of the following values0Do not validate - The forms will be limited to the size of thedata base field, but no other editing will be performed.1If ANY alpha characters exist, then generate WARNING ifBIC validation fails (allows a mix of IBAN and non-IBANbank numbers).2If ANY alpha characters exist, then generate ERROR if BICvalidation fails (allows a mix of IBAN and non-IBAN banknumbers).3Force validation on all bank numbers and generate anERROR if BIC validation failsXnnGenerate an ERROR if the bank number exceeds nncharacters in length.NnnGenerate an ERROR if the account number exceeds nn inlength or if there are any non-numeric characters (Defaultvalue is N09).BANK ACCTUse 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 amaximum of 17 characters in the US and 12 characters in Canada. The default externalcode delivered via seed data is X17. Clients in the US and Canada should not change thisvalue.Leaving this value at the default of X17 will prevent users from updating ACH informationon the Bank Code Rules form GXRBANK. It will also prevent users from entering anincorrect 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-ServiceThe rules are defined under Group IBAN, Internal Code BANK ACCT, Sequence 1. TheExternal Code may have one of the following values:0Do not validate - The forms will be limited to the size of thedata base field, but no other editing will be performed.1If ANY alpha characters exist, then generate a WARNING ifIBAN MOD 97 validation fails (allows a mix of IBAN andnon-IBAN accounts).Human Resources/Position Control Release Guide Support for International Bank Account Number - Functional13

2If ANY alpha characters exist, then generate an ERROR ifIBAN MOD 97 validation fails (allows a mix of IBAN andnon-IBAN accounts).3Force validation on all accounts and generate an ERROR ifIBAN MOD 97 validation fails.XnnGenerate an ERROR if the account number exceeds nncharacters in length (Default value is X17).NnnGenerate an ERROR if the account number exceeds nn inlength or if there are any non-numeric characters .An IBAN is validated by converting it into an integer and performing a basic mod-97operation (as described in ISO 7064) on the number. If the IBAN is valid, the remainderequals 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 isinvalid. 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 ondivision 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 number98765432):IBAN:GB82 WEST 1234 5698 7654 32Rearrange:W E S T12345698765432 G B82Convert to integer:3214282912345698765432161182Compute remainder:3214282912345698765432161182 mod 97 1Banner HR updatesIn order to protect the integrity of the data in Banner HR for direct deposit records, newedits are in place during data entry of bank and direct deposit records for those clients whoare in the US or Canada. For these clients, regardless of the GTVSDAX settings for theBANK ROUT and BANK ACCT entries, no routing numbers in excess of 9 digits oraccount numbers in excess of 17 characters will be permitted.These edits are enforced for US clients when the nation code on the Installation Controlsform (GUAINST) is set, and the value that is used has a corresponding entry on the NationCode Validation form (STVNATN), where the MMREF Code is set to US.These edits are enforced for Canadian clients when the Location on the Position ControlInstallation Rules form (NTRINST) is set to Canada.Human Resources/Position Control Release Guide Support for International Bank Account Number - Functional14

Clients in the US and Canada should not change the external code default values on theCrosswalk 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 producedfrom the check print processes PHPCHEK and PHPCHKL, as well as the Payroll Registerreport, PHRPREG.Human Resources/Position Control Release Guide Support for International Bank Account Number - Functional15

Electronic Approval SuperuserOverride- TechnicalThis section details the technical changes made for enhancement 1-5WNHJF.Changed packagesThe following packages were changed for this enhancement.NOKEPAF (nokepa1.sql)Modified the procedure p edit ea approver action. The Superuser update access getsthe 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 norcmntdatabase table.Added procedure p superuser submit to insert comments and update transaction statusto Approved if superuser Submits the EPAF transaction.Modified procedures p submit epaf initial edit and p submit epaf to check thetransaction status before calling p superuser submit procedure.NOKLIST (noklis1.sql)Added transaction type Superuser Update in the NOBTRAN TRANS STATUS IND listand added action type Superuser Submit in NORROUT ACTION IND list.Changed FormsThe following forms were modified for this enhancement.Human Resources/Position Control Release Guide Electronic Approval Superuser Override- Technical16

Electronic Approval Summary (NOAAPSM)The list of transaction status in the TRANSACTION STATUS key block item is modified toadd the new status, Superuser Update. The GET QUEUE STATUS trigger is modified forthe edit of valid queue status versus the new transaction status. The POST-CHANGEtrigger of NOBTRAN TRANS STATUS IND item is modified to add the new transactionstatus, Superuser Update.Electronic Personnel Action (NOAEPAF)Modified procedure POPULATE NHQTRAN RG to include the Transaction StatusSuperuser Update (U).Modified form trigger CHECK IF UPDATEABLE to allow the superuser to update thetransaction.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 thetransaction status and insert comment for the superuser.Modified the form trigger CHECK FYI to navigate until the last record and allow differentusers for Approver Action FYI.Modified the form trigger OPTM SUBMIT to not make any updates to the routing queuefor superuser update.The procedure p superusersubmit is called to change the transaction status to approvedand insert a comment.Modified the KEY-COMMIT trigger for the blocks NORTERN, NORTLBD to call theprocedure p superuserupdate.Modified the PRE-UPDATE trigger for the blocks NORTRAN to call the procedurep superuserupdate.Modified CHECK STATUS IND function to include the Superuser Update and Approvedtransaction status so that key-next-item would move to the next data enterable fieldinstead of approver action.Modified the form trigger OPTM SUBMIT to check for edits related to the routing queuefor R and W transaction status.Changed processesThe following processes were modified for this enhancement.Human Resources/Position Control Release Guide Electronic Approval Superuser Override- Technical17

Electronic Approvals Report (noraptr.pc)Validate trans status and sel nobtran routines of this process are modified to add thenew Superuser Update transaction status.Mass Salary Table Update (nbpmass.pc)Sel pending routine is modified to add the new Superuser Update transaction status intoselection criteria.New seed dataThe following job submission has been added for this enhancement.ScriptReasonngjbpdefu 081000.sqlModifies job submission help text for parameter01 to GENERAL.GJBPDEF Jobs ParameterDefinition table for the NORAPTR report.ngjbpvali 081000.sqlAdds job submission value for parameter 01 toGJBPVAL records for the new transaction type Ufor Position Control NORAPTR 8.10 process.Human Resources/Position Control Release Guide Electronic Approval Superuser Override- Technical18

New Administrator Proxy Rules form(NTRAPRX) - TechnicalThis section details the functional changes made for enhancement CMS-RPE 31893 anddefect 1-QCRQL2.Changed tablesThe following tables were changed for this enhancement.Proxy Rules Table (NTRPROX)A new column has been added to this table.ColumnData TypeNull /Not NullNTRPROX ADMIN IDVARCHAR2(30)NullCommentsPROXY ADMIN ID: The Oracle ID of theadministrator who changed the record.Proxy Rules Table (NTRPRXY)One new column has been added to this table.ColumnData TypeNull /Not NullNTRPRXY ADMIN IDVARCHAR2(30)NullCommentsPROXY ADMIN ID: The Oracle ID of theadministrator who changed the record.New scriptsThe following scripts are delivered for this enhancement.Note: Unless otherwise noted, new scripts are run as part of the upgradeprocess for a release.Human Resources/Position Control Release Guide New Administrator Proxy Rules form (NTRAPRX) - Technical19

.ScriptReasonntrprox 081000 01.sqlAdds a new column NTRPROX ADMIN ID.ntrprox 081000 02.sqlAdds column comments for the new columnNTRPROX ADMIN ID.ntrprxy 081000 01.sqlAdds a new column NTRPRXY ADMIN ID.ntrprxy 081000 02.sqlAdds column comments for the new columnNTRPRXY ADMIN ID.New Seed DataThe following job submission data has been added for this enhancement.ScriptReasonngubobjsi 081000.sqlAdds the new NTRAPRX Administrator ProxyRule form record to the GENERAL.GUBOBJSGeneral Object Base table.ngurmenui 081000.sqlAdd the new NTRAPRX Administrator ProxyRule form record to the GENERAL.GURMENUGeneral Menu Repeating table.nguroptmi 081000.sqlAdds new options menu records toGENERAL.GUROPTM table for the NTRPRXYform.Changed APIsThe following API was modified for this enhancement.Proxy APIntkd ntrprxy0.sqlA new constant, M NTRPRXY ADMIN ID is added to save the user ID of theadministrator who changed the proxy records, other than the actual user.Human Resources/Position Control Release Guide New Administrator Proxy Rules form (NTRAPRX) - Technical20

ntkb proxy0.sql/ntkb proxy1.sqlA new column ntrprxy admin id is added to save the user ID of the administrator whochanged the proxy records, other than the actual user. A new administrator user ID valueis added into various routines and proxy rec record type.ntkb proxy r0.sql/ntkb proxy r1.sqlAdministrator ID who changes proxy records other than the actual user is validated.ntkb proxy s0.sql/ntkb proxy s1.sqlA new error message, “Admin ID for the nb proxy is not valid,” for the new admin IDcolumn is added. Few other messages are modified to follow API Standard.Human Resources/Position Control Release Guide New Administrator Proxy Rules form (NTRAPRX) - Technical21

Support for International BankAccount Number - TechnicalThe following technical changes were made for the International Banking enhancement(1-1F0QEZZ).Changed TablesThe 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 columnsize 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 thecolumn size of the PEBPAYM BANK ACCT NUM was increased from 17 to 34.New ScriptsThe following new scripts are delivered with this enhancement.Note: Unless otherwise noted, new scripts are run as part of the upgrade.ScriptReasonphrdocm 081000 01.sqlIncrease the column size for two columns:PHRDOCM BANK CODE from 9 to 11 andPHRDOCM BANK ACCT NO from 17 to 34pebpaym 081000 01.sqlIncrease the column size for two columns:PEBPAYM BANK ROUT NUM from 9 to 11 andPEBPAYM BANK ACCT NUM from 17 to 34Human Resources/Position Control Release Guide Support for International Bank Account Number - Technical22

Changed PackagesThe following database packages have b

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 . Refer to the help topic for NTRAPRX in the Banner Online Help system for more detailed information about this form. Human Resources/ 11 Position Control Release Guide .