Understanding GL Interface Processing Setup
This section discusses:
GL Interface Processing Using PeopleSoft General Ledger or Oracle General Ledger
GL Interface Processing Using a Third-Party or Legacy General Ledger System
Note: When customers license PeopleSoft Campus Solutions, they receive a limited use license for Human Resources, Benefits Administration, and Payroll for North America.
Most of the setup that is needed to transfer information between the Student Financials application and the PeopleSoft General Ledger or Oracle General Ledger applications is done within General Ledger and then transferred to Student Financials. Throughout the setup process, you should work closely with staff who coordinate the General Ledger application. They will help you define your setup tables and tell you what information is necessary for the GL Interface process.
If the system interacts with PeopleSoft or Oracle Financials, it uses application messaging to share accounting line information with the PeopleSoft or Oracle General Ledger.
GL Messaging
During the GL Messaging process, Student Financials delivers these queues and messages to the PeopleSoft Financials database:
|
Message Queue |
Message |
Description |
|---|---|---|
|
STUDENT_ADMIN_ACCOUNTING |
STUDENT_FIN_ACCTG_LINE |
Notifies the message broker that new SF_ACCTG_LN records are ready to be retrieved by PeopleSoft Financials and, after journal generation, retrieves the updated SF_ACCTG_LN records into Student Financials. |
|
HR_SETUP |
BUS_UNIT_SF_FULLSYNC |
Sends the BUS_UNIT, DESCR, and DESCRSHORT rows in the BUS_UNIT_TBL_SF to PeopleSoft Financials to seed its BUS_UNIT_TBL_SF. |
|
HR_SETUP |
BUS_UNIT_SF_SYNC |
Sends new Student Financials business units or updates when the DESCR field or DESCRSHORT field is changed. |
During the GL Messaging process, Student Financials delivers these queues and messages to the Oracle Financials database:
|
Message Queue |
Message |
Description |
|---|---|---|
|
STUDENT_ADMIN_ACCOUNTING |
STUDENT_FIN_ACCTG_LINE |
Notifies the message broker that new SF_ACCTG_LN records are ready to be retrieved by Oracle Financials. |
|
SSF_GL_INT |
SSF_GL_SEGMENT_FULLSYNC |
Fetches all available active ledgers, segments from Oracle GL and inserts the data into PS_SSF_EB_SEGMENTS record. |
|
SSF_GL_INT |
SSF_GL_SEGMENT_VAL_REQ SSF_GL_SEGMENT_VAL_RESP |
Full/partial sync of segment values. This inserts/updates the chartfield prompt tables based on mappings from SSF_EB_GLBU_LED. |
|
SSF_GL_INT |
SSF_CF_COMBO_RTVLD_REQ SSF_CF_COMBO_RTVLD_RESP |
Performs realtime validation of entered chartfield combination against the combinations table in Oracle GL. |
|
SSF_GL_INT |
SSF_ACCTG_LINE_TRFM_EBGL |
This is a transformation program used by the batch publish utility. This maps and inserts data from SF_ACCTG_LN and AV_ACCTG_LN into the GL_INTERFACE table in Oracle GL. |
|
SSF_GL_INT |
SSF_GL_ACCTG_LINE_SYNC |
This message receives the non-rowset based message, validates and parses the message, and updates the journal related fields in one of the SF_ACCTG_LN and AV_ACCTG_LN tables. |
The PeopleSoft system delivers a default node of PSFT_HR. If you change this default, you must reconfigure the message channel. However, regardless of whether you change the message node, you must configure it by inserting the proper URL.
Note: An easy way to determine where messaging starts and ends is to name the publishing node with the name of the database to which it publishes or from which it publishes.
In the PeopleSoft Financials database, message definition, queue, and message node naming must match the naming that is used in the Student Financials database.
PeopleSoft Financials subscribes to the published messages in the Student Financials database, takes the accounting lines into the SF_ACCTG_LN table, and runs those lines through Journal Generator to create journal entries. PeopleSoft Financials then publishes the updated accounting lines, Student Financials subscribes to these lines, and then the data that is published by PeopleSoft Financials updates the Student Financials SF_ACCTG_LN table.
In addition, you must select the Display External ChartField check box on the SF Installation Table.
For information about messaging for Oracle Financials:
See CS90 to EBS GL Integration Developer's Reference Guide. The guide is posted to My Oracle Support.
Student Financials provides an extra field for you to use to enter chart of accounts data on your item types, course or class fees, and cashiering tenders or targets. You can use the existing PeopleSoft-delivered ChartFields (ACCOUNT, DEPTID, and so on) to enter your chart of accounts information.
Alternatively, Student Financials provides a 50-character field called External GL Chart Field (field name EXT_GL_CHARTFLD) that you can use to enter chart of accounts data. To enable this field, you must signify to the system that you are not using PeopleSoft or Oracle General Ledger. To indicate that you are not using PeopleSoft or Oracle General Ledger, clear the General Ledger check box on the Installation Table page and select Others as the financial system on the SF Installation page. After you clear this check box and complete setup on the SF Installation page, pages that usually display the PeopleSoft-delivered ChartFields for data entry display instead—or, in some instances, also—the External GL ChartField field.
Using the External GL Chart Field does have some limitations. The system does not perform any editing against this field. In addition, the ChartField validation process does not check the contents of the External GL Chart Field to ensure that you have supplied valid chart of accounts information for each item type, course/class fee, and cashiering tender/target.
Even if you are not using PeopleSoft General Ledger, you must populate the GL setup tables (except the ChartField definition tables) before you can use the GL Interface or Cashiering GL Interface processes.