Budget Alerts and Updates
Updated 1/30/08
- 1/30/08 IMPORTANT BROWSER SETTINGS CHANGES FOR CURRENT YEAR - Review browser configuration information before attempting to use CPBS Web.
- 1/23/08 Internet Explorer version 7.0 is not supported by Hyperion, please do not upgrade at this time.
- 2/10/05 - Windows XP SP2 - To export worksheets, modify browser security settings to allow prompting for downloads
- 1/19/05 - Windows XP SP2 - Allow pop-ups for CPBS Web logon
- 3/11/04 - Timing out of Account Inquiry report in CPBS
- 2/13/04 - Deleted Accounts
1/30/08 IMPORTANT BROWSER SETTINGS CHANGES
Please review the changes in the required browser configuration settings before attempting to logon to CPBS Web. New browser settings for the current year include changes to the required trusted and allowed pop-up sites.
1/23/08 Internet Explorer version 7.0 is not supported by Hyperion, please do not upgrade at this time.
The only supported browser for access to CPBS Web and the Brio-Hyperion Budget Datamarts is Internet Explorer version 5.5 service pack 2 through 6.x. For further information on important settings requirements for your browser see details on how to configure Internet Explorer.
Be sure to check the supported browser information before attempting to use CPBS Web.
2/10/05 - Modify browser security settings to allow prompting for downloads
IMPORTANT: The default settings included with the IE security enhancements in Windows XP SP2 disable the automatic prompting for downloads. As a result, the prompt to open or save an exported worksheet will fail. To allow the prompt, from the Tools menu in IE select Internet Options > Security > Custom Level > Downloads. Select "Enable" Automatic prompting for file downloads.
1/19/05: Allow pop-ups for CPBS Web logon
IMPORTANT: The pop-up blocker included with the IE security enhancements in Windows XP SP2 may cause the initial CPBS Web logon to fail. To prevent logon failure enter the following domains in the Tools > Pop-up Blocker Settings > Address of Web site to allow:
budegting-prod.cit.cornell.edu
dpb.cornell.edu
3/11/04: Timing out of Account Inquiry report in CPBS
Recently, we have had several users timing out when running the "Account Inquiry" report within CPBS Web. The mainframe behind the web application sometimes runs out of memory as it attempts to report on vast amounts of data. For example, if you are running this report for a large organization and only limit on your org number this report may time out due to lack of memory. We will continue to explore this issue.
If this happens to you, please consider using the Budget data marts in Brio-Hyperion - a good standard report that replicates much of the functionality in "Account Inquiry" is called "Detail Financial Planning Rept" and is located in the folder called "Financial Planning REPTS" within the Accounting Budget data mart.
Alternatively, run the web "Account Inquiry" report but break into smaller groups, for example by fund group range or by department range.
2/13/04: Deleted Accounts
Your planning process should include review of accounts that will be removed for the upcoming fiscal year. Deleted accounts cause major problems:
- Budgets on accounts that are flagged for deletion will not be loaded into the accounting system at the end of the budgeting cycle causing your budget to be out of balance
- Workforce records with labor distributions that include such accounts create an invalid transaction in Payroll and cause a delay in processing the charges.
A Brio-Hyperion standard report - the Budget Account Delete report has been created to display accounts with budget entries for the upcoming fiscal year that are flagged for deletion. Before completing your budget review, please process this query to ensure that labor distributions or financial planning budgets are not planned on "deleted" accounts. Access this report from the Cornell Brio-Hyperion Home Page (Accounting/Budget/Budget Acct Delete REPT).
Accounts that you plan to remove prior to the new fiscal year should be considered now and requests sent to Accounting. Requests processed in June are problematic and should be avoided.
