Return to Navigation

Understanding SAIP Setup

Before you install SAIP, you must consider and determine the default settings for your institution to use. These decisions include how to map name and contact information, whether to implement event-based triggers, whether to enable grade import, and whether to point the external system to information in a file path or on a file server.

You must also determine which academic organizations whose academic elements (courses, sections, combined sections, and so on) your institution wants to include within the scope of the initial transfer and subsequent snapshot updates. For course elements, you can override scoping decisions at the element levels, but the institutions, academic organizations, and terms to which they belong must be in scope for the element to be available. For example, if the Biology organization is not included in scope, then none of the Biology courses, sections, or persons data are available for transfer. If, however, the Biology organization is included in scope, and the Spring 2008 term is in scope, then all of the Biology courses, sections, and persons data for the Spring 2008 term are available for inclusion in scope, and can be set as in scope at the organization level. You can override scope inclusion or exclusion at the element level on the pages where you create or view the specific element.

Warning! Changes to the installation settings after initialization affect only data from the date of the change forward. This may introduce different data and formatting, causing the systems to become out of synchronization. You can change the settings and initialize the system at any time to resynchronize the systems, but doing so will overwrite all manual changes including the changes made to include or exclude elements at the specific course, section, and person level. Unless otherwise noted, Oracle recommends that you do not change the default settings after initialization.

You must set service operations, routings, and routing URLs in your PeopleTools Integration Broker specifically for SAIP.

You must also set Integration Broker and PeopleSoft Process Scheduler to use COBOL-based processes for SAIP.

Refer to: