Results for “type_meaning”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AD_CRED_TYPES_V is an Oracle EBS PL/SQL view owned by the APPS schema within the IGS – Student System product family. It presents a denormalized, reporting-friendly projection of credential type definitions used by the Oracle Student System for admissions and academic records processing. Credential types describe the external academic credentials (for example, secondary school diplomas, undergraduate or postgraduate degrees) that an institution recognizes for admissions evaluation and articulation purposes. Because the base credential type table stores a coded system type and a coded step category, the view resolves those codes to their translated meanings so that consumers do not need to join lookup and catalog tables themselves.

The view is documented as VALID in ETRM metadata for both 12.1.1 and 12.2.2. It is intended for read-only use in reporting, integrations, and descriptive flexfield or outbound interface work. The column TYPE_MEANING is the resolved value surfaced by the search term "type_meaning," and it corresponds to the lookup meaning for the credential system type code.

Underlying Base Objects

The ETRM excerpt defines the view text explicitly. It is constructed over three base objects joined in the APPS schema:

• IGS_AD_CRED_TYPES CT — the primary credential type definition table, supplying the surrogate key, credential code, system type code, description, step code, closed indicator, and standard WHO audit columns.
• IGS_LOOKUP_VALUES LK — the lookup values view, restricted with the predicate LK.LOOKUP_TYPE = 'CREDENTIAL_SYSTEM_TYPES'. This join matches CT.SYSTEM_TYPE = LK.LOOKUP_CODE and provides the MEANING that is projected as TYPE_MEANING.
• IGS_TR_STEP_CTLG_ALL TRSC — the step catalog table, joined on CT.STEP_CODE = TRSC.STEP_CATALOG_CD. This is an outer join (note the (+) operator on the TRSC side), so credential types without a matching step catalog entry are still returned, with STEP_CODE_DESC null.

The presence of the Oracle-style outer join syntax confirms the view predates the ANSI join migration and remains unchanged across 12.1.1 and 12.2.2.

Key Columns

• ROW_ID — the rowid of the underlying IGS_AD_CRED_TYPES row, used for row identification in Forms-based update flows.
• CREDENTIAL_TYPE_ID — the unique surrogate key of the credential type.
• CREDENTIAL_TYPE — the short credential type code.
• SYSTEM_TYPE — the coded system type used in the lookup join.
• TYPE_MEANING — the translated meaning of the system type, resolved from IGS_LOOKUP_VALUES for lookup type CREDENTIAL_SYSTEM_TYPES. This is typically the column of interest when searching by "type_meaning."
• DESCRIPTION — the free-text description of the credential type.
• STEP_CODE and STEP_CODE_DESC — the associated step catalog code and its description, the latter left-joined from IGS_TR_STEP_CTLG_ALL.
• CLOSED_IND — indicates whether the credential type is inactive or closed for new use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include admissions setup validation, extraction of credential types for integration with external evaluation services, and reporting on active versus closed credential types. Because the join to IGS_LOOKUP_VALUES is on the lookup code and a fixed lookup type, queries should filter or display TYPE_MEANING rather than the raw SYSTEM_TYPE whenever user-facing output is required.

A representative query listing active credential types with their resolved meanings:

SELECT credential_type_id,
       credential_type,
       type_meaning,
       step_code_desc,
       description
FROM   apps.igs_ad_cred_types_v
WHERE  closed_ind = 'N'
ORDER  BY type_meaning, credential_type;

To group credential types by system type for analytical reporting:

SELECT type_meaning,
       COUNT(*) cred_type_count
FROM   apps.igs_ad_cred_types_v
GROUP  BY type_meaning
ORDER  BY cred_type_count DESC;

Because the view resolves lookup and catalog descriptions, it eliminates repeated joins in downstream SQL and is safe to embed in custom concurrent programs, OBIEE or BI Publisher data models, and outbound interface SQL provided the standard EBS read-only access conventions are observed.