Search Results c_fc_hdr_pa_amountformula
Overview
ONT_OEXOECOD_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Order Management "Open Orders and Backlog" style concurrent report (report short name OEXOECOD), which is executed through the Oracle Reports XML Publisher (BI Publisher) engine. The package is not a public business API; it is a report-support package generated and maintained to hold the server-side PL/SQL logic embedded in the report definition file. Its classification in the ETRM repository as OTHER confirms that it is an internal, report-specific construct rather than a documented integration or public API.
In Oracle EBS 12.1.1 and 12.2.2, packages of this naming convention (the ONT prefix followed by the report code and the XMLP_PKG suffix) are created automatically at report deployment and compilation time. They contain the formula columns, user exit functions, parameter validation routines, and before/after report triggers that the report relies on. The object is reported as VALID and depends only on SYS.STANDARD, indicating that its PL/SQL is self-contained and resolves other database objects at run time through the APPS synonym layer.
Key Procedures and Functions
The ETRM metadata documents 79 program units within this package. The principal entries include:
- BEFOREREPORT and AFTERREPORT — Report-level triggers executed on entry and exit, used to initialize session state, lexical parameters, and currency conversion context.
- C_ORDER_NUM_WHERE and C_OPEN_ORDERS_WHERE — Construct and return the WHERE clause fragments that restrict the report query to specific order numbers or to open orders only, based on report parameters.
- GET_SOB_NAME — Retrieves the display name of the ledger (set of books) associated with the reporting context.
- CONTACT_PHONE — Resolves the contact telephone number for the customer or ship-to contact shown on the report output.
- Currency and amount formulas — C_BASE_CURRENCYFORMULA, C_FUNCTIONAL_CURRENCY_DISPFORM, C_GL_CONV_RATEFORMULA, C_USE_CURRENCYFORMULA, C_FC_ORDER_VALUEFORMULA, C_FC_HDR_PA_AMOUNTFORMULA, C_FC_LIST_PRICEFORMULA, C_FC_SELLING_PRICEFORMULA, C_FC_EXTENDED_PRICEFORMULA, and C_FC_L_PA_AMOUNTFORMULA derive the base, functional, and reporting currency representations and conversion rates applied to order value and price fields.
- Display formulas — C_ORDER_BY_DISPLAYFORMULA, C_OPEN_ORDERS_DISPLAYFORMULA, C_SALES_CREDITS_DISPLAYFORMULA, and C_ADJUSTMENTS_DISPLAYFORMULA control formatting and conditional display of sort order, open-order indicators, sales credit, and adjustment columns.
No parameter lists are documented in the ETRM excerpt; the units are invoked by the Oracle Reports runtime rather than by external callers.
Tables Accessed
The package reads through APPS synonyms against Oracle Trading Community Architecture, Order Management, Inventory, and Payments tables:
- OE_ORDER_HEADERS_ALL — Primary source for order header attributes such as order number, order type, and pricing context.
- HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS — Resolve customer, account, site, and address details printed on the report.
- HZ_CONTACT_POINTS — Supplies telephone and contact point information used by CONTACT_PHONE.
- MTL_CUSTOMER_ITEMS, MTL_CUSTOMER_ITEM_XREFS, MTL_CROSS_REFERENCES, MTL_CROSS_REFERENCE_TYPES — Provide customer item numbers and cross-reference values associated with ordered items.
- IBY_TRXN_SUMMARIES_ALL — Supplies payment transaction summary amounts where the report presents receipt or payment-related balances.
Usage Notes
ONT_OEXOECOD_XMLP_PKG is invoked exclusively by the Oracle Reports / BI Publisher runtime when the associated concurrent program is submitted from the Order Management responsibility or the Submit Requests form. It is not intended for direct invocation from custom PL/SQL, and the ETRM dependency data shows it is referenced by zero other packages. Because the object is regenerated with each report compilation, customizations should be applied to the underlying report definition (.rdf/.xml) rather than to the package itself; direct modifications will be overwritten on the next patch or recompile. Administrators verifying report behavior should confirm the object status is VALID in ALL_OBJECTS and review the concurrent program definition tied to the OEXOECOD report short name.