Results for “as_quota_profiles_v”

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

Overview

The AS_QUOTA_PROFILES_V view belongs to the Oracle E-Business Suite AS – Sales Foundation module, which underpins quota management and sales-force compensation reporting in releases 12.1.1 and 12.2.2. The view presents denormalized quota profile definitions, combining quota assignment attributes from the transactional quota profile table with descriptive values sourced from human resources, sales group, interest, item, and customer reference tables. Each row represents a single quota profile record: the assignment of a quota amount to a specific employee, sales group, interest type/code, or inventory item for a defined period.

The object is documented in ETRM as "Not implemented in this database," meaning it is a seeded, dictionary-defined view that may not exist in every environment depending on whether Sales Foundation quota functionality has been installed. Its role is primarily read-only reporting and integration: downstream queries, custom reports, and interfaces use it to retrieve quota data without replicating the multi-table join logic. The user's search term, revenue_flag, corresponds directly to the REVENUE_FLAG column exposed by this view.

Underlying Base Objects

The view is defined over the following documented base objects:

• AS_QUOTA_PROFILES (aliased AQP) – the primary transactional table holding quota profile rows, including the ROWID and QUOTA_PROFILE_ID.
• JTF_RS_GROUPS_TL (GRP) – resource/sales group translations, joined on SALES_GROUP_ID = GROUP_ID with LANGUAGE = USERENV('LANG') to return the group name in the session language.
• AS_INTEREST_TYPES_VL (AIT) – interest type values, outer-joined on INTEREST_TYPE_ID.
• AS_INTEREST_CODES_VL (AIC1, AIC2) – primary and secondary interest code values, outer-joined on the respective interest code IDs.
• MTL_SYSTEM_ITEMS_B_KFV (MSI) – the item key-flexfield view, outer-joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
• PER_PEOPLE_X (PER) – employee person details, outer-joined on EMPLOYEE_PERSON_ID = PERSON_ID.

All joins to descriptive tables are outer joins, ensuring a quota profile row is returned even when dependent reference data is missing. ETRM documents no additional base objects beyond those in the view text.

Key Columns

• QUOTA_PROFILE_ID / ROW_ID – primary identifier and row locator for the quota profile.
• REVENUE_FLAG – indicates whether the quota is revenue-related, the column most relevant to the searched term.
• QUOTA_AMOUNT – the monetary quota value assigned to the profile.
• PERIOD_TYPE – the period basis (for example, monthly, quarterly, annual) governing the quota.
• ACTIVE_FLAG / RECORD_STATUS – control whether the profile is active or logically deleted.
• ORGANIZATION_ID, INVENTORY_ITEM_ID – organizational and item scope of the quota.
• EMPLOYEE_PERSON_ID, EMPLOYEE_FIRST_NAME, EMPLOYEE_LAST_NAME – the assigned employee.
• SALES_GROUP_ID, SALES_GROUP_NAME – the associated sales group and its translated name.
• INTEREST_TYPE, PRIMARY_INTEREST_ITEM, SECONDARY_INTEREST_CODE_ID – classification and interest-code detail.
• CURRENCY_CODE – currency of the quota amount.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY – descriptive flexfield columns.
• Standard WHO columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used for quota administration and compensation reporting, particularly filtering by revenue-related quotas. A representative query retrieving active revenue-based quotas with employee and group context is:

SELECT quota_profile_id, employee_first_name, employee_last_name, sales_group_name, quota_amount, currency_code, period_type FROM as_quota_profiles_v WHERE revenue_flag = 'Y' AND active_flag = 'Y';

Other common patterns include aggregating quota amounts by sales group or period type, joining the view to order/invoice data for revenue-versus-quota analysis, and extracting rows for an external compensation system using CURRENCY_CODE and ATTRIBUTE columns. Because all descriptive joins are outer joins, reports must anticipate null values in EMPLOYEE_* , SALES_GROUP_NAME, and item flexfield columns.