Search Results pv_allowed_statuses
Overview
The AS_STATUSES_B table is a core master data table within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as the central repository for defining and managing the status codes used across three primary sales entities: opportunities, leads, and quotes. As a base table, it holds the fundamental, non-translatable attributes for each status. Its primary role is to enforce data integrity and provide a standardized set of status values that drive workflow and reporting logic throughout the sales cycle. The table is owned by the OSM schema and is integral to maintaining consistent status definitions across the application.
Key Information Stored
The table's primary key is the STATUS_CODE column, which uniquely identifies each status record. While the provided metadata does not list all columns, the structure of a typical EBS base table and its relationship to the translatable table (AS_STATUSES_TL) implies that AS_STATUSES_B contains the core seeded and user-defined status codes. Key columns typically include STATUS_CODE, STATUS_TYPE (to differentiate between lead, opportunity, and quote statuses), ENABLED_FLAG, DEFAULT_FLAG, and SEEDED_FLAG. These columns control the availability, default selection, and system origin of each status. The table's design ensures that statuses are centrally managed and referenced via foreign keys from transactional tables.
Common Use Cases and Queries
This table is fundamental for reporting, data validation, and configuration. Common use cases include generating lists of active statuses for a given sales object, validating status transitions in custom logic, and configuring status values in setup screens. A typical query retrieves all enabled statuses for opportunities, often joining with the translated table (AS_STATUSES_TL) for user-friendly names in the current session language. For example:
- SELECT b.STATUS_CODE, tl.MEANING FROM AS_STATUSES_B b, AS_STATUSES_TL tl WHERE b.STATUS_CODE = tl.STATUS_CODE AND b.STATUS_TYPE = 'OPPORTUNITY' AND b.ENABLED_FLAG = 'Y' AND tl.LANGUAGE = USERENV('LANG');
Another common pattern is to query the status of a specific lead or opportunity by joining AS_STATUSES_B with transactional tables like AS_SALES_LEADS or AS_LEADS_ALL on the STATUS_CODE column.
Related Objects
AS_STATUSES_B has extensive relationships within the Sales Foundation module, as evidenced by its foreign key constraints. Key related objects include:
- AS_STATUSES_TL: The translatable table that provides language-specific names and descriptions for each STATUS_CODE.
- Transactional Tables: AS_LEADS_ALL, AS_SALES_LEADS, and AS_OPP_WORKSHEET_LINES directly reference status codes for their primary records.
- Denormalized and Supporting Tables: AS_SALES_CREDITS_DENORM and PV_ALLOWED_STATUSES reference this table. PV_ALLOWED_STATUSES uses it twice (FROM_STATUS_CODE, TO_STATUS_CODE) to define valid status transition rules.
- Primary Key: AS_STATUSES_B_PK on the STATUS_CODE column.
-
Table: AS_STATUSES_B
12.1.1
owner:OSM, object_type:TABLE, fnd_design_data:AS.AS_STATUSES_B, object_name:AS_STATUSES_B, status:VALID, product: AS - Sales Foundation , description: Hold three types of status, opportunity, lead and quote , implementation_dba_data: OSM.AS_STATUSES_B ,
-
Table: AS_STATUSES_B
12.2.2
owner:OSM, object_type:TABLE, fnd_design_data:AS.AS_STATUSES_B, object_name:AS_STATUSES_B, status:VALID, product: AS - Sales Foundation , description: Hold three types of status, opportunity, lead and quote , implementation_dba_data: OSM.AS_STATUSES_B ,