Search Results ship_partial_allowed




Overview
Explore in AI Chat

Overview

APPS.OE_AK_SHIP_PARTIAL_V is a dictionary-defined view in the Oracle E-Business Suite Order Management (ONT) schema, registered in FND Design Data as ONT.OE_AK_SHIP_PARTIAL_V. It belongs to the family of "AK" attribute/validation views used by Oracle Application Framework region definitions and the order-entry lookups mechanism. Its sole purpose is to expose the value of the SHIP_PARTIAL_ALLOWED profile-like setting in a form consumable by OA Framework pages and by PL/SQL utilities that must govern whether an order, line, or delivery may be shipped in partial quantities. In the 12.1.1 and 12.2.2 releases the view remains VALID and unchanged in definition, its output being a single VARCHAR2(30) column. Because the object is documented by Oracle as Internal Use Only, direct customer access is unsupported; it must be queried only through standard Oracle Applications programs or for read-only diagnostic purposes.

Underlying Base Objects

The documented dependency list is deliberately narrow. The view is defined over two base objects in the APPS schema:

  • FND_GLOBAL (PACKAGE) — the standard EBS context package supplying runtime session attributes such as ORG_ID, USER_ID, RESP_ID and APPLICATION_ID. It is used to resolve the correct operating unit and application context at query time so that the returned shipping-partial flag reflects the caller's current session.
  • FND_LOOKUPS (VIEW) — the reference lookup view over FND_LOOKUP_TYPES and FND_LOOKUP_VALUES. The shipped-partial-allowed value is derived from a lookup definition rather than a dedicated table, which is why the view presents a single denormalised column instead of joining transactional shipping entities.

The view is in turn referenced by APPS.ONT_SHIP_PARTIAL_DEF_UTIL (documented twice, for both the specification and body variants in ETRM), which is the Order Management utility package that consumes SHIP_PARTIAL_ALLOWED when defaulting ship-set and delivery behaviour during shipping and pick-release processing. This narrow chain — FND_GLOBAL and FND_LOOKUPS feeding the view, and the view feeding ONT_SHIP_PARTIAL_DEF_UTIL — confirms its role as a lightweight configuration accessor rather than a reporting view over order data.

Key Columns

The view exposes exactly one column:

  • SHIP_PARTIAL_ALLOWED (VARCHAR2(30)) — the resolved setting indicating whether partial shipment is permitted. It is not mandatory at the column level (no NOT NULL constraint is documented), so callers should be prepared for a NULL result when no lookup row is effective for the current context. Typical values are the lookup meanings or codes maintained for the ship-partial-allowed lookup type; the exact coded values are installation-dependent and are governed by the lookup seeded in FND_LOOKUPS.

No other columns are documented. There are no identifiers, dates, or organisation attributes exposed directly, indicating the view is designed for a single scalar fetch rather than set-based reporting.

Common Use Cases and Queries

The principal supported use case is internal resolution of the partial-shipping default by ONT_SHIP_PARTIAL_DEF_UTIL during order shipping cycles. Customers and integrators most commonly encounter the view when diagnosing why a delivery was split, why remaining quantities were backordered, or why a ship-set was consolidated. A diagnostic query is straightforward:

  • SELECT SHIP_PARTIAL_ALLOWED FROM APPS.OE_AK_SHIP_PARTIAL_V; — retrieves the effective partial-shipping setting for the current session context.
  • Wrapping the query within an FND_GLOBAL initialisation, for example after calling FND_GLOBAL.APPS_INITIALIZE for the target operating unit and responsibility, ensures the correct organisation-scoped value is returned.
  • Comparing the result against SELECT * FROM FND_LOOKUPS WHERE LOOKUP_TYPE LIKE '%SHIP_PARTIAL%'; helps validate that the underlying lookup rows are correctly defined and enabled for the responsibility.

Because the view is flagged Oracle Internal Use Only, it should not be embedded in custom reports, concurrent programs, or interfaces intended for production support. It is best treated as a troubleshooting aid: confirm the returned value, reconcile it with the lookup configuration, and rely on supported Order Management APIs and profile options for any functional change to partial-shipment behaviour.