Search Results as_statuses_vl




Overview
Explore in AI Chat

Overview

AS_STATUSES_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the AS – Sales Foundation product, the module that supplies shared foundation entities for Oracle Sales, Oracle Territory Management, and Oracle TeleSales. The view presents a translated, user-facing representation of sales status definitions, which are the configurable codes used to describe the lifecycle stage of a lead or an opportunity (for example, "New," "Qualified," "Won," or "Lost").

Functionally, AS_STATUSES_VL joins the base table that stores the non-translatable attributes of a status to the translation table that stores the language-dependent meaning and description. The "_VL" suffix denotes a "view with language," a standard Oracle Applications naming convention indicating that the view returns rows only for the session language as determined by USERENV('LANG'). This makes the view suitable for direct use in forms, concurrent programs, BI Publisher reports, and integration interfaces where the displayed status text must appear in the user's current language.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies two referenced base objects, both exposed to APPS as synonyms: AS_STATUSES_B and AS_STATUSES_TL. AS_STATUSES_B ("B" for base) holds the language-independent definition of each status, including its unique STATUS_CODE and the many behavioral flags that control how the status behaves across leads and opportunities. AS_STATUSES_TL ("TL" for translation) holds the MEANING, DESCRIPTION, and language columns for each STATUS_CODE.

The view text joins these two tables on STATUS_CODE and filters with the condition T.LANGUAGE = USERENV('LANG'). Because the join is on a single code column and the language filter returns exactly one translation row per status per session language, the view behaves like a one-to-one projection over AS_STATUSES_B for the active language. Inserts and updates are not performed directly against a "_VL" view in normal application usage; maintenance is performed on the underlying base table through the standard Sales Foundation setup forms, with the translation table populated by the MLS framework or the Translation/MLS maintenance screens.

Key Columns

  • STATUS_CODE — Primary identifier of the status; the join key between the base and translation tables.
  • MEANING — The translated display name of the status in the session language; the value most often shown to end users.
  • DESCRIPTION — The translated long description of the status.
  • ENABLED_FLAG — Indicates whether the status is active and selectable in the application.
  • LEAD_FLAG and OPP_FLAG — Indicate whether the status applies to leads, to opportunities, or to both, which is essential when validating a status against the entity being processed.
  • OPP_OPEN_STATUS_FLAG and OPP_DECISION_DATE_FLAG — Control whether an opportunity in this status is treated as open and whether it requires a decision date; these drive pipeline and forecast logic.
  • FORECAST_ROLLUP_FLAG and WIN_LOSS_INDICATOR — Govern whether amounts for the status roll into forecasts and whether the status represents a win or a loss.
  • STATUS_RANK — A numeric ordering used to sequence statuses in lists and workflow progression.
  • USAGE_INDICATOR — Classifies the usage context of the status.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle Applications descriptive flexfield (DFF) columns, available for customer-defined status attributes.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

The view is most commonly referenced during sales setup reviews, data validation, and reporting on opportunity pipelines. A typical query lists all enabled opportunity statuses in ranked order for the current language:

SELECT status_code, meaning, status_rank, win_loss_indicator
FROM   apps.as_statuses_vl
WHERE  enabled_flag = 'Y'
AND    opp_flag = 'Y'
ORDER BY status_rank;

When validating lead data, the LEAD_FLAG column is used to restrict the result set, and the WIN_LOSS_INDICATOR and FORECAST_ROLLUP_FLAG columns support forecast reconciliation reporting against opportunity statuses. Because the view resolves translations automatically, it is preferred over querying AS_STATUSES_B and AS_STATUSES_TL separately in any custom report, interface, or lookup-based validation logic that must display status text in the user's language.