Search Results qa_occurrence_s

Overview

QA_RESULTS_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Quality Management (QA) module, which supports inspection, sampling, and results-entry processing for manufacturing and receiving quality workflows. The package encapsulates the core data-maintenance logic required to manipulate disposition records held in the QA_RESULTS table, including the insert, update, lock, and delete operations associated with those results. It also interacts with QA_OCCURRENCE_S, the sequence-backed table that supplies surrogate primary key values for QA entities. The package is classified as OTHER within the documented API taxonomy, meaning it is not a published, externally supported interface such as an OPEN or PL/SQL API, but rather an internal implementation component. The ETRM metadata records its status as VALID at version 12.1.1 and 12.2.2, confirming that the body compiles cleanly against those releases. Notably, the object is not referenced by any other database object, and its four documented procedures are its only exposed entry points.

Key Procedures and Functions

Four procedures are documented for this package, all following the naming convention used by Oracle Forms-generated and Oracle Designer-generated table handlers:

• INSERT_ROW — Creates a new row in QA_RESULTS. It is the entry point for recording a fresh inspection or disposition result, and it is responsible for obtaining the next primary key value from the QA_OCCURRENCE_S sequence before the row is written.
• LOCK_ROW — Acquires a row-level lock on a specific QA_RESULTS record. This supports the read-modify-write pattern used by forms and batch processes to prevent concurrent modification of the same result row.
• UPDATE_ROW — Applies changes to an existing QA_RESULTS row, such as revised disposition codes, quantities, or status flags. It is typically preceded by LOCK_ROW to enforce optimistic or pessimistic concurrency control.
• DELETE_ROW — Removes a QA_RESULTS record, allowing correction or cancellation of incorrectly captured results during data cleanup or re-inspection.

The exact parameter lists are not enumerated in the available metadata and are therefore not reproduced here.

Tables Accessed

Three tables are documented as dependencies, each accessed through APPS synonyms:

• QA_RESULTS — The primary target of all four procedures. It stores the inspection outcome and disposition data that the package creates, locks, modifies, and deletes.
• QA_OCCURRENCE_S — A sequence used to generate unique surrogate keys for new rows. This is the object most directly associated with the searched term "qa_occurrence_s", and it explains why QA_RESULTS_PKG appears in that search context.
• DUAL — The standard Oracle single-row utility table, consulted for sequence-currency checks or simple scalar expression evaluation during key retrieval.

All access is performed under the APPS schema, so privileges and synonyms are resolved consistently across the EBS instance.

Usage Notes

Because QA_RESULTS_PKG is not referenced by any other database object, it is not an internally chained dependency of other server-side code. Its documented role and the presence of the Designer-style table handler procedures indicate that it is invoked primarily from Oracle Forms in the Quality Management module, where result-entry blocks call INSERT_ROW, LOCK_ROW, UPDATE_ROW, and DELETE_ROW in the standard POST-INSERT, ON-LOCK, POST-UPDATE, and ON-DELETE triggers. It may also be called from concurrent programs or custom PL/SQL that performs bulk result maintenance, although the OTHER classification means such use is unsupported and carries upgrade risk. The package additionally references APP_EXCEPTION and FND_MESSAGE, which indicates that error conditions are raised through the EBS message dictionary and the application exception framework rather than raw Oracle errors. Implementers extending or diagnosing QA results behavior should treat this package as an internal construct, prefer supported APIs where available, and re-validate any direct calls after patching between 12.1.1 and 12.2.2.