Results for “accepted_date”

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

Overview

APPS.OE_QUERY is a VALID PL/SQL package body in the Oracle E-Business Suite Order Management (OM) module. As its name implies, it provides the query and derived-attribute layer used throughout Order Management to resolve transactional facts about orders, lines, and schedules without exposing callers to the underlying table joins. Rather than acting as a transactional API that inserts or updates order data, OE_QUERY is a read-oriented utility package: it returns calculated values such as line totals, reserved and released quantities, hold status, configuration indicators, and scheduling information for a given order, line, or shipment context.

Because it is a package body that is not referenced by any other database object per the metadata, its consumers are application-tier code — Oracle Forms, concurrent programs, and other OM packages — rather than database views or triggers. The package is a foundational dependency: twelve other packages reference it, indicating it is embedded in the standard order-entry and shipping flows shipped with EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented interface exposes 56 procedures and functions. The principal ones include:

• LINE_TOTAL / SERVICE_TOTAL / CONFIGURATION_TOTAL — aggregate monetary values for a line, a service line, or a configured (ATO/PTO) item, used for order and line pricing display.
• SCHEDULE_STATUS / II_SCHEDULE_STATUS_CODE — return the scheduling state of a line or its inventory interface equivalent.
• ATO_INDICATOR / GET_ATO_INDICATOR — determine whether an item is an Assemble-to-Order or Pick-to-Order configuration.
• RELEASED_QUANTITY / P_LINE_RELEASED_QUANTITY — report the quantity already released to inventory for a line and its picking line.
• II_RESERVED_QUANTITY / II_RELEASED_QUANTITY / RESERVED_QUANTITY — expose reserved and released quantities, including the inventory interface view of those values.
• HOLD — indicates whether an order or line is currently on hold.
• SHIPMENT_NUMBER / LINE_NUMBER / ORDER_TYPE / SOURCE_ORDER_NUMBER / SOURCE_ORDER_TYPE — resolve descriptive attributes for a given entity identifier.
• ITEM_CONC_SEG — returns the concatenated item segment description for a line.
• SUPPLY_RES_DETAILS — retrieves supply reservation detail for a line.

Tables Accessed

The package reads from APPS synonyms across order, pricing, inventory, and receivables tables. Order structure comes from SO_HEADERS, SO_LINES, SO_LINE_DETAILS, SO_ORDER_TYPES, and SO_ORDER_HOLDS_ALL. Fulfilment and supply data are drawn from SO_PICKING_LINES, SO_PICKING_LINE_DETAILS, SO_RESULTS, MTL_DEMAND_INTERFACE, MTL_SO_RMA_INTERFACE, and MTL_SO_RMA_RECEIPTS. Item and lot information is resolved through MTL_SYSTEM_ITEMS_KFV and MTL_LOT_NUMBERS. Pricing and tax values come from SO_PRICE_ADJUSTMENTS and TAX_EXEMPTIONS_QP_V, while financial context is obtained from AR_PAYMENT_SCHEDULES and RA_CUSTOMER_TRX_LINES. Lookup decoding uses SO_LOOKUPS and AR_LOOKUPS, and organizational context uses HR_OPERATING_UNITS. FND_MESSAGE and FND_REQUEST support messaging and concurrent request submission.

Usage Notes

OE_QUERY is typically invoked indirectly. The Oracle Order Management forms (Sales Order, Shipping, and Returns) call these functions to populate calculated fields and status indicators on the order line and shipment windows. Concurrent programs processing order imports, pick release, and shipping confirmation also use it to obtain consistent, business-rule-compliant values. Custom extensions and reports may call OE_QUERY directly when they require the same calculations, but because its interface is not formally an API, direct calls should be limited and validated against the target release. The presence of FND_MESSAGE and FND_REQUEST dependencies indicates the package also performs message lookup and, in at least one path, submits a concurrent request.