Search Results c_source_type2formula




Overview

INV_INVTRSTS_XMLP_PKG is the PL/SQL package associated with the Oracle Inventory transaction source report, an Oracle Reports (XML Publisher) concurrent program historically identified as INVTRSTS. The package is declared AUTHID CURRENT_USER and acts as the server-side driver for the report, holding global state variables and formula functions that Oracle Reports invokes through its PL/SQL interface. Its business purpose is to produce a listing of transaction usage and quantities in Inventory, grouped and filtered by transaction source type, item, category, and subinventory. The P_SOURCE_TYPE1FORMULA through P_SOURCE_TYPE4FORMULA (declared as P_STYPE1 to P_STYPE4) support the summarization and display of data by transaction source type. Users searching for "c_source_type2formula" have located the function C_SOURCE_TYPE2FORMULA, which supplies the value for the second transaction source type column in the report output.

Key Procedures and Functions

Tables Accessed

The package reads MTL_CATEGORY_SETS through the APPS synonym to resolve category set definitions, names, and structure IDs referenced by the category formula functions. It also reads MTL_TXN_SOURCE_TYPES to resolve transaction source type codes and descriptions used by the C_SOURCE_TYPE*FORMULA functions and the report's grouping logic. These lookups support the report's parameter validation and column derivation rather than direct transactional updates; the package is read-only against Inventory setup tables.

Usage Notes

INV_INVTRSTS_XMLP_PKG is invoked indirectly by the Oracle Inventory "Transaction Source" report concurrent program and by Oracle Reports runtime when the report definition calls its formula functions and report triggers. It is not intended to be called directly from forms or custom code; the package specification is deployed under APPS as part of the Inventory XML Publisher report library. Customizations should avoid modifying the packaged formulas and instead extend the underlying report query or use a custom concurrent program, since the globals (for example P_ORG_ID, P_CONC_REQUEST_ID, P_SORT_ID) are populated by the report at runtime. The ETRM metadata records no other packages referencing this package, confirming it is a leaf-level report library with no downstream API dependents.