Results for “as_statuses_b”

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

Overview

AS_STATUSES_B is a foundational reference table in the Oracle E-Business Suite Sales Foundation (AS) module, owned by the OSM schema. It defines the master repository of statuses used across the three primary sales objects managed by the AS product family: opportunities, leads, and quotes. Because a single status code can apply to more than one of these functional areas, the table centralizes status definitions rather than duplicating them per entity.

The table appears in both Oracle EBS 12.1.1 and 12.2.2. In the 12.2.2 documented physical schema it carries 34 columns, anchored by a primary key constraint AS_STATUSES_B_PK on STATUS_CODE. A unique index, AS_STATUSES_B_U1, spans STATUS_CODE together with ZD_EDITION_NAME, which reflects the editioning mechanism used in the later release. Under a heuristic Data Vault classification derived from its foreign-key structure, AS_STATUSES_B is hub-leaning — a reasonable modeling suggestion is to treat it as a hub keyed on STATUS_CODE, with descriptive attributes carried in satellite structures such as AS_STATUSES_TL for translated text.

Key Information Stored

The most operationally significant columns include:

• STATUS_CODE — the business identifier and primary key value for each status record.
• ENABLED_FLAG — controls whether the status is active and selectable.
• LEAD_FLAG and OPP_FLAG — indicate whether the status is valid for leads, opportunities, or both.
• OPP_OPEN_STATUS_FLAG — marks the status as representing an open opportunity.
• OPP_DECISION_DATE_FLAG — signals that the status requires or implies a decision date.
• STATUS_RANK — an ordinal value used to order statuses in lists and reports.
• FORECAST_ROLLUP_FLAG — determines whether the status contributes to forecast rollups.
• WIN_LOSS_INDICATOR — distinguishes won from lost outcomes, critical for pipeline analytics.
• USAGE_INDICATOR — further classifies how the status is intended to be consumed.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS enforcing row-level data security.
• OBJECT_VERSION_NUMBER — supports optimistic locking under the Oracle Applications Framework.
• ZD_EDITION_NAME — the edition identifier used in Edition-Based Redefinition (EBR) environments.

The surrogate primary key is STATUS_CODE on its own for the base constraint, while the unique index AS_STATUSES_B_U1 treats STATUS_CODE plus ZD_EDITION_NAME as the business-key candidate in the editioned schema. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and fifteen generic ATTRIBUTE columns are also present.

Common Use Cases and Queries

AS_STATUSES_B is consulted whenever the application or a report needs to translate a stored status code into meaningful descriptive behavior — for example, determining whether a lead is still active or whether an opportunity is won or lost.

A typical lookup joins the transactional table to the status definition:

• SELECT l.lead_id, l.status, s.status_code, s.win_loss_indicator
FROM as_sales_leads l, as_statuses_b s
WHERE l.status_code = s.status_code;

Reporting scenarios commonly filter on ENABLED_FLAG = 'Y' and WIN_LOSS_INDICATOR to build pipeline or conversion funnels. Forecast reporting frequently relies on FORECAST_ROLLUP_FLAG, while opportunity stage reporting uses OPP_OPEN_STATUS_FLAG and STATUS_RANK to order stages. Because translated names reside in AS_STATUSES_TL, multilingual reports should join through STATUS_CODE to that table.

Related Objects

AS_STATUSES_B is referenced by several transactional and configuration tables via its STATUS_CODE primary key:

• AS_LEADS_ALL — joins on AS_LEADS_ALL.STATUS = AS_STATUSES_B.STATUS_CODE.
• AS_OPP_WORKSHEET_LINES — joins on AS_OPP_WORKSHEET_LINES.STATUS = AS_STATUSES_B.STATUS_CODE.
• AS_SALES_LEADS — joins on AS_SALES_LEADS.STATUS_CODE = AS_STATUSES_B.STATUS_CODE.
• AS_SALES_CREDITS_DENORM — joins on AS_SALES_CREDITS_DENORM.STATUS_CODE = AS_STATUSES_B.STATUS_CODE.
• AS_STATUSES_TL — the translated-language table, joining on AS_STATUSES_TL.STATUS_CODE.
• PV_ALLOWED_STATUSES — defines permitted transitions, joining on both TO_STATUS_CODE and FROM_STATUS_CODE to AS_STATUSES_B.
• FND_SECURITY_GROUPS — the referenced parent for SECURITY_GROUP_ID.

Collectively, these relationships position AS_STATUSES_B as the central status hub for the AS sales domain, governing lead, opportunity, and quote lifecycle semantics across the module.