Results for “igs_ad_location_type”

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

Overview

IGS_AD_LOCATION_TYPE is a reporting and integration view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It presents the set of location type codes used to classify physical and logical locations recorded against students, organizations, and admissions entities within Oracle Student System. Because the object is a view rather than a base table, it exposes no independent storage; it is a filtered projection of a single underlying table and exists primarily to enforce multi-organization (Operating Unit) security at query time.

The view carries a status of VALID and is available in both EBS 12.1.1 and 12.2.2. It is documented in the ETRM repository with the object type VIEW and the owner APPS, and its structure is stable across the two releases described here.

Underlying Base Objects

Although the ETRM metadata records no referenced base objects, the documented view text establishes the dependency explicitly. IGS_AD_LOCATION_TYPE is defined entirely over the table IGS_AD_LOCATION_TYPE_ALL, aliased in the view definition as TAB. Every column exposed by the view is a direct projection of a column in that table, plus the pseudocolumn ROWID, which is surfaced as ROW_ID.

The view applies a single filter predicate on ORG_ID. The predicate compares the ORG_ID of each row against the current Operating Unit identifier derived from the USERENV('CLIENT_INFO') session value, using the standard Oracle EBS multi-org security pattern. It extracts the first ten bytes of CLIENT_INFO, converts them to a number, and substitutes -99 when the leading character is a space or the value cannot be interpreted. Rows are retained only where the table's ORG_ID matches this derived value. This is the mechanism by which the view is partitioned by Operating Unit, and it is why the "_ALL" table exists as the unrestricted base.

Key Columns

• ROW_ID — The ROWID of the underlying IGS_AD_LOCATION_TYPE_ALL row, providing a stable physical address for the record.
• ORG_ID — The Operating Unit identifier that owns the location type. This column drives the security predicate applied in the view WHERE clause.
• LOCATION_TYPE — The location type code itself; the primary business key used when assigning a type to a location record.
• DESCRIPTION — The descriptive text associated with the location type code.
• S_LOCATION_TYPE — The system-level or seeded indicator for the location type, distinguishing delivered values from user-defined ones.
• CLOSED_IND — Indicates whether the location type has been closed and is therefore unavailable for new assignments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the row, and when.

Common Use Cases and Queries

The primary use of IGS_AD_LOCATION_TYPE is to supply validated location type values for lookups, validation, and reporting without requiring callers to implement multi-org security themselves. Typical scenarios include populating a location type list of values on an admissions or student data entry form, validating a code before insertion into a location record, and producing reports of configured location types per Operating Unit.

Because the view already restricts rows by Operating Unit, queries do not need to add an ORG_ID predicate. A representative query retrieving active location types is:

• SELECT location_type, description, s_location_type FROM igs_ad_location_type WHERE closed_ind = 'N' ORDER BY location_type;
• SELECT location_type, description FROM igs_ad_location_type WHERE closed_ind = 'N' AND s_location_type = 'Y';
• SELECT org_id, location_type, description, creation_date, created_by FROM igs_ad_location_type ORDER BY location_type;

Developers requiring access to location types across all Operating Units, for example in a global cross-reference report, must query IGS_AD_LOCATION_TYPE_ALL directly, since the view intentionally suppresses rows outside the caller's Operating Unit context. All queries should be issued from a session in which CLIENT_INFO has been initialized by the EBS application, as is the case for standard concurrent programs and forms.