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

Student Financial Planning

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:
    • curl -X POST -u sfp-ops:*****  -o oas_curl_qasfp12_FastStudentAwardInformationReport_FN1_v1111.pdf -H "Content-Type:multipart/form-data"  -F "ReportRequest={\"attributeFormat\":\"pdf\",\"attributeTemplate\":\"Offer_Letter_FN_v2\",\"parameterNameValues\":{\"listOfParamNameValues\":{\"item\":[{\"name\":\"fasStudentId\",\"values\":{\"item\":\"1\"}},{\"name\":\"academicYearNumber\",\"values\":{\"item\":\"1\"}},{\"name\":\"latestAwardingVersionNumber\",\"values\":{\"item\":\"1\"}},{\"name\":\"packagingVersionNumber\",\"values\":{\"item\":\"1\"}}]}}};type=application/json" https://qa.sfp.ocs.oc-test.com/sfp12/bip/xmlpserver/services/rest/v1/reports/SFP%20Letters%20Samples%252FFasStudentAwardInformationReport_FN1/run

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

• For more information on OAS, see these resources:
  • Configuring OAS
  • Scheduling Reports with OAS
  • Creating Data Models with OAS
  • Designing Reports with OAS
  • Audit Report Download

Financial Plan Event Trigger for Provisional Aid Offer Letter

With this release, we have introduced a Provisional Aid Offer Letter (PO1 Letter), giving your institution a competitive advantage by producing an offer letter that incorporates funding that has not yet met "Awarding" criteria.  This letter can help your students make informed decisions on their financial aid and their ability to pay for school earlier in the process.  The Provisional Aid Offer Letter resembles the Offer Letter however we have added columns for Projected and Estimated funding along with the Awarded funds.  We've also enabled the letter engine to use the FasFinancialPlanOutboundv2Event as a letter trigger.  This event triggers with every package and repackage; providing you more flexibility when creating custom letters.

Provisional Aid Offer Letter (FasFinancialPlanOutboundReport_PO1)

Our provided baseline groovy script will trigger the letter when the following scenarios are met:

• Academic year contains any projected or estimated funds (both Title IV and/or NFF Funds) in an open ISIR Award Year AND any of the following conditions also exist:
  • Fund Amounts change from the prior generated FPO
  • COA for the Academic Year has been updated
  • Any Fund Status has been updated within the Academic year

The letter will no longer trigger when the ISIR Award Year has closed, or all funds in the Academic Year have progressed to an Awarded Status.

Navigation to the letter:

OAS > Shared Folders > SFP Letters Samples > FasFinancialPlanOutboundReport_PO1

Letter Parameters passed to OAS:

• Enrollment ID
• Academic Year Number
• Award Version Number
• Packaging Version Number

Financial Plan Event Trigger

The FasFinancialPlanOutboundv2Event is triggered each time the packaging engine creates a new packaging version for the student.  The following bindings will be available for your groovy scripts utilizing the FasFinancialPlanOutboundEvent:

• acy
• AllAwardYearIsirs
• AllAwardYearReceivedDocuments
• COA
• COD
• CommonLineLoans
• Disbursements
• Dloan
• Enrollment
• Enrollments
• FafsaAwardYearInfoList
• FasStudent
• FinancialPlan
• FundAcceptance
• FundCodeConfig
• IsirRecords
• PreviousFinancialPlan
• PrimaryProgram
• Program
• R2t4
• ReceivedDocuments
• Sap
• StudentGroups

Steps to Enable

• Within OAS
  • Update the product FasFinancialPlanOutboundReport_PO1 to incorporate your schools desired verbiage
  • Paste the updated letter into your SFP Letters folder 

• Configuration within Student Financial Aid
  • Letter.csv workbook
    • Add the FasFinancialPlanOutboundV2Event and PO1 letter (see baseline configuration for 23C)
  • ProvisionalAidOffer.groovy
    • Review the provided ProvisionalAidOffer.groovy script and make any necessary school specific updates

Tips And Considerations

• If you're using the baseline groovy script, students will receive both the Provisional Aid Offer Letter and an Offer Letter for the same Academic Year if there are both Awarded funds along with Projected/Estimated funds.  The groovy script can be updated if receiving both letters is not your schools expected scenario.  

• Letters utilizing the same triggering event will need to share the same Letter_Code_Criteria path location and groovy script.  If you decide to use the Provisional Aid Offer Letter and create a custom letter, please ensure your column 'I' on the Letter workbook is the same for both letters.

Key Resources

• Watch Financial Plan Event Trigger for Provisional Aid Offer Letter Readiness Training

• For more information, see these resources:

  • Idea 528989

Reporting to Assist with Continuous Monitoring

Monitoring your financial aid process in a highly automated system is crucial to maintaining compliance and a seamless flow from ISIR processing to disbursing.  These reports allow you to ensure there are no preventable delays in your ISIR processing and your disbursements disburse timely.  With advanced product reports your institution can be proactive in isolating potential issues and you're provided 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.

MPN and EC Reconciliation Report

Having a valid Master Promissory Note (MPN) and an Entrance Counseling (EC) on file is critical to maintain compliance while disbursing TIV funding.  With the MPN and EC Reconciliation Report you will now be able to monitor the influx of each file type, review students on the received files, and determine which students in SFP were included on the file.  This report can be used as an important tool to review files are being received and that matching logic is working correctly within SFP.  The report consists of 4 tabs:

• Summary Tab:
  • Provides an overall summary of files received within the data range
    • Total Number of Records Received
    • Total Number of students on the file - This will include all students on the file even if they are not in SFP.
    • File Type - MPN or EC
    • Total Number of unmatched students - This is the number of student records on the file not matched in SFP.  If a student has more than one record on the file, they will be counted more than once on this column

• MPN and EC Tabs (Both tabs are set up the same)
  • Provides student level detail for each file type, will also include student records not matched to a student in SFP
    • Student ID
    • SSN
    • First Name
    • Last Name
    • Award Year
    • Received date

• Reference Tab
  • Provides Parameter definitions, Legend, Suggested Monitoring Frequency, and Recommended Actions

Navigation to Report:

• OAS > Catalog > Shared Folders > SFP Reports > Product Reports > Operational Reports > MPN and EC Reconciliation Report

Suggested Monitoring Frequency:

• We recommend this report be run daily to validate received CRPN and CREC files are being matched to students.

Run parameters:

• Required
  • Start and End Date Range - Date range based on the received date of the MPN or EC file

• Optional
  • SSN - This can be used to pull an individual student record.  Using this parameter will pull in a student with the matching SSN if they are on any file received regardless of that files matching status in SFP.
  • SSN Masked - This allows you to determine how much, if any, of the SSN will be displayed when the report is rendered.

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

• Student has submitted an MPN or Entrance Counseling file and it has not been matched to them in Student Financial Planning
• Entire File fails to load or match to students
• MPN or EC disbursing criteria is "Not Met" in error

Steps to Enable

• Access to the "Delayed ISIR Processing Report' and the "MPN and EC Reconciliation 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

• MPN and EC Reconciliation Report suggested run parameters
  • File Received Start and End Date – If running daily as suggested, the start and end date should be run for the prior day
  • SSN Masked – This field allows you to run the report with various levels of security
    • No Mask - Full SSN will be displayed
    • Semi Masked - This will display the last 4 digits of the SSN
    • Fully Masked - This will hide all 9 digits of the SSN

Key Resources

• Watch Delayed ISIR Processing Report Readiness Training
• Watch MPN and EC Reconciliation Report Readiness Training