Results for “inv_mgd_mvt_data_str”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
INV_MGD_MVT_DATA_STR is a PL/SQL specification package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM taxonomy as "OTHER". The package name and header comments establish its function clearly: it defines shared data structures — record types and REF cursors — used by the Oracle Inventory movement statistics engine rather than by any single program directly. The "STR" suffix denotes "structure", and the source header describes the file as a "Spec of INV_MGD_MVT_DATA_STR" whose purpose is "Data Structure definitions: Includes record types, REF cursors."
The business function it supports is the generation and maintenance of movement statistics data for inventory transactions. Movement statistics record the flow of material into, out of, and between inventory organizations, including cross-organization transfers, outside processing, receiving, and RMA (return material authorization) transactions. By centralizing the record and cursor definitions in one specification, the package provides a stable, shared contract that other movement-statistics packages can reference for cursor types and record layouts.
The package was created in March 2000 and evolved through several enhancements, most notably support for Include Establishments (Bug 5920143, 2007) and RMA Triangulation uptake (Bug 7165989, 2008), which modified the Movement_Transaction_Rec_Type record to add an additional attribute. The 120.2.12010000.2 header indicates a 12.1.1-era build, while the object remains present and referenced in 12.2.2.
Key Procedures and Functions
ETRM documents zero procedures or functions for this package. That is expected rather than exceptional. INV_MGD_MVT_DATA_STR is a pure specification package: it declares types and cursors but exposes no callable API subprograms of its own. Consumers use the declared types — principally Material_Transaction_Rec_Type, Trans_Rec, Movement_Transaction_Rec_Type, and the Val_crsr, TRNI/TRNR, XFER, OPSO, and RECV cursors — to fetch and pass movement data between their own procedures.
Consequently, the practical "API" of this package is its type definitions. Material_Transaction_Rec_Type carries attributes that are not themselves present in the movement statistics table but are required to derive values for it — for example transaction_type_id, transaction_action_id, transfer_organization_id, and outside_processing_account. Note the change recorded in November 2002, when defaulting parameters for Trans_Rec to FND_API.G_MISS_NUM were removed, altering how callers must populate that record before use.
Tables Accessed
Although the spec itself performs no DML, its cursors and record types are modelled on the following tables, accessed through APPS synonyms:
- MTL_MATERIAL_TRANSACTIONS — the transactional source of inventory movements; most record attributes mirror its columns.
- MTL_MOVEMENT_STATISTICS — the target/destination table populated with derived movement statistics rows.
- MTL_STAT_TYPE_USAGES — determines which transaction types are configured for statistics collection.
- RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS — receiving data underpinning RECV and OPSO (outside processing) cursor logic.
- PO_HEADERS_ALL — supplier and document context for receiving-related movements.
- OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_DROP_SHIP_SOURCES — order and drop-ship context relevant to RMA triangulation.
- WSH_DELIVERY_DETAILS — shipping/delivery detail linking movements to dispatch.
Usage Notes
This package is not invoked from a form or concurrent program directly. It is referenced by twelve other packages, which import its record types and cursor declarations when building movement statistics. Typical invocation paths are the movement statistics concurrent programs and the Order Management, Purchasing, and Shipping flows that trigger statistics generation, together with custom extensions that need to assemble movement data in the same canonical shape. Because the package uses AUTHID CURRENT_USER, any custom code calling it must have the appropriate privileges on the underlying MTL, RCV, OE, PO, and WSH objects. Developers extending movement statistics should reference this specification rather than redefining record types locally, ensuring compatibility with Oracle's derivation logic and with future patch upgrades.