Results for “edw_collection_hook”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EDW_COLLECTION_HOOK is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). It is a supporting component of the Oracle Enterprise Data Warehouse (EDW) collection infrastructure, which extracts and stages data from EBS transactional sources into the warehouse. The package functions as a hook or callback library: rather than performing collection itself, it exposes a set of well-known pre- and post-processing entry points that the EDW collection engine invokes around each stage of a collection run.

This design allows Oracle, and to a limited extent customers, to inject custom logic—validation, defaulting, auditing, or transformation—without modifying the collection drivers themselves. The package's status is VALID in the ETRM dictionary, and its API classification is recorded as OTHER, reflecting its role as an internal extension framework rather than a public business API.

Key Procedures and Functions

The ETRM metadata documents ten procedures, organized as paired pre/post hooks for each collection phase:

• PRE_COLL / POST_COLL — Umbrella entry points invoked at the very beginning and very end of an overall collection cycle. They provide a single place to initialize session state or wrap up after all collection phases complete.
• PRE_DIMENSION_COLL / POST_DIMENSION_COLL — Hooks fired immediately before and after the dimension collection phase, where dimension records are gathered from source tables.
• PRE_FACT_COLL / POST_FACT_COLL — Hooks surrounding fact collection, the phase in which transactional fact rows are extracted.
• PRE_MAPPING_COLL / POST_MAPPING_COLL — Hooks surrounding the mapping collection phase, which gathers source-to-target key mappings and lookup relationships.
• PRE_DERIVED_FACT_COLL / POST_DERIVED_FACT_COLL — Hooks wrapping derived fact collection, where facts are computed or combined from other collected data rather than read directly from a source.

In the delivered package, these procedures are deliberately lightweight stubs, providing hook points that can be extended or overridden by collection-specific logic. No parameter lists are documented in the ETRM metadata, and the shipped bodies function primarily as no-ops or minimal placeholders.

Tables Accessed

No tables are documented as directly referenced by EDW_COLLECTION_HOOK via APPS synonyms in the ETRM metadata. This is consistent with its role as a hook package: any data manipulation is delegated to the calling collection programs or to customer extensions. The package depends only on the SYS STANDARD package, confirming it performs no intrinsic SQL against EBS application tables.

Usage Notes

EDW_COLLECTION_HOOK is not intended to be called directly from forms, concurrent programs, or ad hoc SQL. It is invoked internally by the EDW collection drivers. The dependency list confirms this: EDW_ALL_COLLECT, EDW_DERIVED_FACT_FACT_COLLECT, and EDW_MAPPING_COLLECT all reference it, and it also references itself. During a collection run, the active driver calls the appropriate PRE_* hook before a phase and the matching POST_* hook afterward.

Because it is an APPS-owned, Oracle-maintained package, direct modification is not supported. Customizations should be applied through the supported extension mechanisms rather than editing the package body, as patching or upgrades will overwrite delivered code. Administrators diagnosing collection behavior should treat this package as an instrumentation and extension seam—useful for tracing phase boundaries and for understanding where custom logic may legitimately be attached—rather than as a functional data-processing module in its own right.