Search Results ce_forecast_opening_bal_s

Overview

CE_CSH_FCST_POP is a public PL/SQL package body in the APPS schema that supports the Cash Forecasting module of Oracle Cash Management. Its principal business role is to populate the forecast data structures used by the Cash Forecast Execution and generation engine — specifically the transaction cells, opening balances, and column definitions that drive the Cash Forecast report. The package assembles forecast cell content from a combination of open receivables, payment terms, bank account configuration, currency rates, and general ledger account assignments, then writes those results into the forecast transaction tables where the forecasting engine and report templates consume them.

The header revision string of $Revision: 120.73.12020000.3 $ indicates this is a late-maintenance release of the package body, consistent with EBS 12.1.1 and 12.2.2 deployments. The package exposes self-describing functions (BODY_REVISION and SPEC_REVISION) that report version information at runtime, which is useful for diagnostic and patching purposes.

Key Procedures and Functions

• SPEC_REVISION — Returns the package specification revision string (G_spec_revision), enabling callers to verify which version of the specification is currently compiled.
• BODY_REVISION — Returns the package body revision string, mirroring the header revision identifier for support and release verification.
• POPULATE_CELLS — The core worker routine that fills forecast cells with computed amounts for the active forecast, deriving values from the underlying source tables and column definitions.
• ZERO_FILL_CELLS — Initialises forecast cells to zero, ensuring that periods or combinations with no qualifying transactions do not inherit stale values from a prior run.
• INSERT_FCAST_CELL — Inserts an individual forecast cell row into the forecast transaction cells table; the low-level atomic write used by the population routines.
• POPULATE_OPENING_BAL — Computes and stores the opening balance for the forecast, drawing on the forecast opening balance table and related sources.
• GET_AVERAGE_PAYMENT_DAYS — Calculates the average number of days between invoice transaction date and receipt application date for a given customer, site use, currency, and historical period. It joins AR_RECEIVABLE_APPLICATIONS_ALL to AR_PAYMENT_SCHEDULES_ALL, filtering on applied status 'APP', display flag 'Y', and confirmed receipts, and returns zero when no qualifying applications exist. This value feeds downstream Build_XXX_Query logic used in cash forecast projections.

Note on the search term: min_col does not appear as a documented procedure, parameter, or package-level identifier in the ETRM metadata for CE_CSH_FCST_POP. Any reference to a minimum-column concept would be internal to the unlisted body logic rather than part of the exposed API surface.

Tables Accessed

• AR_PAYMENT_SCHEDULES_ALL and AR_RECEIVABLE_APPLICATIONS_ALL — source data for average payment days and receivables-driven forecast amounts.
• AP_TERMS_LINES — payment terms used to project due dates and cash timing.
• CE_FORECASTS, CE_FORECAST_COLUMNS, CE_FORECAST_TRX_CELLS — the forecast definition, column metadata, and output cells written by the population routines.
• CE_FORECAST_OPENING_BAL, CE_FORECAST_OPENING_BAL_S — opening balance storage and its sequence.
• CE_FORECAST_EXT_TEMP, CE_FORECAST_EXT_VIEWS, CE_CURRENCY_RATES_TEMP — staging and rate-conversion support objects.
• CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, CE_GL_ACCOUNTS_CCID — bank account and GL account derivation for cash accounts.
• FND_NEW_MESSAGES — message lookup for error and status reporting.

Usage Notes

CE_CSH_FCST_POP is invoked indirectly by the Cash Forecast generation flow rather than directly by end users. It is typically called from the Cash Forecasting concurrent program or from the Cash Management Forecast workbench when a forecast is executed or refreshed. In 12.1.1 and 12.2.2, the calling context remains the Cash Management responsibility under the forecast execution path. Because the package is classified as an OTHER API and is referenced by one other package, customisations should treat it as an internal dependency of the forecasting engine and avoid direct invocation outside that flow. Any extension should reuse the documented entry points — POPULATE_CELLS, ZERO_FILL_CELLS, INSERT_FCAST_CELL, and POPULATE_OPENING_BAL — rather than duplicating the underlying AR and CE table logic, and should account for the zero-fill semantics when periods contain no qualifying transactions.