Search Results revenue_account_code




Overview
Explore in AI Chat

Overview

APPS.IGSBV_LOCATIONS is a read-only database view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and part of the Oracle Student System (IGS) product family. The "BV" suffix in its name indicates that it is a "Base View," the lowest-level, singular-object view typically published for use by higher-level business views and external interfaces. Its role is to expose location reference data maintained by the institution's student and academic administration modules in a denormalized, renamed form that is convenient for reporting, integration, and extension development.

The view projects a subset of columns from the IGS_AD_LOCATION_ALL table, renaming them to more descriptive alias names such as LOCATION_CODE, MAIL_DELIVERY_WORKING_DAYS, CLOSED_INDICATOR, REVENUE_ACCOUNT_CODE, and COORDINATE_PERSON_ID. This column alias strategy mirrors Oracle's convention of publishing stable reporting interfaces over internally named columns, insulating downstream reports, extracts, and custom code from physical column-name changes. Because the view is defined with the WITH READ ONLY clause, it cannot be used to perform data manipulation; it is strictly a query surface.

Underlying Base Objects

Per the documented view text, IGSBV_LOCATIONS is defined exclusively as a SELECT with aliased columns over the base table IGS_AD_LOCATION_ALL. No additional documented base objects are referenced. This makes the view a straightforward, single-table projection with no joins, unions, or analytical logic. Because IGS_AD_LOCATION_ALL is a table ending in _ALL, it is generally the multi-organization or "all records" table, meaning the view inherits whatever organizational visibility and security the base table carries. The WITH READ ONLY clause is applied at view definition time and cannot be overridden by a DML statement issued against the view. In practice, this means reports and integrations can select from IGSBV_LOCATIONS without concern for row-level locking or accidental writes, but any data maintenance must target the underlying table directly.

Key Columns

The view exposes ten columns, each corresponding to a renamed base column:

  • LOCATION_CODE (LOCATION_CD) — The unique business identifier for the location record.
  • DESCRIPTION — The human-readable description of the location.
  • LOCATION_TYPE — Classifies the location; the base column and its values drive downstream filtering and validation.
  • MAIL_DELIVERY_WORKING_DAYS (MAIL_DLVRY_WRK_DAYS) — Indicates the working days used for mail delivery scheduling.
  • CLOSED_INDICATOR (CLOSED_IND) — A flag marking whether the location is inactive or closed.
  • REVENUE_ACCOUNT_CODE (REV_ACCOUNT_CD) — The revenue account associated with the location, used for billing or accounting integration.
  • COORDINATE_PERSON_ID (COORD_PERSON_ID) — The person identifier of the primary coordinator or responsible contact for the location. This is the column users locate when searching for "coord_person_id," and it is the renamed form of COORD_PERSON_ID.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard Oracle WHO columns for audit and lineage.

Common Use Cases and Queries

The view is most commonly used to resolve a location's coordinator or revenue account for operational reporting. A typical query returning active locations for a coordinator is:

  • SELECT location_code, description, coordinate_person_id, revenue_account_code FROM apps.igsbv_locations WHERE closed_indicator = 'N' AND coordinate_person_id = :p_person_id;
  • Enumerate locations and their coordinators: SELECT location_code, description, coordinate_person_id FROM apps.igsbv_locations ORDER BY location_code;
  • Audit recently changed records: SELECT location_code, last_update_date, last_updated_by FROM apps.igsbv_locations WHERE last_update_date >= :p_since_date;

Because the view is read only and defined over a single table, it is safe to join it to person, account, and delivery-related objects on COORDINATE_PERSON_ID and REVENUE_ACCOUNT_CODE, respectively. For write operations or access to columns not published by the view, the underlying IGS_AD_LOCATION_ALL table must be used.