This guide provides a high level overview of how to configure PeopleSoft to work with our SIS integration.



Once you have the data in PeopleSoft, you will use the Population Update capabilities within PeopleSoft to finish the process of updating the checklist item from the imported data.

If you’re not familiar with the Population Update here is a link to some docs on Oracle's website:

https://docs.oracle.com/cd/E56917_01/cs9pbr4/eng/cs/lscc/task_UsingthePopulationSelectionProcess-2c7fe9.html#topofpage



First create a new record definition in App Designer, and build it in the database. This is really the only step that may require a developer. Everything else is just basic configurations in PeopleSoft.



File Parser setup has three components:


First, create a context definition. There can be parent-child relationships defined here, but for our purposes it’s just a simple 1:1 with a single table.


Next, create a Field Conversion Definition for my AID_YEAR field so that I can map CampusLogic's output to my AID_YEARs in PeopleSoft


Finally, create a File Mapping Definition to map the specifics of the CSV to the context definition:








At this point, you can load a preview file in to make sure that everything maps as expected.



If the preview looks good, send the test file over to actually load it up.


If all went well, my file got loaded and now you can start writing queries against it.



In regard to the Database Matches, schools will either need to do a SQL Script or use their Population Update program to do this programmatically.


One possible solution is to just automatically set the overrides on all of those. We use our custom Query Based Update process to do that, but it would be relatively straightforward to just write some SQL scripts to do the same. Specifically, it’s a series of fields on the PS_STDNT_AID_ATRBT record, which users can manually update on the Packaging Status Summary/Database Matches page:



Update that record to set each override field to “Y” for every student as soon as they’re aid year activated (i.e. as soon as we get the ISIR in). If we didn’t do that, at the time of awarding PeopleSoft would still enforce its built in edits and consider the student ineligible for Title IV aid. Since this is essentially short-circuiting that, we’ll rely on the checklist item that’s associated with verification in CampusLogic as an “all-or-nothing” check to prevent packaging and disbursement of those funds.


Once this is setup, please continue to the next guide here: Flat File Testing .