Search Results boundary_code




Overview
Explore in AI Chat

Overview

GL_LOOKUPS_BOUNDARIES_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM documentation records its status as VALID and its description as "10SC ONLY," indicating that the object was created for a specific localized or regional implementation context (the "10SC" designation) rather than as a general-purpose, globally shipped reporting view. It is not a core public API and should be treated as an implementation-specific artifact.

Functionally, the view presents a filtered, presentation-ready list of lookup values belonging to the BOUNDARY_TYPE lookup type. Rather than exposing the full GL_LOOKUPS maintenance table, it publishes a narrow, denormalized projection consisting of the boundary code and its display meaning. This is consistent with the role of many GL "lookup" views: they serve as stable, read-only sources for forms, concurrent programs, report templates, and integration extracts that need a constrained, human-readable enumeration instead of raw lookup rows. Because the object is a VIEW, it stores no data of its own and inherits the security, indexing, and performance characteristics of its base object.

Underlying Base Objects

The documented view text defines GL_LOOKUPS_BOUNDARIES_V over a single referenced base object: GL_LOOKUPS. In the EBS 12.1.1 / 12.2.2 data dictionary, GL_LOOKUPS is itself exposed as a VIEW in the APPS schema that resolves to the underlying FND_LOOKUP_VALUES / FND_LOOKUPS lookup infrastructure. The view is therefore a two-level projection: it selects from GL_LOOKUPS and further filters on LOOKUP_TYPE = 'BOUNDARY_TYPE'.

No joins, aggregations, or external tables are present in the documented definition. The relationship to the base object is strictly a filtered one-to-one projection with column renaming; for every qualifying row in GL_LOOKUPS where the lookup type equals 'BOUNDARY_TYPE', exactly one row appears in GL_LOOKUPS_BOUNDARIES_V. Referential and validation behavior, including enabled/disabled lookup states, effective dates, and language-specific meanings, is inherited from the standard lookup framework underlying GL_LOOKUPS.

Key Columns

  • BOUNDARY_CODE — Sourced from GL_LOOKUPS.LOOKUP_CODE. This is the internal code identifying each boundary value within the BOUNDARY_TYPE lookup type. It is the column most frequently referenced in queries and is the anchor for any search on "boundary_code."
  • SHOW_BOUNDARY — Sourced from GL_LOOKUPS.MEANING. This is the user-facing, translatable description associated with the boundary code and is the value typically displayed in forms, reports, and user interfaces.

The view intentionally withholds other GL_LOOKUPS attributes, such as description, tag, start/end dates, and enabled flag. Consumers requiring those attributes must query GL_LOOKUPS directly or use the underlying FND lookup views.

Common Use Cases and Queries

The principal use case is to populate a boundary selection list or validate a supplied boundary value against the codes defined for the BOUNDARY_TYPE lookup. A representative query retrieving all available boundaries is:

SELECT boundary_code, show_boundary FROM apps.gl_lookups_boundaries_v ORDER BY boundary_code;

To resolve a single code to its display meaning, for example when joining boundary data to a transaction or report extract:

SELECT show_boundary FROM apps.gl_lookups_boundaries_v WHERE boundary_code = :p_boundary_code;

Because the view exposes only enabled-agnostic lookup rows from GL_LOOKUPS, callers in a 12.1.1 or 12.2.2 environment should confirm whether disabled or date-expired lookup values are returned by the base lookup view before relying on the result set for validation logic. Given the "10SC ONLY" designation, use of this view outside its originating implementation context should be reviewed against the corresponding functional specification.