Search Results pjm_projects

Overview

APPS.EAM_FORECAST_PVT is a private PL/SQL package body in Oracle E-Business Suite that provides the backend engine for Enterprise Asset Management (EAM) forecasting. It supports the Maintenance and Budgeting functionality by extracting, converting, copying, and deleting forecast data related to work orders, resource requirements, and historical costs. The package operates on forecast records associated with maintenance activities and prepares them for budgetary analysis. Its header comment identifies it as part of the "Maintenance and Budgeting project," with the stated purpose of supporting Oracle Applications Release 12.

The package is classified as PVT (private), meaning it is not intended as a public API; it is called internally by other EAM components and concurrent processes rather than by external integrations. It carries a package-level constant G_PKG_NAME and integrates with FND_LOG for runtime logging, reflecting standard Oracle Application Framework diagnostic conventions.

Key Procedures and Functions

The package exposes 36 documented procedures and functions. The principal documented procedures fall into several functional groups:

• Extraction: EXTRACT_FORECAST, EXTRACT_HISTORICAL_FORECAST, EXTRACT_AUTONOMOUS_FORECAST, and EXTRACT_FUTURE_FORECAST retrieve forecast data by category (historical, autonomous, future).
• Generation and Conversion: GENERATE_FORECAST and CONVERT_WORK_ORDERS build forecast records from work order data.
• Historical Costs: GET_HISTORICALCOSTS (declared as Get_HistoricalCosts) determines the historical cost and account information of a work order and returns it to the calling program, which inserts values into EAM_FORECAST_CEBBA. Its signature includes p_api_version, p_commit, p_validation_level, p_forecast_id, p_organization_id, p_wip_entity_id, account range parameters, and standard who-columns (user, request, program, login), returning x_hist_cost_tbl and x_return_status.
• Copy Operations: 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 transfer data between staging and forecast tables.
• Insert Operations: INSERT_INTO_CEBBA_AUTO, INSERT_INTO_WDJ_AUTO, INSERT_INTO_WOP_AUTO, and INSERT_INTO_WOR_AUTO populate the corresponding forecast staging tables.
• Deletion: DELETE_FORECAST_DATA, DELETE_WORK_ORDER, and DELETE_FORECAST remove forecast-related records.

Tables Accessed

The package reads and writes a set of EAM forecast tables and supporting reference tables via APPS synonyms:

• EAM_FORECASTS and EAM_FORECASTED_WORK_ORDERS: core forecast header and work order records.
• EAM_FORECAST_CEBBA, EAM_FORECAST_WDJ, EAM_FORECAST_WEDI, EAM_FORECAST_WO, EAM_FORECAST_WOR, EAM_FORECAST_WRO: staging tables for costs by accounting, work order detail/journal, work order, resource, and requirements data.
• CST_EAM_BALANCE_BY_ACCOUNTS: source of EAM cost balances used in historical costing.
• BOM_RESOURCES: resource definitions associated with work orders.
• CSI_ITEM_INSTANCES: asset instance data tied to maintenance work.
• EAM_WO_STATUSES_V: status lookup for work orders.
• FND_LOOKUP_VALUES: reference lookup values.
• GL_CODE_COMBINATIONS and GL_PERIODS: accounting flexfield and period validation for cost records.

Usage Notes

EAM_FORECAST_PVT is invoked internally by the Maintenance and Budgeting engine rather than directly by end users. It is referenced by zero other packages in the documented metadata, indicating it sits at a leaf of the call hierarchy, typically invoked from concurrent programs and EAM forms that manage forecasting and budgeting. Its procedures accept standard FND_API parameters such as p_api_version, p_commit, p_init_msg_list, and p_validation_level, and use x_return_status for error propagation, consistent with Oracle's API design standards. Custom code should not call this private package directly; integrations should use the corresponding public APIs. The package is relevant to searches for "pjm_projects" because EAM maintenance forecasting integrates with project and budgeting constructs, though the package itself operates on EAM rather than PJM tables.