Results for “owner_salesforce_id”

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

Overview

AS_AP_TRACKING_OBJECTIVES is a transactional table in the AS (Sales Foundation) product family of Oracle E-Business Suite, residing in the OSM schema. It stores the revenue objectives defined against account plans, capturing the targets that a sales organization intends to achieve for a given account plan over a defined period. Each row associates a tracking objective with an account plan, an owning sales resource, and — optionally — a product category, category set, inventory item, and inventory organization, allowing objectives to be expressed at account level, product level, or item level.

From a Data Vault modeling perspective, the metadata's foreign-key structure (multiple parent references, no descriptive history columns required for its own grain) suggests classification as a link table. This is a heuristic suggestion only: AS_AP_TRACKING_OBJECTIVES behaves as an associative entity connecting account plans to sales resources and product definitions, while carrying its own measures such as TARGET_VALUE.

Key Information Stored

The table contains 34 documented columns. The most significant are:

• TRACKING_OBJECTIVE_ID — the surrogate primary key, enforced by AS_AP_TRACKING_OBJECTIVE_PK and also covered by the unique index AS_AP_TRACKING_OBJECTIVES_U1. This is the business-key candidate for the objective record.
• ACCOUNT_PLAN_ID — foreign key to AS_AP_ACCOUNT_PLANS, identifying the account plan to which the objective belongs.
• TRACKING_OBJECTIVE_TYPE — classifies the nature of the objective (for example, revenue, unit, or category-based target).
• START_DATE and DUE_DATE — define the objective's effective window.
• OWNER_SALESFORCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS, identifying the sales resource accountable for the objective.
• PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID — foreign keys to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B, enabling objectives scoped to a product category within a category set.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — foreign keys to MTL_SYSTEM_ITEMS_B, enabling item-level objectives that are organization-specific.
• TARGET_VALUE — the numeric objective amount the sales resource is expected to achieve.
• STATUS_CODE — the current lifecycle state of the objective.

The table also carries standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), an OBJECT_VERSION_NUMBER for optimistic locking, ATTRIBUTE_CATEGORY, and fifteen flexfield columns (ATTRIBUTE1 through ATTRIBUTE15) for customer-specific extensions.

Common Use Cases and Queries

Typical uses center on quota and pipeline reporting: comparing TARGET_VALUE against actual attainment, listing all objectives for an account plan, and identifying objectives owned by a given sales resource. A representative query joining the primary parent is:

SELECT t.tracking_objective_id, t.tracking_objective_type,
       t.start_date, t.due_date, t.target_value, t.status_code
FROM   osm.as_ap_tracking_objectives t
WHERE  t.account_plan_id = :account_plan_id
ORDER  BY t.start_date;

To resolve the responsible sales resource and any item-scoped target, join JTF_RS_RESOURCE_EXTNS on OWNER_SALESFORCE_ID and MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID. Reporting extracts frequently filter on STATUS_CODE and DUE_DATE to isolate open objectives, and aggregate TARGET_VALUE by TRACKING_OBJECTIVE_TYPE or by product category for territory roll-ups.

Related Objects

• AS_AP_ACCOUNT_PLANS — joined on AS_AP_TRACKING_OBJECTIVES.ACCOUNT_PLAN_ID; the mandatory parent account plan.
• JTF_RS_RESOURCE_EXTNS — joined on OWNER_SALESFORCE_ID; supplies the owning sales resource.
• MTL_CATEGORY_SETS_B — joined on PRODUCT_CAT_SET_ID; defines the category set used for category-level objectives.
• MTL_CATEGORIES_B — joined on PRODUCT_CATEGORY_ID; supplies the specific product category.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; supplies the item and organization for item-level objectives.

These foreign-key relationships define the principal integration surface for the table and should be observed when building queries or extracts against AS_AP_TRACKING_OBJECTIVES.