Integration Guiding Principles
Student Financial Aid has a REST-Based Interface and uses two primary message types, event based and asynchronous.
Student Financial Aid Primary Message Types:
-
Event-Based: Triggered at the time certain events occur
-
Asynchronous Request/Reply: Triggered when a system makes a request for the information
Messages are Directional and are considered to be either Inbound or Outbound. Inbound messages are transmitted to Student Financial Aid from an external system. Outbound messages are created by Oracle Fusion Cloud Student Financial Aid Cloud Service and are intended to be consumed by an external system or the Student Portal.
Every message contains a Globally Unique Identifier (GUID) in the MessageId content to identify it as a unique message. Each message is validated before the data in the message is persisted to database. If an invalid message is received, an error is logged to the database and the message is discarded.
A message is considered invalid if:
-
It does not match the XML schema.
-
It has at least one field that is not compliant with the business validation rule(s) specified for that field.
XML Schema Definition
The latest XSD files can be found in the API Update in the Release Notes posted on Cloud Customer Connect. Search for the API updates for a specific release using the "Release Notes" tag. You may find downloading the latest API assets beneficial as you work through the implementation process.