Search Results p_date_lo

Overview

INV_INVTRSTS_XMLP_PKG is a generated PL/SQL package used by the Oracle Inventory transaction source / transaction register style XML Publisher (BI Publisher) concurrent report. The package follows the standard Oracle Reports-to-XML conversion pattern: the report definition (.rdf converted to XML) is executed through the concurrent manager, and the accompanying PL/SQL package supplies the user-facing report parameters as package globals, evaluates bind and lexical substitution variables, and performs before/after report and before/after parameter form logic. The package header is declared with AUTHID CURRENT_USER, so all unqualified references to the APPS synonyms are resolved under the invoking user's privileges, consistent with other APPS-side report packages.

The package is part of the Inventory module (INV) and exposes a large set of public global variables that mirror the report's parameter list, such as P_STRUCT_NUM, P_STYPE1 through P_STYPE5, P_DATE_LO, P_DATE_HI, P_ORG_ID, P_CONC_REQUEST_ID, P_CAT_FLEX, P_ITEM_FLEX, P_CAT_HI, P_CAT_LO, P_SUBINV_HI, P_SUBINV_LO, P_ITEM_HI, P_ITEM_LO, P_WHERE_CAT, P_WHERE_ITEM, P_VIEW, P_CAT_SORT, P_ORDER_ITEM and P_DROP. Defaulted values, like P_VIEW initialized to 'txn_usage_view' and the multi-segment P_CAT_FLEX concatenation expression, are established at package instantiation so they are available to the report's data model and layout triggers.

Key Procedures and Functions

The documented callable units are:

• BEFOREREPORT, AFTERREPORT, BEFOREPFORM and AFTERPFORM — the standard XML report event handlers invoked by the report engine at the corresponding lifecycle points to set up and tear down report context and parameter state.
• C_FROM_CATFORMULA and C_WHERE_CATFORMULA — compute the FROM and WHERE clause fragments used to join and filter the category flexfield structure based on the selected category set.
• C_SOURCE_TYPE1FORMULA, C_SOURCE_TYPE2FORMULA and C_SOURCE_TYPE3FORMULA — return the display text for the source type columns (STYPE1–STYPE3) based on the selected transaction source types. The search term c_source_type1formula refers specifically to the first of these, which supplies the value rendered for the primary source type column.
• C_WHERE_SUBINVFORMULA — builds the WHERE clause restricting the query to the selected subinventory range.
• C_ITEM_TOTALFORMULA — computes the item-level total (or summed quantity) shown on the report output.
• C_CAT_SET_NAMEFORMULA — returns the descriptive name of the category set being reported.
• C_CURRENCY_CODEFORMULA — resolves the currency code displayed on the report, typically derived from the ledger or organization profile option.
• C_STATUS_WHEREFORMULA — constructs the WHERE clause fragment filtering records by transaction or item status.
• C_CAT_PADFORMULA — pads category segment values so that concatenated or compared category strings align correctly.
• P_VIEW_PUTVALIDTRIGGER — the trigger used when P_VIEW_PUT is populated, validating or setting the view used by the report query.

Tables Accessed

Per the documented metadata, the package references two APPS synonyms:

• MTL_TXN_SOURCE_TYPES — used by the C_SOURCE_TYPEnFORMULA functions to translate the numeric source type identifiers into their display descriptions for the report columns.
• MTL_CATEGORY_SETS — used by the category-related functions (C_FROM_CATFORMULA, C_WHERE_CATFORMULA, C_CAT_SET_NAMEFORMULA, C_CAT_PADFORMULA) to resolve the category set structure, segment configuration and display name driving the category filters and columns.

Usage Notes

INV_INVTRSTS_XMLP_PKG is not intended to be called directly from forms or custom code; it is bound to the Inventory transaction source XML report and is invoked by the concurrent manager when the report is submitted. Report parameters entered on the concurrent request form populate the package globals, and the report's group filters and formula columns call the C_*FORMULA functions at execution time. Because the package executes AUTHID CURRENT_USER and references APPS synonyms, it must be run in an environment where the APPS synonyms are visible to the running user. The metadata records that no other packages reference this package, confirming its role as a leaf-level report support unit dedicated to a single concurrent program.