Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
New flag field which uses the Federal Ethnicity Code to classify race and ethnicity categories
The new Federal Ethnicity Code flag would collapse racial and demographic information into one line rather than multiple lines per individual. Following the IPEDS reporting requirements, which is what higher education institutions must use, it categorizes individuals into the five categories for race and follows special rules for Hispanic and multiracial. If an individual selects 'I am Hispanic or Latino' they will be categorized as 'Hispanic' over all else. If an individual selects 'African American' and 'Asian', they will be categorized as two or more races. The new field would better account for individuals that are multiracial, rather than creating multiple lines for each race they check.
The new field's simplification of the categories more accurately and concisely reports on an institution's racial and ethnic background. It greatly speeds up the time it takes to build a report as well. All of this can be currently done through custom datasets or calculations, however, it is a lengthy process that can often result in errors, especially when reporting on the historical data in this category. The time it takes to load visuals with the custom datasets are much longer than visuals created with data straight from the subject area.
Comments
-
Caroline - We will review this and revert
0 -
Hi @CarolineAnderson, is the new Federal Ethnicity Code flag a custom DFF created on top of Person ethnicities?
With respect to the scenario mentioned above, below is an example of what this flags behaviour seems like. Please confirm if our understanding is correct.
Person Number
Ethnicity
Ethnicity Display for the Worker
1001
I am Hispanic or Latino
Hispanic
1001
Asian
Hispanic
1002
American
Two or More Races
1002
Asian
Two or More Races
1003
Chinese
Chinese
0 -
Hi @AnishaPatra-Oracle your example looks like what we are looking for! It would be fine to be a custom DFF or just a new attribute in the HCM Subject areas such as workforce core.
0 -
Hi @CarolineAnderson , thanks for confirming! I have an additional request in this context, could you share a snapshot of how currently this field "new Federal Ethnicity Code flag" looks like in your HCM system? Is a custom DFF field created to support this?
0 -
We created a custom dataset to do this. Here is the query we used:
SELECT "HCM - Workforce Core"."Basic Information"."Person Number",
CASE
WHEN COUNT(DISTINCT "HCM - Workforce Core"."Ethnicity"."Ethnicity - All") > 1 AND "HCM - Workforce Core"."Basic Information"."Person Number" IN (SELECT "HCM - Workforce Core"."Basic Information"."Person Number" FROM "HCM - Workforce Core" WHERE "HCM - Workforce Core"."Ethnicity"."Ethnicity - All" = 'I am Hispanic or Latino.') THEN 'I am Hispanic or Latino.'
WHEN COUNT(DISTINCT "HCM - Workforce Core"."Ethnicity"."Ethnicity - All") > 1 THEN 'Two or more races'
WHEN "HCM - Workforce Core"."Ethnicity"."Ethnicity - All" IS NULL THEN 'Not disclosed'
ELSE "HCM - Workforce Core"."Ethnicity"."Ethnicity - All" END AS Ethnicity_Custom,
CASE
WHEN COUNT(DISTINCT "HCM - Workforce Core"."Ethnicity"."Ethnicity - All") > 1 AND "HCM - Workforce Core"."Basic Information"."Person Number" IN (SELECT "HCM - Workforce Core"."Basic Information"."Person Number" FROM "HCM - Workforce Core" WHERE "HCM - Workforce Core"."Ethnicity"."Ethnicity - All" = 'I am Hispanic or Latino.') THEN 'Minority'
WHEN COUNT(DISTINCT "HCM - Workforce Core"."Ethnicity"."Ethnicity - All") > 1 THEN 'Minority'
WHEN "HCM - Workforce Core"."Ethnicity"."Ethnicity - All" IS NULL THEN 'Not disclosed'
ELSE 'Minority' END AS Ethnicity_Type
FROM "HCM - Workforce Core"0 -
We would greatly benefit from this information collapsed into one line per individual as well. We are considering Caroline's workaround and another option but the options will take additional time / effort to set up as well as ongoing maintenance.
1 -
Our company would also find this solution tremendously beneficial. We also worked out a custom column formula to "collapse" but it is complex and doesn't work consistently across all subject areas. I couldn't agree more with the business case outlined above and fully support anything that can be done to enhance the reporting capabilities for race/ethnicity!
1
