Search Results qpr_report_hdrs_tl
Overview
QPR_REPORT_HDRS_PKG is the header-level DML package for the Oracle E-Business Suite report definition repository used by Oracle Quality and related reporting infrastructure. It provides the standard multi-row API pattern for maintaining report header records and their translated descriptive attributes across a bilingual (base plus translation) schema. The package implements the canonical Oracle Forms and concurrent processing integration contract: an INSERT_ROW that writes both a base entity row and its translation row, LOCK_ROW and UPDATE_ROW for maintenance of existing definitions, DELETE_ROW for removal, and ADD_LANGUAGE for installing translated rows for additional installed languages. The classification as OTHER indicates it is an internal, non-public API rather than a formally published open interface; it is intended for use by the owning application's forms and generators rather than by third-party extension code.
Key Procedures and Functions
- INSERT_ROW — Creates a new report header. It inserts the base entity record into QPR_REPORT_HDRS_B (including the identifying report header ID, the generated report type header ID, user and plan context, seeded and validity flags, the enabled options CLOB, and standard WHO audit columns) and then inserts the corresponding translatable attributes — report name and report title — into QPR_REPORT_HDRS_TL for the base language. The procedure returns the ROWID of the newly created base row for subsequent forms navigation. Notably, the translation insert derives its LANGUAGE and SOURCE_LANG values from the environment and carries login and request identifiers forward to the translation row.
- LOCK_ROW — Acquires a row-level lock on the identified report header so that a form session can safely enter update mode without a lost-update conflict.
- UPDATE_ROW — Applies changes to an existing report header, updating both the base row attributes and the translation row's report name and title for the appropriate language.
- DELETE_ROW — Removes a report header definition, deleting the associated translation and base rows.
- ADD_LANGUAGE — Installs the translation row for a report header in a specified installed language, propagating the base-language name and title as the initial source values. This procedure supports the standard "Add Language" maintenance flow for multilingual deployments.
Tables Accessed
- QPR_REPORT_HDRS_B — The base table holding language-independent report header attributes: report header ID, program login and request IDs, report type header ID, user ID, plan ID, seeded report flag, report valid flag, enabled options CLOB, and WHO columns. Insert and update targets.
- QPR_REPORT_HDRS_TL — The translation table holding report name and report title keyed by report header ID, language, and source language. Both the direct insert path and the ADD_LANGUAGE path target this table.
- FND_LANGUAGES — The Oracle Application Object Library language repository, consulted to resolve installed and base languages when creating translation rows, including during ADD_LANGUAGE processing.
Usage Notes
The package is normally invoked indirectly. Oracle Forms maintenance screens for report header definitions call the insert, lock, update, and delete entry points as part of the standard block-level DML events, supplying the out ROWID so the block can reposition itself after a create. The ADD_LANGUAGE entry point is invoked from the multilingual maintenance flows that propagate seeded or existing definitions to newly installed languages. Concurrent programs or internal generators that create report definitions may call INSERT_ROW directly. Because the package is classified as OTHER and references no other packages, it is a leaf-level utility in the dependency graph, depending only on the FND and QPR tables it manipulates. Customizations should avoid calling it as a supported public API; the preferred integration point is the underlying report definition data model or the owning application's form. When the object appears in searches such as "qpr_report_hdrs_tl", the reference typically concerns the translation table rather than the package body itself, since the TL table is the object most commonly queried for report names and titles in a given language. In R12.1.1 and 12.2.2 the package behaves identically with respect to the online patching editioning model; the base and translation tables are editioned objects and the package body resolves to the run-edition copy at execution time.
-
APPS.QPR_REPORT_HDRS_PKG SQL Statements
12.1.1
-
APPS.QPR_REPORT_HDRS_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.QPR_REPORT_HDRS_PKG
12.2.2
-
VIEW: QPR.QPR_REPORT_HDRS_TL#
12.2.2
owner:QPR, object_type:VIEW, object_name:QPR_REPORT_HDRS_TL#, status:VALID,
-
PACKAGE BODY: APPS.QPR_REPORT_HDRS_PKG
12.1.1
-
SYNONYM: APPS.QPR_REPORT_HDRS_TL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:QPR_REPORT_HDRS_TL, status:VALID,
-
SYNONYM: APPS.QPR_REPORT_HDRS_TL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:QPR_REPORT_HDRS_TL, status:VALID,
-
APPS.QPR_REPORT_ENTITIES_PVT SQL Statements
12.2.2
-
VIEW: APPS.QPR_REPORT_HDRS_VL
12.2.2
-
APPS.QPR_REPORT_ENTITIES_PVT SQL Statements
12.1.1
-
VIEW: APPS.QPR_REPORT_HDRS_VL
12.1.1
-
VIEW: QPR.QPR_REPORT_HDRS_TL#
12.2.2
-
PACKAGE BODY: APPS.QPR_REPORT_ENTITIES_PVT
12.1.1
-
PACKAGE BODY: APPS.QPR_REPORT_ENTITIES_PVT
12.2.2
-
TABLE: QPR.QPR_REPORT_HDRS_TL
12.1.1
owner:QPR, object_type:TABLE, object_name:QPR_REPORT_HDRS_TL, status:VALID,
-
TABLE: QPR.QPR_REPORT_HDRS_TL
12.2.2
owner:QPR, object_type:TABLE, object_name:QPR_REPORT_HDRS_TL, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
VIEW: APPS.QPR_REPORT_HDRS_VL
12.1.1
owner:APPS, object_type:VIEW, object_name:QPR_REPORT_HDRS_VL, status:VALID,
-
VIEW: APPS.QPR_REPORT_HDRS_VL
12.2.2
owner:APPS, object_type:VIEW, object_name:QPR_REPORT_HDRS_VL, status:VALID,
-
PACKAGE BODY: APPS.QPR_REPORT_ENTITIES_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:QPR_REPORT_ENTITIES_PVT, status:VALID,
-
PACKAGE BODY: APPS.QPR_REPORT_HDRS_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:QPR_REPORT_HDRS_PKG, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.QPR_REPORT_ENTITIES_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:QPR_REPORT_ENTITIES_PVT, status:VALID,
-
PACKAGE BODY: APPS.QPR_REPORT_HDRS_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:QPR_REPORT_HDRS_PKG, status:VALID,
-
PACKAGE BODY: APPS.QPR_USER_PLAN_INIT_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:QPR_USER_PLAN_INIT_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.QPR_USER_PLAN_INIT_PVT SQL Statements
12.1.1
-
APPS.QPR_USER_PLAN_INIT_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.QPR_USER_PLAN_INIT_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:QPR_USER_PLAN_INIT_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.QPR_USER_PLAN_INIT_PVT
12.1.1
-
PACKAGE BODY: APPS.QPR_USER_PLAN_INIT_PVT
12.2.2
-
APPS.QPR_USER_PLAN_INIT_PVT dependencies on QPR_REPORT_HDRS_TL
12.1.1
-
APPS.QPR_REPORT_HDRS_PKG dependencies on QPR_REPORT_HDRS_TL
12.2.2
-
APPS.QPR_REPORT_ENTITIES_PVT dependencies on QPR_REPORT_HDRS_TL
12.2.2
-
APPS.QPR_REPORT_HDRS_PKG dependencies on QPR_REPORT_HDRS_TL
12.1.1
-
APPS.QPR_REPORT_ENTITIES_PVT dependencies on QPR_REPORT_HDRS_TL
12.1.1
-
APPS.QPR_USER_PLAN_INIT_PVT dependencies on QPR_REPORT_HDRS_TL
12.2.2
-
APPS.QPR_REPORT_HDRS_PKG dependencies on FND_LANGUAGES
12.1.1
-
APPS.QPR_REPORT_HDRS_PKG dependencies on FND_LANGUAGES
12.2.2
-
APPS.QPR_REPORT_ENTITIES_PVT dependencies on QPR_REPORT_HDRS_B
12.1.1
-
APPS.QPR_REPORT_ENTITIES_PVT dependencies on QPR_REPORT_RELNS
12.1.1
-
APPS.QPR_REPORT_ENTITIES_PVT dependencies on QPR_REPORT_HDRS_B
12.2.2
-
APPS.QPR_REPORT_ENTITIES_PVT dependencies on QPR_REPORT_RELNS
12.2.2
-
APPS.QPR_REPORT_HDRS_PKG dependencies on QPR_REPORT_HDRS_B
12.1.1
-
APPS.QPR_REPORT_HDRS_PKG dependencies on QPR_REPORT_HDRS_B
12.2.2