Search Results qa_chart_headers_pkg




Overview
Explore in AI Chat

Overview

The APPS.QA_CHART_HEADERS_PKG package body is a core Oracle Quality (QA) module utility responsible for defining, persisting, and managing the metadata that underpins Quality charts in Oracle E-Business Suite 12.1.1 and 12.2.2. Quality collection elements, specifications, and results are frequently analyzed visually through trend, Pareto, histogram, and control charts. Each of these chart types requires a header record that identifies the chart, its axes, its criteria, and the type-specific parameters that drive rendering. QA_CHART_HEADERS_PKG encapsulates the business logic that creates, maintains, and deletes these chart header definitions, insulating callers from the underlying table structures and from the chart-type-specific packages that consume the header data.

The package is classified as OTHER in the ETRM API metadata, indicating it is an internal supporting API rather than a formally published public interface. Its status is VALID, and it resides entirely within the APPS schema, relying on APPS synonyms for table access and on companion QA chart packages for type-specific behavior.

Key Procedures and Functions

The documented interface exposes seven procedures and functions:

  • CREATE_CHART — Establishes a new chart header record, validating inputs and deriving the type-specific attributes required by the downstream chart-rendering packages.
  • CREATE_CHART_AUTONOMOUS — Performs the same creation logic within an autonomous transaction, allowing a chart definition to be committed independently of the caller's transaction context.
  • DELETE_CHART — Removes a chart header and its associated definition records as part of the caller's current transaction.
  • DELETE_CHART_AUTONOMOUS — Deletes a chart definition in an autonomous transaction, ensuring the removal persists regardless of the enclosing transaction's outcome.
  • SET_X_LABEL — Assigns or updates the X-axis label associated with a chart header.
  • SET_Y_LABEL — Assigns or updates the Y-axis label associated with a chart header.
  • GET_FUNCTION_AXIS_LABEL — Returns the appropriate axis label derived from a function or aggregated measure, supporting dynamic labeling of chart axes.

The presence of paired standard and autonomous variants reflects the common EBS pattern of separating UI-driven transactions from background or logging work that must commit independently.

Tables Accessed

Through APPS synonyms, the package manipulates the following documented tables:

  • QA_CHART_HEADERS — The primary store for chart header definitions, holding chart identity, type, axis information, and linkage to owning criteria.
  • QA_CHART_HEADERS_S — The corresponding sequence or secondary table used to generate and track unique header identifiers.
  • QA_CRITERIA_HEADERS — Provides the criteria context against which charts are defined, ensuring charts are anchored to a valid Quality collection plan or criterion.

The package additionally depends on FND_GLOBAL for session context, FND_MESSAGE for user-facing messages, QA_CHARS_API for character/collection element validation, QA_ERES_UTIL for electronic records and signatures support, and the QA_SS_CONST constants package. It orchestrates chart-type-specific logic through QA_CHART_CONTROL_PKG, QA_CHART_GENERIC_PKG, QA_CHART_HISTOGRAM_PKG, QA_CHART_PARETO_PKG, and QA_CHART_TREND_PKG.

Usage Notes

QA_CHART_HEADERS_PKG is not referenced by any other database object per the dependency metadata; it is invoked directly by Oracle Quality forms, concurrent programs, and customization code that create or manage chart definitions. Oracle Forms calls the standard CREATE_CHART and DELETE_CHART variants during interactive chart setup, while the AUTONOMOUS variants support background processing or diagnostic logging where an independent commit is required. Because the package is not a formally published API and is not referenced by other packages, its procedures should be treated as internal; customizations should validate behavior carefully across 12.1.1 and 12.2.2, as the online patching architecture in 12.2.2 can affect editioning and dependency resolution.