Search Results boundary_type




Overview
Explore in AI Chat

Overview

APPS.GL_LOOKUPS_BOUNDARIES_V is a lightweight reporting view in the Oracle E-Business Suite General Ledger module. It presents a filtered, two-column projection of general ledger lookup values, restricted to a single lookup type: BOUNDARY_TYPE. In Oracle EBS 12.1.1 and 12.2.2, the view functions as a curated access layer over the underlying lookup repository, exposing only the boundary-related lookup codes and their displayed meanings. This makes the view suitable for concurrent programs, BI Publisher data models, forms-based validation lists, and integration interfaces that must resolve boundary definitions without navigating the broader GL_LOOKUPS structure. Because it derives its content from the standard lookup framework, the view automatically reflects any additions, renamings, or end-dating performed on BOUNDARY_TYPE lookup values through the application's lookup maintenance screens.

Underlying Base Objects

The documented base object for this view is GL_LOOKUPS, itself a view in the APPS schema. GL_LOOKUPS provides the lookup_code, meaning, description, and related attributes for general ledger lookup types such as BOUNDARY_TYPE, and supports the designation of enabled versus disabled lookup values. The view definition applies a simple filter:

  • gl_lookups l — source object supplying lookup_code and meaning.
  • WHERE l.lookup_type = 'BOUNDARY_TYPE' — restricts the result set to boundary-type lookups.

No joins to additional tables are documented. The view is therefore a single-source projection with a predicate, giving it low overhead and predictable performance.

Key Columns

  • BOUNDARY_CODE — sourced from GL_LOOKUPS.LOOKUP_CODE. The stored code value identifying a boundary definition.
  • SHOW_BOUNDARY — sourced from GL_LOOKUPS.MEANING. The user-facing description of the boundary, suitable for display in reports and lists of values.

Common Use Cases and Queries

Typical scenarios include populating a parameter list of valid boundary codes, resolving a stored boundary code to its display meaning in a report, and validating boundary values during data conversion or inbound interface processing.

List all boundaries with their display meanings:

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

Resolve a specific boundary code:

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

Drive a value set or LOV query for a concurrent program parameter:

SELECT show_boundary "Boundary",
       boundary_code "Code"
FROM   apps.gl_lookups_boundaries_v;

Because the view filters on the BOUNDARY_TYPE lookup type, queries remain stable even as other lookup types are maintained. The view does not expose description, tag, or enabled-flag columns, so consumers requiring those attributes must query GL_LOOKUPS directly with the same lookup type predicate.