Gender Identity support in PeopleSoft HCM and Campus Solutions. (Doc ID 2854804.1)

Last updated on DECEMBER 09, 2022

Applies to:

Details

The Campus Solutions team supports the management of gender-related values in release 9.2. The PeopleSoft HCM team recently delivered an update to gender values in HCM PI 41 (January 21, 2022).HCM delivered the new fields Regulatory Region, Birth Sex, Pronoun, Sexual Orientation and Gender Identity. The values of these fields are controlled by Regulatory Region. The HCM team plans to deliver the services support (Person Basic Sync Version 8 and External Search Match updates) for the new Gender fields in HCM PI 42 (April 2022). Information about the HCM update can be found here https://blogs.oracle.com/peoplesoft/post/gender and PeopleBooks > PeopleSoft Human Capital Management 9.2 > Core Functionality > Application Fundamentals >  Setting Up Personal Information Foundation Tables > Setting Up Gender Details.

For customers also using PeopleSoft Campus Solutions, this document answers possible questions about how the HCM management of gender values will impact how Campus Solutions manages this same category of data. This information is most pertinent for customers using the delivered PeopleSoft HCM-CS Person sync process.

Actions

At this time, Oracle does not plan to provide delivered synchronization between Campus Solutions and HCM for the gender values. We deliver the ability for customers to extend the delivered Person synchronization so they can deploy their institution-specific synchronization requirements.

FAQ

1. What are the values related to Gender provided by Campus Solutions and HCM?
1. Campus Solutions supports (PERS_DATA_EFFDT)
1. Sex
2. Campus Solutions supports (SCC_PERS_BIOG)
1. Birth Gender
2. Gender Identity
3. Other Identity
4. Preferred Pronouns
5. Other Pronouns
6. Sexual Orientation
7. Other Orientation
8. Plus 8 other Biographic fields
3. HCM supports (PERS_DATA_EFFDT)
1. Current Sex (was called "gender")
2. Birth Sex
3. Pronoun
4. Sexual Orientation
5. Gender Identity
   
   
2. What synchronization is delivered between Campus Solutions and HCM for the gender values?
   1. Currently, the value PERS_DATA_EFFDT.SEX field is synced between HCM and Campus Solutions. NOTE: To preserve this synchronization, you must add the translate value “X” to the ‘SEX’ on the HCM table.  For consistency, the long name is ‘Indeterminate/Intersex/Unspec’ and the short name  is ‘Intersex’.
   2. At this time, Oracle does not plan to provide additional delivered synchronization between Campus Solutions and HCM for the above values. We deliver the ability for customers to extend the delivered Person synchronization so they can deploy their institution-specific synchronization requirements.
      
      
3. What are the plans to synchronize the gender values between Campus Solutions and HCM?
   1. At this time, Oracle does not plan to provide delivered synchronization between Campus Solutions and HCM for the above values. We deliver the ability for customers to extend the delivered Person synchronization so they can deploy their institution-specific synchronization and data governance requirements.
   2. The customer will need to define the data governance rules for which application “owns” which gender attribute (for example, which values entered in the HCM application will update corresponding values in CS and cannot be overridden in CS). (Please refer to to PeopleBooks > PeopleSoft Campus Solutions 9.2 > Products > Campus Solutions > Campus Solutions Application Fundamentals > Integrating Campus Solutions with Human Capital Management > Understanding CS-to-HCM Integration for guidance on the delivered HCM-CS integration support.)
      
      
4. Why did Oracle choose not to deliver integration to enable synchronization of the gender values?
   1. Oracle understands that most Institutions prefer to manage their own data governance policies as well as prefer to manage how gender values are maintained in both applications.
   2. Institutions may be using delivered CS-HCM person synchronization now, which syncs bio-demographic attributes. At this point, the Campus Solutions team doesn’t see a strong use case for syncing gender values across HCM and CS applications. The teams will look at IdeaLabs for input on use cases from our customers for this requirement.
      
      
5. As an Institution, how do employees who are also students (and vice versa) manage these gender attributes?
   1. Each Institution will determine where the users in each role will maintain gender data.  Unless the Institution builds synchronization between HCM and CS, the individual will maintain their gender data in both the HCM and CS applications, independently.
      
      
6. In the situation where a student has updated Campus Solutions with the gender values, and then becomes an employee at the institution, how will the gender values from CS update the HCM table containing the new gender values?  Same question for an individual who is initially an employee in HCM and then becomes a student in CS.
   1. See answer to Question 3.
      
      
7. As an Institution, we want the gender values stored in the HCM tables to take precedent over the CS gender data (or the opposite request).  How do we make sure the data flows correctly? Is there a delivered way for us to express our governance policy in the HCM-CS sync messages?
   1. See answer to Question 3. Oracle will not deliver any updates to the existing integration support for HCM and CS.
      
      
8. As an Institution, we want the gender values to be maintained separately in HCM and CS.  How do we make sure there is no syncing of these values?
   1. See answer to Question 3.
      
      

Contacts