Results for “forecast_customer_id”

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

Overview

AMS_FORECAST_CUSTOMERS is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the set of customers eligible for a specific version of a forecast. Each row represents an association between a forecast (identified through the QP_LIST_HEADER_ID and related qualifier attributes) and a customer account, thereby defining the audience against which forecast planning and demand shaping activities are performed. The table is owned by the AMS schema and carries a VALID status in the data dictionary.

The ETRM metadata classifies this object heuristically through its foreign key structure as a standalone data vault artifact. In Data Vault modeling terms, this suggests the table behaves less like a pure hub or satellite and more as an independent qualifying or linking structure scoped to forecast audiences — it is not dependent on a parent hub-and-satellite chain for its identity. The primary key, AMS_FORECAST_CUSTOMERS_PK, is defined on FORECAST_CUSTOMER_ID, which also appears in the unique index AMS_FORECAST_CUSTOMERS_U1.

Key Information Stored

The table contains 15 documented columns. The most significant are described below.

• FORECAST_CUSTOMER_ID — Surrogate primary key and the column most commonly referenced in user searches. It uniquely identifies each eligibility record.
• QP_LIST_HEADER_ID — Identifies the forecast or list header (from Oracle Advanced Pricing) to which the customer eligibility belongs.
• QUALIFIER_ID and QUALIFIER_GROUPING_NO — Qualifier context for the forecast audience, supporting grouping logic.
• OBJ_TYPE and OBJ_ID — Generic object type and identifier pair, allowing the row to reference different source object types flexibly.
• CUST_ACCOUNT_ID — Foreign key to HZ_CUST_ACCOUNTS, identifying the customer account eligible for the forecast.
• SITE_USE_ID and SITE_USE_CODE — Identify the specific customer site and its usage (for example, ship-to or bill-to) eligible for the forecast.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling secure access to the forecast customer record.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard who-column auditing.

The documented unique indexes are AMS_FORECAST_CUSTOMERS_U1 on FORECAST_CUSTOMER_ID, reinforcing it as the business-key candidate alongside the primary key.

Common Use Cases and Queries

Typical usage centers on determining which customers are targeted by a given forecast version and joining to customer master data for reporting. A representative query joining to the customer account is:

• SELECT afc.forecast_customer_id, afc.cust_account_id, hca.account_name FROM ams.ams_forecast_customers afc JOIN hz_cust_accounts hca ON hca.cust_account_id = afc.cust_account_id WHERE afc.qp_list_header_id = :p_list_header_id;

Additional scenarios include counting eligible customers per forecast, filtering by site use code to report ship-to level eligibility, and enforcing security group filtering in multi-org or secured reporting. Because the table is classified as standalone, queries frequently treat it as a direct audience staging table rather than traversing deep hierarchies.

Related Objects

The following objects are most significant in relation to AMS_FORECAST_CUSTOMERS, based on documented foreign key and primary key relationships:

• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID to retrieve customer identity and Trading Community Architecture details.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for secured access control.
• AMS_FORECAST_CUSTOMERS_PK — primary key constraint defining FORECAST_CUSTOMER_ID.
• AMS_FORECAST_CUSTOMERS_U1 — unique index on FORECAST_CUSTOMER_ID.
• QP_LIST_HEADER_ID dimension tables in Oracle Advanced Pricing — referenced for forecast/list header context.
• HZ_CUST_SITE_USES_ALL — referenced through SITE_USE_ID and SITE_USE_CODE for customer site usage detail.