Results for “mail_dlvry_wrk_days”

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

Overview

IGS_AD_LOCATION is a VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS – Student System (Oracle Student System / Oracle iGS) product family. In EBS 12.1.1 and 12.2.2 the view exposes address and location reference data used by the Student System for tracking physical or operational locations associated with an operating unit. Functionally, it provides a reporting and integration layer over the location master data stored in the IGS_AD_LOCATION_ALL table, applying Multi-Org (business unit / org_id) security at query time.

The view is a filtered projection of its base table. It does not add derived calculations; instead it passes through the descriptive, classification, and descriptive flexfield (DFF) attribute columns while restricting rows to the operating unit identifiable from the session’s CLIENT_INFO. This makes it the customary read interface for concurrent programs, OAF pages, and downstream interfaces that must respect operating unit context, while direct DML continues to be performed against the underlying table.

Underlying Base Objects

The ETRM metadata documents the referencing object as IGS_AD_LOCATION_ALL. No other base tables, synonyms, or additional joined objects are documented; the view is a single-table definition, not a join. The defining text references the base table once, aliased as TAB, and selects TAB.ROWID as ROW_ID for row identification.

The only filter is the operating unit predicate. It compares the row’s ORG_ID to the value decoded from USERENV('CLIENT_INFO'), taking the first ten bytes of the session client information and converting them to a number. When CLIENT_INFO is unset or begins with a blank, the decode returns NULL and the NVL logic substitutes -99, so rows with a NULL or -99 ORG_ID are also returned. This is the standard EBS Multi-Org view pattern used across 11i and R12.

Key Columns

• ROW_ID – the base table ROWID, exposing physical row identity for update-through-view scenarios.
• ORG_ID – operating unit identifier; drives the Multi-Org security filter.
• LOCATION_CD – the unique location code, the natural business key used by callers to look up a location.
• DESCRIPTION – the free-text name or description of the location.
• LOCATION_TYPE – classification of the location (for example, campus, delivery, or administrative type).
• MAIL_DLVRY_WRK_DAYS – the mail delivery working days indicator for the location.
• COORD_PERSON_ID – identifier of the coordinating person associated with the location.
• CLOSED_IND – indicates whether the location is closed and therefore inactive for new use.
• REV_ACCOUNT_CD – revenue account code associated with the location.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 – the descriptive flexfield structure, allowing institution-specific location attributes. Note that ATTRIBUTE8 through ATTRIBUTE20 are selected directly from the base table alongside ATTRIBUTE7, so the full DFF segment set is available to reporting.

Common Use Cases and Queries

Typical uses include validating location codes prior to interface load, populating LOVs restricted to the current operating unit, and reporting on active locations and their DFF attributes.

List all open locations for the current operating unit:

• SELECT LOCATION_CD, DESCRIPTION, LOCATION_TYPE FROM IGS_AD_LOCATION WHERE NVL(CLOSED_IND,'N') = 'N' ORDER BY LOCATION_CD;

Retrieve a single location by code, including flexfield values:

• SELECT LOCATION_CD, DESCRIPTION, COORD_PERSON_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM IGS_AD_LOCATION WHERE LOCATION_CD = :p_location_cd;

Audit recent maintenance of location records:

• SELECT LOCATION_CD, LAST_UPDATED_BY, LAST_UPDATE_DATE, REV_ACCOUNT_CD FROM IGS_AD_LOCATION WHERE LAST_UPDATE_DATE >= SYSDATE - 30 ORDER BY LAST_UPDATE_DATE DESC;

Because the view enforces Multi-Org security, callers must initialize the org context (for example via FND_GLOBAL or the standard CLIENT_INFO initialization) before querying; otherwise the -99 substitution may cause no rows or unintended rows to be returned. Direct inserts and updates should target IGS_AD_LOCATION_ALL rather than the view.