Financial Information Services

KDW-Prime is a copy of KDW, but without any labor detail. This was made available by CIT, and supported by DFA, as an interim solution for units who have developed, and now need to remediate, local reporting systems using Brio Designer. The long-term objective is to transition to using the new OBIEE+ tools. Brio Designer users can request access to KDW-Prime by e-mailing Sarah Christen.

While Brio (Hyperion Interactive Reporting) is no longer being used to deliver monthly accounting reports, the tool itself is still available. A copy of the data warehouse (without the labor detail) called KDW-Prime can be used by Brio Designer users to remediate local reporting systems.

The new tools are very interactive and allow users to “query” their financial information in a number of ways – right on the dashboards, without having to write their own ad hoc queries.

Brio (Hyperion Interactive Reporting) will no longer be used to deliver monthly accounting reports. Financial information will now be delivered using Oracle Business Intelligence Enterprise Edition (OBIEE+) dashboards.

The Kuali (Financial) Data Warehouse (KDW) replaces the Accounting Data Warehouse (ADW) as the repository of financial data, beginning in fiscal year 2011-12, with the implementation of the Kuali Financial System (KFS).  

There are two ways to see what roles a person has in the system. If you are a KFS User, go to the Administration tab, then in the System panel. Under the Identity header, you will see "Person, Group, Role..." From there, choose one of these methods:
 

You may see an error that reads something like, "kfs-prod:the KFS Form you were using:Could not open OJB PersistenceBroker; nested exception is org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=enWorkflowDataSource, user=null, password=..."

In the legacy world, applications like JEMS and the Payment Request System were completely separate applications from the actual financial system on the mainframe. KFS is different in that we are processing our transactions in the live production system. As a result, occasionally you may be trying to make a transaction using an item (e.g., an account, vendor, etc.) that someone else is also working on, thereby "locking" that item. When this happens, you will not be able to save or submit your e-doc, but you can resolve the situation by doing the following:

The Disbursement Voucher uses address information maintained in Workday and PeopleSoft as the address for reimbursements to faculty and staff members, alumni, and students. The home address is used for faculty, staff members and alumni. Any address information is updated by the employee through Workday.

The address used for students is the best address we have on file in PeopleSoft. Any address is updated by the student using Student Center, a self-service application.

If the payment is taxable, the individual must be set up as a vendor. Prizes, awards, and stipends require vendor setup, even if the individual is a Cornell student.