Results for “set_rowlimit”

4 results




Overview
Explore in AI Chat

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

Overview

APPS.INV_OBJECT_GENEALOGY is a public PL/SQL package in Oracle E-Business Suite that supports object genealogy and traceability within Oracle Inventory. The package resolves relationships between inventory objects — items, lots, serial numbers, WIP entities, and related transaction entities — and exposes that information to callers such as inventory forms, WIP serial tracking logic, and custom extensions. It is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner.

The package is central to the R12 Lot Serial Genealogy project, which extended traceability by returning additional context such as the current lot number, WIP entity, operation sequence number, and intraoperation step type. It is classified under ETRM as an "OTHER" API and is referenced by eight other packages, confirming its role as a shared utility within the Inventory and manufacturing data model.

Key Procedures and Functions

  • GETOBJECTTYPE — Returns the numeric object type classification for a supplied object ID, allowing callers to determine whether an identifier represents a lot, serial number, or another tracked entity.
  • GETOBJECTNUMBER — Retrieves the display number associated with an object, optionally accepting a secondary object ID and type to support composite or related-object lookups.
  • GETOBJECTINFO — The principal retrieval routine, provided as two overloads. The base version returns object name, description, type name, expiration date, primary UOM, inventory item ID, object number, material status, and unit number. The overloaded version adds WIP-related outputs: WIP entity ID, operation sequence number, intraoperation step type, and the current lot number introduced by the Lot Serial Genealogy project.
  • GETSOURCE — Returns source information associated with a genealogy object or transaction.
  • GETTRADINGPARTNER — Resolves the trading partner associated with a transaction, drawing on customer and party data.
  • GETTRANSACTIONINFO — Provides transaction-level detail for genealogy records.
  • INIT — Initializes package state or internal structures prior to genealogy processing.
  • INV_POPULATE_CHILD_TREE — Populates child-level genealogy relationships, traversing downward through the object hierarchy.
  • INV_POPULATE_PARENT_TREE — Populates parent-level genealogy relationships, traversing upward through the object hierarchy.
  • GETJDATA — Returns genealogy data, typically formatted for tree or structured display consumption.
  • SET_ROWLIMIT — Establishes a row limit governing how many genealogy records the tree population and data retrieval routines return, providing a safeguard against unbounded result sets during hierarchy traversal.

Tables Accessed

The package reads and writes Inventory and Order Management data through APPS synonyms. MTL_OBJECT_GENEALOGY is the core repository of parent-child object relationships, while MTL_LOT_NUMBERS, MTL_SERIAL_NUMBERS, MTL_SYSTEM_ITEMS_KFV, and MTL_PARAMETERS supply item, lot, and serial attribute context. WIP and counting activity draws on MTL_CYCLE_COUNT_HEADERS and MTL_PHYSICAL_INVENTORIES. Movement request data comes from MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES. Transaction and costing references include CST_COST_UPDATES and the temporary working table MTL_GEN_TEMP. Trading partner resolution uses HZ_CUST_ACCOUNTS and HZ_PARTIES, and sales order context is sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.

Usage Notes

INV_OBJECT_GENEALOGY is invoked primarily from Inventory and WIP forms that display lot, serial, and genealogy information, and from concurrent programs that build or refresh genealogy trees. Because it is referenced by eight other packages, it functions as a shared service layer for traceability queries. Custom code should call the published functions and procedures rather than querying MTL_OBJECT_GENEALOGY directly, and should set a row limit via SET_ROWLIMIT before invoking tree population to control result set size.