Understanding Integration with Oracle Student Financial Planning Cloud Service

Oracle PeopleSoft Campus Solutions (CS) customers can opt to integrate with the Oracle Student Financial Planning Cloud Service (SFP) as an alternative to using CS Financial Aid. SFP supports student financial aid programs in the United States but can also be used globally. SFP does not presently support financial aid localizations for Great Britain or Canada.

The integration between CS and SFP is an exchange of data in the form of sending and receiving specialized messages between the two systems.

CS uses 4 outbound messages to send data to SFP:

  • Student Initiation Event: Initiates new students in SFP with biographic information from CS. These messages are logged with Message Class of STIN.

  • Student Update Event: Sends updated biographic information from CS for students already established in SFP. If an emplid has a biographic or demographic update, CS will allow the PERSON_BASIC_SYNC message to trigger the SFP’s Student Update Event message. These messages are logged with Message Class of STUP.

  • Student Academic and Financial Information (SAFI) Event: Sends Student Record (Academic Program, Enrolled Classes, Grades, etc.), Student Financial (Charges, Student Resources), and Projected Course Units (SFP’s Packaging) information to SFP. Details of a student's academic program can be taken from either STNDT_CAR_TERM table or ADM_APPL_PROG table. These messages are logged with Message Class of SAFI.

    Note: On a student program change, a terminating SAFI needs to be sent for the old program before a SAFI is sent for the new program. The terminating SAFI is a SAFI with no projected courses. Assuming no enrollment changes, all other attributes for the terminating SAFI should mirror the last SAFI for the old program, with the exception being a lack of projected courses.

  • Leaves of Absence and Breaks in Attendance Event: Sends Student Records Leave of Absence information to SFP. These messages are logged with Message Class of STLA.

CS accepts 6 inbound messages to receive data from SFP:

  • Disbursement Information Event: Provides SFP disbursements to CS by populating SF Group Data Entry for follow on Group Post. To process SFP Plus loans, the FasPlusApplicationInformationRequest web service is invoked to obtain biographic and demographic data of the borrower or parent. The FasPlusApplicationInformationReply service is used to continue processing the Plus loan disbursement. These messages are logged with Message Class of DISB.

  • Return to Lender Event: Provides information about disbursed payments that have been reduced (triggered from repackaging, R2T4, etc.). The transactions update CS SF Group Data Entry for follow-on Group Post. These messages are logged with Message Class of RTLN.

  • Anticipated Aid Event: Provides information about students’ anticipated financial aid in SFP for possible use in Self Service (Account View, Make a Payment), Customer Account, Payment Plans, Billing, Aging, and Term/Class Cancellation. These messages are logged with Message Class of AAID.

  • Title 4 Data Needed: Sends a message that a R2T4 calculation is being made and requires data to be sent to use for this calculation. This message is sent if the SAFI is not created with the correct Return to Title IV elements. These messages are logged with Message Class of T4DN.

  • Notification Events: Sends a message containing SFP notification data that can be used in the CS Notification Framework. These messages are logged with Message Class of NTF.

  • Unsupported: Sends additional messages that do not automatically trigger CS system processes at this time. These messages are logged with Message Class of UNSP.