While the disbursement API updater can be useful for existing awards, clients would like the ability to create new awards in the system using the API. Often times (especially Banner schools, and private universities) will have an award that is originated in Banner. The University of Notre Dame outlined some scenarios where this would be very helpful, particularly with fund swapping, setting budgets in BAM, and renewals. I also know that Brown University, at one point years ago, mentioned that it would beneficial, as it seems like the next step in the evolution of the API.
Client Name "shard name" | brown, nd |
User | System Admin |
Functional Unit | API |
Employee Name | Brandon Spiller |
UCLA could use this as well, since BAM is not our database of record. Like others, strictly scholarships are in BAM, but all other types of aid are in the other system-which is also where compliance makes modifications to awards when necessary.
We have a process that extracts scholarship offers and import them into banner. And to extract decisions on those scholarships and imports them back into BAM.
Banner is the Database of record. however most scholarships are handled in BAM (offers, student followup) , all Financial Aid is managed in Banner as banner also holds all other forms forms of Financial Aid. Federal, State..etc.
We at ND are getting close to having our API from BAM to Banner functional for the swapping process and this would enable us to keep BAM and BANNER in sync as not 100% of our awards will be made in BAM. By doing so we can have our post accpetance process out of BAM for all awrds whether they we made in BAM or in BANNER.
Please see similar use case from Drexel in the merged enhancement