13.07.2015 Views

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 23 Problem ResolutionsReports and Processes• (#88797)The Budget Roll Process (NBPBROL) was deleting all working budget recordsfrom the NHRTBUD table when budgets were approved. When approvingbudgets, records are moved from the NHRTBUD table to the NHRDIST table bythe Budget Roll Process (NBPBROL) process. Records being inserted anddeleted in the NHRTBUD table were based on Fiscal Year, Budget ID and Phase.This could cause Working Budget records to be in NBRPTOT, and associatedtables, with no corresponding NHRTBUD table record.This has been corrected to look at the Fiscal Year, Chart of Accounts, BudgetID and Phase whenever inserting or deleting data from the NHRTBUD table.Resolved in Position Control <strong>Release</strong> <strong>7.0</strong>.• (#88106)The Budget Roll Process (NBPBROL), when run to approve budgets, was notpopulating the NHRDIST_INTERFACED_IND field when moving informationfrom the Temporary Budget Table (NHRTBUD) to the NHRDIST table. This hasbeen corrected to synchronize the NHRTBUD and NHRDIST interfaced indicatorswhen records are copied from the NHRTBUD table. Thus, theNHRDIST_INTERFACED_IND would be a 'Y' if working budget records had beenfed to Finance Budget Development. Resolved in Position Control <strong>Release</strong> <strong>7.0</strong>.• (#88015)The Budget Roll Process (NBPBROL) was not considering the Chart ofAccounts value when rolling budgets into a working status. This problem onlyoccurred for those clients using multiple chart of accounts on salary budgetrecords. This happened when budgets had different chart of accounts values,but the same Budget ID and Phase. This defect had been corrected. Resolvedin Position Control <strong>Release</strong> <strong>7.0</strong>.NBPSPUP #94895Technical Fix: In nokfoa1.sql, when p_edit_foapal was called with a null value itimmediately exited. The cur_handle variable had already had a cursor assigned toit because it had been initialized in the declarative section. This caused an ORA-1000MAX OPEN CURSORS EXCEEDED and ORA-1001 INVALID CURSOR error inprograms that use this procedure such as the Salary Planner Update Process(NBPSPUP). Resolved in Position Control <strong>Release</strong> <strong>7.0</strong>.NHRBDSTNHRDISTNHREDSTNHRSDST(#85295)Previously, when trying to run processes Organization Payroll Distribution Process(NHRDIST), the Employee Distributions Report (NHREDST), the EmployeePayroll Summary by Organization Report (NHRSDST) and the Budget DistributionReport (NHRBDST) without entering the Chart of Accounts in various parameters,the processes would abort with an Oracle error message, ORA-01400: cannot insertNULL into ("GENERAL"."GJBCOLR"."GJBCOLR_VALUE”). This error message wasnot very user-friendly and gave no indication of the actual error. The processes havenow been modified to abort with an error message displayed in the log file as towhere the process stopped. Resolved in Position Control <strong>Release</strong> 6.1.January 2005 <strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 317

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!