Skip to content

Schema Reference

The application schema is used to configure the objects returned from a connector.

Note

  • The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.

  • The schema attributes that are not present by default must be defined as strings if not specified.

The Oracle PeopleSoft HCM Database connector uses the following default correlation and object configurations.

Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.

Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.

Caution

Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.

To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

Account ID Schema Object Type
EMPLID Account

Default Account Attributes

The Oracle PeopleSoft HCM Database connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

Attribute Name Description
EMPLID The ID of the employee.
COUNTRY The country of the employee.
CITY The city of the employee.
STATE The state of the employee.
PER_ORG The organization of the employee.
ADDRESS1 The postal address1 of the employee.
ADDRESS2 The postal address2 of the employee.
ADDRESS3 The postal address3 of the employee.
FIRST_NAME The first name of the employee.
HR_RESPONSIBLE_ID The HR Responsible ID of the employee.
LAST_NAME The last name of the employee.
MIDDLE_NAME The middle name of the employee.
NAME The name of the employee.
NAME_PREFIX The prefix of the employee.
NAME_SUFFIX The suffix of the employee.
NAME_TITLE The title of the employee.
POSTAL The postal pin code of the employee.
PREF_FIRST_NAME The preferred first name of the employee.
EMPL_RCD The job employee record.
EFFDT The effective date of the job.
DEPTID The department ID of the job.
JOBCODE The job code of the job.
POSITION_NBR The position number of the job.
SUPERVISOR_ID The supervisor ID of the job.
HR_STATUS The HR status of the job.
EMPL_STATUS The employee status of the employee.
ACTION The action code of the job.
ACTION_REASON The action reason of the job.
LOCATION The location of the job.
FULL_PART_TIME A full or part time job.
COMPANY The company of the employee in the current job.
EMPL_TYPE The employee type of the job.
OFFICER_CD The officer code of the job.
EMPL_CLASS The employee class of the job.
ACCT_CD The account code of the job.
BUSINESS_UNIT The business unit of the job.
REPORTS_TO The person to whom the employee reports.
HIRE_DT The hiring date of the employee.
TERMINATION_DT The termination date of the employee.
EMAIL_ADDR The email address of the employee.
PHONE The personal phone of the employee.

Additional Attributes

The following attributes need to be added in the schema for:

networkID

  • MCF_IMUSERID

Note

MCF_IMUSERID is mapped with the Network ID on the PeopleSoft portal. The Network ID is not provided out of the box and must be added in the schema attributes to retrieve the NetworkID using the BuildMap rule.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.