Results for “ast_lookups”

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

Overview

AST_LOOKUPS is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It is registered as a valid object within the AST (TeleSales) product family and appears in the ETRM object inventory for both release 12.1.1 and 12.2.2. The view exposes a filtered projection of Oracle Application Object Library lookup values, restricted to the lookup data associated with the TeleSales application. Its purpose is to give TeleSales forms, reports, and concurrent programs a stable, application-scoped interface to lookup codes without requiring each consumer to embed the application identifier and language predicates directly in its own SQL.

Because it is a view rather than a table, AST_LOOKUPS stores no data of its own. Every query against it is resolved at runtime against the underlying lookup repository, filtered by the current session language. This design means that changes made to lookup values through the standard Lookup Codes form are immediately visible to consumers of the view, with no synchronization or materialization step required. The view is therefore best understood as a presentation and filtering layer over the shared reference-data infrastructure rather than as an independent data source.

Underlying Base Objects

According to the documented view text, AST_LOOKUPS is defined over a single base object: FND_LOOKUP_VALUES, accessed through the synonym FNDLKPV. The view applies two mandatory predicates in addition to the language filter. First, VIEW_APPLICATION_ID must equal 521, which is the application identifier assigned to TeleSales. Second, SECURITY_GROUP_ID must equal 0, which selects the standard shared security group and excludes rows belonging to alternate or restricted groupings. A third predicate binds LANGUAGE to USERENV('LANG'), the language of the active session, so that the MEANING and DESCRIPTION returned are the translations appropriate to the current user environment. The columns exposed by the view map one-to-one to columns on FND_LOOKUP_VALUES, including the fifteen descriptive flexfield attribute columns ATTRIBUTE1 through ATTRIBUTE15 and the ATTRIBUTE_CATEGORY discriminator.

Key Columns

• LOOKUP_TYPE — Identifies the lookup category (for example, a TeleSales-specific lookup such as a call outcome or lead status code set). Together with LOOKUP_CODE it forms the logical key of the row.
• LOOKUP_CODE — The internal code value stored on transactional records and referenced by application logic.
• MEANING — The translated, user-facing label displayed on forms and reports; language-dependent.
• DESCRIPTION — Optional longer text explaining the code, also translated.
• ENABLED_FLAG — Indicates whether the value is currently active for selection; typically Y or N.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range of the lookup value, used to prevent retired codes from being chosen.
• TAG — A free-form marker occasionally used by the owning application for additional classification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments that allow the application to store additional structures or attributes against a lookup value.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard who-column auditability.

Common Use Cases and Queries

Typical usage includes validating codes captured for TeleSales entities, driving LOVs in custom forms or OAF pages, and reporting on lead and opportunity outcomes using the translated MEANING rather than the raw code. The view is also useful when extracting configuration for data migration, since it mirrors the exact lookup set the application itself consumes.

A basic query listing active values for a given lookup type follows:

SELECT lookup_code, meaning, description
FROM apps.ast_lookups
WHERE lookup_type = 'MY_LOOKUP_TYPE'
AND enabled_flag = 'Y'
ORDER BY lookup_code;

To restrict results to values effective on a specific date, additional predicates on START_DATE_ACTIVE and END_DATE_ACTIVE can be applied. Because the underlying FND_LOOKUP_VALUES table is shared across the entire instance, consumers should never update it through this view; lookup maintenance should be performed through the standard Application Developer responsibility so that the language and application filters remain consistent with what AST_LOOKUPS exposes.