Search Results osp_plans

Overview

QA_SS_OSP is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Quality management module and its Supplier Self-Service (SS) integration layer, which exposes quality inspection and Outside Processing (OSP) functionality to external supplier users through the Oracle iSupplier Portal (ICX) framework. The package name follows the QA_SS_ naming convention, denoting that it is one of the Quality module's Supplier Self-Service support packages rather than a callable Open Interface or public API.

The package's central business purpose is to determine whether Outside Processing plans are applicable to the supplier-facing workbench, and to convert supplier-entered OSP events into Quality collection records. It is tightly coupled to QA_SS_CORE, a sibling support package that handles common supplier self-service quality logic, and to QA_SS_CONST, which supplies the constant values used across the QA_SS_ family. The package status in the Enterprise Technical Reference Model (ETRM) is VALID, and its API classification is OTHER, indicating that it is an internally consumed component rather than a published integration API.

Key Procedures and Functions

• ARE_OSP_PLANS_APPLICABLE — Evaluates whether Outside Processing inspection plans apply to the current supplier context. This function is used to conditionally enable or disable OSP-related quality activity on the supplier workbench.
• OSP_TO_QUALITY — Performs the substantive transformation that maps Outside Processing activity into Quality collection/result data, moving supplier-entered OSP information into the Quality tables so that inspection records are created for received outside-processed items.
• DEFAULT_OSP_VALUES — Populates default values for the Outside Processing fields presented to the supplier, ensuring the collection UI is pre-seeded with standard data before submission.
• OSP_PLANS — Retrieves and returns the set of applicable Outside Processing plans, typically driving the list of plans available on the supplier-facing page.

Tables Accessed

The documented dependency list includes PO_HEADERS_ALL and PO_RELEASES_ALL, which are accessed (via APPS synonyms) to retrieve purchasing document and release information against which outside processing events are validated. PO_HEADERS_ALL supplies header-level data such as supplier, document type, and status, while PO_RELEASES_ALL provides the release-level detail needed to associate quality collections with a specific purchase order release. HTP is also listed as a referenced dependency, reflecting use of the Oracle HTML toolkit for generating supplier-facing output.

In addition, the package reads from the view WIP_ICX_OSP_WORKBENCH_V, the Work in Process supplier workbench view that exposes outside processing jobs and operations to the iSupplier Portal, and it depends on QA_SS_CORE, QA_SS_CONST, and ICX_SEC. The QA_SS_CORE and QA_SS_CONST dependencies supply shared collection logic and shared constants respectively; ICX_SEC provides the security context and session information required for a self-service user.

Usage Notes

QA_SS_OSP is not referenced by any database object according to the dependency metadata, confirming that it sits at the upper edge of the call graph. It is therefore invoked predominantly from the Oracle iSupplier Portal Outside Processing and Quality workbench pages — the flows surfaced through WIP_ICX_OSP_WORKBENCH_V — rather than from concurrent programs or public APIs.

Because the package is classified as OTHER and is not a documented public interface, customizations should not call its procedures directly. Recommended practice is to rely on the supported supplier self-service UI, or on documented Oracle Quality Open Interfaces, when integrating OSP-to-Quality processing in either Release 12.1.1 or 12.2.2. The ETRM notes that QA_SS_OSP is referenced by three other packages, reinforcing its role as a shared internal utility within the QA_SS_ supplier self-service stack.