Search Results aging_date

Overview

The APPS.ISC_FS_TASK_BAC_AGE_ETL_PKG package is a Supply Chain Intelligence (ISC) extract-transform-load (ETL) utility that supports the "BAC Aging" (Backlog Aging / Booked-Action-Complete Aging) reporting subject area within Oracle E-Business Suite. Its central role is to populate and refresh the fact and collection tables that drive aging analysis of fulfillment tasks — measuring how long order-related tasks remain open relative to a reference aging point. The aging_date for which the user searched is the temporal anchor of this package: the ETL logic derives aged buckets by comparing task dates to a configured aging date and to the calendar dimensions in the FII time tables.

The package body carries the standard ETRM/ISC framework scaffolding. It declares package globals for user, login, program, application, and concurrent request identifiers, plus status constants (g_success, g_error, g_warning) and a global start date retrieved from bis_common_parameters.get_global_start_date. Helper procedures such as local_init, logger, and bis_collection_utilities_log initialize the session context and route diagnostics into the BIS collection logging subsystem. A get_schema_name function resolves the target ISC schema at runtime, allowing the package to run against the correct collection schema. The g_max_date constant (4712/01/01) supports open-ended date ranges in the aging computation.

Key Procedures and Functions

• INITIAL_LOAD — Performs the full (first-time) load of the BAC aging fact data. It establishes the baseline snapshot of task aging information into the ISC collection tables, seeding the date dimension rows and fact rows required for subsequent reporting.
• INCREMENTAL_LOAD — Refreshes the aging facts on an ongoing basis, extracting only changed or newly eligible records since the last run. This is the procedure normally scheduled for recurring ETL cycles.
• GET_PERIOD_BIT_TBL — Returns a period "bit table" used by the aging logic to map calendar periods (day, week, period, quarter, year) into the bit-mapped structures that the ISC collection framework uses to resolve the aging date against available time dimension hierarchies.

Tables Accessed

The package reads and writes the following objects via APPS synonyms:

• ISC_FS_TASK_BAC_DATES_F — The primary fact/target table for BAC aging dates, referenced explicitly by g_object_name in the package body. This is the principal write target of the ETL.
• ISC_FS_TASK_BAC_DATES_C — The associated collection (staging) table holding the raw extracted rows prior to final fact load.
• FII_TIME_DAY, FII_TIME_WEEK, FII_TIME_ENT_PERIOD, FII_TIME_ENT_QTR, FII_TIME_ENT_YEAR — The FII calendar/time dimension tables. These supply the calendar keys and are essential to computing the aging date buckets and their hierarchical rollups.
• OKI_DBI_MULTIPLEXER_B — The ISC multiplexer base table, used by the collection framework to determine the correct collection/schema target for the load.

Usage Notes

This package is invoked as part of the ISC collections execution framework, typically through concurrent programs registered by the Supply Chain Intelligence ETL or the DBI collection manager, and may be called from forms using the standard ISC collection APIs. It is referenced by one other package, indicating it participates as a dependent step in a larger ETL chain. Because it relies on fnd_global and bis_common_parameters, it must run within a properly initialized EBS session (concurrent manager or an ISC-initialized form) so that the aging date and global start date parameters resolve correctly. Administrators should run INITIAL_LOAD once during implementation and schedule INCREMENTAL_LOAD thereafter; the aging results feed BAC aging reports and dashboards in the ISC/DBI reporting layer. The package header ($Header: iscfsbacageetlb.pls 120.2 2005/10/26) indicates it was last versioned in the 11i/12.0 era and carried forward into 12.1.1 and 12.2.2, so it should be treated as a stable, framework-owned object rather than a customization point.