Search Results p_requestor




Overview

QA_SOLUTION_CAR_PKG is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It falls under the Quality Management (QA) module, and its naming convention—QA_SOLUTION_CAR—indicates that it supports the Corrective Action Request (CAR) and solution-management functionality of Oracle Quality. In Oracle EBS, a Corrective Action Request is a formal record used to track a nonconformance, its root cause, the proposed corrective action, and the associated approval and routing workflow. The _PKG suffix and the AUTHID CURRENT_USER declaration confirm it is an invoker's-rights package, meaning that privilege checks are evaluated against the calling user rather than the package owner. This design is consistent with an internal API layer that CABC (Corrective Action Board Committee) workflow components, OAF pages, and concurrent programs invoke on behalf of a logged-in operator.

The package header carries the version stamp 120.0.12020000.2, last modified in July 2012, which places it in the 12.1.1/12.2.2 code line. Its stable signature set has been retained across both releases.

Key Procedures and Functions

The package exposes exactly two documented callable units:

  • ENG_CHANGE_ORDER — A procedure that raises and processes an engineering change order (ECO) in response to a quality-driven corrective action. Its parameters carry the change notice identifier, change type, description text, approval list, reason code, requestor, ECO department, priority code, collection identifier, occurrence, organization code, plan name, launch action, and an action-fired indicator. The routine writes the change request into the Engineering Change Order interface and coordinates the configured launch/action behavior so that the CAR can propagate into Oracle Engineering as a formal ECO.
  • ENG_CHANGE_ORDER_INT — A function that performs the same interface operation but returns a VARCHAR2 status value, allowing the caller to branch on success or failure without raising an exception. It accepts a narrower set of inputs (change notice, change type, description, approval list, reason code, requestor, ECO department, priority code, and organization code). It is typically used for validation, dry-run invocation, or when the calling form must present a result message to the user.

The split between a procedure and a function of similar purpose reflects a common EBS pattern: the procedure performs the committed interface write, while the function returns a diagnostic string for interactive or batch control flow.

Tables Accessed

The package reads and writes data through three APPS synonyms:

  • FND_USER — Resolves the requestor and approver identities supplied in the change notice, and applies the application's user-defined security context.
  • MTL_PARAMETERS — Supplies inventory/organization defaults for the organization code passed by the caller, ensuring the ECO is raised against a valid, enabled organization.
  • QA_PLANS — Determines the quality plan and collection context that govern the corrective action, linking the collection identifier and occurrence to the plan name referenced on the change order.

Usage Notes

QA_SOLUTION_CAR_PKG is an internal API, not a form-bound library in the ordinary sense. It is invoked from Oracle Quality's Corrective Action Request pages when an operator chooses to escalate a CAR into an engineering change, from the CABC approval workflow, and from any custom concurrent program or PL/SQL script that needs to programmatically create an ECO from a quality record. Because the package is AUTHID CURRENT_USER, the calling session must have the necessary privileges on MTL_PARAMETERS, QA_PLANS, and the Engineering Change Order interface tables. The referenced-by count of zero confirms that no other shipped package depends on it, so its interface may be treated as relatively self-contained. Corrective action users should note that the documentation does not expose the underlying ECO interface table names, and customization should call only the two published entry points rather than relying on internal logic.