Results for “include_ind”

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

Overview

The view IGS_AD_SOURCE_CAT is a multi-organization (multi-ORG) reporting and integration object within the Oracle E-Business Suite IGS – Student System product family, historically associated with Oracle Student System / Oracle Academic Enterprise (ETRM). It is classified as an obsolete component in release 12.1.1 and 12.2.2 environments. The view exposes admissions source category setup data, which governs how applicant and student records are attributed to marketing or recruitment sources, categories, and discrepancy handling rules.

As documented, the object is described as a "Multi ORG view based on IGS_AD_SOURCE_CAT_ALL table." This positions it as the organization-secured projection of a partitioned base table — the _ALL table stores rows across every operating unit (ORG_ID), while the view restricts visibility to the ORG_ID returned by the Multi-Org security mechanism based on USERENV('CLIENT_INFO'). In practical reporting and integration terms, the view provides a rowid-backed, ORG-safe cursor over admissions source category definitions used by admission, prospect, and recruitment processing.

Per ETRM metadata, the view is not implemented in the database documented, meaning its reported "implementation/DBA data" is empty. This is consistent with an obsolete object that may not exist or may remain in legacy schemas pending cleanup.

Underlying Base Objects

The view is defined over a single documented base object: IGS_AD_SOURCE_CAT_ALL. The metadata lists no other referenced base objects, so all columns are sourced directly from that ORG-partitioned table.

The multi-ORG filter is implemented through a WHERE clause comparing the table's ORG_ID to the ORG_ID decoded from USERENV('CLIENT_INFO'), using:

• SUBSTRB(USERENV('CLIENT_INFO'), 1, 10) to extract the current operating unit identifier from the session's client information.
• A leading-space test (SUBSTRB(..., 1, 1) = ' ') that yields NULL when the client information is unset.
• NVL(..., -99) applied on both sides, defaulting both the row ORG_ID and the session ORG_ID to -99 when no operating unit is established.

Because both sides of the predicate use the same NVL default, rows with an ORG_ID of -99 become visible when no ORG context is set — a behavior typical of Multi-Org secured views that permit access to shared/global data. The view also exposes TAB.ROWID as ROW_ID, enabling row-level identification of the underlying base row.

Key Columns

The view exposes nineteen columns. The most significant include:

• ROW_ID — the physical ROWID of the base table row; useful for row addressing and updates through the view.
• ORG_ID — the operating unit that owns the source category setup record; the Multi-Org discriminator.
• SRC_CAT_ID — the primary key identifying the source category definition.
• SOURCE_TYPE_ID — foreign key linking the category to its admissions source type.
• CATEGORY_NAME — the descriptive label of the source category.
• MANDATORY_IND — indicates whether selection of this category is required during data entry.
• INCLUDE_IND — the flag queried by users; it controls whether the category is included in source category processing, selection lists, or roll-up handling. It is the focus of the include_ind search.
• DISCREPANCY_RULE_CD — code governing how discrepancies between provided and derived source information are resolved.
• SS_IND and SS_MANDATORY_IND — self-service indicators controlling availability and mandatory status in self-service flows.
• DISPLAY_SEQUENCE — the ordering used when presenting categories in a user interface or list.
• DETAIL_LEVEL_IND — indicates the level of detail associated with the category.
• AD_TAB_NAME and INT_TAB_NAME — the admissions and integration interface table names associated with the category.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO audit columns.

Common Use Cases and Queries

Typical scenarios involve validating source category setup per operating unit, driving recruitment reporting, and tracing which categories are active for inclusion in admissions processes. The inclusion flag is frequently the subject of troubleshooting, since INCLUDE_IND determines whether a category surfaces in selection lists.

Sample query listing included categories for the current operating unit:

• SELECT SRC_CAT_ID, CATEGORY_NAME, SOURCE_TYPE_ID, INCLUDE_IND, MANDATORY_IND, DISPLAY_SEQUENCE, ORG_ID FROM IGS_AD_SOURCE_CAT WHERE INCLUDE_IND = 'Y' ORDER BY DISPLAY_SEQUENCE;

Sample query reviewing inclusion status across all accessible sources:

• SELECT ORG_ID, SRC_CAT_ID, CATEGORY_NAME, INCLUDE_IND, SS_IND, SS_MANDATORY_IND FROM IGS_AD_SOURCE_CAT WHERE NVL(INCLUDE_IND,'N') = 'Y';

Because the object is documented as obsolete and not implemented in the target database, these patterns should be preceded by a data dictionary check (e.g., ALL_VIEWS/ALL_TAB_COLUMNS) confirming the view's presence. Where it is absent, equivalent reporting should target the base table IGS_AD_SOURCE_CAT_ALL with explicit ORG_ID and INCLUDE_IND predicates.