Search Results pa_forecastitem




Overview
Explore in AI Chat

Overview

PA_PURGE_UNASGN_FI is an Oracle Applications schema package that supports the Project Costing and project forecasting purge infrastructure within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its principal business function is the removal of unassigned forecast item records — that is, forecast line entries that were generated or imported but never associated with a valid project, task, or assignment. Because forecast quantities and amounts feed project budgeting, commitment tracking, and revenue/cost forecasting, orphaned or unassigned rows can accumulate through repeated interface loads, failed imports, or rejected adjustments. The package provides the technical mechanism to identify and physically delete such records for a specified purge context, keeping the PA_FORECAST_ITEMS and its related amount-detail tables free of stale data.

Key Procedures and Functions

The documented package interface exposes four named program units:

  • PA_FORECASTITEM — Identifies and processes unassigned forecast item rows. This is the core selection routine used to determine which forecast items qualify for purge treatment.
  • DELETE_FI — Performs the delete of forecast item records and their dependent amount and detail rows. This is the destructive routine invoked once candidates have been identified.
  • ARPR_LOG — Writes diagnostic and progress information to the logging mechanism used by the purge process, enabling review of what was selected and removed.
  • ARPR_OUT — Produces output messages or status text for the calling process or concurrent program, typically supporting report or log output generation.

The naming suggests ARPR refers to the application's purge reporting/output convention. Parameter lists are not documented in the metadata and should be inspected in the package specification before direct invocation.

Tables Accessed

The package reads and writes several Project Accounting tables through APPS synonyms. Forecast records are handled in PA_FORECAST_ITEMS and PA_FORECAST_ITEM_DETAILS, with their archive counterparts PA_FRCST_ITEMS_AR and PA_FRCST_ITEM_DTLS_AR. Amount data is stored in PA_FI_AMOUNT_DETAILS and archived in PA_FI_AMOUNT_DETAILS_AR — indicating the purge may archive before deletion. Purge bookkeeping uses PA_PURGE_BATCHES_S and PA_PURGE_PRJ_DETAILS to track batch identity and purge scope. PA_IMPLEMENTATIONS is consulted for configuration and business-group context, while PA_PROJECTS_ALL provides project validation. DUAL and PLITBLM are standard infrastructure references. The package depends on PA_PLSQL_DATATYPES for shared datatype definitions.

Usage Notes

PA_PURGE_UNASGN_FI is an internal implementation package rather than a public application programming interface; ETRM classifies it as OTHER and records zero inbound references from other packages. It is therefore not intended to be called from custom code directly. In practice it is invoked from the Project Accounting purge concurrent programs or from the purge processing logic that manages forecast cleanup, using the purge batch identifier created in PA_PURGE_BATCHES_S to constrain the scope of deletion. Because the DELETE_FI routine physically removes rows and its companion routines handle logging and output, the package runs as part of a scheduled administrative purge rather than during online transaction entry. Clients should exercise caution: any direct invocation bypasses validation and audit controls normally applied by the concurrent manager, and dependency on PA_PLSQL_DATATYPES and the archive tables must be considered when applying patches or cloning. Standard practice is to run purge activity during maintenance windows after backup and reconciliation of forecast balances.