Results for “wf_role_name”

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

Overview

The QA.QA_SAMPLING_ASSOCIATION table is an Oracle E-Business Suite Quality (QA) module object that stores the association between skip lot/sampling criteria and the sampling plans applied to them. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the configuration link that determines which sampling plan is used when a given sampling or skip-lot criterion is evaluated during inspection, receiving, or collection processing. Its status is VALID in the QA schema and it is documented as containing 11 columns in the 12.2.2 physical schema.

From a data-modeling perspective, ETRM metadata classifies this object heuristically as a link (Data Vault classification). This is a modeling suggestion rather than a physical implementation: the table resolves a many-to-many-style relationship between criteria, sampling plans, and collection (test) plans, and it is therefore best understood as an intersection or association entity rather than a transactional fact or a standalone hub.

Key Information Stored

The table holds the configuration records that bind criteria to plans, along with effectivity and audit columns. The most important columns are:

• CRITERIA_ID — Foreign key to QA_SL_SP_RCV_CRITERIA; identifies the skip lot/sampling/receiving criterion being associated.
• SAMPLING_PLAN_ID — Foreign key to QA_SAMPLING_PLANS; identifies the sampling plan applied when the criterion is met.
• COLLECTION_PLAN_ID — Foreign key to QA_PLANS; identifies the associated collection (test) plan.
• WF_ROLE_NAME — Workflow role name used for notification or approval routing in the QA workflow context.
• EFFECTIVE_FROM — Start date from which the association is active.
• EFFECTIVE_TO — End date on which the association ceases to be active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS who/audit columns.

No separate surrogate primary key column is documented in the ETRM excerpt; the combination of the foreign keys (notably CRITERIA_ID with SAMPLING_PLAN_ID and effectivity dates) functions as the business-key candidate identifying a unique association record. The three FK columns — CRITERIA_ID, SAMPLING_PLAN_ID, and COLLECTION_PLAN_ID — are the principal join keys to related tables.

Common Use Cases and Queries

Typical usage centers on resolving which sampling plan applies to a given criterion, validating effective-dated configuration, and auditing plan usage.

• Resolving the sampling plan for a criterion:

  SELECT a.criteria_id, a.sampling_plan_id, a.collection_plan_id, a.effective_from, a.effective_to
  FROM   qa.qa_sampling_association a
  WHERE  a.criteria_id = :criteria_id
  AND    SYSDATE BETWEEN a.effective_from AND NVL(a.effective_to, SYSDATE);

• Joining to the sampling plan definition:

  SELECT a.criteria_id, p.*
  FROM   qa.qa_sampling_association a, qa.qa_sampling_plans p
  WHERE  a.sampling_plan_id = p.sampling_plan_id;

• Reporting active associations by effectivity window and workflow role for configuration audits.

Related Objects

• QA_SL_SP_RCV_CRITERIA — joined on CRITERIA_ID; source of the skip lot/sampling/receiving criteria.
• QA_SAMPLING_PLANS — joined on SAMPLING_PLAN_ID; the sampling plan definition.
• QA_PLANS — joined on COLLECTION_PLAN_ID; the collection/test plan definition.
• Additional QA inspection and receiving plan tables that consume sampling criteria during inspection creation.
• QA workflow/notification components that reference WF_ROLE_NAME.