Results for “qa_skiplot_rcv_criteria_val_v”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
QA_SKIPLOT_RCV_CRITERIA_VAL_V is an APPS-owned database view in the Oracle E-Business Suite Quality (QA) module. It exposes the set of valid skip lot criteria that apply to the receiving process, providing a denormalized, query-ready representation of skip lot rules and their associated parameters. In Oracle EBS 12.1.1 and 12.2.2, skip lot inspection allows an organization to reduce the frequency of incoming inspection for items, vendors, or combinations thereof that have demonstrated consistent quality. The receiving function must be able to determine, at the time a receipt is processed or inspected, whether a given transaction falls under an active skip lot rule and, if so, at which inspection stage the skip should take effect. This view serves as the integration and reporting surface for that determination.
Because it consolidates skip lot association attributes (effective dates, lot size ranges, workflow role, inspection stage) with the receiving criteria attributes (organization, vendor, item, revision, category, manufacturer, project, task), the view is well suited to inbound inspection planning, quality reporting, and any custom logic that must replicate the standard skip lot lookup performed by Oracle Quality and Purchasing/Receiving.
Underlying Base Objects
The view is defined with a simple equijoin over two APPS synonyms:
- QA_SL_SP_RCV_CRITERIA (QSSRC) — supplies the receiving-specific criteria attributes such as ORGANIZATION_ID, VENDOR_ID, VENDOR_SITE_ID, ITEM_ID, ITEM_REVISION, ITEM_CATEGORY_ID, MANUFACTURER_ID, PROJECT_ID, and TASK_ID, together with CRITERIA_ID and the standard WHO columns.
- QA_SKIPLOT_ASSOCIATION (QSLA) — supplies the skip lot rule parameters: PROCESS_ID, EFFECTIVE_FROM, EFFECTIVE_TO, LOTSIZE_FROM, LOTSIZE_TO, WF_ROLE_NAME, and INSP_STAGE.
The join condition is QSSRC.CRITERIA_ID = QSLA.CRITERIA_ID, so each row represents one skip lot association linked to a receiving criteria definition. The view therefore inherits the grain of QA_SKIPLOT_ASSOCIATION restricted to those criteria that are established for receiving. No aggregation or filtering beyond the join is applied in the view text, which means callers are responsible for applying effective-date and lot-size window predicates appropriate to their context.
Key Columns
- CRITERIA_ID — identifier linking a receiving criteria record to its skip lot association; the principal join key.
- PROCESS_ID — the skip lot process to which the association belongs.
- ORGANIZATION_ID — inventory organization in which the skip lot rule is effective.
- VENDOR_ID / VENDOR_SITE_ID — supplier and supplier site scope of the criteria.
- ITEM_ID / ITEM_REVISION / ITEM_CATEGORY_ID / MANUFACTURER_ID — item-level and category-level scope, including manufacturer where applicable.
- PROJECT_ID / TASK_ID — project and task scope for project-driven receiving.
- EFFECTIVE_FROM / EFFECTIVE_TO — the validity window of the skip lot association.
- LOTSIZE_FROM / LOTSIZE_TO — the receipt lot size range (the searched term lotsize_to corresponds to the upper bound) within which the rule applies.
- WF_ROLE_NAME — workflow role associated with the skip lot process.
- INSP_STAGE — the inspection stage at which the skip decision is applied.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
Common Use Cases and Queries
Typical usage includes resolving which skip lot rules apply to a receipt, validating lot size ranges during inspection planning, and building quality dashboards. A representative query joining the view to receipt context might be:
- Retrieve active rules for a vendor/item at a point in time, filtering on EFFECTIVE_FROM <= SYSDATE and (EFFECTIVE_TO IS NULL OR EFFECTIVE_TO >= SYSDATE).
- Identify the applicable lot size band using LOTSIZE_FROM and LOTSIZE_TO around a known receipt quantity.
- Report skip lot criteria by organization and inspection stage for audit or compliance review.
Sample SQL:
SELECT criteria_id, organization_id, vendor_id, item_id,
effective_from, effective_to, lotsize_from, lotsize_to, insp_stage
FROM apps.qa_skiplot_rcv_criteria_val_v
WHERE organization_id = :org_id
AND vendor_id = :vendor_id
AND item_id = :item_id
AND SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE)
AND :qty BETWEEN lotsize_from AND lotsize_to;
Because the view is a thin projection over the two base synonyms, custom code should treat it as read-only reference data and avoid DML. For 12.2.2 online patching environments, querying through the APPS synonym ensures editioning is handled transparently.
-
Valid Skip Lot criteria for Receiving
APPS.QA_SKIPLOT_RCV_CRITERIA_VAL_V·↳ QA_SKIPLOT_ASSOCIATION·↳ QA_SL_SP_RCV_CRITERIA·Explore QA module →
-
Valid Skip Lot criteria for Receiving
APPS.QA_SKIPLOT_RCV_CRITERIA_VAL_V·↳ QA_SKIPLOT_ASSOCIATION·↳ QA_SL_SP_RCV_CRITERIA·Explore QA module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction