Setting Up Integration Between Campus Solutions and PeopleSoft Financials
PURPOSE: The purpose of this document is to illustrate the steps required to setup and use delivered integration between PeopleSoft
Campus Solutions and PeopleSoft Financials applications.
SCOPE: The setup outlined in this document will be applicable for Campus Solutions product 8.9, and 9.0, and for PeopleSoft
Financials 8.9 and higher. An example of a delivered service operation to populate Campus Solutions with PeopleSoft Financials
chartfield information using a FULLSYNC and SYNC message, and the setup required to use the STUDENT_FIN_ACCTG_LINE
message will be shown.
ASSUMPTIONS: This document does not include any steps on setting up integration broker at the application server level. It will
assume the integration broker configuration has been completed, and is working.
The PeopleSoft Financials environment used in this document is Finance 9.0.
Step 1: Ping the Nodes
Before starting any service operation configuration, ping the nodes of the respective application to be interfaced to. For example, on
the Campus Solutions application, ping the Financials application node. On the Financials application, ping the Campus Solutions
node.
H900ZXZX is the Campus Solutions node, and E900ZXZX is the Financials 9.0 node.
Sign onto Campus Solutions, and ping the Financials node:
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
1
Click the ‘Ping
Node’ button:
The ping should result in ‘Success’ status. If the result is not success, there is an issue with the application server integration broker
configuration.
From Financials, ping the Campus Solutions node:
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
2
Click the ‘Ping Node’ button:
When both nodes can be pinged successfully, service operation configuration can commence.
FULLSYNC Service Operation Configuration
A FULLSYNC service operation will send the entire content of the table associated with the service operation to the subscribing node.
A FULLSYNC message is a convenient method to initially populate the corresponding table on the subscribing application.
The ACCOUNT_CHARTFIELD_FULLSYNC service operation will be shown in the examples below. The steps to activate this
FULLSYNC service operation can be applied to any FULLSYNC service operation.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
3
A service operation is a ‘wrapper’ around a message. Each message will be associated to a physical table within the database.
Typically, the table will reside on the publishing application and on the subscribing application. Below is the
ACCOUNT_CHARTFIELD_FULLSYNC message object.
The table name associated to the message is illustrated above.
Financials will be the publishing application in this FULLSYNC example, and Campus Solutions will be the subscribing application.
On Financials application, the setup of the ACCOUNT_CHARTFIELD_FULLSYNC message is shown below:
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
4
On the General Tab of the service operation on the Publishing application check the Active box. The service operation must be active.
Note the Queue Name used on the service operation. ACCOUNT_CHARTFIELD_FULLSYNC uses the GL_SETUP queue.
On the Publishing application, a handler is not required; the setup of this tab on the publishing application can skipped.
Click on the Routings tab.
A routing definition must exist on the service operation on the publishing application and the subscribing application. The routing
defines the ‘sending’ node and the ‘subscribing’ node.
Enter a routing name
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
5
Click the ‘Add’ button
Populate the Sender Node field with the node name of application that will be sending the data. In this example, Financials is our
Sending Node.
Populate the Receiver Node with the node name of the application that will be subscribing to, or receiving the data. In this example,
Campus Solutions is our Receiver node.
Click ‘Save’, then ‘Return’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
6
The routing definition has been completed, and is Active. Routings MUST be active for the message to be published or subscribed to!!
Click Save.
On Financials, the Queue the service operation uses must be set to Run Status:
ACCOUNT_CHARTFIELD_FULLSYNC uses the GL_SETUP queue:
Queue objects are delivered with Queue Status = Pause. Click the drop down box, and select Run.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
7
Click ‘Save’ to save the changes.
Setup of the service operation on the publishing application, Financials, is now complete.
Campus Solutions, as the subscribing application, must also setup the service operation and queue. The snapshots below are from
Campus Solutions.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
8
Click the Active box on the ‘General’ tab
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
9
Since Campus Solutions is the subscribing application, a handler must be activated. A handler is the ‘logic’ the application uses to
insert the data from the publishing node into the table associated with the service operation.
Click on the Handlers tab of the component.
Handlers are delivered inactive. To activate the handler, click the drop down box and select active.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
10
A Routing must also be defined. Click on the Routing tab.
Enter a Routing Name and click ‘Add’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
11
Enter the node name of the sending, or publishing application. Financials is the publishing application.
Enter the node name of the receiving, or subscribing application. Campus Solutions is the subscribing application.
Click ‘Save’, then ‘Return’.
The routing is defined, and is Active. The routing must be active for subscription to occur.
Click ‘Save’.
Ensure the Queue associated with the service operation is set to Run. The Queue for ACCOUNT_CHARTFIELD_FULLSYNC is
GL_SETUP.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
12
Full Data Publish Setup and Execution
A FULLSYNC service operation is executed on the publishing application using the Full Data Publish process.
Some setup is required before the Full Data Publish can be run. This setup is required on the publishing application only.
On Financials, setup the Full Data Publish Rules.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
13
To setup the full data publish rules for a FULLSYNC service operation, the status must be Active, and the Create Message Header and
Create Message Trailer boxes must be checked on
Click ‘Save’ to save these changes.
To run the Full Data Publish, select a run control and populate the run control page.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
14
The request Id can be any value.
The description is free form text, and any descriptive information can be entered.
Populate the Message Name field with the name of the Full Data Publish Rule to be executed.
Click ‘Save’ to save the run control and click ‘Run’ to submit the job to the process scheduler.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
15
Select the EOP_PUBLISHT process name, and click ‘OK’.
When the EOP_PUBLISHT has finished running check the services operation monitor to confirm the success of the publication.
If the service operation does not have all transactions in ‘Done’ status, an issue has been encountered and must be resolved before
proceeding.
Click on the number in the ‘Done’ column
A FULLSYNC message uses a Header and Trailer; the first and last transaction id shown on the Operation instances tab will be the
header and trailer respectively. The middle transaction id will contain the data from the table. Click on the Details hyperlink of the
middle transaction id:
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
16
Note the statuses of the publication and the subscription.
Check the service operation on the Campus Solutions Service Operation Monitor:
The service operation is in Done status. Click on the number in the Done column.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
17
Click the ‘Details’ hyperlink on the middle transaction Id.
The subscription is in ‘Done’ status, indicating the data from Financials has been populated into the Campus Solutions table associated
with the service operation.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
18
SYNC Service Operation Configuration
A SYNC service operation will send updates from a change to a row of data on the publishing application to the subscribing application.
Unlike the FULLSYNC service operation, which is executed by the Full Data Publish process, a SYNC message is typically triggered
from online activity. For example, when a change is made to an existing Account value on Financials, the
ACCOUNT_CHARTFIELD_SYNC message will fire, and publish the changes to the subscribing application.
Steps to configure a SYNC service operation are the same as the FULLSYNC service operation. The setup of the
ACCOUNT_CHARTFIELD_SYNC service operation on Financials follows. The setup of the any SYNC service operation will need the
following setup performed on the respective application.
Check the ‘Active’ box.
No Handler is required on the publishing application
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
19
Define a routing, specifying the Sender Node and Receiver Node.
The queue attached to the service operation must be set to run:
Setup of the ACCOUNT_CHARTFIELD_SYNC message on Campus Solutions:
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
20
Make the service operation ‘Active’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
21
Campus Solutions is the subscribing application, and the above handler must be active.
Add a routing, and ensure it is active.
On Campus Solutions the queue for the service operation must be in ‘Run’ Status.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
22
Using the SYNC Service Operation:
SYNC Service Operations are typically triggered from an online activity. To trigger the ACCOUNT_CHARTFIELD_SYNC message
from Financials to Campus Solutions, a change to an existing Account Chartfield value must be made.
An example follows. The chartfield change is made on the Financials environment. Select the account to be changed:
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
23
Enter a new effective dated row. NOTE – Using correction mode change on entities which trigger a SYNC message can result in failure
on the subscribing environment!! Always insert a new effective dated row.
Click ‘Save’.
Check the Services Operation Monitor on Financials:
The ACCOUNT_CHARTFIELD_SYNC service operation has been published by the change made to the application page.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
24
On Campus Solutions, check the services operation monitor:
Click on the number in the Done column, then on the Details hyperlink:
Subscription has been successful. The change to the chartfield has been sent, and subscribed to on Campus Solutions.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
25
Setting up the STUDENT_FIN_ACCTG_LINE Service Operation
The STUDENT_FIN_ACCTG_LINE service operation is unique. Campus Solutions publishes accounting line information to Financials.
Financials subscribes to this information, through the service operation. Financials processing will create journals from the accounting
information; when the journals are created for the accounting lines, the journal id, journal date are sent back to Campus Solutions using
the STUDENT_FIN_ACCTG_LINE service operation. This service operation is the only bi-directional service operation between
Campus Solutions and Financials; therefore, the setup of the service operation is unique. Both Campus Solutions and Financials will
publish and subscribe to this message.
Campus Solutions setup of STUDENT_FIN_ACCTG_LINE service operation:
Click the ‘Active’ box.
Note the Queue Name used by this service operation – STUDENT_ADMIN_ACCOUNTING.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
26
Campus Solutions must subscribe to the message from Financials containing the journal id and journal date; therefore, the handler
must be set to active.
Enter a routing name, and click the ‘Add’ button.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
27
Enter a routing where the sender node is the Campus Solutions node, and the receiver node is the Financials node. Click ‘Save’, then
‘Return’.
Add a routing for the service operation published from Financials to Campus Solutions.
Click ‘Add’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
28
This routing will specify the Sender node as the Financials node, and the Receiver Node as Campus Solutions. Click ‘Save’, then
‘Return’.
Click ‘Save’ to save the service operation.
Activate the Queue used by this Service Operation on Campus Solutions.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
29
Queue objects are delivered with a Status = ‘Paused’. Change the Queue Status = ‘Run’ and click ‘Save’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
30
Configuring the STUDENT_FIN_ACCTG_LINE Service Operation on Financials
The steps to activate the STUDENT_FIN_ACCTG_LINE on Financials are identical to the steps taken on Campus Solutions.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
31
Check the Active Box.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
32
Activate the handler on the service operation.
Enter a routing name, and click ‘Add’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
33
Enter Campus Solutions node as the Sender Node, and the Financials node as the Receiver Node.
Click ‘Save’, then ‘Return’.
Enter a routing name for the routing of this service operation from Financials to Campus Solutions.
Click ‘Add’.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
34
On this routing, enter the Financials node name as the Sender Node, and the Campus Solutions node as the Receiver Node.
Click ‘Save’, then click ‘Return’.
Click ‘Save’ to save all changes to the service operation.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
35
Set the STUDENT_ADMIN_ACCOUNTING queue to ‘Run’ status, and click the ‘Save’ button.
On Campus Solutions, the STUDENT_FIN_ACCTG_LINE message is published by the ‘Batch Publish’ process. The Batch Publish
process will publish all previously unpublished accounting lines from the SF_ACCTG_LN table.
SF_ACCTG_LN is populated by two processes within Campus Solutions, Student Financials. SFDPTREC.SQR is one of these
processes. This SQR is ‘Generate Cashiering Entries’ process, located at menu Student Financials, GL Interface, Generate Cashiering
Entries.
The other process which populates the SF_ACCTG_LN table is the SFPGLINT cobol program. This process is located at menu
Student Financials, GL Interface, Generate Accounting Entries.
Before the publication can occur, a Batch Publish Rule must be defined on Campus Solutions.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
36
Enter a Publish Rule Id value. Use the service operation name in this field.
Enter a Description. This is free form text, but is a required field.
Change the Status to Active.
Uncheck the Create Message Header, and Create Message trailer boxes. STUDENT_FIN_ACCTG_LINE is not a FULLSYNC
Message.
Click on the Batch Programs tab of the component.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
37
On the Batch Programs tab, enter the names of the processes used to create the SF_ACCTG_LN data. Only the process names used
need to be entered. For example, if a customer is not running the Generate Cashiering Entries process, SFDPTREC does not have to
be specified on this page.
Click ‘Save’ to save the changes.
To execute the Batch Publish Rule, navigate to the following page. A run control will be needed.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
38
Complete the run control as shown. Any request id, and description can be used.
The process name which created the SF_ACCTG_LN rows to be published must be entered in the ‘Process Name’ field.
When the run control has been populated, click the ‘Run’ button.
Click ‘OK’ to submit the job to the process scheduler.
When the batch publish process has finished successfully, navigate to the Campus Solutions integration broker monitor.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
39
The STUDENT_FIN_ACCTG_LINE service operation should appear in the monitor, and be in ‘Done’ status. Click on the number in the
‘Done’ column.
Click on the ‘Details’ hyperlink.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
40
Publication is done on Campus Solutions.
Check the service operation on the Financials application.
STUDENT_ADMIN_ACCOUNTING queue has had one publication. Click on the number in the ‘Done’ column.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
41
Click on the ‘Details’ hyperlink.
Subscription is done. The data has been successfully sent to Financials.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
42
