Search Results get_default_source_type




Overview
Explore in AI Chat

Overview

OE_DEFAULT_SOURCE_TYPE_PVT is a private (PVT-classified) PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle Order Management (OE) module and is responsible for resolving the default source type for an order line based on the sourcing rules defined for the item, the order cycle, the line type, and the associated warehouse. In Oracle Order Management, the "source type" determines how a line is fulfilled — for example, from internal inventory, from an external supplier, or through a drop-ship arrangement. The package encapsulates the logic that decides which of those sourcing modes applies when a user enters or manipulates an order line.

The package is classified as PVT, meaning it is an internal implementation package rather than a public, supported API. Its single entry point, GET_DEFAULT_SOURCE_TYPE, is called by other Order Management components — forms, business logic, or public APIs — rather than by external customers directly. The package header carries the original CVS identifier OEXVDSTS.pls 115.0 99/07/16, indicating the source has been stable since the late 1990s and carried forward through the 12.x code lines.

Key Procedures and Functions

The package exposes exactly one documented procedure, GET_DEFAULT_SOURCE_TYPE. It is declared with the default AUTHID CURRENT_USER, so it executes with the privileges of the calling user, consistent with APPS-schema standards.

  • GET_DEFAULT_SOURCE_TYPE — Determines and returns the default source type for a given order line context. It accepts an API version indicator and identifiers/attributes describing the line (item, cycle, line type, option flag, item type, and optionally a warehouse), and returns the standard Order Management API status triple (return status, message count, and message data) along with the resolved source type value and its internal server identifier. Callers use the returned source type to populate the line's sourcing attribute and to drive downstream fulfillment processing.

The procedure follows the conventional EBS API signature pattern of paired IN parameters, a standard OUT status triple (P_Return_Status, P_Msg_Count, P_MSG_Data), and business-specific OUT value parameters. The warehouse parameter is defaulted to null, allowing the caller to omit it when warehouse context is not relevant to the sourcing decision.

Tables Accessed

The package reads from two documented tables through APPS synonyms:

  • MTL_SYSTEM_ITEMS — The master item definition table in Oracle Inventory. The package uses it to validate the item and to retrieve item-level attributes that influence sourcing, such as whether the item is internally or externally sourced, purchased, or associated with specific planning and sourcing rules.
  • SO_CYCLE_ACTIONS — The Order Management cycle action definition table. This table holds the actions and processing rules associated with an order cycle. The package consults the cycle actions to determine the appropriate sourcing behavior based on the cycle and line type under which the line is being processed.

No insert, update, or delete activity is documented; the package's role is consultative, returning a derived value rather than persisting data.

Usage Notes

Because OE_DEFAULT_SOURCE_TYPE_PVT is a private package, it is not exposed as a documented public API and Oracle does not guarantee its signature across upgrades. It is typically invoked from Order Management forms and internal business logic, specifically within the order line entry and defaulting flow. When a user creates or modifies an order line, the form calls GET_DEFAULT_SOURCE_TYPE to populate the source type field based on the item, cycle, line type, and warehouse context.

Developers who need equivalent behavior should prefer supported public APIs such as OE_ORDER_PUB or the Order Management line defaulting APIs rather than calling this private package directly. Custom code that does reference GET_DEFAULT_SOURCE_TYPE must be prepared to handle the standard API status triple and must account for the possibility that the signature changes between patch levels. The package is not referenced by any other documented packages, confirming its role as a leaf-level utility invoked from the application layer rather than a shared library routine.