Search Results amt_receivedformula
Overview
ONT_OEXOEORD_XMLP_PKG is the PL/SQL package body associated with the Oracle EBS Order Management report "Open Order / Return Report" (concurrent program short name OEXOEORD, historically OEXOEORDS). It is an XML Publisher (BI Publisher)-enabled concurrent program package, owned by APPS, that produces the printed or exported listing of open sales orders and returns entered against the Order Management application. The package exposes the standard concurrent-program interface functions required by the Oracle Reports/XML Publisher integration layer, together with a set of parameter validation triggers and formula functions that populate derived columns in the report output.
The package serves the Order Management functional area and is used primarily by order management clerks, customer service representatives, and returns processing staff who require a curated view of open orders and outstanding RMA (Return Material Authorization) lines. It supports filtering by return number range, return date range, customer name and number, sales representative, item, line category, and organization, and it permits selection of whether only open returns are displayed. The header comment indicates a source revision last touched in 2008, and the object is marked "noship," meaning it is delivered without a formal shipping designation but remains present in the APPS schema.
Key Procedures and Functions
The documented package exposes 24 procedures and functions. The report lifecycle functions BEFOREREPORT and AFTERREPORT initialize and clean up package-level state and resolve report title, subtitle, company name, functional currency, and data-found indicators. AFTERPFORM executes after the parameter form is submitted and performs additional session setup.
The remaining members fall into two families. Parameter validation triggers enforce user-entered selection criteria before the report runs: P_ORDER_BYVALIDTRIGGER validates the ORDER BY sort selection, P_ITEM_FLEX_CODEVALIDTRIGGER validates the item flexfield input, P_ITEM_DISPLAYVALIDTRIGGER validates the item display choice, and P_CREDIT_ONLYVALIDTRIGGER validates the credit-only filter. These triggers are the documented entry points tied to the ORDER BY parameter (P_ORDER_BY) that the user searched for.
Formula functions compute derived report values: AMT_EXPECTEDFORMULA, AMT_RECEIVEDFORMULA, and AMT_ACCEPTEDFORMULA derive expected, received, and accepted RMA amounts; REF_NUMFORMULA returns a reference number; C_TOTAL_RMAFORMULA and C_TOTAL_LINESFORMULA produce aggregate counts for the report totals; and C_MASTER_ORGFORMULA resolves the master organization identifier. A set of parameter-prefix functions (RP_REPORT_NAME_P, RP_SUB_TITLE_P, RP_COMPANY_NAME_P, RP_FUNCTIONAL_CURRENCY_P, RP_DATA_FOUND_P, RP_ITEM_FLEX_ALL_SEG_P) supply layout values used by the XML Publisher template.
Tables Accessed
The package reads reference and transactional data through APPS synonyms, including FND_CONCURRENT_REQUESTS for concurrent request context, FND_CURRENCIES for functional currency resolution, the MTL_CUSTOMER_ITEMS, MTL_CUSTOMER_ITEM_XREFS, MTL_CROSS_REFERENCES, MTL_CROSS_REFERENCE_TYPES, and MTL_SYSTEM_ITEMS_KFV inventory tables for item and cross-reference detail, the OE_ORDER_HEADERS and OE_ORDER_LINES_ALL tables for open order and return lines, OE_TRANSACTION_TYPES_TL for transaction type descriptions, RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES_ALL for related receivables transactions, and DUAL for scalar evaluations. These reads support the report's join between order, return, item, and customer data.
Usage Notes
The package is normally invoked indirectly when the OEXOEORD concurrent program is submitted with a Reports/XML Publisher layout, rather than called directly by end users. Its parameter validation triggers fire automatically when the concurrent program's parameter form is submitted, and the formula functions are referenced from the report definition or XML template. Custom code should not call these members directly because the package is not designated as a public API; instead, customizations should be layered through the underlying Order Management tables or through supported OM APIs. The package is referenced by zero other packages, confirming it is a self-contained report artifact rather than a shared library.