Results for “sequence_nextval”

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

Overview

QA_PLAN_CHARS_V is a PL/SQL view owned by the APPS schema in the Oracle E-Business Suite Quality (QA) module. Its purpose is to present a denormalized, report-friendly picture of collection plans and their associated collection elements (characteristics). In QA terminology, a collection plan (QA_PLANS) groups a set of collection elements (QA_CHARS) that are attached to that plan through the intersection entity QA_PLAN_CHARS. This view joins those three layers together and enriches the result with lookup meanings, unit-of-measure descriptions, and datatype translations, so that a single query can return a fully labeled specification of a plan's characteristics.

Because the view resolves foreign keys to FND_LOOKUPS and MFG_LOOKUPS meanings at the database level, it is well suited for concurrent-program extracts, Discoverer or BI Publisher reports, and inbound/outbound integration interfaces that need to synchronize collection plan definitions between EBS and external quality systems. The view is documented as VALID and is part of the standard 12.1.1 and 12.2.2 ETRM data model.

Underlying Base Objects

The documented referenced base objects are QA_PLANS, QA_CHARS, and QA_PLAN_CHARS (all exposed through APPS synonyms), which supply the core plan, characteristic, and plan-characteristic data. Lookup resolution is performed against the QA_LOOKUPS and MFG_LOOKUPS views, while FND_COMMON_LOOKUPS provides the enabled, mandatory, displayed, and values-exist meanings. MTL_UNITS_OF_MEASURE supplies the unit-of-measure text. The FND_GLOBAL package is referenced to supply session context such as organization and user identifiers. QA_DEVICE_INFO is also listed among the referenced objects, reflecting the QA data-collection infrastructure that surrounds the collection plan model.

Key Columns

The view exposes the primary and foreign keys PLAN_ID, CHAR_ID, and ORGANIZATION_ID, together with standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). Descriptive columns include PLAN_NAME, PLAN_DESCRIPTION, CHAR_NAME, and PROMPT. The CHAR_TYPE_CODE and its decoded CHAR_TYPE_MEANING identify the element type, while DATATYPE and DATATYPE_MEANING specify the value domain.

Control flags are returned both as codes and as translated meanings: ENABLED_FLAG with ENABLED_MEANING, MANDATORY_FLAG with MANDATORY_MEANING, DISPLAYED_FLAG with DISPLAYED_MEANING, and VALUES_EXIST_FLAG with VALUES_EXIST_MEANING. These columns are the typical target of a search for the "sys_yes_no" lookup, since the underlying lookups resolve to Yes/No values. Additional columns cover DEFAULT_VALUE, DEFAULT_VALUE_ID, DECIMAL_PRECISION, UOM_CODE and UNIT_OF_MEASURE, DISPLAY_LENGTH, DATA_ENTRY_HINT, and the RESULT_COLUMN_NAME used when results are written to a database table. Validation and sequencing metadata (SQL_VALIDATION_STRING via SQL_STRING_FLAG, FK_LOOKUP_TYPE, FK_TABLE_NAME, FK_ID, and the SEQUENCE_* columns) is also exposed.

Common Use Cases and Queries

Typical uses include auditing which collection elements are mandatory on a plan, generating specification documentation, and driving interface loads of plan definitions.

• List enabled mandatory elements for an organization: SELECT plan_name, char_name, prompt, mandatory_meaning FROM qa_plan_chars_v WHERE organization_id = :org AND enabled_flag = 'Y' AND mandatory_flag = 'Y' ORDER BY prompt_sequence;
• Report datatypes and units: SELECT char_name, datatype_meaning, unit_of_measure, decimal_precision FROM qa_plan_chars_v WHERE plan_id = :plan_id;
• Find elements validated by an SQL string: SELECT plan_name, char_name, sql_string_flag FROM qa_plan_chars_v WHERE sql_string_flag = 'Y';

Because the view is not a table, it should be treated as read-only and filtered on indexed columns such as PLAN_ID or ORGANIZATION_ID to preserve performance.