Search Results get_func_curr_indicator
Overview
JAI_PA_COSTING_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that belongs to the Oracle Financials for India (JAI) localization product family. Its primary business function is to support India-specific tax and cost processing for procurement and payables transactions, and to feed the resulting tax and cost amounts into Oracle Projects (PA) through the Project Costing interface. The package resolves non-recoverable tax amounts on transactions originating in Purchasing (requisitions, purchase orders, and receipts) and Payables (invoices), computing those amounts in either the functional currency or the transaction currency. It then stages and updates the corresponding interface cost records so that the Indian tax component is reflected correctly in project cost distribution.
The version history embedded in the package source shows that it was created on 17-JAN-2007 (version 115.0, bug 5765161) and forward-ported to Release 12 from 11i (version 120.0, bug 6012567). The header identifies it as a non-shipped ("noship") object that is nevertheless deployed in the APPS schema in both 12.1.1 and 12.2.2 environments where the India localization is licensed.
Key Procedures and Functions
- GET_FUNC_CURR_INDICATOR — Returns the constant indicator value that signals tax amounts should be expressed in the functional currency (documented as the constant gv_functional_currency).
- GET_TRX_CURR_INDICATOR — Returns the constant indicator value that signals tax amounts should be expressed in the transaction currency (documented as the constant gv_transaction_currency).
- GET_NONREC_TAX_AMOUNT — The core calculation routine. Given a transaction source, a line type (requisition, purchasing, PO_RECEIPT, or invoice), a transaction header identifier, and a transaction distribution identifier, it returns the non-recoverable tax amount for that transaction. It accepts an optional currency-of-return argument; when no value is supplied, the amount is returned in the transaction currency. This is the function most directly relevant to purchase-order receipt processing.
- PRE_PROCESS — Performs setup and validation logic before interface cost records are processed.
- POST_PROCESS — Performs completion and cleanup logic after interface processing.
- UPDATE_INTERFACE_COSTS — Updates cost rows in the Projects interface tables with the computed Indian tax/cost amounts.
- UPDATE_INTERFACE_COST_TAX — Updates the tax-specific portion of the interface cost records.
- GET_COMTMNT_AMT — Returns the commitment amount associated with the transaction, used in encumbrance-related costing.
Tables Accessed
The package references a broad set of APPS synonyms. Purchasing and receiving tax data is read from JAI_PO_TAXES, JAI_PO_REQ_LINE_TAXES, JAI_RCV_LINE_TAXES, JAI_RCV_RGM_LINES, and JAI_RCV_TRANSACTIONS; the JAI_RCV_TRANSACTIONS table is the repository for receipt-level tax and cost detail, which is why PO_RECEIPT transactions rely on this package. Payables-side data comes from AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, and JAI_AP_MATCH_INV_TAXES. Common tax setup and staging data is held in JAI_CMN_TAXES_ALL, JAI_PA_TAX_TRXS, and JAI_CMN_DEBUG_CONTEXTS. Project Costing integration reads from PA_IMPLEMENTATIONS and PA_INTERFACE_ID_S. FND_USER and FND_LOGINS are used for audit and debugging context, consistent with the debug-context table also referenced.
Usage Notes
JAI_PA_COSTING_PKG is not intended for direct end-user invocation. It is invoked indirectly by the India localization cost and tax processing logic, typically from concurrent programs and packaged APIs that post procurement, receiving, and payables transactions into Oracle Projects. The ETRM metadata records that the package is referenced by two other packages, confirming that it is a utility layer called by other JAI components rather than an entry point. Custom code that needs the non-recoverable Indian tax amount for a PO receipt, invoice, or requisition line should call GET_NONREC_TAX_AMOUNT, passing the appropriate transaction source and line type (for example, PO_RECEIPT with an RCV_TRANSACTIONS.transaction_id) and the header and distribution identifiers. Administrators troubleshooting India Projects costing issues can inspect JAI_CMN_DEBUG_CONTEXTS output, since the package writes debug information keyed to FND_USER and FND_LOGINS.