Search Results forecast_customer_id

Overview

The AMS_FORECAST_CUSTOMERS table is a core data repository within the Oracle E-Business Suite (EBS) Marketing (AMS) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to manage and store the list of customer accounts deemed eligible for inclusion in a specific forecast version. A forecast version is a critical planning construct in AMS, used to project sales, revenue, or other key performance indicators. This table acts as the definitive source for which customers are considered in-scope for a given forecast, thereby linking the master customer list to the forecasting engine. Its integrity is essential for accurate forecast generation, territory planning, and quota management processes.

Key Information Stored

Based on the provided metadata, the table's structure is anchored by the primary key column, FORECAST_CUSTOMER_ID. This unique identifier is a system-generated sequence number (likely from a sequence like AMS_FORECAST_CUSTOMERS_S) that serves as the primary key for each record in this table. While the full column list is not detailed in the excerpt, the table's description implies it must contain at least two critical foreign key references: one to the forecast version (likely a column like FORECAST_VERSION_ID linking to AMS_FORECAST_VERSIONS_B) and one to the customer (likely a column like CUSTOMER_ID linking to HZ_PARTIES or a related Trading Community Architecture table). Additional columns would typically store creation dates, last update dates, and the identifiers of the users who created and last updated the record, following Oracle EBS audit convention.

Common Use Cases and Queries

The primary use case is validating and reporting on the customer population for a forecast. Common operational queries include listing all eligible customers for a specific forecast version or identifying which forecast versions a particular customer is associated with. For reporting, this table is frequently joined to customer master and forecast header tables to analyze forecast coverage by customer attributes like region or industry. A typical query pattern would be:

• SELECT afc.forecast_customer_id, afc.customer_id, hp.party_name FROM ams_forecast_customers afc, hz_parties hp WHERE afc.customer_id = hp.party_id AND afc.forecast_version_id = :p_forecast_ver_id;

Data is primarily populated through the AMS forecasting user interface or via batch import processes when setting up or updating a forecast version.

Related Objects

The table maintains key relationships with other AMS and core EBS objects. The primary key, FORECAST_CUSTOMER_ID, is referenced by the constraint AMS_FORECAST_CUSTOMERS_PK. As a child table, it almost certainly has a foreign key relationship to the forecast version master table (e.g., AMS_FORECAST_VERSIONS_B) on a column like FORECAST_VERSION_ID. It also has a critical foreign key relationship to the Trading Community Architecture's customer tables, most likely HZ_PARTIES, on a column like CUSTOMER_ID. It may serve as a parent table to other forecast-related detail tables. In application logic, it is accessed by AMS forecasting APIs and public interfaces, and it underpins key forecast reports and list of values (LOVs) within the AMS module.