Search Results delete_fi_hdr

Overview

PA_FORECASTITEM_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and defined with AUTHID CURRENT_USER. It encapsulates the core business logic for creating, maintaining, and removing forecast items and forecast item details associated with project assignments, resources, and persons. Within Oracle EBS 12.1.1 and 12.2.2, this package functions as an internal engine that underpins the forecast generation and adjustment features exposed through the Project Management and forecasting user interfaces. Because it is classified as a private API, it is not intended as a public integration point; instead it is called by sibling packages and by the forecast-related forms and concurrent programs that rely on it. The package groups the atomic operations needed to build forecast headers and details, reverse existing forecast records, and validate or fetch assignment and project context data. The search term "delete_fi_hdr" corresponds to the documented procedure DELETE_FI_HDR, which is the routine responsible for removing a forecast item header and its dependent detail records.

Key Procedures and Functions

The package exposes 43 documented procedures and functions. The principal groups are as follows.

• CREATE_FORECAST_ITEM — Overloaded creation routine that generates forecast items from an assignment, a resource, a person, or a pre-populated error header table. It is the primary entry point for building forecast records.
• DELETE_FORECAST_ITEM — Removes forecast items for a given assignment, resource, and date range.
• DELETE_FI, DELETE_FI_HDR, DELETE_FI_DTL — Layered deletion routines. DELETE_FI_HDR is the header-level deletion procedure sought by the user; it removes the forecast item header record together with its associated detail rows, while DELETE_FI_DTL targets details and DELETE_FI serves as the umbrella delete operation.
• REVERSE_FI_HDR, REVERSE_FI_DTL — Reverse previously generated forecast header and detail records, typically when forecast inputs change.
• FETCH_FI_HDR, FETCH_FI_DTL — Retrieve existing forecast header and detail data for downstream processing.
• BUILD_FI_HDR_REQ, BUILD_FI_DTL_REQ, BUILD_FI_HDR_ASG, BUILD_FI_DTL_ASG — Construct forecast headers and details from resource requirements or from assignment data.
• GENERATE_REQUIREMENT_FI, GENERATE_ASSIGNMENT_FI — High-level generators that produce forecast items driven by requirement or assignment context.
• INITIALIZE_DAY_FI, BUILD_DAY_FI — Day-level initialization and construction of forecast items, supporting time-phased forecasting.
• GET_ASSIGNMENT_DTLS, GET_PROJECT_DTLS — Retrieval helpers that return assignment and project context used during forecast construction.
• PRINT_MESSAGE — Diagnostic utility for emitting messages during processing.

Tables Accessed

The package reads and writes the following tables through APPS synonyms.

• PA_FORECAST_ITEMS, PA_FORECAST_ITEMS_S — Base and secondary forecast item tables holding header-level forecast records.
• PA_FORECAST_ITEM_DETAILS — Detail rows linked to forecast item headers.
• PA_PROJECTS_ALL — Project definitions supplying context for forecast generation.
• PA_PROJECT_ASSIGNMENTS — Assignment records that drive forecast creation and deletion.
• PA_PROJECT_TYPES_ALL — Project type attributes influencing forecast behavior.
• PA_RESOURCES_DENORM — Denormalized resource information for resource-based forecasting.
• PA_SCHEDULES — Calendar and scheduling data used for time-phased builds.
• DUAL, PLITBLM — Utility references, including the PL/SQL table used for message handling.

Usage Notes

As a PVT-classified package, PA_FORECASTITEM_PVT is invoked indirectly. It is referenced by eight other packages, which call its create, delete, reverse, and generate routines when forecast data must be maintained. The DELETE_FI_HDR procedure is typically reached from higher-level forecast maintenance logic—such as forms that let users remove a forecast item, or concurrent programs that regenerate forecasts and must clear prior headers before rebuilding. Because the procedures use OUT NOCOPY parameters for return status, message count, and message data (a pattern introduced under Bug 4537865), callers are expected to check the return status and retrieve messages through the standard message stack. Custom code should not call this package directly as a supported interface; instead, public forecast APIs or the delivered forecast forms and concurrent programs should be used. Any direct invocation must account for the package's dependence on valid assignment, resource, and date parameters and on the underlying forecast tables being in a consistent state.