« Agenda for Thursday's Meeting | Main | Extended System Maintenance »

Q & A from Thursday's Meeting

A recap of the questions from yesterday's meeting on the upcoming EFS Conversion:

  • Q: Is UM_ENTITY the same as CUFS_AREA or DEPTID? If so, why the duplicate?

    A: During conversion for the new financial system, only entries for active employees will be converted. For these individuals, UM_ENTITY will contain the 4-character data values that were previously carried in the DEPTID column. DEPTID will contain a 5-digit value matching the financial system. CUFS_AREA will be blank. Entries for non-active employees, e.g. terminated employees, will not be converted. For them, UM_ENTITY will be blank, DEPTID will be the old 4 character data value and CUFS_AREA will contain the old CUFS area value that corresponds to the 4 character DEPTID value.

  • Q: Will AREA CLASS be replaced?

    A: Yes, by RRC. But, for FY 2008 and older, tables will still have AREA_CLASS. FY 2009 and newer will have RRC.

  • Q: Is access to DWTEST confined to Functional IDs?

    A: No. You can request access to DWTEST via the ARF. You will be given the same access to data that you have in DWPROD. You will NOT be given access to data from the new financial system.

  • Q: For people without Functional IDs: How can we combine payroll and financial info? Is it correct that the new reports won't detail people's expenses (i.e. HR and Financial data together)?

    A: Individuals without Functional IDS who want to combine data from the financial and payroll systems will have to download the information separately from the Financial Reporting Instance and the Data Warehouse and combine it in a local application such as Excel. For information that can be found in system provided reports, contact the EFS project.

    Q: How will those without Functional IDs get them?

    A: The process for securing a Functional ID is documented on the Data Security web page. Once the ID is secured, requests for access to the financial gateway views can be submitted to the EFS project. However, access to these views is restricted and requires significant justification. For most individuals, access to financial data will be through the reporting instance.

  • Q: : Is there a DEPTID map table created?

    A: Yes, and you don't need a Functional ID to access. It will be available as one of the setup tables in the data warehouse.

  • Q: Will a Functional ID guarantee direct access to financial tables?

    A: No. While a Functional ID is a requirement for access financial data via the gateway, it is not all that’s needed to get access. Requests for direct access will be evaluated on a case by case basis. They must demonstrate that local requirements cannot be met through the standard reporting instance access.

  • Q: Can you get FY 2009 financial data without a Functional ID?

    A: Yes. You can access it through the reporting instance, just not through the data warehouse.

  • Q: Can you clarify what data can be seen in DWPROD/DWTEST and the Reporting Instance as well as what type of ID you need to see it?

    A: In DWTEST you will be able to access historical and post financial implementation HR, Payroll and student data as we make modifications, as well as historical financial data from CUFS. In DWPROD you will be able to access historical and post financial implementation HR, Payroll and student data, as well as historical financial data from CUFS. Information from the new financial systems is and will be available from the Financial Reporting Instance. You use your normal data warehouse user ID for accessing these data.

    In DWTEST now and in DWPROD after 7/1, you will be able to access some financial data from the new system IF you request it and are approved. You will need a Functional ID to get this access. Your access will only be approved if you have a local application requiring financial data that must be loaded via an automatic process. This type of access is not to be used for ad hoc querying. Ad hoc querying of financial data must be done in the Financial Reporting Instance.

  • Q: What's corollary to PS_UMN_DEPT_TREE?

  • Q: Are these posted dates (on the blog) the dates when the updates will actually happen in DWPROD?

    A: Yes.

  • Q: So, how long will jobs be down?

    A: No more than two days (hopefully).

  • Q: What will happen if our (an end user's) job runs before the table is released from testing (after conversion)?
    A: It will be unavailable until we're finished testing the table. Access to tables will be removed until they’ve been completely tested. You will get a table/view does not exist error if you try to use a table that has not had its access restored yet.

  • Q: Where is the best place to find out the most current deployment/change dates?

    A: The blog.

  • Q: How do you get access to other PPLSoft departments?

    A: Go to the access forms page.

  • Q: How do you get new views, or customized views added to those available via the gateway?

    A: No formal process in place--contact Bill Decker.

  • Q: Will the Academic Health Center's customized (user specific) views be updated as well?

    A: Yes.

  • Q: Will the Sponsored Financials Reports on the web get updated after CUFS goes away?

    A: No. Go to EFS Reporting Instance for FY 2009 and use the reports that have been developed there.

  • Q: Who's going to own UM Reporting? Who can I talk to about additional financial reporting after implementation?

    A: We don’t know for sure at this time. No owner or process is specified that we know of. Contact the project?

  • Q: Will Lookup tables be available for the various CHARTFIELD values?

    A: Yes, these tables will be available as setup tables. It will also be possible to see current values for these CHARTFIELDs via data dictionary queries.

  • Q: Many tables have been mapped--is a big Data Dictionary project in PPLSoft in the works?

    A: We don't know. Perhaps in the future. In the meantime, PSQUERY in financial reporting instance has some data dictionary capability, provided by PPLSoft.

  • Q: Question about specific columns in Tuition.

    A: Look at DWTA specs on the blog.