Search Results get_version_number




Overview
Explore in AI Chat

Overview

APPS.OE_DEFAULT_HEADER is a defaulting engine that supports Oracle Order Management (OM) in Oracle E-Business Suite 12.1.1 and 12.2.2. It is invoked by the Order Management order-capture flow to derive or validate header-level attribute values on an order or return before that data is written to the transactional tables. The package operates on the public API record type OE_ORDER_PUB.Header_Rec_Type, applying the "old" record (the persisted or previously entered value set) against the incoming record to decide whether dependent defaults must be re-evaluated.

The package is registered in ETRM under owner APPS with an API classification of OTHER, confirming that it is an internal supporting package rather than a published, customer-callable API. Its source header identifies a shipment at version 120.3.12010000.2 (2010/04/06), which places it in the 11i10/12.0 lineage carried forward into 12.1.1 and 12.2.2. The body maintains a global constant G_PKG_NAME and a global row variable G_HEADER_REC typed against OE_AK_ORDER_HEADERS_V, and it honors OE_DEBUG_PUB.G_DEBUG_LEVEL, emitting trace messages via OE_DEBUG_PUB.ADD when debugging is enabled.

Key Procedures and Functions

ETRM documents one entry point for this package: ATTRIBUTES. The package body additionally exposes GET_FREIGHT_CARRIER, which returns a VARCHAR2 freight carrier code and is the primary defaulting routine visible in the archived source.

  • ATTRIBUTES — The documented public entry point. It is the routine the Order Management defaulting framework calls to populate or refresh header-level attributes on the order header record. As the only entry listed in the ETRM metadata, it constitutes the supported interface surface for this package.
  • GET_FREIGHT_CARRIER — Derives the freight carrier code for a header. It accepts the incoming header record and the prior header record. If the shipping method code and ship-from organization are both present and not FND_API.G_MISS sentinels, and if any of shipping_method_code, ship_from_org_id, or freight_carrier_code differ from the old record (compared through OE_GLOBALS.EQUAL), it resolves the carrier. For code release level 110509 or later it queries WSH_CARRIERS, WSH_CARRIER_SERVICES, and WSH_ORG_CARRIER_SERVICES joined on organization, carrier service, and ship method with enabled_flag = 'Y'; for older release levels it falls back to WSH_CARRIER_SHIP_METHODS. This logic originates from fixes recorded as Performance Issue 2830725 and bug 3610480.

Tables Accessed

The package reads and writes the Order Management header tables OE_ORDER_HEADERS_S, OE_BLANKET_HEADERS, and OE_BLANKET_HEADERS_EXT, which hold the sales order and blanket agreement header attributes subject to defaulting. Customer context is resolved through HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_SITE_USES. Condition and pricing defaulting uses OE_DEF_CONDN_ELEMS, and OE_XML_MESSAGE_SEQ_S supports message sequencing. Carrier resolution depends on the shipping execution tables WSH_CARRIERS, WSH_CARRIER_SERVICES, WSH_CARRIER_SHIP_METHODS, and WSH_ORG_CARRIER_SERVICES. DUAL is used for scalar expressions.

Usage Notes

OE_DEFAULT_HEADER is invoked internally by Order Management during order entry and order import, rather than being called directly by end users. It is referenced by one other package, consistent with a layered internal dependency. Customizations should avoid calling it directly; preference should be given to the supported Order Management public APIs in OE_ORDER_PUB.

Regarding the search term "get_version_number": no procedure or function of that name exists in this package or in its documented metadata. In Oracle EBS, version identification for a PL/SQL object is normally obtained from the source header revision string (here 120.3.12010000.2), from FND_OBJECTS/FND_FORM_FUNCTIONS registration metadata, or from the AD_* file version tables. Verification of the installed version for OE_DEFAULT_HEADER should therefore be performed through those mechanisms rather than through a package entry point.