Results for “x_axis_prompt”

8 results




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

Overview

QA_CRITERIA_HEADERS_V is an APPS-owned database view in the Oracle E-Business Suite Quality (QA) module. It resides in the APPS schema and is documented as VALID across both 12.1.1 and 12.2.2. The view exposes the definition and rendering settings for quality criteria, combining the criteria header record with the characteristics assigned to the X and Y axes. Its documented purpose is to present chart and Quality Dynamic Reportwriter settings, making it the primary access point for consumers that need a fully resolved, single-row view of a criteria definition without navigating the characteristic and plan-character tables independently.

The view does not store data. It is a read-only projection built entirely from base tables and related views, and it inherits the multi-org context of the underlying criteria rows through the ORGANIZATION_ID column. Because the chart and reportwriter configuration is central to how quality results are graphed and reported, the view is used both by Oracle's own Quality forms and reports and by customer extensions that need to reproduce those settings in custom concurrent programs or BI Publisher layouts.

Underlying Base Objects

Per the documented view metadata for 12.2.2, QA_CRITERIA_HEADERS_V is defined over the following objects, all referenced through APPS synonyms:

  • QA_CRITERIA_HEADERS — the driver table providing criteria identity, name, plan, output type, title, description and chart settings.
  • QA_PLANS — supplies PLAN_NAME for the associated quality plan.
  • QA_CHARS — supplies the X-axis and Y-axis characteristic definitions (QC1 and QC2 aliases).
  • QA_PLAN_CHARS — supplies plan-specific overrides for prompts, decimal precision and result column names (QPC1 and QPC2 aliases).
  • MTL_UNITS_OF_MEASURE_TL — supplies the unit of measure description resolved from the UOM_CODE.
  • FND_LOOKUP_VALUES — supplies lookup meaning resolution for foreign-key-based characteristics.
  • QA_SPECS and QA_SPEC_CHARS — joined for specification-level characteristic context.

The X-axis and Y-axis branches are structurally symmetric. Each branch joins QA_CHARS to QA_PLAN_CHARS, with NVL logic preferring the plan-character override when present and falling back to the base characteristic value for prompt, decimal precision and unit of measure. The MTL_UNITS_OF_MEASURE_TL join is similarly resolved through NVL between the plan-character and characteristic UOM codes.

Key Columns

The following columns are the most significant for query and integration purposes:

The FK_MEANING column is the object of the search that led to this view. Users querying for FK_MEANING are typically resolving a foreign-key characteristic back to a displayable meaning, so that a chart label or report column shows the lookup meaning rather than the raw ID.

Common Use Cases and Queries

Typical scenarios include generating chart axis labels for a Dynamic Reportwriter output, validating plan-character overrides against base characteristic settings, and extracting criteria configuration for a custom graph or dashboard.

To list all criteria with their axis characteristics:

SELECT CRITERIA_ID, NAME, PLAN_NAME, OUTPUT_TYPE, CHART_TYPE
FROM   APPS.QA_CRITERIA_HEADERS_V
WHERE  ORGANIZATION_ID = :org_id;

To inspect foreign-key meaning resolution on the X and Y axes, which is the specific case behind a "fk_meaning" search:

SELECT CRITERIA_ID,
       NAME,
       X_AXIS_CHAR_NAME,
       X_AXIS_FK_LOOKUP_TYPE,
       X_AXIS_FK_MEANING,
       Y_AXIS_CHAR_NAME,
       Y_AXIS_FK_MEANING
FROM   APPS.QA_CRITERIA_HEADERS_V
WHERE  X_AXIS_FK_MEANING IS NOT NULL
   OR  Y_AXIS_FK_MEANING IS NOT NULL;

To review chart rendering parameters for a given plan:

SELECT CRITERIA_ID, NAME, CHART_TYPE, NUM_BARS, NUM_POINTS,
       X_AXIS_PROMPT, Y_AXIS_PROMPT
FROM   APPS.QA_CRITERIA_HEADERS_V
WHERE  PLAN_ID = :plan_id;

Because each axis branch performs an NVL between the plan-character override and the base characteristic, results reflect the effective configuration that the Quality charting and reportwriter engines will actually apply. This makes the view authoritative for reproducing Quality output behavior in custom reports without reimplementing the fallback logic against the base tables.