Search Results status_code_pk




Overview

APPS.BIL_DIMV_OPTY_STATUSES is a public Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data reference BIL.BIL_DIMV_OPTY_STATUSES. Its documented status is VALID across Oracle EBS 12.1.1 and 12.2.2. The object is classified as a public view, meaning Oracle supports its use for custom reporting and other supplementary data requirements even though it is not itself an end-user application form or concurrent program.

The view exposes the set of statuses that can be assigned to a sales opportunity or sales lead. Its source schema is Oracle Sales Online (OSO), and within the broader BIL schema family it functions as a small dimension-style lookup, providing the descriptive attributes and behavioral flags that govern how each opportunity status behaves in sales processing, pipeline analysis, and forecasting. Rather than returning transactional opportunity records, the view returns the status definitions themselves, which makes it a reference source for joins, validation queries, and reporting prompts.

Underlying Base Objects

The ETRM metadata documentation for this object does not enumerate underlying base tables, and no referenced base objects are documented. Practically, the view is defined over the status setup table in the Oracle Sales Online data model and is exposed in the APPS schema so that it can be queried alongside other EBS reporting objects without requiring direct access to the OSO schema. Because dependency information is not published in the ETRM entry, the view should be treated as a supported reporting interface rather than as a target for direct DML. All columns are read-only from the perspective of the APPS consumer, and any change to the underlying setup data must be made through the corresponding Sales Online administration screens rather than through the view.

Key Columns

The view returns setup attributes for each opportunity status. The following columns are the most significant for reporting and integration:

  • STATUS_CODE_PK (VARCHAR2, 30) — Primary key and status code for the opportunity status. This is the value referenced by opportunity and lead records and the column most commonly used in joins and filters.
  • MEANING (VARCHAR2, 240) — The display name of the opportunity status.
  • DESCRIPTION (VARCHAR2, 240) — A longer description of the status.
  • ENABLED_FLAG — Indicates whether the status is currently enabled for use.
  • LEAD_FLAG and OPP_FLAG — Indicate whether the status applies to sales leads, sales opportunities, or both.
  • OPP_OPEN_STATUS_FLAG — Identifies statuses that represent an open opportunity.
  • FORECAST_ROLLUP_FLAG — Indicates whether opportunities in this status appear in the forecast; valid values are 'Y' and 'N'.
  • WIN_LOSS_INDICATOR — Identifies Won and Closed ('W'), Lost and Closed ('L'), or neither ('N'), validated against the open status flag.
  • USAGE_INDICATOR (VARCHAR2, 30) — Controls data exposure; valid values are 'OS', 'PRM', and 'ALL'.
  • OPP_DECISION_DATE_FLAG and STATUS_RANK — Documented as not used currently.
  • Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Audit information.

Common Use Cases and Queries

The view is typically used to enumerate valid statuses, to resolve status codes into descriptive names, and to segment opportunities by forecasting or win/loss behavior. A representative query lists all enabled opportunity statuses that roll up into the forecast:

  • SELECT status_code_pk, meaning, win_loss_indicator FROM apps.bil_dimv_opty_statuses WHERE enabled_flag = 'Y' AND opp_flag = 'Y' AND forecast_rollup_flag = 'Y';
  • SELECT status_code_pk, meaning FROM apps.bil_dimv_opty_statuses WHERE opp_open_status_flag = 'Y' AND usage_indicator IN ('OS','ALL');
  • Joining to opportunity fact or staging tables on status_code_pk to label pipeline reports.

Because the view is small, static, and public, it is well suited for use in reporting prompts, validation value sets, and integration extracts where a stable status reference is required.