Coursedog

Submit a ticket My Tickets
Welcome
Login  Sign up

PeopleSoft Integration

Introduction

This is a high-level discussion of the N2N  integration for PeopleSoft Course Catalog and Schedule of Classes. This document focuses narrowly on the PeopleSoft tier and NOT the full integration layer provided by the N2N Illuminate Platform. This integration relies on PeopleSoft Web Services which will be deployed on the CUNY infrastructure. These are web services delivered and supported by N2N. The items discussed in this document are based on standard N2N PeopleSoft API's. Every PeopleSoft institution has unique configuration, customization and infrastructure characteristics that must be accounted for in the implementation phase. N2N will likely make changes to these API to account for CUNY's unique requirements. 

The preliminary list of PeopleSoft web services that will be deployed will interact with the following functional areas of PeopleSoft.

  • Term table

    • A "GET" API to pull a list of valid terms defined in PeopleSoft

  • Subject Table

    • A "GET" API to pull a list of valid subjects defined in PeopleSoft

  • Course Catalog

    • A "GET" API to pull existing courses.

    • A "POST" or create API to create and update courses. (delivered in future update)

  • Schedule of Classes

    • A "GET" API to pull existing classes

    • A "POST" or create API to create and update existing classes (delivered in future update)

PeopleSoft Technical Overview

This proposed integration relies on standard PeopleSoft Integration Broker Service Operations. The Illuminate Platform will connect to the CUNY Integration Broker over HTTPS from cloud servers. N2N will provide IP addresses that should be whitelisted in the client firewalls so that integration broker connectivity can be established.

There are two main types of integrations:

  • "GET" or data pulls from PeopleSoft.

  • "POST" or data updates into PeopleSoft.

The GET operations are performed using standard PeopleSoft service operation technology and gather data with SQL and return it to the Illuminate platform for translation and normalization to Coursedog.

The POST operations function differently. The N2N PeopleSoft web services always perform PeopleSoft updates using component interface (CI). A CI is just a "wrapper" around an existing PeopleSoft component. A component encapsulates a large amount of business logic about how data should be entered and enforces data integrity and logic. A component can have thousands of lines of code behind the scenes that trigger. Additionally, everyone can customize that code and Oracle is constantly changing the code with bundles. Since we are integrating with CI, that underlying code can easily change and there is little to no impact on the integration code. Any custom logic or delivered logic like PeopleSoft syncs or audits are all triggered when CI is used. This approach is the only way to correctly integrate with PeopleSoft and ensures high data quality.

The diagram below shows a high-level schematic of the PeopleSoft integration components.

 

Development Process

Since PeopleSoft is highly customizable, the N2N staff is requesting access to a client's development environment. This will enable us to efficiently test and debug the APIs against the client's unique  configuration and usage of PeopleSoft. N2N is requesting the following access for an N2N PeopleSoft expert.

 

  • Access to a client terminal server with PeopleTools Application Designer configured. This may require some form of VPN access.

  • Developer access to a non-production database.

The client's change control team will be used for all staging and production migrations. N2N will work with your change control team to provide the required information for production migration.

The naming convention of all PeopleSoft objects delivered by N2N are prefixed with "N_".

Detailed API Information

The sections below give detail around the PeopleSoft web services deployed. N2N will own and support these web services. Additionally, the request and response of these web services are tightly coupled with the Illuminate Platform integration layer code. We ask that the client refrain from making any code changes without the direction of N2N. N2N will likely need to make code patches at various times. The source of truth of the code will NOT be the client's PeopleSoft database. The source of truth will be in development databases owned by N2N. Client changes to the code will likely be lost if those changes are not coordinated with N2N.  

Data Query API (N_DATA_QUERY)

The N_DATA_QUERY service operation is a web service that allows the Illuminate Platform to "ask" for any number of tables in PeopleSoft. This web service was designed to be called by a trusted server. This is not a web service that would ever be exposed to an end user. It returns structured XML data that mimics the PeopleSoft data structure. It is similar in spirit to GraphQL but only works inside a PeopleSoft database. The response body structure will vary based on the input request parameters. 

Features

  • The web service is XML-based to support the broadest number of PeopleSoft versions. 

  • The Illuminate Platform can request a PeopleSoft record be returned and can include a where clause in various forms. Child and grandchildren table nesting are supported using specific request syntax.

  • All record fields are exported unless the request specifically asks for certain fields to NOT be included. This allows the web service to automatically include custom fields or fields added by Oracle during patching or updates. The Illuminate Platform can request some fields to not be included which can be useful on tables that have sensitive data (SNN, Salary) that you may not be using and you don't want logged across the infrastructure.

  • The service supports adding human readable code descriptions to the output. For example, if a CAMPUS code is "SDIEG" a description attribute may be returned that says "San Diego".

  • The service supports pagination to extract large tables in smaller chunks. For example, we may ask for 50 class sections in each API call and each call will return information on how to get the "next page" of data in a subsequent call. 

  • Effective data logic is automatically handled. 

  • Records that have the EFF_STATUS field pull only the active value.

Intended Use Cases

  • This web service can serve as a "GET" operation for almost any situation and provides flexibility for different scenarios. This can accommodate custom client tables to be included in standard GET operations by just changing the request body. 

    • We try to use this operation as the GET mechanism first. If it cannot accommodate the request then we deliver a specific operation.

  • Extracting "pick lists" or "prompt tables" values. For example a list of subjects, locations, and XLAT values.

  • Extracting client "custom"/bolt-on tables that we don't have specific web service for.

  • Generating "Changes since x hours ago" queries. Many institutions may have large numbers of tables that you only want to pull out changes since the last sync. In this situation, you need some way to query "what has changed in the last hours" and then only pull those objects that have changed. You can use this web service and the "where clause" functionality to craft a query to find these then potentially use other web services to only pull those objects.

Data Security

Data security is an important aspect to all Institutions. This web service technically has the ability to extract out any PeopleSoft table or view out of the client system. Most institutions want the service limited to only pull certain tables depending on the integration. We have developed a client owned "whitelist" table. This is a simple listing of tables that this web service can be allowed to pull from the client system. The web service always checks this whitelist table before extracting any data. If the table is NOT whitelisted, data will not be returned. This is similar in concept to PeopleSoft query tree security. 

There is a PeopleSoft page where this is configured.

  • Menu Name: N_DE_SETUP

  • Component Name: N_DE_WHITELIST

  • Record Name: N_DE_WHITELIST

This page intentionally allows record names to be entered that are NOT defined in PSRECDEFN (Prompt table no edits). That is because we can use an "ALL" keyword to tell the web service that all tables are allowed. 

Here is an example where there are a few tables that are whitelisted. In this case, these are the only tables that can be pulled by this web service.

Here is an example where the "ALL" keyword is configured. This means any PeopleSoft table can be pulled. This is generally just used in development.

 

Tables To be Read (preliminary)

  • ACAD_GROUP_TBL

  • BLDG_TBL

  • CAMPUS_TBL

  • CLASS_ASSOC

  • CLASS_CHRSTC

  • CLASS_INSTR

  • CLASS_MTG_PAT

  • CLASS_NOTES

  • CLASS_PRMSN

  • CLASS_TBL

  • CMPNT_CHRSTC

  • CRSE_ATTENDANCE

  • CRSE_ATTR_TBL

  • CRSE_ATTR_VALUE

  • CRSE_ATTRIBUTES

  • CRSE_CATALOG

  • CRSE_COMPONENT

  • CRSE_OFFER

  • CRSE_TOPICS

  • FACILITY_TBL

  • GRADE_TBL

  • GRADESCHEME_TBL

  • GRD_BASE_CHOICE

  • INSTITUTION_TBL

  • INSTRUCT_MODE

  • LOCATION_TBL

  • MILESTONE_TBL

  • PSXLATITEM

  • ROOM_CHRSTC_TBL

  • RQ_GRP_TBL

  • SESSION_TBL

  • SSR_CRS_MILESTN

  • STND_MTGPAT_TBL

  • SUBJECT_TBL


  • TODO: There are several other setup tables that need to be added here. 

Example Data Query


Let's look at the general data query request and response. The client will never need to know this and N2N will handle all these details. We are including this example for the curious technical reader that wants some understanding of this web service.


Here is a request body that is asking for the TERM_TBL and it's child the SESSION_TBL table. We are asking for a specific INSTITUTION value as well as STRM that begin after 2020-01-01. The request is asking for the first 3 rows. There is a certain XML syntax that the web service knows how to parse and generate the proper SQL using PeopleTools meta-data.


<?xml version="1.0" encoding="utf-8"?>

<request>

    <query isDebugMode="false">

        <record>

            <recordName>TERM_TBL</recordName>

            <parentRecordName></parentRecordName>

            <rowLimit>3</rowLimit>

            <whereClause/>

            <noExportFields>

            </noExportFields>

            <promptLookups includeAll="TRUE">

            </promptLookups>

            <effectiveDateToUse/>

            <afterPage></afterPage>

            <whereFields>

                <fieldName value="PSUNV">INSTITUTION</fieldName>

                <fieldName value="2020-01-01" operator=">=">TERM_BEGIN_DT</fieldName>

            </whereFields>

        </record>

        <record>

            <recordName>SESSION_TBL</recordName>

            <parentRecordName>TERM_TBL</parentRecordName>

            <rowLimit></rowLimit>

            <whereClause/>

            <noExportFields>

            </noExportFields>

            <promptLookups includeAll="FALSE">

                <fieldName>SESSION_CODE</fieldName>

                <fieldName>HOLIDAY_SCHEDULE</fieldName>

            </promptLookups>

            <effectiveDateToUse/>

            <afterPage></afterPage>

            <whereFields>

            </whereFields>

        </record>

    </query>

</request>


The response from a demo PeopleSoft database will resemble this.


<?xml version="1.0"?>

<response NEXT_PAGE="INSTITUTION:PSUNV|ACAD_CAREER:CNED|STRM:0840" PAGINATED="True" STATUS_CODE="200" STATUS_STRING="OK" psftTransactionId="eda9d77d-53a5-11ea-a3f6-f6152027c411">

    <data>

        <TERM_TBL class="R">

            <INSTITUTION description="PeopleSoft University">PSUNV</INSTITUTION>

            <ACAD_CAREER description="Graduate Business">BUSN</ACAD_CAREER>

            <STRM description="2020 Spring">0840</STRM>

            <DESCR>2020 Spring</DESCR>

            <DESCRSHORT>2020 Spr</DESCRSHORT>

            <TERM_BEGIN_DT>2020-01-24</TERM_BEGIN_DT>

            <TERM_END_DT>2020-05-08</TERM_END_DT>

            <SESSION_CODE/>

            <WEEKS_OF_INSTRUCT>15</WEEKS_OF_INSTRUCT>

            <TERM_CATEGORY description="Regular Term">R</TERM_CATEGORY>

            <ACAD_YEAR>2020</ACAD_YEAR>

            <TRANSCIPT_DT_PRT description="Do Not Print Any Dates">N</TRANSCIPT_DT_PRT>

            <HOLIDAY_SCHEDULE description="Academic Holiday Schedule">PSS</HOLIDAY_SCHEDULE>

            <SIXTY_PCT_DT>2020-03-28</SIXTY_PCT_DT>

            <USE_DYN_CLASS_DATE>N</USE_DYN_CLASS_DATE>

            <SSR_TRMAC_LAST_DT>2020-01-24</SSR_TRMAC_LAST_DT>

            <SSR_SSENRLDISP_BDT>2019-01-01</SSR_SSENRLDISP_BDT>

            <SSR_SSENRLDISP_EDT>2020-05-08</SSR_SSENRLDISP_EDT>

            <SSR_SSPLNRDISP_BDT>2020-01-01</SSR_SSPLNRDISP_BDT>

            <SSR_SSPLNRDISP_EDT>2020-05-08</SSR_SSPLNRDISP_EDT>

            <SSR_SSWHIFADVR_BDT>1900-01-01</SSR_SSWHIFADVR_BDT>

            <SSR_SSWHIFADVR_EDT>1900-01-01</SSR_SSWHIFADVR_EDT>

            <SSR_SSWHIFPREM_BDT>1900-01-01</SSR_SSWHIFPREM_BDT>

            <SSR_SSWHIFPREM_EDT>1900-01-01</SSR_SSWHIFPREM_EDT>

            <SSR_SSWHIFSTD_BDT>1900-01-01</SSR_SSWHIFSTD_BDT>

            <SSR_SSWHIFSTD_EDT>1900-01-01</SSR_SSWHIFSTD_EDT>

            <SESSION_TBL class="R">

                <INSTITUTION>PSUNV</INSTITUTION>

                <ACAD_CAREER>BUSN</ACAD_CAREER>

                <STRM>0840</STRM>

                <SESSION_CODE description="Regular Academic Session">1</SESSION_CODE>

                <SESS_BEGIN_DT>2020-01-24</SESS_BEGIN_DT>

                <SESS_END_DT>2020-05-08</SESS_END_DT>

                <ENROLL_OPEN_DT>2019-12-01</ENROLL_OPEN_DT>

                <SESSN_ENRL_CNTL/>

                <SESSN_APPT_CNTL/>

                <FIRST_ENRL_DT>2019-11-01</FIRST_ENRL_DT>

                <LAST_ENRL_DT/>

                <LAST_WAIT_DT>2020-01-23</LAST_WAIT_DT>

                <HOLIDAY_SCHEDULE>PSS</HOLIDAY_SCHEDULE>

                <WEEKS_OF_INSTRUCT>15</WEEKS_OF_INSTRUCT>

                <CENSUS_DT>2020-02-21</CENSUS_DT>

                <USE_DYN_CLASS_DATE>N</USE_DYN_CLASS_DATE>

                <SIXTY_PCT_DT>2020-03-28</SIXTY_PCT_DT>

                <FACILITY_ASSIGNMNT>2019-10-01</FACILITY_ASSIGNMNT>

                <SSR_ENR_APT_APPROV>N</SSR_ENR_APT_APPROV>

                <SSR_VAL_APT_APPROV>N</SSR_VAL_APT_APPROV>

                <SSR_SSPLNRDISP_BDT/>

                <SSR_SSPLNRDISP_EDT/>

            </SESSION_TBL>

        </TERM_TBL>

        <TERM_TBL class="R">

            <INSTITUTION description="PeopleSoft University">PSUNV</INSTITUTION>

            <ACAD_CAREER description="Graduate Business">BUSN</ACAD_CAREER>

            <STRM description="2020 Summer">0845</STRM>

            <DESCR>2020 Summer</DESCR>

            <DESCRSHORT>2020 Sum</DESCRSHORT>

            <TERM_BEGIN_DT>2020-05-23</TERM_BEGIN_DT>

            <TERM_END_DT>2020-08-14</TERM_END_DT>

            <SESSION_CODE/>

            <WEEKS_OF_INSTRUCT>12</WEEKS_OF_INSTRUCT>

            <TERM_CATEGORY description="Summer Term">S</TERM_CATEGORY>

            <ACAD_YEAR>2020</ACAD_YEAR>

            <TRANSCIPT_DT_PRT description="Do Not Print Any Dates">N</TRANSCIPT_DT_PRT>

            <HOLIDAY_SCHEDULE description="Academic Holiday Schedule">PSS</HOLIDAY_SCHEDULE>

            <SIXTY_PCT_DT>2020-07-11</SIXTY_PCT_DT>

            <USE_DYN_CLASS_DATE>N</USE_DYN_CLASS_DATE>

            <SSR_TRMAC_LAST_DT>2020-05-23</SSR_TRMAC_LAST_DT>

            <SSR_SSENRLDISP_BDT>2019-01-01</SSR_SSENRLDISP_BDT>

            <SSR_SSENRLDISP_EDT>2020-08-14</SSR_SSENRLDISP_EDT>

            <SSR_SSPLNRDISP_BDT>2020-01-01</SSR_SSPLNRDISP_BDT>

            <SSR_SSPLNRDISP_EDT>2020-08-14</SSR_SSPLNRDISP_EDT>

            <SSR_SSWHIFADVR_BDT>1900-01-01</SSR_SSWHIFADVR_BDT>

            <SSR_SSWHIFADVR_EDT>1900-01-01</SSR_SSWHIFADVR_EDT>

            <SSR_SSWHIFPREM_BDT>1900-01-01</SSR_SSWHIFPREM_BDT>

            <SSR_SSWHIFPREM_EDT>1900-01-01</SSR_SSWHIFPREM_EDT>

            <SSR_SSWHIFSTD_BDT>1900-01-01</SSR_SSWHIFSTD_BDT>

            <SSR_SSWHIFSTD_EDT>1900-01-01</SSR_SSWHIFSTD_EDT>

            <SESSION_TBL class="R">

                <INSTITUTION>PSUNV</INSTITUTION>

                <ACAD_CAREER>BUSN</ACAD_CAREER>

                <STRM>0845</STRM>

                <SESSION_CODE description="Twelve Week">12W</SESSION_CODE>

                <SESS_BEGIN_DT>2020-05-23</SESS_BEGIN_DT>

                <SESS_END_DT>2020-08-14</SESS_END_DT>

                <ENROLL_OPEN_DT>2020-04-01</ENROLL_OPEN_DT>

                <SESSN_ENRL_CNTL/>

                <SESSN_APPT_CNTL/>

                <FIRST_ENRL_DT>2020-03-01</FIRST_ENRL_DT>

                <LAST_ENRL_DT/>

                <LAST_WAIT_DT>2020-05-22</LAST_WAIT_DT>

                <HOLIDAY_SCHEDULE>PSS</HOLIDAY_SCHEDULE>

                <WEEKS_OF_INSTRUCT>12</WEEKS_OF_INSTRUCT>

                <CENSUS_DT>2020-06-20</CENSUS_DT>

                <USE_DYN_CLASS_DATE>N</USE_DYN_CLASS_DATE>

                <SIXTY_PCT_DT>2020-07-11</SIXTY_PCT_DT>

                <FACILITY_ASSIGNMNT>2020-02-01</FACILITY_ASSIGNMNT>

                <SSR_ENR_APT_APPROV>N</SSR_ENR_APT_APPROV>

                <SSR_VAL_APT_APPROV>N</SSR_VAL_APT_APPROV>

                <SSR_SSPLNRDISP_BDT/>

                <SSR_SSPLNRDISP_EDT/>

            </SESSION_TBL>

        </TERM_TBL>

        <TERM_TBL class="R">

            <INSTITUTION description="PeopleSoft University">PSUNV</INSTITUTION>

            <ACAD_CAREER description="Continuing Education">CNED</ACAD_CAREER>

            <STRM description="2020 Spring">0840</STRM>

            <DESCR>2020 Spring</DESCR>

            <DESCRSHORT>2020 Spr</DESCRSHORT>

            <TERM_BEGIN_DT>2020-01-24</TERM_BEGIN_DT>

            <TERM_END_DT>2020-05-08</TERM_END_DT>

            <SESSION_CODE/>

            <WEEKS_OF_INSTRUCT>15</WEEKS_OF_INSTRUCT>

            <TERM_CATEGORY description="Regular Term">R</TERM_CATEGORY>

            <ACAD_YEAR>2020</ACAD_YEAR>

            <TRANSCIPT_DT_PRT description="Do Not Print Any Dates">N</TRANSCIPT_DT_PRT>

            <HOLIDAY_SCHEDULE description="Academic Holiday Schedule">PSS</HOLIDAY_SCHEDULE>

            <SIXTY_PCT_DT>2020-03-28</SIXTY_PCT_DT>

            <USE_DYN_CLASS_DATE>N</USE_DYN_CLASS_DATE>

            <SSR_TRMAC_LAST_DT>2020-01-24</SSR_TRMAC_LAST_DT>

            <SSR_SSENRLDISP_BDT>2019-01-01</SSR_SSENRLDISP_BDT>

            <SSR_SSENRLDISP_EDT>2020-05-08</SSR_SSENRLDISP_EDT>

            <SSR_SSPLNRDISP_BDT>2020-01-01</SSR_SSPLNRDISP_BDT>

            <SSR_SSPLNRDISP_EDT>2020-05-08</SSR_SSPLNRDISP_EDT>

            <SSR_SSWHIFADVR_BDT>1900-01-01</SSR_SSWHIFADVR_BDT>

            <SSR_SSWHIFADVR_EDT>1900-01-01</SSR_SSWHIFADVR_EDT>

            <SSR_SSWHIFPREM_BDT>1900-01-01</SSR_SSWHIFPREM_BDT>

            <SSR_SSWHIFPREM_EDT>1900-01-01</SSR_SSWHIFPREM_EDT>

            <SSR_SSWHIFSTD_BDT>1900-01-01</SSR_SSWHIFSTD_BDT>

            <SSR_SSWHIFSTD_EDT>1900-01-01</SSR_SSWHIFSTD_EDT>

            <SESSION_TBL class="R">

                <INSTITUTION>PSUNV</INSTITUTION>

                <ACAD_CAREER>CNED</ACAD_CAREER>

                <STRM>0840</STRM>

                <SESSION_CODE description="Regular Academic Session">1</SESSION_CODE>

                <SESS_BEGIN_DT>2020-01-24</SESS_BEGIN_DT>

                <SESS_END_DT>2020-05-08</SESS_END_DT>

                <ENROLL_OPEN_DT>2019-12-01</ENROLL_OPEN_DT>

                <SESSN_ENRL_CNTL/>

                <SESSN_APPT_CNTL/>

                <FIRST_ENRL_DT>2019-11-01</FIRST_ENRL_DT>

                <LAST_ENRL_DT/>

                <LAST_WAIT_DT>2020-01-23</LAST_WAIT_DT>

                <HOLIDAY_SCHEDULE>PSS</HOLIDAY_SCHEDULE>

                <WEEKS_OF_INSTRUCT>15</WEEKS_OF_INSTRUCT>

                <CENSUS_DT>2020-02-21</CENSUS_DT>

                <USE_DYN_CLASS_DATE>N</USE_DYN_CLASS_DATE>

                <SIXTY_PCT_DT>2020-03-28</SIXTY_PCT_DT>

                <FACILITY_ASSIGNMNT>2019-10-01</FACILITY_ASSIGNMNT>

                <SSR_ENR_APT_APPROV>N</SSR_ENR_APT_APPROV>

                <SSR_VAL_APT_APPROV>N</SSR_VAL_APT_APPROV>

                <SSR_SSPLNRDISP_BDT/>

                <SSR_SSPLNRDISP_EDT/>

            </SESSION_TBL>

        </TERM_TBL>

    </data>

    <meta>

        <dbname>CS92U009</dbname>

        <toolsVer>8.56</toolsVer>

        <psftTransactionId>eda9d77d-53a5-11ea-a3f6-f6152027c411</psftTransactionId>

        <currentUser>N_ILLUMINATE_NODE</currentUser>

        <wasSuccessful>True</wasSuccessful>

        <paginated>True</paginated>

        <debugMessages>

            <![CDATA[]]>

        </debugMessages>

    </meta>

</response>


 

Course Update (N_COURSE_POST)

  • Section Status: Draft - This section will be revised based on scoping with CUNY


The Course post service operation can both create new courses and update existing courses. It performs all updates using a Component Interface based on COMPONENT:CRSE_CATALOG.

  • NO SQL Updates, Inserts or Deletes are performed directly from PeopleCode on the database. All SQL in proxied via the CI.

  • This service handles one course update at a time and is close to real-time"

Here is a listing of tables and fields that are available for update on PeopleSoft.

CRSE_CATALOG update fields

  • EFFDT

  • EFF_STATUS

  • UNITS_MINIMUM

  • UNITS_MAXIMUM

  • CRSE_CONTACT_HRS

  • DESCR

  • DESCRLONG

  • COURSE_TITLE_LONG

  • GRADING_BASIS

  • CRSE_REPEATABLE

  • ALLOW_MULT_ENROLL

  • UNITS_REPEAT_LIMIT

  • CRSE_REPEAT_LIMIT

CRSE_OFFER Update fields

  • CRSE_OFFER_NBR

  • CATALOG_NBR

  • INSTITUTION

  • ACAD_GROUP

  • SUBJECT

  • CAMPUS

  • ACAD_ORG

  • ACAD_CAREER

  • COURSE_APPROVED

  • SCHEDULE_PRINT

  • SCHED_TERM_ROLL

  • CIP_CODE

  • OEE_IND

  • OEE_DYN_DATE_RULE

CRSE_COMPONENT Update fields

  • SSR_COMPONENT

  • FINAL_EXAM

  • DEFAULT_SECT_SIZE

  • GRADE_ROSTER_CMPNT

  • COMPONENT_PRIM_FLG

If additional custom tables are needed they can be added with minimal effort.

Class Update API (N_CLASS_POST)

  • Section Status: Draft - This section will be revised based on scoping with CUNY


This service operation can both create new classes and update existing classes. It performs all updates using a Component Interface based on COMPONENT:CLASS_DATA.

  • NO SQL Updates, Inserts or Deletes are performed directly from PeopleCode on the database. All SQL in proxied via the CI.

  • This service handles one class update at a time and is close to realtime

Here is a listing of tables and fields that are available for update on PeopleSoft.

CLASS_TBL update fields

  • SESSION_CODE

  • CLASS_SECTION

  • START_DT

  • END_DT

  • CLASS_TYPE

  • CLASS_STAT

  • ASSOCIATED_CLASS

  • CAMPUS

  • LOCATION

  • EMPLID

  • ACAD_ORG

  • HOLIDAY_SCHEDULE

  • INSTRUCTION_MODE

  • ROOM_CAP_REQUEST

  • ENRL_CAP

  • LMS_FILE_TYPE

CLASS_ATTRIBUTE update fields

  • CRSE_ATTR_VALUE

  • CRSE_ATTR

CLASS_MTG_PAT update fields

  • FACILITY_ID

  • STND_MTG_PAT

  • MEETING_TIME_START

  • MEETING_TIME_END

  • MON

  • TUES

  • WED

  • THURS

  • FRI

  • SAT

  • SUN

  • START_DT

  • END_DT

  • DESCR

CLASS_INSTR update fields

  • EMPLID

  • INSTR_LOAD_FACTOR

CLASS_CHRSTC update fields

  • ROOM_CHRSTC

  • ROOM_CHRSTC_QUANTI

If additional custom tables or fields are needed they can be added with minimal effort.

C
Coursedog is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.