Cloud Readiness / Oracle Student Aid Eligibility Cloud
What's New
Expand All


  1. Update 23C
  1. Revision History
  2. Overview
  3. Feature Summary
  4. Student Aid Eligibility
    1. Reports and Letters
        1. Upgrade of BI Publisher to OAS
        2. Reporting to Assist with Continuous Monitoring

Update 23C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Module Feature Notes
23 JUN 2023     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Student Aid Eligibility

Reports and Letters

Upgrade of BI Publisher to OAS

Reporting to Assist with Continuous Monitoring

Student Aid Eligibility

SUPPORTING DOCUMENTS

You can download additional documents and attachments to update and maintain your Student Financial Planning implementation. To view and download these documents, see Oracle Fusion Cloud Student Financial Planning: Release Notes 23C (Doc ID 2956278.1) on My Oracle Support at https://support.oracle.com. The supporting documents can include these:

  • Release preview slides and video
  • Resolved defects Configuration for new and updated baseline fields
  • API updates
  • Reporting subject documentation
  • Product report updates
  • Operation report updates
  • Known issues

Reports and Letters

Upgrade of BI Publisher to OAS

With update 23C we have upgraded BI Publisher to the latest version, which has been renamed to Oracle Analytics Server or OAS.  OAS is a powerful tool that enables your school to make better decisions, take informed actions, and implement more-efficient business processes.  In addition to all the current capabilities you have with BI Publisher; you can now take advantage of reporting audits as well as enhanced data chunking.  Data chunking can improve performance when running reports with large amounts of data.

The overall look and feel of OAS is very similar to that of BI Publisher. In order to provide a seamless migration, the following items will also be migrated from BI Publisher:

  • Product Reports and Letters
    • Same folder structure that currently resides in BI Publisher
  • Custom Reports and Letters
  • Roles and Permissions

We have also maintained continuity with the URLs, the existing URLs for BI Publisher will now direct you to your OAS instance.

Data Chunking

Data chunking is the process of grouping different bits of information together into more manageable or meaningful chunks.  By using data chunking you can reduce the time and memory used for processing large volumes of data.  Data chunking can be enabled at the instance level by your administrator and then selected granularly at the report and data model levels.

Audit Reports

Once you have your instance of OAS you will need to enable the "Monitoring and Audit" option on the OAS server settings. Once that is complete set the JNDI connection and download the Report file from the "Oracle Analytics Publisher Downloads" page where further instructions can also be found. The sample reports use the JNDI connection to fetch data from the data source for auditing.  The report layout and data models are pre-designed with sample reports, however you can customize the report layouts.  Each sample report is configured to run as a scheduled job because the size of the audited information can be large.

Steps to Enable

  • Private Keys will not be included in the migration for security reasons and will need to be reloaded into your OAS instance.  If you need your private key reloaded, please log an SR.  
  • If your school uses a Rest API to run reporting, you'll need to update the syntax for parameters; as the API went through a minor change.  You will need to include 'item' following 'listofParamNameValues' for each of the parameters passed in the API.  
    • For Example:

Tips And Considerations

  • As part of the migration, access to JasperSoft will be deprecated.
    • In preparation of this, we recommend exporting all reports and letters from JasperSoft to a local directory as you will no longer be able to access any custom queries from JasperSoft after the deprecation. 
    • Within SFP, the "Letter Engine Administrator" permission will be removed from any user and role currently assigned to that permission.  If your Role.csv workbook contains this permission it will fail to load, and you'll need to remove the permission in order to load config.
    • The "Letters Generation" UI will also be removed from SFP as all letters will now be generated out of OAS.
  • Access to the VM schema will be removed
    • OAS will not be able to access the VM Schema, please ensure all custom data models and reports are utilizing the Reporting Views for all data retrieval.  If you are having any issues re-writing a query to move from VM to reporting views, please log an SR for assistance. 

Key Resources

  • View Idea 664462 for details on the requested report audit logging

Reporting to Assist with Continuous Monitoring

Monitoring your financial aid process in a highly automated system is crucial to maintaining compliance and seamless ISIR processing.  Leveraging the new ISIR Delayed Processing Report will ensure there are no unnecessary delays in ISIR processing by identifying potential issues and providing with instructions on how to rectify the issue and advance your students through the financial aid process.

Delayed ISIR Processing Report

Building on additional ISIR reporting delivered in 23A, we have now included a Delayed ISIR Processing Report.  This report will help you determine if there are any potential delays with a Pending or Corrected ISIR that can be resolved by manual interaction or by reaching out to the student to direct them on next steps.  Any delays with an ISIR moving through the validation process can block or delay awarding funds to students.  Being proactive with these ISIRs can reduce frustration with the students and provide a more seamless awarding cycle.

Navigation to Report:

  • OAS > Catalog > Shared Folders > SFP Reports > Product Reports > Operational Reports > Delayed ISIR Processing Report

Suggested Monitoring Frequency:

  • We recommend this report be run weekly in order to ensure ISIRs are promptly moving to a valid status.

Run parameters:

  • Required
    • Award Year - This is a single select parameter.  If the report is needed for multiple award years it will need to be run individually per year
  • Optional
    • Start and End Date Range - Based on the date the ISIR was received 
    • ISIR Delay: In Days - Minimum number of Days the ISIR has been in a Pending or Corrected status (24 or less hours equals 1 day)
    • School Student ID - This can be used to narrow the report to an individual student

The following use cases are examples of what can be identified with the report:

  • ISIR has been in a Corrected Status for 5 days or longer
    • Potential issue with the department sending out ISIRs, or with SFP receiving ISIR.  Instructions on next steps can be found on the Reference Tab of the report.
  • ISIR has been in a Pending Status for 10 days or longer
    • There may be open ISIR tasks that need to be reviewed internally, or a communication may need to be sent to the student if the ISIR is Pending due to documents.

Steps to Enable

  • Access to the "Delayed ISIR Processing Report" is provided through delivered OAS Shared Folders.
    • Access for specific users can be controlled via your college or universities admin user.

Tips And Considerations

  • Delayed ISIR Processing Report suggested run parameters
    • ISIR Delay – Set the delay to 5 days. This will pull in any ISIR in a Corrected or Pending status for 5 days or greater
    • Award Year – This is a single select and should be run for each Award Year where ISIR processing is still open

Key Resources