Search Results forecast_customer_id




Overview
Explore in AI Chat

Overview

The OZF_FORECAST_CUSTOMERS table is a core data object within the Oracle Trade Management (OZF) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. Its primary function is to define and maintain the set of customers eligible for a specific forecast version. In the context of Trade Management, a forecast is a critical planning tool used to predict and manage promotional spending, product demand, and related financial commitments. By storing the eligible customer list, this table directly links forecast models to the specific trading partners (customers) for whom the forecast is being generated, enabling targeted and accurate trade planning and analysis.

Key Information Stored

The table's structure is centered on linking forecast versions to customer entities. While the full column list is not detailed in the provided metadata, the documented keys reveal its essential data relationships. The primary key column, FORECAST_CUSTOMER_ID, uniquely identifies each record. A critical foreign key column is OBJ_ID, which links to related transactional objects. This OBJ_ID column establishes relationships with two key tables: OZF_OFFERS, which manages trade promotions and deals, and OZF_WORKSHEET_HEADERS_B, which stores header information for planning worksheets. This design indicates that a customer eligibility record can be associated with either a specific offer or a planning worksheet, centralizing customer definitions for different forecast contexts.

Common Use Cases and Queries

This table is primarily accessed during forecast creation, validation, and reporting processes. Common operational and analytical use cases include validating customer eligibility before generating a forecast report, listing all customers assigned to a specific forecast version for review, and analyzing forecast coverage across a customer hierarchy. A typical query pattern would join this table to customer master data (such as HZ_PARTIES) via the customer identifier and filter by a forecast version identifier. For example, to retrieve all eligible customers for a specific forecast linked to an offer, one might use a SQL pattern joining OZF_FORECAST_CUSTOMERS to OZF_OFFERS on OBJ_ID and then to the customer tables.

Related Objects

As indicated by its foreign key constraints, OZF_FORECAST_CUSTOMERS has direct dependencies and relationships with several other OZF tables. The primary related objects are:

  • OZF_OFFERS: The table stores trade promotion offers. The foreign key relationship suggests a forecast customer list can be specifically tied to an offer's forecast.
  • OZF_WORKSHEET_HEADERS_B: This table holds header information for planning worksheets. The relationship indicates forecast customer eligibility can also be defined at the worksheet level for planning purposes.
  • Customer Master Tables (e.g., HZ_PARTIES): While not explicitly listed in the metadata, this table will invariably join to the Trading Community Architecture (TCA) customer tables to resolve the actual customer name and attributes.
These relationships position OZF_FORECAST_CUSTOMERS as a pivotal junction table connecting forecast definitions, transactional objects, and the customer master.