Results for “collection_id”

50+ results




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

Overview

QA_ERES_INTEGRATION_PLANS_V is an APPS-owned database view in the Oracle E-Business Suite Quality (QA) module, classified as VALID in the ETRM metadata for release 12.2.2 (and equally applicable to 12.1.1). Its stated purpose is to expose the top-level plans and collection IDs associated with electronic records (ERES). In the context of Oracle EBS integration with an external electronic records repository, such as Oracle Universal Content Management or a comparable ERES archive, this view provides the driving data set of plan-level records that require upload or synchronization. The view is intentionally narrow: rather than returning every plan occurrence, it returns only those QA_RESULTS rows whose OCCURRENCE value is not referenced as a CHILD_OCCURRENCE in the QA_PC_RESULTS_RELATIONSHIP table. This exclusion is the defining characteristic of "top-level" planning records. The inclusion of the "child_occurrence" term in the user's search reflects that the view's filtering predicate is exactly the anti-join against CHILD_OCCURRENCE, which distinguishes parent plan occurrences from their subordinate children.

Underlying Base Objects

The view is defined over three documented base objects, all accessed through APPS synonyms:

  • QA_RESULTS (SYNONYM) — aliased QR. Supplies PLAN_ID and COLLECTION_ID, and supports the OCCURRENCE column used in the NOT IN predicate.
  • QA_PLANS (SYNONYM) — aliased QP. Supplies the plan NAME and supplies the PLAN_ID used in the equi-join to QA_RESULTS.
  • QA_PC_RESULTS_RELATIONSHIP (SYNONYM) — referenced in the correlated subquery on its CHILD_OCCURRENCE column, which identifies plan results that are children of another occurrence.

The join condition QR.PLAN_ID = QP.PLAN_ID links each result row to its parent plan definition, while the subquery eliminates child occurrences. The DISTINCT clause collapses the result set so that only unique PLAN_ID, NAME, and COLLECTION_ID combinations are returned, consistent with a view whose purpose is to enumerate plan-level integration targets rather than individual occurrences.

Key Columns

  • PLAN_ID — Identifier of the QA plan to which the electronic record belongs; joins to QA_PLANS.PLAN_ID and is the primary integration key.
  • NAME — The plan name from QA_PLANS.NAME, used for display, cross-reference, and descriptive tagging of the corresponding ERES collection.
  • COLLECTION_ID — Identifier of the electronic records collection associated with the plan result; this is the value consumed by the ERES integration layer to determine where records are filed.

Because only three columns are exposed, the view is tightly scoped and functions as a lightweight lookup rather than a detail-level reporting source.

Common Use Cases and Queries

Typical use cases include feeding an ERES integration program with the set of top-level plans that require collection assignment, reconciling which plans already possess collection IDs, and auditing plan-to-collection mappings for electronic records compliance. A representative query retrieves all integration-relevant plans, optionally filtered to those already assigned to a collection:

  • SELECT plan_id, name, collection_id FROM apps.qa_eres_integration_plans_v ORDER BY name;
  • SELECT plan_id, name, collection_id FROM apps.qa_eres_integration_plans_v WHERE collection_id IS NOT NULL;
  • SELECT name, collection_id FROM apps.qa_eres_integration_plans_v WHERE collection_id = :p_collection_id;
  • SELECT v.name, v.collection_id FROM apps.qa_eres_integration_plans_v v, apps.qa_plans p WHERE v.plan_id = p.plan_id AND p.enabled_flag = 1;

In each case the view returns only plan occurrences that are not present as CHILD_OCCURRENCE values in QA_PC_RESULTS_RELATIONSHIP, ensuring that integration routines do not duplicate child occurrences already represented under their parents. The sample SQL is grounded in the documented column list; additional joins to QA_PLANS or other QA tables can be added where plan status or organizational context is required.