Results for “cat_set_validate_flag”

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

Overview

QA_SPECS_VAL_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Quality (QA) module. As its product description states, the view "shows valid specifications." It provides a denormalized, business-friendly projection of quality specifications stored in the QA_SPECS table, enriched with descriptive attributes resolved from lookups and joined master data. Rather than requiring report developers and integrators to reconstruct the many foreign-key relationships and lookup decodes manually, QA_SPECS_VAL_V presents specification records with human-readable meanings already resolved.

The view is validated (status VALID) and is available in both Oracle EBS 12.1.1 and 12.2.2. Because it belongs to the APPS schema and joins only synonyms and lookup views, it behaves consistently across these releases and is a stable target for custom reporting, BI Publisher data templates, and interface extracts. It is particularly relevant to users searching for HIDE_PLAN_CHARS_FLAG, since that column is explicitly exposed and decoded within this view.

Underlying Base Objects

The view is defined over the following documented base objects:

• QA_SPECS (synonym) — the primary specification table, joined to itself (QS2) to resolve common or parent specifications.
• MFG_LOOKUPS (view) — joined three times (ML2, ML3, ML4) to decode assignment type, the hide plan characters flag, and specification status.
• MTL_CATEGORY_SETS_B / MTL_CATEGORY_SETS_TL (synonyms) — supply category set names, structure identifiers, and validation flags.
• MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_TL (synonyms) — provide item revision control flags and item descriptions.
• AP_SUPPLIERS and HZ_PARTIES (synonyms) — resolve vendor number and vendor party name.
• HZ_CUST_ACCOUNTS and HZ_PARTIES (synonyms) — resolve customer account number and customer party name.

The joins are driven primarily by lookup codes and foreign-key identifiers, with DECODE logic normalizing sentinel values such as -1 and 'NONE' to NULL for cleaner reporting output.

Key Columns

• SPEC_ID, SPEC_NAME, ORGANIZATION_ID — unique specification identifier, name, and owning organization.
• EFFECTIVE_FROM / EFFECTIVE_TO — validity window of the specification.
• COMMON_SPEC_ID / COMMON_SPEC_NAME — reference to a shared parent specification, resolved via the self-join.
• ASSIGNMENT_TYPE / ASSIGNMENT_TYPE_MEANING — the specification type and its decoded meaning from QA_SPEC_TYPE.
• CATEGORY_SET_ID, CATEGORY_ID, CATEGORY_SET_NAME — category assignment for the specification.
• ITEM_ID, ITEM_REVISION, ITEM_DESCRIPTION, REV_CONTROL_FLAG — item context and revision control behavior.
• VENDOR_ID, VENDOR_NUMBER, VENDOR_NAME — supplier context for vendor specifications.
• CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME — customer context for customer specifications.
• HIDE_PLAN_CHARS_FLAG / HIDE_PLAN_CHARS_MEANING — the flag controlling whether planning characteristics are hidden, decoded via the SYS_YES_NO lookup.
• SPEC_STATUS / MEANING — status code and its decoded description.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.

Common Use Cases and Queries

This view is commonly used to produce specification master reports, cross-reference specifications to items, vendors, and customers, and drive conditional behavior based on flags such as HIDE_PLAN_CHARS_FLAG.

SELECT spec_id, spec_name, organization_id,
       assignment_type_meaning, spec_status,
       hide_plan_chars_flag, hide_plan_chars_meaning,
       item_description, vendor_name, customer_name
  FROM apps.qa_specs_val_v
 WHERE organization_id = :p_org_id
   AND hide_plan_chars_flag = 'Y';

Additional scenarios include filtering valid specifications by effective dates, joining to inventory items for quality planning, or extracting descriptive flexfield attributes for downstream integration. Because sentinel values are decoded to NULL, consumers can apply straightforward null checks without special-case logic.