Search Results c_shipped_amountformula

Overview

APPS.ONT_OEXOEOSR_XMLP_PKG is the PL/SQL package body generated by Oracle Reports for the XML Publisher/Oracle Reports concurrent program "Order Organizer Report" (report file OEXOEOSRS). It encapsulates all server-side logic that would otherwise reside in the report's formula columns, user parameters, and group filters. The package is part of the Oracle Order Management (ONT) module and provides a structured, database-resident implementation of the report's business rules, allowing the concurrent program to execute parameter validation and data formatting directly within the database.

The package exposes a large set of global PL/SQL variables and constants that map directly to the report's user parameters, such as P_ORDER_NUM_LOW, P_ORDER_NUM_HIGH, P_ORDER_TYPE_LOW, P_ORDER_TYPE_HIGH, P_CUSTOMER_NAME_LOW, P_CUSTOMER_NAME_HIGH, P_SALESREP_LOW, P_SALESREP_HIGH, and date range parameters. Additional lexicals such as LP_ORDER_NUM, LP_COUNTRY, LP_SALESREP, LP_CUSTOMER_NAME, and LP_ORDER_TYPE are used to hold display values tokenized into the report layout. The user search term "lp_order_num" corresponds to one of these lexical placeholders, which carries the formatted order number value rendered in the report output.

Key Procedures and Functions

The package documents 38 procedures and functions. The key processing units are:

• BEFOREREPORT — initializes package state before the report opens, typically resolving the concurrent request ID into context values.
• AFTERREPORT — performs cleanup tasks after the report completes.
• AFTERPFORM — executes after the parameter form is submitted, used to derive dependent parameters such as currency labels or organization contexts.
• RP_CURR_LABELFORMULA — returns a label describing the functional currency for display in the report.
• C_DATA_NOT_FOUNDFORMULA — determines whether the query returned no rows and controls the "no data found" message block.
• C_ORDER_COUNTFORMULA, C_LINE_COUNTFORMULA — compute the count of orders and order lines returned by the report query.
• C_ORDER_AMOUNTFORMULA, C_LIST_AMOUNTFORMULA, C_SHIPPED_AMOUNTFORMULA — compute aggregate monetary values for orders, list prices, and shipped quantities.
• C_CURRENCYFORMULA — resolves the currency code or symbol for the selected reporting context.
• CF_1FORMULA — a general-purpose formula column used for calculated report output.
• RP_USE_FUNCTIONAL_CURRENCYFORM — determines whether amounts should be presented in the functional currency.
• RP_REPORT_NAME_P, RP_SUB_TITLE_P, RP_COMPANY_NAME_P — supply the report title, subtitle, and company name header values.
• RP_FUNCTIONAL_CURRENCY_P — returns the functional currency for the reporting set of books.
• RP_DATA_FOUND_P — indicates whether the report has data to display.
• RP_ORDER_NUMBER_RANGE_P, RP_SALESREP_RANGE_P — build formatted display strings for the order number and sales representative range parameters.

Tables Accessed

The package queries the following tables through APPS synonyms:

• FND_CONCURRENT_REQUESTS — resolves request context, such as the responsible application and user, from the concurrent request ID.
• FND_CURRENCIES — supplies currency names, symbols, and formatting for the currency label and amount display columns.
• OE_AGREEMENTS — provides agreement information associated with orders when the report includes agreement data.
• OE_ORDER_LINES_ALL — the primary source of order line detail, including ordered, listed, and shipped amounts and quantities.
• OE_ORDER_SOURCES — classifies the order source (for example, manual entry, EDI, or web) for the order source column.
• OE_TRANSACTION_TYPES_TL — supplies translated transaction type names used in the order type parameter and display columns.

Usage Notes

ONT_OEXOEOSR_XMLP_PKG is invoked exclusively by the Order Organizer Report concurrent program through the Oracle Reports runtime. It is not intended for direct invocation by forms or custom PL/SQL. In Oracle EBS 12.1.1 and 12.2.2, the package is deployed in the APPS schema and is regenerated whenever the report definition is recompiled. The package is referenced by no other packages, confirming its role as a report-specific container. Customizations should avoid modifying the package directly, since changes are overwritten on regeneration; instead, report-level enhancements should be applied through the Oracle Reports source file OEXOEOSRS.rdf. The lexical "lp_order_num" is populated at runtime to render the order number in the report output and should not be manipulated outside the report execution context.