Search Results closed_indicator




Overview
Explore in AI Chat

Overview

IGSBV_LOCATIONS is a read-only view owned by the APPS schema within the IGS (Student System) product family of Oracle E-Business Suite. It exposes records describing the physical locations that are available to the institution for scheduling, delivery, and administrative purposes. The view is defined as a projection over the location entity, presenting a business-friendly column naming convention (for example, LOCATION_CODE rather than LOCATION_CD, and REVENUE_ACCOUNT_CODE rather than REV_ACCOUNT_CD).

Its primary role is to support reporting and integration requirements where the full underlying location entity is not required or where a stable, read-only interface to location data is preferred. Because the view is marked WITH READ ONLY, it cannot be used as a target for DML operations, making it appropriate for extraction, ad hoc query, and inbound reference by downstream systems. The object was validated in the 12.2.2 documented metadata, and its structure is consistent with the 12.1.1 release.

Underlying Base Objects

The view text is defined over a single base table, IGS_AD_LOCATION_ALL. This table holds the canonical location records for the Student System, including location codes, descriptions, classification, mailing schedule behaviour, and accounting references. IGSBV_LOCATIONS does not introduce joins or aggregations; it is a straightforward column alias and renaming layer over the base table, restricted to read-only access.

The _ALL suffix on the base table indicates that, in a multi-organisation installation, the underlying table may carry an operating unit column. The view itself does not expose any ORG_ID column, so it should be treated as a reporting surface that returns the location set visible to the querying session under the standard EBS security model. No other base objects are documented as contributing to this view.

Key Columns

  • LOCATION_CODE — The unique business key for the location, renamed from LOCATION_CD. Used to identify a location in scheduling and reporting extracts.
  • DESCRIPTION — The human-readable name or description associated with the location.
  • LOCATION_TYPE — Classifies the location for the purposes of scheduling and reporting (for example, distinct categories of teaching, administrative, or service venues).
  • MAIL_DELIVERY_WORKING_DAYS — The pattern of working days applied when the location is used as a mailing address, renamed from MAIL_DLVRY_WRK_DAYS.
  • CLOSED_INDICATOR — Flag indicating whether the location is currently closed, renamed from CLOSED_IND. Relevant when filtering active venues.
  • REVENUE_ACCOUNT_CODE — The revenue account associated with the location, renamed from REV_ACCOUNT_CD. This is the column most likely sought by users searching for "revenue_account_code", since it carries the accounting code used when revenue is attributed to a location.
  • COORDINATE_PERSON_ID — Reference to the person who coordinates the location, renamed from COORD_PERSON_ID.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard EBS audit columns.

Common Use Cases and Queries

Typical usage includes extracting active locations with their assigned revenue accounts, validating that every open location carries a revenue account code before period close, and supplying location reference data to scheduling or finance integrations. A representative query returning open locations and their revenue codes follows:

SELECT location_code, description, location_type, revenue_account_code
FROM apps.igsbv_locations
WHERE closed_indicator = 'N';

To identify locations missing an accounting assignment, which is often the root cause of downstream revenue posting issues:

SELECT location_code, description
FROM apps.igsbv_locations
WHERE revenue_account_code IS NULL;

Because the view is read-only and directly mirrors IGS_AD_LOCATION_ALL, any referential or security restrictions applied to the base table also apply here. Queries should therefore be run with an appropriately privileged APPS session, and results should not be assumed to include records outside the session's organisational access.