Search Results bis_global_start_date

Overview

APPS.ISC_MAINT_WO_ETL_PKG is a PL/SQL extraction, transformation, and load (ETL) package responsible for collecting maintenance work order data from Oracle Enterprise Asset Management (EAM) and Work in Process (WIP) source tables and staging that data for downstream analytical or reporting consumption. The package supports the maintenance work order collection process in Oracle EBS 12.1.1 and 12.2.2, providing both an initial (full) load path and an incremental (delta) load path so that large source volumes do not need to be reprocessed on every collection cycle.

The package is owned by APPS and is classified generically as OTHER rather than as a public or private API. It manipulates package-level globals initialized from FND_GLOBAL, including user, login, concurrent program, and request identifiers, and a g_global_start_date value seeded from SYSDATE and g_last_collection_date. These globals anchor the collection window used by the incremental load logic and carry session context into error logging via BIS_COLLECTION_UTILITIES.

Key Procedures and Functions

• GET_WORK_ORDERS_INITIAL_LOAD — Performs the initial, full extraction of maintenance work order records. It is intended for first-time collection or after a staging reset, populating the interface table with the complete set of work order rows within scope.
• GET_WORK_ORDERS_INCR_LOAD — Performs the incremental extraction. It leverages the stored last collection date so that only work orders changed since the prior successful run are picked up, improving collection performance and reducing redundant data movement.
• Save_Last_Collection_Date — An internal function returning BOOLEAN that maintains the collection watermark. It reads the sentinel row (Organization_Id = -99, Work_Order_Id = -99, Entity_Type = -1) from ISC_MAINT_WORK_ORDERS_F; if absent, it inserts the sentinel record, otherwise it updates LAST_UPDATE_DATE to SYSDATE. Errors are captured with a statement number and SQLCODE, rolled back, and written through BIS_COLLECTION_UTILITIES.put_line.

Tables Accessed

• ISC_MAINT_WORK_ORDERS_F — The primary staging/interface table written by the package. It holds collected maintenance work order data and the sentinel watermark row that drives incremental collection.
• EAM_WORK_ORDER_DETAILS — Source of EAM work order detail attributes used during extraction.
• WIP_DISCRETE_JOBS — Source of discrete job information related to maintenance work orders.
• WIP_ENTITIES — Supplies entity-level work in process information joined into the work order extraction.
• DUAL — Used for single-row calculations and date retrieval.
• DBMS_SQL — Referenced for dynamic SQL execution, allowing flexible or conditional extraction logic.

Usage Notes

The package is normally invoked in the context of concurrent program execution. Package globals such as g_program_id, g_request_id, and g_program_login_id are sourced from FND_GLOBAL.CONC_* values, which are populated only when a concurrent request is active. The initial load procedure is run once during implementation or after a full re-collection; subsequent cycles should invoke the incremental load. Because the package references the user’s search term context around a global start date variable, administrators investigating bis_global_start_date behavior should recognize that the package’s own global is g_global_start_date, initialized to SYSDATE and distinct from any BIS/DSS global of similar naming.

The package is referenced by no other packages according to the metadata, indicating it is an entry-level collection program rather than a shared utility. Error handling relies on BIS_COLLECTION_UTILITIES, so that package must be valid and its logging configured for diagnostics to be captured. Session context (user_id, login_id) defaults to -1 when FND_GLOBAL values are unavailable, which is expected for background collection runs.