Search Results get_shipment_number

Overview

OE_DEFAULT_LINE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its status is VALID, and it is classified as an "OTHER" API within the Oracle Order Management (OM) module. The package encapsulates the defaulting logic used throughout the order capture and order maintenance flow. When a user enters an order line in the Sales Orders form or when order lines are created programmatically through public APIs such as OE_ORDER_PUB, a substantial number of attributes must be derived rather than manually entered: item type, unit of measure conversions, freight carrier, blanket agreement references, invoice line linkage, shipment numbering, and descriptive flexfield context values.

OE_DEFAULT_LINE centralizes those derivation rules so that defaulting behavior remains consistent whether an order is created interactively, imported through Order Import, copied, split, configured, or generated by a service or retrofit billing process. It depends on OE_ORDER_PUB, meaning it operates in concert with the public order interface rather than bypassing it, and it relies on FND_STANDARD (SYS.STANDARD) for standard date and utility handling.

Key Procedures and Functions

ETRM documents sixteen procedures and functions. The primary accessors are:

• GET_LINE and RETURN_ATTRIBUTES — retrieve a line record and its associated attribute set, supporting the defaulting cycle.
• ATTRIBUTES, ATTRIBUTES_FROM_INVOICE_LINE, and ATTRIBUTES_FROM_ORDER_LINE — populate default attribute collections, with specialized variants that source values from an existing invoice line or an existing order line (used during copy and return/credit flows).
• GET_LINE_NUMBER and GET_SHIPMENT_NUMBER — generate the next line and shipment sequence values within the order context.
• GET_DEFAULTING_ORDER_LINE, GET_DEFAULTING_INVOICE_LINE, and GET_DEF_INVOICE_LINE_INT — identify the source line from which defaults should be inherited, including the internal routine used for invoice-line defaulting.
• GET_DUAL_UOM — resolves dual unit of measure defaults, supporting primary and secondary UOM processing.
• GET_ITEM_TYPE — determines whether an item is a standard, model, kit, option, or service item, which drives downstream configuration and pricing behavior.
• GET_FREIGHT_CARRIER — derives the applicable freight carrier for the line.
• GET_BLANKET_NUMBER_SVC_CONFIG and DEFAULT_BLANKET_VALUES — resolve blanket purchase agreement references, including values for service and configuration lines.
• INSERT_INTO_SET — inserts a line into the appropriate OE_LINE_SETS grouping.

Tables Accessed

Access is performed through APPS synonyms. Order-management tables include OE_BLANKET_HEADERS, OE_BLANKET_HEADERS_ALL, OE_BLANKET_HEADERS_EXT, OE_BLANKET_LINES, OE_BLANKET_LINES_ALL, OE_BLANKET_LINES_EXT (blanket agreement sourcing), OE_DEF_CONDN_ELEMS (defaulting condition elements), OE_LINE_SETS (line grouping), and OE_LOT_SERIAL_NUMBERS (lot and serial defaulting). Inventory and item data come from MTL_SYSTEM_ITEMS and MTL_ITEM_CATEGORIES, with MTL_MATERIAL_TRANSACTIONS supporting transaction-linked defaulting. Customer data is sourced from HZ_CUST_ACCOUNTS and HZ_PARTIES, and multilingual lookups from FND_LANGUAGES.

Usage Notes

OE_DEFAULT_LINE is not typically invoked directly by end users. It is called internally by the order entry forms, by Order Import and the public OE_ORDER_PUB API stack, and by eleven documented dependent packages including OE_ORDER_PVT, OE_CONFIG_PVT, OE_ADV_PRICE_PVT, OE_SPLIT_UTIL, OE_SCHEDULE_UTIL, OE_SERVICE_UTIL, OE_SET_UTIL, OE_RETROBILL_PVT, OE_CONFIG_PRICE_UTIL, OE_CONFIG_SCHEDULE_PVT, and OE_LINE_UTIL_EXT. Because the package is referenced by so many internal components, customers should not modify it directly; enhancements should use the documented extension points such as OE_LINE_UTIL_EXT to preserve upgrade safety in 12.1.1 and 12.2.2.