Search Results prm_org_id

Overview

The APPS.JA_JAINST3_XMLP_PKG package body supports the Oracle E-Business Suite (EBS) India Localization tax reporting framework, specifically the JAINST3 report — a service tax and education cess installment/register report. In EBS 12.1.1 and 12.2.2, this package is generated automatically by the Oracle Reports to XML Publisher (XMLP) migration utility, which converts report-level formula columns and group functions into callable PL/SQL functions inside a wrapper package stored under the APPS schema. Each function encapsulates a specific derived calculation or conditional expression that previously lived in the report template.

The package serves as the computational backbone for a concurrent report that reconciles service tax credits, education cess balances, and recoverable amounts across reporting periods. It is classified as OTHER in the ETRM metadata, indicating it is not a public API but an internal report-support package. The excerpt confirms XML Publisher conventions: a 2007 header, formula functions such as CF_REALISED_AMOUNTFORMULA and CF_1FORMULA, and use of the standard PRM_-prefixed report parameters that XMLP passes into generated packages.

Key Procedures and Functions

The package exposes 36 documented functions, all following the CF_*FORMULA convention. Notable entries include:

• CF_REALISED_AMOUNTFORMULA — computes a rounded realised tax amount from tax, recovered, and charged/billed inputs, guarding against division by zero via NVL.
• CF_1FORMULA / CF_2FORMULA — return asterisk indicators based on the fiscal period derived from PRM_FROMDT, distinguishing April–September and October–March halves.
• CF_SERVICEFORMULA — aggregates service cess and service amounts from JAI_RGM_TRX_RECORDS filtered by regime, primary registration number, organization, and date range.
• CF_INVOICE_NUMFORMULA — resolves and formats invoice identification for the report.
• CF_ST_SERVICE_AMOUNTFORMULA, CF_RETURN_NULL — provide service-amount derivation and null-safe returns.
• Balance-oriented functions — CF_OPENING_BALANCEFORMULA, CF_CREDIT_AVAILEDFORMULA, CF_CREDIT_RECEIVEDFORMULA, CF_CREDIT_UTILIZEDFORMULA, CF_TOTAL_CREDITFORMULA, CF_CLOSING_BALANCEFORMULA, and the education-cess variants CF_EDUCESS_OPENING_BALANCEFORM, CF_EDUCESS_CREDIT_AVAILEDFORMU, CF_EDUCESS_CLOSING_BALANCEFORM.
• Cess-credit functions — CF_CREDIT_INPUT_SERVICESFORMUL, CF_CCRD_ST_DISTRIBUTEDFORMULA, CF_CCRD_CLOSING_BALANCEFORMULA, CF_ECRD_EC_DISTRIBUTEDFORMULA, and related distributed-credit calculators.

All functions share the same role: encapsulating period-end tax arithmetic so the XML Publisher template can render calculated columns without embedding SQL or PL/SQL logic directly.

Tables Accessed

Documented table access relies on APPS synonyms and covers both transactional and infrastructure data:

• JAI_RGM_TRX_RECORDS, JAI_RGM_MANUAL_TRXS, JAI_RGM_TRX_REFS — the core India tax regime transaction tables storing credit, debit, and reference data used in service cess and balance calculations.
• AP_INVOICES_ALL, AP_INVOICE_PAYMENTS_ALL — source payables invoices and payments referenced when reconciling realised and recovered amounts.
• JAI_CMN_VENDOR_SITES, JAI_INV_ITM_SETUPS — vendor-site and item-setup configuration for localization reporting.
• FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS — concurrent program definition and request rows, used for report execution context and audit.
• V$DATABASE, V$PROCESS, V$SESSION — dynamic performance views, typically for session/database identification invoked at report start.

Usage Notes

This package is invoked indirectly rather than called by other PL/SQL code — the metadata notes it is referenced by zero other packages. It executes when the JAINST3 concurrent program runs, with XML Publisher passing report parameters (including PRM_ORG_ID, PRM_FROMDT, PRM_TODT, PRM_RGM_PRIM_REGNO, and PRM_SERVICE_TYPE) into the generated functions as bind arguments. The NVL(PRM_ORG_ID, ...) pattern visible in CF_SERVICEFORMULA allows the report to run either for a specific operating unit or across all organizations.

Because the package is regenerated whenever the underlying report definition changes, customizations should not be applied directly — they would be overwritten on patch or upgrade. In 12.2.2 the package behaves identically to 12.1.1, as it is a report wrapper with no Online Patching editioning requirements beyond standard APPS schema handling.