Search Results create_forecast

Overview

OZF_FORECAST_UTIL_PVT_W is a private PL/SQL utility package owned by APPS in the Oracle EBS Trade Management (formerly Oracle Advanced Pricing / Oracle Trade Management) schema. It belongs to the OZF module, which houses the forecasting and trade promotion infrastructure used by the Trade Management application. In Oracle EBS 12.1.1 and 12.2.2 the package provides the low-level engine that builds and evaluates forecasts for trade promotion objects such as promotions, offers, and campaigns.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer. It functions as a private worker package ("_PVT_W" suffix), meaning it is not intended as a supported public API, but is instead called by the public API layer, by concurrent programs, and by the Trade Management forms. Its central purpose is to transform base sales history and lift factors into forecast quantities across configurable time periods and dimensional breakdowns.

Key Procedures and Functions

The package exposes three documented program units. Parameter lists are as declared in the package specification and are not reproduced here; the descriptions below reflect the documented signatures only.

• GET_BEST_FIT_LIFT — A function that returns a NUMBER. It determines the best-fit lift value for a given object, forecast, and market combination. Inputs cover the object type and identifier, the forecast identifier, the base quantity reference, market type and market identifier, product attribute context, attribute, and value, the product identifier, the trade promotion (TPR) percent, and a report date. The returned number represents the selected lift factor used in downstream forecast calculations.
• CREATE_FORECAST — A procedure that creates a forecast record. It accepts the object type and identifier, forecast unit of measure, start and end dates, base quantity type and reference, a last scenario identifier, and an offer code. It returns, through OUT and IN OUT parameters, the generated forecast identifier, an activity metric identifier, and the standard return status, message count, and message data diagnostic trio. This is the primary entry point that the search term "create_forecast" targets.
• CREATE_BASE_SALES — A procedure that creates the base sales rows underlying a forecast. It accepts the object type and identifier, forecast and activity metric identifiers, level and dimension, forecast UOM, start and end dates, period level, base quantity type and reference, a last forecast identifier, base quantity start and end dates, and an offer code. It returns two generic OUT values (p19_a0 and p19_a1) plus the return status, message count, and message data parameters.

Tables Accessed

The ETRM metadata does not enumerate the tables referenced by this package through APPS synonyms. Based on the package's role in the OZF schema, it operates against the Trade Management forecast and base sales tables, including the forecast header, forecast line, activity metric, and base sales storage used by the OZF forecasting model. The absence of a documented table list means table-level lineage should be confirmed by inspecting the package body in the target environment.

Usage Notes

Because OZF_FORECAST_UTIL_PVT_W is a private worker package, it is invoked indirectly. Typical call paths include the public OZF forecasting APIs, Trade Management concurrent programs that generate or refresh forecasts, and the Trade Management HTML and Forms user interfaces when a user defines or recalculates a promotion forecast. The metadata records zero packages referencing it, so callers are expected to be application code rather than other PL/SQL packages.

When invoking CREATE_FORECAST or CREATE_BASE_SALES from custom code, callers should pass a valid API version, respect the p_init_msg_list and p_commit conventions, and always inspect x_return_status together with x_msg_count and x_msg_data to handle errors. Direct calls should be treated as unsupported and re-validated after any Oracle EBS upgrade, since private packages may change without notice.