Search Results reference_code_type_desc




Overview
Explore in AI Chat

Overview

IGS_PS_US_REQ_REF_CD_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It presents unit section requirement reference code data — the reference codes attached to unit section requirements within the academic structure — in a denormalized, human-readable form suitable for reporting and integration. The view is defined over IGS_PS_US_REQ_REF_CD joined to IGS_GE_REF_CD_TYPE, and its primary purpose is to resolve the numeric reference code type into a descriptive value so that downstream consumers do not need to perform the lookup themselves.

The view is particularly relevant to queries involving the UNIT_SECTION_REFERENCE_ID column, which links each reference code row back to the parent unit section reference record. This makes the view a useful entry point when tracing requirement-level reference codes for a given unit section.

Underlying Base Objects

The view text defines an inner join between two tables:

  • IGS_PS_US_REQ_REF_CD (aliased USRRC) — the base table holding unit section requirement reference code rows. It supplies the primary key, the unit section reference identifier, the reference code type, the reference code, its free-text description, and the standard WHO audit columns.
  • IGS_GE_REF_CD_TYPE (aliased RCT) — the reference code type lookup table. It supplies REFERENCE_CODE_TYPE_DESC through the join predicate USRRC.REFERENCE_CD_TYPE = RCT.REFERENCE_CD_TYPE.

Because the join is an equality join on reference code type, a row is returned only when the type exists in the lookup table. The view exposes USRRC.ROWID as ROW_ID and projects a literal NULL into the REFERENCE_CODE_ID column, indicating the base table does not carry a surrogate reference code identifier in this release. No additional base objects beyond these two tables are documented.

h4>Key Columns

Common Use Cases and Queries

Typical uses include validating that reference codes are attached correctly to unit section requirements, generating setup extracts, and feeding integrations that require readable type descriptions.

SELECT unit_section_reference_id,
       reference_cd_type,
       reference_code_type_desc,
       reference_code,
       reference_code_desc
FROM   apps.igs_ps_us_req_ref_cd_v
WHERE  unit_section_reference_id = :p_unit_section_reference_id;

A second pattern lists all codes of a given type across unit sections:

SELECT unit_section_reference_id,
       reference_code,
       reference_code_desc
FROM   apps.igs_ps_us_req_ref_cd_v
WHERE  reference_cd_type = :p_reference_cd_type;

Because REFERENCE_CODE_ID is hard-coded to NULL, consumers should not rely on it for joins; use UNIT_SECTION_REQ_REF_CD_ID or UNIT_SECTION_REFERENCE_ID instead. Compliance and audit extracts can select the WHO columns directly.