Search Results p_order_amount_low
Overview
APPS.ONT_OEXPRPRS_XMLP_PKG is the server-side PL/SQL package body that backs the Oracle Order Management seeded concurrent program Pricing Report - Summary (internal short name OEXPRPRS). It belongs to the Oracle Order Management (ONT) application and, in the ETRM classification scheme, is registered as an OTHER API rather than a public programmatic interface. The package exists to support the XML Publisher (BI Publisher) report definition: it supplies the report's before-report and after-report initialization logic, the after-formula trigger used during parameter validation, and a large set of formula functions that format and derive the columns displayed in the printed output.
The package is not a general-purpose business API. It is generated and maintained as part of the report's XMLP integration layer, and it is tightly coupled to the report's data model, bind parameters, and group structure. The header comment attributes the source file to OEXPRPRSB.pls, last revised in January 2008, which indicates the code has remained stable since the 11i-era report was migrated to the XML Publisher framework used in Release 12.1.1 and 12.2.2.
Key Procedures and Functions
The documented interface comprises 38 functions and procedures. The principal control-flow entry points are:
- BEFOREREPORT — the before-report trigger. It reads the RECURRING_CHARGES system parameter through OE_SYS_PARAMETERS.VALUE for the current operating unit, captures the concurrent request ID from FND_GLOBAL, records the current organization via MO_GLOBAL, and resolves the report name and company/functional currency information into report-level placeholders.
- AFTERREPORT — the after-report trigger, used for end-of-run cleanup and final placeholder assignment.
- AFTERPFORM — the after-parameter-form trigger, which executes once the user submits the concurrent program parameter form and can adjust values used later by the data query.
- RP_ORDER_BYFORMULA — builds the dynamic ORDER BY clause applied to the report's result set, allowing sort behavior to vary with user parameters.
The remaining documented functions are formula columns of the XMLP report layout. They fall into a consistent family: C_DISCOUNT_PRICE, C_ORDER_AMOUNT, and C_ORDER_LIST, each with the base version plus variants suffixed _CU (currency), _OT (order type), _C, and _P. These variants present the discount price, extended order amount, and list price values in the format appropriate to each grouping level of the report. C_DATA_NOT_FOUNDFORMULA renders a placeholder when no rows qualify. CF_1FORMULA and CF_2FORMULA are the two conditional formatting functions that drive highlighting or formatting rules in the published template.
Tables Accessed
- FND_CONCURRENT_REQUESTS — joined to FND_CONCURRENT_PROGRAMS_VL in BEFOREREPORT to derive the user-facing program name from the running request ID.
- FND_CURRENCIES — joined to GL_SETS_OF_BOOKS to validate and obtain the functional currency code for the ledger.
- OE_AGREEMENTS — supplies pricing agreement information used by the discount and list price formula columns.
- OE_TRANSACTION_TYPES_TL — provides the translated transaction type name, supporting the order-type formula variants (_OT).
All access is read-only and is performed through APPS synonyms.
Usage Notes
The package is invoked implicitly by the concurrent manager whenever the Pricing Report - Summary program is run; it is not called directly from Oracle Forms. Because it is classified as OTHER in ETRM and is referenced by no other packages, customers should treat it as an internal implementation detail of the seeded report. The package name appears in searches such as p_salesrep_hi because the high value of the sales representative parameter is one of the bind variables passed into the package's formula functions; that parameter constrains the report to a sales representative range and is bound into the report query rather than into any documented procedure signature. Customizations should be limited to copying the report and its package, since modifications to the seeded package body are overwritten by patching and are not supported under the standard support policy.