Results for “qa_solution_car_pkg”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.QA_SOLUTION_CAR_PKG package body is a Quality Management module component within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It provides the server-side PL/SQL implementation for creating and managing Engineering Change Orders (ECOs) that arise during the resolution of quality issues. In the Oracle Quality schema, a "solution" defines the corrective or preventive action taken in response to a nonconformance or defect captured on a collection plan. When that solution requires a formal engineering change, this package supplies the programmatic entry point for raising the corresponding ECO record and linking it back into the quality workflow.
Per the header annotation, the file was created in 2007 and shipped as qasocorb.pls, script version 120.0.12000000.2. It is owned by the APPS schema and classified as an OTHER API within the ETRM repository. The package depends on the Oracle Quality plan infrastructure and standard application utilities to resolve organization, plan, and user context before performing its core work.
Key Procedures and Functions
The ETRM metadata documents two public procedures or functions in the package specification:
ENG_CHANGE_ORDER— The primary public API for creating a new Engineering Change Order from a quality solution context. It is designed to accept identifying details for the ECO and the quality plan against which the change is raised, then persist the ECO through the appropriate underlying engineering tables. Parameter names visible in the source excerpt includep_change_notice,p_change_type,p_description,p_approval_list,p_requestor,p_eco_department,p_reason_code,p_priority_code,p_collection_id,p_occurrence, andp_plan_name.ENG_CHANGE_ORDER_INT— An internal or integration counterpart to the main procedure. It is typically invoked from dependent logic or batch processes that must instantiate an ECO while sharing common validation and lookup resolution with the public entry point.
Supporting private routines include get_mfg_lookups_value, get_organization_id, and get_plan_id. These handle lookup-code translation and context resolution for the public APIs. Package constants define standardized status and yes/no values (g_success, g_failed, g_warning, g_lookup_yes, g_lookup_no). A 2007 modification replaced numeric lookup codes with the VARCHAR2 literals 'YES' and 'NO', removing the dependency on mfg_lookups for these values.
Tables Accessed
The documented table dependencies are:
FND_USER— Used to resolve and validate the requestor or operating user associated with the ECO.MTL_PARAMETERS— Read to determine the inventory organization context, since engineering changes are organization-specific.QA_PLANS— Referenced to validate the collection plan identified byp_plan_nameand to tie the ECO to the quality plan under which the issue was raised.
The package directly manipulated ECO records in the underlying engineering change tables; the three tables above represent the documented access set surfaced by ETRM, and additional engineering schema objects are implied by the ECO creation logic.
Usage Notes
This package is normally invoked from Oracle Quality solution or collection plan processing, particularly when a corrective action escalates to a formal engineering change. It may be called from a concurrent program, from Oracle Forms triggers on the Quality solution screen, or from custom PL/SQL that automates ECO creation from quality data. Callers must supply or permit resolution of the organization, plan, and requestor context. Because the package is owned by APPS and exposes a public API classification, custom code should call the packaged procedures rather than inserting into the underlying tables directly. The referenced-by count of zero indicates no other packaged object in the documented set depends on it.
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.QA_PLANS 12.2.2
-
SYNONYM: APPS.QA_PLANS 12.1.1
-
VIEW: APPS.MFG_LOOKUPS 12.2.2
-
VIEW: APPS.MFG_LOOKUPS 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
SYNONYM: APPS.FND_USER 12.2.2
-
SYNONYM: APPS.FND_USER 12.1.1
-
eTRM - PO Tables and Views 12.1.1
Temporary table for tracking a receiving upgrade from Release 9 to Release 10
-
eTRM - INV Tables and Views 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - PO Tables and Views 12.1.1
Temporary table for tracking a receiving upgrade from Release 9 to Release 10