Search Results extract_forecast

Overview

APPS.EAM_FORECAST_PVT is the private implementation package for Enterprise Asset Management (EAM) forecasting in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the maintenance forecasting feature that projects future maintenance costs and work order activity by combining historical work order transactions with open and unreleased work orders, then materializing the results into a set of forecast staging and reporting tables. The package is classified as PVT (private), meaning it is not intended as a published public API; it is invoked internally by the EAM forecast generation logic and, indirectly, by concurrent programs and forms that drive that logic. The package declares strongly typed collection types over its forecast tables — including wdj_table_type, wop_table_type, wor_table_type, wro_table_type, wedi_table_type and cebba_table_type — and a record type, eam_forecast_rec_type, that mirrors the structure of EAM_FORECAST_CEBBA. These types support bulk processing of forecast rows and are central to the package's copy and insert routines. The header carries a 12.2.0-level revision marker, confirming support for the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The documented procedures cluster into four functional groups. Forecast generation and extraction routines include GENERATE_FORECAST, EXTRACT_FORECAST, EXTRACT_HISTORICAL_FORECAST, EXTRACT_AUTONOMOUS_FORECAST, EXTRACT_FUTURE_FORECAST and GET_HISTORICALCOSTS; these drive the overall forecast build, separating historical cost retrieval from forward-looking projection. Copy routines move rated or staged data into the final forecast structures and include COPY_CEBBA_TO_FORECAST_AUTO, COPY_WDJ_TO_FORECAST, COPY_WDJ_TO_FORECAST_AUTO, COPY_WOR_TO_FORECAST, COPY_WOR_TO_FORECAST_AUTO and COPY_WRO_TO_FORECAST. Bulk insert routines — INSERT_INTO_CEBBA_AUTO, INSERT_INTO_WDJ_AUTO, INSERT_INTO_WOP_AUTO and INSERT_INTO_WOR_AUTO — populate the CEBBA, work-order detail, work-order operation and work-order resource staging tables respectively. The routine named in the user's search, INSERT_INTO_WOR_AUTO, is therefore the automated bulk loader for EAM_FORECAST_WOR resource-level forecast rows. Cleanup routines include DELETE_FORECAST, DELETE_FORECAST_DATA, DELETE_WORK_ORDER and CONVERT_WORK_ORDERS, which remove or transform forecast and work order data between runs. All 36 documented entries are private helpers rather than callable public APIs.

Tables Accessed

The package reads and writes the EAM forecast table family: EAM_FORECASTS, EAM_FORECAST_CEBBA (cost element/balance-by-account detail), EAM_FORECAST_WDJ (work order distribution/journal), EAM_FORECAST_WEDI, EAM_FORECAST_WO, EAM_FORECAST_WOR and EAM_FORECAST_WRO. Supporting reads come from EAM_FORECASTED_WORK_ORDERS, EAM_WO_STATUSES_V, BOM_RESOURCES, CSI_ITEM_INSTANCES, CST_EAM_BALANCE_BY_ACCOUNTS, GL_CODE_COMBINATIONS, GL_PERIODS and FND_LOOKUP_VALUES. The GL and lookup tables supply period validation, account derivation and status decoding, while the cost and resource tables supply the rates and structure needed to value projected maintenance activity. All references resolve through APPS synonyms.

Usage Notes

Because EAM_FORECAST_PVT is a private package, it is not called directly from custom code in supported implementations. It is executed by the EAM forecast generation flow — typically a concurrent program or the forecast window in the EAM maintenance workbench — with the request context supplied by the calling program. The package executes with AUTHID CURRENT_USER, so privileges are resolved from the invoking schema. The package is referenced by zero other documented packages, reinforcing its internal role. Customizations should never call the PVT procedures directly; developers requiring forecast behavior should use the supported public forecast APIs and concurrent programs instead.