EB14 Fix After Move to Baseline

Status

key	updated	assignee	priority	status	resolution

Loading...

Refresh

Due date

Annual

On this page

1 Problem statement
2 Research/Backup
3 Helpful SQL Queries

Problem statement

EB14 isn’t generating values since going baseline.

Research/Backup

Issue

EB14’s logic is unfortunately a lot simpler than we thought. That case is being partially tracked on this Ellucian case.

Background

Since going baseline we have only reported 5 distinct values for that field.

Proposal

We will have to use the DED values on validation table, GORRACE.

Actions

key	summary	updated	due	assignee	priority	status	resolution

Loading...

Refresh

Dependency Investigation

We do not intend to change the data on SPBPERS_ETHN_CODE (SPAIDEN Table, STVETHN Validation Table). According to https://sequoias.atlassian.net/l/c/y0YPx0nJit pulls from that field to populate Ethnicity_Code and ETHNICITY_DESC.

Helpful SQL Queries

GORRACE Codes Used and their Description

SELECT DISTINCT GORPRAC_RACE_CDE, GORRACE_DESC
FROM SPBPERS
LEFT JOIN GORPRAC
ON SPBPERS_PIDM = GORPRAC_PIDM
LEFT JOIN GORRACE
ON GORPRAC_RACE_CDE = GORRACE_RACE_CDE