Search Results c_inv_order_amt_p

Overview

ONT_OEXOEIOS_XMLP_PKG is a public package owned by APPS within Oracle E-Business Suite, and it is associated with the Oracle Order Management module. This package is not a general-purpose business API; its classification in ETRM is OTHER, indicating it is a supporting package behind a specific concurrent-program report rather than a published integration interface. The package acts as the server-side PL/SQL library for a report-related executable, exposing the global parameters, package-level variables, and report trigger functions that beget and save the report's runtime state. The naming convention (XMLP) indicates that the report is designed for Oracle XML Publisher, while the leading ONT and internal OE source header confirm a lineage in Order Management and Order Entry. In practice, the package holds the bind parameters populated from the report's parameter form, the dynamically generated lexical parameters, and the column-oriented totals and labels used by the report layout. One of the exported helper functions exposed by the package is get_euro_code, a currency-handling utility whose purpose is to resolve the appropriate Euro conversion code required when order amounts and balances are displayed in the report. Packages of this type are tightly coupled to the concurrent program that invokes them and are not intended for ad hoc use by custom code.

Key Procedures and Functions

The documented interface of ONT_OEXOEIOS_XMLP_PKG comprises 34 procedures and functions. Several are report lifecycle triggers invoked automatically by the Oracle Reports runtime:

• BEFOREREPORT — Prepares the environment before the report body executes.
• AFTERREPORT — Handles cleanup and any final formatting once the report completes.
• AFTERPFORM — Executes after the parameter form is submitted, before report execution.
• BEFOREPFORM — Prepares values or state prior to displaying the parameter form.

A second group comprises formula columns and label functions that shape the output:

• C_DATA_NOT_FOUNDFORMULA, C_ORDER_COUNTFORMULA, and C_LINE_COUNTFORMULA — Formula columns that determine whether data was returned and compute order and line counts.
• C_COMPUTE_AMOUNTSFORMULA — Computes order, invoice, balance, and credit amounts, taking transaction, currency, conversion type, and order date information into account.
• C_ORDER_AMOUNTFORMULA, C_INV_ORDER_AMT_P, C_BALANCE_DUE_P, C_CREDIT_AMOUNT_P, and C_AMOUNT_P — Amount-oriented summary and placeholder functions.
• C_PRECISIONFORMULA — Determines decimal precision for displayed currency values.
• RP_CURR_LABELFORMULA and RP_USE_FUNCTIONAL_CURRENCYFORM — Resolve currency labels and flag functional-currency usage.
• RP_REPORT_NAME_P, RP_SUB_TITLE_P, RP_COMPANY_NAME_P, and RP_FUNCTIONAL_CURRENCY_P — Populate report header attributes such as report name, sub-title, company name, and functional currency.

The package also exposes numerous global variables (for example P_ORDER_TYPE_LOW, P_ORDER_NUM_LOW, P_CUSTOMER_NAME_LOW, P_ORG_ID, P_OPEN_ORDERS_ONLY, P_COUNTRY, and P_USE_FUNCTIONAL_CURRENCY) and lexical parameters (LP_COUNTRY, LP_SALESREP, LP_ORDER_NUM, LP_CUSTOMER_NAME, LP_ORDER_TYPE, LP_OPEN_ORDERS_ONLY) that carry parameter-form selections into the SQL query.

Tables Accessed

The package reads data through APPS synonyms for several base objects. FND_CONCURRENT_REQUESTS supplies concurrent request context, while FND_CURRENCIES provides currency definitions and attributes such as precision. OE_TRANSACTION_TYPES_TL supplies translated order-type descriptions for the report filters. OE_ORDER_LINES supplies order line detail. RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL provide invoice header and line amounts used to derive invoiced quantities and balances, and AR_PAYMENT_SCHEDULES supplies payment schedule information from which balance-due and credit amounts are computed. These tables collectively support the report's purpose of listing open orders alongside their invoiced and outstanding monetary values.

Usage Notes

This package is invoked indirectly by the concurrent program and Oracle Reports/XML Publisher definition that reference it; the report's parameter form populates its global variables before the report triggers fire, and the formulas consume those values during layout. It is not referenced by any other documented package, and it has no published API classification, so customers should not call its functions directly from custom PL/SQL. Customization should instead be applied through the associated report definition or by wrapping it with a copy rather than modifying the shipped package. The presence of the get_euro_code helper further indicates that the report is currency-aware and was written to support Euro conversion handling for European implementations, so parameter values for currency and conversion type should be supplied consistently with the functional currency settings to avoid mis-stated amounts.