Results for “qa_eres_result_type”

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

Overview

QA_ERES_PLANS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered in the ETRM repository as VIEW: APPS.QA_ERES_PLANS_V with status VALID. As the name implies, it exposes Oracle Quality collection plan data in the form used by the e-records (ERES) and electronic signature infrastructure. Collection plans are the central Quality Management constructs that define the characteristics to be collected, the specification limits applied, and the actions performed when results are recorded. This view provides a denormalized, reporting-friendly projection of plans so that callers do not need to join the base Quality tables and the Oracle Application Object Library (AOL) lookup views themselves.

The view is documented with the standard Oracle internal-use warning: it is not supported for direct customer access except through standard Oracle Applications programs. Nonetheless, it is widely referenced in EBS 12.1.1 and 12.2.2 for custom reporting, integration extracts, and diagnostic queries because it is stable and carries translated meaning columns rather than raw codes.

Underlying Base Objects

The ETRM dependency listing for this view records the following referenced objects:

• QA_PLANS (synonym) — the primary base, holding the collection plan header records.
• MTL_PARAMETERS (synonym) — supplies the inventory organization context with which the plan is associated.
• HR_ALL_ORGANIZATION_UNITS_TL (synonym) — the translated organization name for the owning organization.
• FND_COMMON_LOOKUPS (view) — one of the AOL lookup sources used to resolve meaning/description values.
• QA_LOOKUPS (view) — the Quality-specific lookup view, resolving plan type, specification assignment, and related coded values.
• MFG_LOOKUPS (view) — the manufacturing lookup view, providing additional meaning resolution.
• FND_GLOBAL (package) — used within the view definition to establish the runtime environment, including the current user and application context, and to drive multi-org (organization_id) filtering.

Because FND_GLOBAL is referenced, the view is effectively session- and organization-aware: the rows returned depend on the current organization and login context established by the EBS security model.

Key Columns

The view exposes the collection plan header and its associated descriptive flexfield columns:

• PLAN_ID — unique collection plan identifier; the primary integration key.
• ORGANIZATION_ID — inventory organization to which the plan belongs.
• NAME and DESCRIPTION — the plan name and its descriptive text.
• PLAN_TYPE_CODE, PLAN_TYPE_MEANING, PLAN_TYPE_DESCRIPTION — the coded plan type together with its lookup-resolved meaning and description, allowing reports to display readable classifications.
• EFFECTIVE_FROM and EFFECTIVE_TO — the date range within which the plan is active.
• SPEC_ASSIGNMENT_TYPE and SPEC_ASSIGNMENT_MEANING — the specification assignment type and its decoded meaning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE11 — the descriptive flexfield structure defining column and its segments, used for customer-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard "who" audit columns.

With respect to the search term esig_mode_meaning: the columns documented for this view do not include an ESIG-related column, nor an esig_mode_meaning. The view's lookup join columns are limited to plan type and specification assignment meanings. Querying an esig_mode_meaning against QA_ERES_PLANS_V directly will therefore fail; that attribute must be obtained from the electronic signature and e-records configuration views and lookup tables that govern signature mode per function or event, not from the plan header view itself.

Common Use Cases and Queries

The view is typically queried to enumerate active collection plans for an inventory organization, to report on plan types and specification assignment behavior, and to drive downstream extracts that need plan metadata alongside e-records context. A representative query follows:

• List active plans in the current organization: SELECT plan_id, organization_id, name, plan_type_meaning, spec_assignment_meaning, effective_from, effective_to FROM apps.qa_eres_plans_v WHERE TRUNC(SYSDATE) BETWEEN NVL(effective_from, TRUNC(SYSDATE)) AND NVL(effective_to, TRUNC(SYSDATE));
• Enumerate plan type distribution by organization: SELECT organization_id, plan_type_meaning, COUNT(*) FROM apps.qa_eres_plans_v GROUP BY organization_id, plan_type_meaning;
• Retrieve descriptive flexfield context for a plan: SELECT plan_id, name, attribute_category, attribute1, attribute2 FROM apps.qa_eres_plans_v WHERE plan_id = :b1;
• Identify recently modified plans: SELECT plan_id, name, last_updated_by, last_update_date FROM apps.qa_eres_plans_v ORDER BY last_update_date DESC;

When e-signature mode information is required, the query should be extended against the e-records/signature configuration tables and joined to QA_ERES_PLANS_V on the plan or organization key, since the signature mode meaning is not materialized on this view.