Results for “igs_he_ex_rn_dat_fd”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_HE_EX_RN_DAT_FD is a child table within the Oracle EBS Student System (IGS) product family, appearing under the Higher Education extract framework. Its documented purpose is to determine the field-level details of each extract line produced by the Extract run process. In practical terms, it stores the atomic name/value pairs that make up a single structured output line, allowing each generated extract record to be decomposed into individually addressable fields while retaining the parent line context.
The table is marked obsolete and, importantly, the ETRM metadata records it as "Not implemented in this database." This indicates that in the specific 12.1.1/12.2.2 environment documented, the physical object does not exist or was never created. The row above it in the hierarchy, IGS_HE_EX_RN_DAT_LN, provides the line context, and this table refines that context down to the field.
The heuristic Data Vault classification is satellite-leaning. This is a modeling suggestion rather than a documented fact. Because the table carries descriptive attributes (VALUE, OVERRIDE_VALUE) keyed to a parent business key, it behaves like a satellite hanging off the extract line. It is not a true hub, since its identity depends on the parent extract run and line rather than an independent business key. It is also not a link, since it records attributes rather than relationships between distinct hubs. The composite key (EXTRACT_RUN_ID, LINE_NUMBER, FIELD_NUMBER) reinforces the satellite interpretation: the grain is one field per line per run.
Key Information Stored
The documented schema contains eleven columns. The most significant are the following.
- RN_DAT_FD_ID — A surrogate identifier for the row. This is the only single-column unique index candidate (IGS_HE_EX_RN_DAT_FD_U2), making it the most reliable row-level handle for direct lookups.
- EXTRACT_RUN_ID — Identifies the extract run that produced the data. Combined with the next two columns, it forms the composite primary key.
- LINE_NUMBER — Identifies the specific line within the extract output. This is the join path back to IGS_HE_EX_RN_DAT_LN.
- FIELD_NUMBER — Sequences the individual field within the line, completing the composite primary key.
- VALUE — The extracted field content itself, the primary payload of the table.
- OVERRIDE_VALUE — An alternate value that supersedes VALUE when a downstream override is applied, supporting correction without destroying the original.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each field record, and when.
The distinction between the surrogate key (RN_DAT_FD_ID) and the natural business-key candidates is important. The unique index IGS_HE_EX_RN_DAT_FD_U1 (EXTRACT_RUN_ID, LINE_NUMBER, FIELD_NUMBER) represents the true business grain, while U2 provides an efficient single-column access path for tooling and APIs.
Common Use Cases and Queries
Typical use is reconstructing a full extract line from its constituent fields, or auditing a single field's value across runs. A representative pattern joins the field table to its parent line table on the shared key columns.
SELECT fd.EXTRACT_RUN_ID, fd.LINE_NUMBER, fd.FIELD_NUMBER, fd.VALUE, fd.OVERRIDE_VALUE
FROM IGS_HE_EX_RN_DAT_FD fd
WHERE fd.EXTRACT_RUN_ID = :p_run_id
ORDER BY fd.LINE_NUMBER, fd.FIELD_NUMBER;
A second frequent pattern pivots fields into columns for reporting, using OVERRIDE_VALUE where present and falling back to VALUE. Reconciliation queries comparing VALUE against OVERRIDE_VALUE help identify lines that were manually corrected before downstream delivery. Because the object is obsolete and not implemented, any such SQL should be validated against the actual customer database before reliance in a 12.2.2 upgrade path.
Related Objects
- IGS_HE_EX_RN_DAT_LN — The parent line table. The documented foreign key maps IGS_HE_EX_RN_DAT_FD.EXTRACT_RUN_ID and LINE_NUMBER to the corresponding columns on IGS_HE_EX_RN_DAT_LN. This is the primary join path and the most significant dependency.
- The extract run header table — Referenced indirectly through EXTRACT_RUN_ID, providing run-level context such as run date and parameters.
- IGS_HE_EX_RN_DAT_FD_PK — The primary key constraint over (EXTRACT_RUN_ID, LINE_NUMBER, FIELD_NUMBER).
- IGS_HE_EX_RN_DAT_FD_U1 and U2 — Unique indexes defining the business grain and the surrogate identifier respectively.
Given the obsolete status and the "not implemented" note, dependent logic is likely vestigial or replaced by successor extract structures. Integrators should confirm object existence in the target instance before designing joins or interfaces around this table.
-
Determines the field level details of each extract line comes from the Extract run process
-
Table: IGS_HE_EX_RN_DAT_FD 12.2.2
Determines the field level details of each extract line comes from the Extract run process
Not implemented in this database·Explore IGS module →
-
Base View for HESA extract data fields
APPS.IGSBV_HESA_EXT_RUN_DAT_FIELDS·↳ IGS_HE_EX_RN_DAT_FD·Explore IGS module →
-
View: IGS_HE_EX_RN_FD_DTLS_V 12.1.1
Links user defined return class fields with extract run ID.
APPS.IGS_HE_EX_RN_FD_DTLS_V·↳ IGS_HE_EXT_RUN_DTLS·↳ IGS_HE_EX_RN_DAT_FD·↳ IGS_HE_USR_RT_CL_FLD·Explore IGS module →
-
Links Extract Lines with Extract Fields
APPS.IGS_HE_EX_RN_FD_LN_DTLS_V·↳ IGS_HE_EX_RN_DAT_FD·↳ IGS_HE_EX_RN_DAT_LN·Explore IGS module →
-
Full View for HESA extract data fields
APPS.IGSFV_HESA_EXT_RUN_DAT_FIELDS·↳ IGS_HE_EXT_RUN_DTLS·↳ IGS_HE_EX_RN_DAT_FD·↳ IGS_HE_SYS_RT_CL_FLD·Explore IGS module →
-
Links Extract Lines with Extract Fields
Not implemented in this database·Explore IGS module →
-
View: IGS_HE_EX_RN_FD_DTLS_V 12.2.2
Links user defined return class fields with extract run ID.
Not implemented in this database·Explore IGS module →
-
Table: IGS_HE_EX_RN_DAT_LN 12.2.2
Holds the line level information of the data extracted from the Extract process. Each line in the actual extract file will exist as a record in this table
Not implemented in this database·Explore IGS module →
-
Base View for HESA extract data fields
Not implemented in this database·Explore IGS module →
-
Full View for HESA extract data fields
Not implemented in this database·Explore IGS module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2