Integrating SailPoint with Oracle PeopleSoft ERP

Revised Date: 31 May 2024

This document is designed to give specific information about the requirements and field definitions needed to get a working instance of an Oracle PeopleSoft source in IdentityNow. The Oracle PeopleSoft ERP manages the administrative entities of the PeopleSoft server (User Profiles and Roles) and communicates to the PeopleSoft server through component interfaces.


This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/oracle/peoplesoft_erp/help/integrating_oracle_peoplesoft_erp/intro.html

The Connector documentation should reference the Source Type Display name somewhere in the Documentation, probably on the first page. For this instance, the connector is described here as the “Oracle PeopleSoft ERP” connector in the list andd this document, but the Source Type listed in SailPoint is just “PeopleSoft”

Likewise, there is an “Oracle PeopleSoft HCM” in the Documentation, and in ISC, it is called “PeopleSoft HCM Database” as the Source Type.

Hi Geoff! Thanks for reaching out. We will look into this.

Just following up on this. Had the same questions from a client about how they know which documentation goes with the connector they chose.

Hi Geoff, I agree it is confusing when the UI doesn’t match the full connector name. The easiest way for customers to see which guides go with their configured sources is by selecting the Documentation links that are available in the UI. I would also direct you to the Identity Security Cloud Compass landing page, the second column should match what is in the UI as far as connector names goes. If you’re seeing mismatches in that table, please let us know and they will be updated.

@ryan_mccall Thank you for the quick response.

I went back and looked in the UI, and the only link for the documentation is when you are creating a new source and selecting a new connector. If your application is set up already, there is no link to the documentation anywhere on that page. This is the situation we are in when we are onboarding new team members who are trying to learn about the connectors in use.

My ask here is just that for each of the connectors, that a sentence be added to the First page that includes the name that this connector shows up as in Sailpoint, if it differs from the name used for the connector.

I did look at the link you provided to compass, and it does indeed have the information I was looking at on it, however it seems this information should be included with the connector documentation too to improve the usefulness for users. Either a Link to the compass article could be added to the Connector page in the upper part, or better yet, the table from the compass article can be incorporated into the main connector documentation page, since the compass article already has the links.

It just seems complex to tell our new users that the connector documentation is here, but if you can’t find it, go over to compass to this article to look it up, then click the link to bring you back to the documentation for the one you are looking for.

Hi Geoffe, we’re looking to make an update to the landing page to make it easier to identify the guides where there is a mismatch between the UI and the guide name. These guides will have that information added to the landing page underneath the link, similar to how we handle guides where the marketing name has changed. For example, under the Entra ID we have the information that it was previously the Azure Active Directory guide.

1 Like