Results for “budget_status_code”

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

Overview

The AST_OPPORTUNITIES_BALI_V view is a denormalized reporting object owned by the APPS schema within the Oracle E-Business Suite TeleSales (AST) module. Its purpose is to consolidate opportunity, lead, sales-stage, and offer information into a single queryable structure suitable for operational reporting, list-of-values presentation, and integration interfaces. The view joins the core opportunity table AS_LEADS_ALL against lookup, source-code, sales-stage, status, and offer tables to resolve internal identifiers into their business-friendly meanings.

The object is marked as VALID across both EBS 12.1.1 and 12.2.2. A user searching for min_win_probability will find this view particularly relevant because it exposes both MIN_WIN_PROBABILITY and MAX_WIN_PROBABILITY columns sourced from the sales-stage definition, alongside the opportunity-level WIN_PROBABILITY. This enables direct comparison between an individual opportunity's probability and the thresholds configured for its sales stage.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms or views:

• AS_LEADS_ALL — the primary table (aliased OPP), supplying opportunity and lead attributes. This is the driving table for the join.
• AMS_SOURCE_CODES — provides the campaign/source promotion code (alias AMSS), joined via SOURCE_PROMOTION_ID.
• OE_LOOKUPS — a view resolving the sales channel lookup meaning (alias ASOCHANNELS) for LOOKUP_TYPE = 'SALES_CHANNEL'.
• AS_SALES_STAGES_ALL_B — the base sales-stage definition (alias STGB), providing MIN_WIN_PROBABILITY and MAX_WIN_PROBABILITY.
• AS_SALES_STAGES_ALL_TL — the translated sales-stage name (alias STGTL), language-filtered.
• AS_STATUSES_TL — the translated status meaning (alias ASSTATUSES), joined on status code and language.
• AMS_ACT_OFFERS — the offer/activity table (alias OFR), providing OFFER_CODE.

Most joins to the ancillary tables are outer joins, so opportunities are retained even when a corresponding lookup, stage, or offer record does not exist.

Key Columns

• LEAD_ID, LEAD_NUMBER — the opportunity/lead identifier and its displayed number.
• STATUS_CODE / STATUS — the internal status code and its translated meaning.
• SALES_STAGE_ID / SALES_STAGE — the stage identifier and translated name.
• MIN_WIN_PROBABILITY, MAX_WIN_PROBABILITY — the probability bounds defined for the opportunity's sales stage.
• WIN_PROBABILITY — the opportunity's own closing probability.
• TOTAL_AMOUNT, CURRENCY_CODE, CUSTOMER_BUDGET — revenue and budget figures.
• CAMPAIGN_CODE, CHANNEL, OFFER_CODE — source, channel, and offer attribution.
• DECISION_DATE, DECISION_TIMEFRAME_CODE, BUDGET_STATUS_CODE — decision context.
• PARENT_PROJECT, CUSTOMER_ID, CREATION_DATE, DESCRIPTION — ownership and descriptive attributes.

Common Use Cases and Queries

A frequent requirement is identifying opportunities whose win probability falls below the configured minimum for their stage. The following query returns such records with resolved names:

SELECT lead_number,
       sales_stage,
       win_probability,
       min_win_probability,
       max_win_probability
FROM   apps.ast_opportunities_bali_v
WHERE  win_probability < min_win_probability;

Reporting by campaign and channel is equally common:

SELECT campaign_code,
       channel,
       status,
       SUM(total_amount) AS pipeline_value
FROM   apps.ast_opportunities_bali_v
GROUP  BY campaign_code, channel, status;

Because the view resolves translated stage, status, and channel meanings, it is well suited to list-of-values, dashboard, and BI Publisher data sources where readable labels are required without further joins.