Results for “stage_sequence”

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

Overview

AS_SALES_METH_STAGE_MAP is a table owned by the OSM schema within the AS - Sales Foundation product of Oracle E-Business Suite. Its documented purpose is to map sales stages to task template groups, forming the configuration backbone that determines which task templates are instantiated as a sales opportunity advances through the stages of a given sales methodology. In practice, the table binds three independent configuration concepts — a sales methodology, a sales stage, and a task template group — into a single associative record, and optionally qualifies that record with win-probability banding.

The ETRM metadata classifies this object heuristically as a link table in Data Vault terms. This is a modeling suggestion rather than a mandatory construct: the table's identity is defined by the composite of two foreign keys rather than by a single surrogate business attribute, which is the classic signature of a link resolving a many-to-many relationship. As with all such mappings, the rows are configuration data rather than transactional data, and the table is typically small relative to transactional sales objects.

Key Information Stored

The primary key is defined by the index AS_SALES_METH_STAGE_MAP_PK over SALES_STAGE_ID and SALES_METHODOLOGY_ID. A second unique index, AS_SALES_METH_STAGE_MAP_U1, covers SALES_METHODOLOGY_ID, SALES_STAGE_ID, and ZD_EDITION_NAME; this is the business-key candidate and confirms that the combination of methodology and stage is intended to be unique within an edition. The presence of ZD_EDITION_NAME reflects the editioning mechanism used in the 12.2.x data model.

The most consequential columns are as follows. SALES_METHODOLOGY_ID identifies the sales methodology to which the mapping belongs, while SALES_STAGE_ID identifies the stage within that methodology. Together they form the composite key. TASK_TEMPLATE_GROUP_ID references JTF_TASK_TEMP_GROUPS_B and designates the group of task templates to be applied at that stage. STAGE_SEQUENCE establishes the ordinal position of the stage within the methodology, which governs progression order. MIN_WIN_PROBABILITY and MAX_WIN_PROBABILITY define the win-probability band associated with the stage and reference AS_FORECAST_PROB_ALL_B; these are frequently used in forecast roll-ups.

Supporting columns follow standard EBS conventions: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for audit tracking; OBJECT_VERSION_NUMBER for optimistic locking; and SECURITY_GROUP_ID for multi-tenant data partitioning against FND_SECURITY_GROUPS. A TEMPLATE_ID column provides an additional template reference. The documented physical schema contains fifteen columns in total.

Common Use Cases and Queries

The principal use case is configuration validation: confirming that every stage in a methodology has exactly one task template group assigned, and that no stage is orphaned. A typical diagnostic query joins the mapping to the stage and methodology base tables to expose gaps.

• Retrieve the mapping for a given methodology, ordered by stage sequence, to visualize progression and template assignment.
• Detect duplicate or missing stage mappings by grouping on SALES_METHODOLOGY_ID and SALES_STAGE_ID.
• Report win-probability bands per stage to validate forecast weighting assumptions used in pipeline reporting.
• Trace TASK_TEMPLATE_GROUP_ID back to JTF_TASK_TEMP_GROUPS_B to audit which task templates fire at each stage.

A representative pattern selects SALES_METHODOLOGY_ID, SALES_STAGE_ID, TASK_TEMPLATE_GROUP_ID, STAGE_SEQUENCE, MIN_WIN_PROBABILITY, and MAX_WIN_PROBABILITY from AS_SALES_METH_STAGE_MAP, filtered by methodology and ordered by STAGE_SEQUENCE. Because the table is editioned, queries against the 12.2.x data model should account for ZD_EDITION_NAME or use the editioning view.

Related Objects

The table participates in five documented foreign key relationships, each anchoring a different dimension of the configuration:

• AS_SALES_STAGES_ALL_B via SALES_STAGE_ID — supplies the stage definition and its descriptive attributes.
• AS_SALES_METHODOLOGY_B via SALES_METHODOLOGY_ID — supplies the methodology header.
• JTF_TASK_TEMP_GROUPS_B via TASK_TEMPLATE_GROUP_ID — the task template group applied at the stage.
• AS_FORECAST_PROB_ALL_B via MIN_WIN_PROBABILITY and MAX_WIN_PROBABILITY — the forecast probability bands bounding the stage.
• FND_SECURITY_GROUPS via SECURITY_GROUP_ID — enforces data security partitioning.

Joins to AS_SALES_STAGES_ALL_B and AS_SALES_METHODOLOGY_B are the most frequently executed, since together they reconstruct the full methodology-to-stage hierarchy that the mapping qualifies.