Search Results push_edw_proj_project_lstg

Overview

APPS.FII_PROJECT_M_C is a PL/SQL package that belongs to the Oracle Projects family of database objects within Oracle E-Business Suite. Its role is to extract and publish Projects-related master and reference data from the EBS transactional tables into the Oracle Business Intelligence / Enterprise Data Warehouse (EDW) staging layer. The package forms part of the FII (Financials Intelligence) integration used by Oracle Financial Analytics and related Projects Analytics products, where master data must be periodically synchronized from the source EBS instance to the reporting warehouse before transaction fact loads can take place.

The package is classified in ETRM as an OTHER API, meaning it is not an open public interface for general customer extension. It is intended to be invoked by the standard EDW extraction programs, typically via concurrent program wrappers, rather than by end-user forms. The date-bounded procedure signatures (p_from_date, p_to_date) reflect the standard incremental-load pattern used throughout the FII master-data ETL: callers supply a lower and upper date bound so that only changed or newly created records within the window are pushed to the warehouse.

Key Procedures and Functions

The package exposes nineteen documented procedures, all sharing the same date-range pattern.

• PUSH — the top-level entry point. It accepts the standard concurrent program errbuf and retcode OUT parameters plus p_from_date and p_to_date as VARCHAR2. It orchestrates the individual list-loading procedures below, running them as a single logical load batch.
• PUSH_EDW_PROJ_TASK_LSTG — extracts the project task listing.
• PUSH_EDW_PROJ_TOP_TASK_LSTG — extracts the top-level task listing.
• PUSH_EDW_PROJ_PROJECT_LSTG — extracts the primary project listing.
• PUSH_EDW_PROJ_PRJ_TYP_LSTG — extracts the project type listing.
• PUSH_EDW_PROJ_CLS1_LSTG through PUSH_EDW_PROJ_CLS7_LSTG — seven procedures that extract the project classification flexfield values for class categories one through seven.
• PUSH_EDW_PROJ_CATEG1_LSTG through PUSH_EDW_PROJ_CATEG7_LSTG — seven procedures that extract the project category values for categories one through seven.

All list procedures use DATE parameters for p_from_date and p_to_date; only the outer PUSH uses VARCHAR2, indicating a conversion is performed before the child calls execute.

Tables Accessed

The package writes to fifteen documented EDW staging tables, accessed through APPS synonyms. These are the targets of the corresponding list procedures:

• EDW_PROJ_TASK_LSTG and EDW_PROJ_TOP_TASK_LSTG — task and top-task master rows.
• EDW_PROJ_PROJECT_LSTG — the core project master listing.
• EDW_PROJ_PRJ_TYP_LSTG — project type reference data.
• EDW_PROJ_CLS1_LSTG through EDW_PROJ_CLS7_LSTG — the seven project classification value listings.
• EDW_PROJ_CATEG1_LSTG through EDW_PROJ_CATEG7_LSTG — the seven project category value listings.

Each procedure reads master rows from the EBS Projects transactional model (PA_PROJECTS, PA_TASKS, class and category flexfield views, and reference lookups) filtered by the date window, then inserts or updates the corresponding staging table for downstream warehouse consumption.

Usage Notes

FII_PROJECT_M_C is normally invoked through the standard EDW master-data load concurrent program rather than directly. The outer PUSH procedure conforms to the dual errbuf/retcode convention required by Oracle Application Object Library, so it can be registered as a concurrent program executable in the System Administrator responsibility. When called from PL/SQL directly, callers should pass the date window in the character format expected by PUSH and ensure the corresponding child procedures receive converted DATE values.

The package is not referenced by any other documented package (0 referencing dependencies), which confirms its role as a top-level driver rather than a shared utility. Incremental loads should use a p_from_date equal to the high-water mark of the last successful run to avoid re-extracting unchanged master rows. Because the staging tables are truncated or merged by the warehouse process, custom code should not write to these EDW tables directly; instead, invoke PUSH within the supported ETL schedule.