Results for “default_ship_values”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QA_SS_SHIP is a member of the Oracle Quality "Self-Service" (QA_SS) family of packages, delivered under the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its business purpose is to support supplier-facing quality and shipping plan data in the Oracle iSupplier Portal and associated Procurement views. The package exposes functions that the purchasing and receiving view layer (for example, the ICX shipment view referenced in the source comments) uses to determine whether shipping-plan rules apply to a given purchase order line, and to derive default shipping values for shipments that flow into the supplier self-service channel. In practical terms, it bridges Purchasing shipment data in PO_HEADERS_ALL and PO_RELEASES_ALL with Quality collection-plan logic, allowing the application to decide moment-by-moment whether a shipment is subject to a quality/shipping plan. The ETRM classification is "OTHER," reflecting that this is an internal supporting package rather than a public, published API. Because it is invoked from within view definitions, the code is called implicitly whenever the view is queried, rather than through an explicit user action.

Key Procedures and Functions

  • ARE_SHIP_PLANS_APPLICABLE — Determines whether shipping-plan rules are applicable to a shipment, given identifying context such as the purchase order, line, release, shipment, ship-to location, supplier item, ordered quantity, unit of measure, vendor, vendor site, organization, item, item revision, and item category. It returns a VARCHAR2 result and is the primary entry point used by the shipment view to decide whether plan evaluation should proceed. The source notes a design limitation: an additional organization ID parameter was deferred to improve performance, and a view change would be required to pass it.
  • SHIP_TO_QUALITY — Creates or associates the quality/shipping record tied to a shipment, completing the hand-off from shipping plan determination into the Quality collection stream.
  • DEFAULT_SHIP_VALUES — Populates default shipping attribute values for a shipment, providing the baseline data used when a supplier records or confirms shipment details.
  • SHIPPING_PLANS — Retrieves the applicable shipping plan definitions that govern how a given shipment must be handled, supplying the plan detail consumed by the other routines and by the calling view.

All four are documented as functions/procedures within the package. Parameter lists are not reproduced here; only the demonstrated ARE_SHIP_PLANS_APPLICABLE signature is visible in the source excerpt, and remaining signatures should be confirmed against the shipped source.

Tables Accessed

  • PO_HEADERS_ALL — Supplies purchase order header context (PO number, vendor, vendor site) used when evaluating shipping-plan applicability.
  • PO_RELEASES_ALL — Supplies release-level detail so that plan rules can be resolved for blanket and planned orders.
  • HTP — The HTML/PLSQL toolkit package used for rendering supplier-portal output, indicating that part of the processing feeds web page generation in iSupplier Portal.

In addition, the source excerpt shows a cursor querying INV_ORGANIZATION_NAME_V to resolve an organization name to an organization ID (case-insensitive match), replacing the earlier ORG_ORGANIZATION_DEFINITIONS query as part of a SQL repository fix. The commented code and Bug 4958773 reference confirm this was a deliberate performance/correctness change.

Usage Notes

QA_SS_SHIP is not intended for direct invocation by end users or custom code. It is referenced by three other packages and is called implicitly as part of the shipment view definition in the supplier self-service layer. Because the functions execute inside a view, they run with the privileges of the querying session against APPS synonyms, and organization resolution occurs at query time. Update level information (qltssshb.plb 120.2) indicates the object was last revised in 2006, so behavior is stable across 12.1.1 and 12.2.2. Customizations should avoid modifying the package body and should instead extend the calling views or wrap the logic, since the deferred organization-ID parameter noted in the source implies the current interface may be revised in a future release.