Results for “pqh_budget_data_migration”

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

Overview

PQH_BUDGET_DATA_MIGRATION is an Oracle EBS APPS schema package that supports migration of budget data from the legacy Oracle Human Resources budget model (the PER_BUDGETS family of tables) into the Oracle Public Sector / HRMS budgeting model (the PQH_BUDGETS family of tables). It is part of the budgeting component of Oracle Human Resources and is used during upgrades, implementations, and data conversions where budget definitions, elements, versions, and period values must be transferred between the two schemas. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the defining user, so effective access to the underlying tables is governed by the invoking session. It carries an old-style header (pqbdgmig.pkh, version 115.12) indicating it has been essentially stable since the 11.5.x era and carried forward into 12.1.1 and 12.2.2 without structural change.

Key Procedures and Functions

Twenty documented procedures and functions make up the public surface of the package.

• EXTRACT_DATA — primary entry point that reads budget data for a given budget name, budget set, and business group, returning status via the standard concurrent program errbuf/retcode convention.
• POPULATE_BUDGETS — creates a PQH_BUDGETS row from a PER_BUDGETS record and returns the new budget ID and total budget value.
• POPULATE_BUDGET_VERSIONS — the procedure matching the reported search term; inserts PQH_BUDGET_VERSIONS rows from PER_BUDGET_VERSIONS records, keyed to the parent PQH budget, and returns the new budget version ID.
• POPULATE_BUDGET_DETAILS — creates PQH_BUDGET_DETAILS rows from PER_BUDGET_ELEMENTS records for a given budget version.
• POPULATE_BUDGET_PERIODS — creates PQH_BUDGET_PERIODS rows from PER_BUDGET_VALUES records.
• POPULATE_BUDGET_SETS, POPULATE_BUDGET_ELEMENTS, POPULATE_BUDGET_FUND_SRCS — populate the corresponding PQH budget set, element, and funding-source tables.
• POPULATE_EMPTY_BUDGET_VERSIONS — generates placeholder budget version rows where no source version exists.
• POPULATE_PERIOD_DETAILS — expands budget period rows using the default budget set definitions.
• POPULATE_PER_SHARED_TYPES and GET_SHARED_TYPE_ID — synchronise shared budget unit types between PER and PQH models and resolve a type ID from a unit value.
• POPULATE_GLOBALS — initialises package-level global state used by the migration run.
• SET_P_BGT_LOG_CONTEXT, SET_P_BVR_LOG_CONTEXT, SET_P_BDT_LOG_CONTEXT, SET_P_BPR_LOG_CONTEXT — set logging context (budget, budget version, budget detail, budget period) so diagnostic rows can be written to PQH_PROCESS_LOG.
• CHECK_PARAMS and CHECK_VALID_BUDGET — validate input parameters and confirm the source budget is eligible for migration.
• MIGRATE_BDGT — orchestration driver that sequences the population steps for a single budget.

Tables Accessed

The package reads from the legacy PER tables and writes to the PQH tables, using APPS synonyms throughout.

• Source (read): PER_BUDGETS, PER_BUDGET_VERSIONS, PER_BUDGET_ELEMENTS, PER_BUDGET_VALUES.
• Target (write): PQH_BUDGETS, PQH_BUDGET_VERSIONS, PQH_BUDGET_DETAILS, PQH_BUDGET_PERIODS, PQH_BUDGET_ELEMENTS, PQH_BUDGET_SETS, PQH_BUDGET_FUND_SRCS.
• Reference/default: PQH_DFLT_BUDGET_SETS, PQH_DFLT_BUDGET_ELEMENTS, PQH_DFLT_FUND_SRCS supply default set, element, and funding definitions used when source values are absent.
• Logging: PQH_PROCESS_LOG records migration progress and errors.

Usage Notes

PQH_BUDGET_DATA_MIGRATION is not referenced by any other documented package (referenced by 0 packages), which confirms it is a terminal utility rather than a library. In practice it is invoked from the Oracle HRMS budget setup forms and, more commonly, wrapped by a concurrent program or a custom PL/SQL driver supplied by the implementation team. Because EXTRACT_DATA follows the concurrent-program signature convention, it is the natural target for a concurrent executable registration. Callers should invoke it in a controlled maintenance window, ensure business group and budget set values are supplied, and review PQH_PROCESS_LOG afterwards. As with all migration utilities, a full backup of both PER and PQH budget tables is recommended before execution on production data.