Search Results v_program_id

Overview

JA_JAINRACT_XMLP_PKG is an Oracle E-Business Suite package body owned by the APPS schema and classified under ETRM as OTHER. It supports the JA_JAINRACT report — a localization report tied to Indian statutory reporting (the JA prefix denotes the India localization, and JA_IN_RACT relates to the excise/CENVAT reconciliation and register reporting used by Indian organizations). The package follows the standard Oracle Reports PL/SQL library pattern used in EBS 12.1.1 and 12.2.2: an XML Publisher/Reports executable invokes the package's BeforeReport and AfterReport formula functions at defined phases of report execution, while additional packaged functions support parameter validation and value derivation.

The package is intentionally small, containing three documented functions. It does not encapsulate business logic for the report's query itself; instead it manages report lifecycle tasks — session configuration, optional SQL tracing, and the mapping of user-selected accounting nature parameters to the derived values consumed by the report layout. The header comment (JAINRACTB.pls 120.1, dated 25-DEC-2007) indicates the package has been stable across releases and is marked as a nonshipped localization object.

Key Procedures and Functions

• P_ACCT_NATUREVALIDTRIGGER — This is the function directly associated with the search term p_acct_naturevalidtrigger and functions as a parameter validation trigger. It evaluates the report parameter P_ACCT_NATURE and derives dependent parameter values. When P_ACCT_NATURE equals 'MODVAT', the function assigns 'CENVAT' to P_CENVAT; when it equals 'Expense', it assigns 'Capital Expense' to P_EXPENSE. It returns BOOLEAN (TRUE) to signal successful validation. It does not raise exceptions or perform lookups against any table.
• BEFOREREPORT — Invoked by the report engine before the main query executes. It initializes P_CONC_REQUEST_ID from FND_GLOBAL.CONC_REQUEST_ID, then queries FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS for the concurrent program ID and the ENABLE_TRACE flag. If tracing is enabled ('Y'), it dynamically issues ALTER SESSION SET EVENTS '10046 trace name context forever, level 4' to generate a SQL trace. All failures inside this block are trapped by an internal WHEN OTHERS handler, so tracing problems never abort the report. Returns BOOLEAN (TRUE).
• AFTERREPORT — Invoked after report output is produced. In this version its only substantive content is a commented-out SRW.USER_EXIT('FND SRWEXIT') call, retained for legacy Reports compatibility. It returns BOOLEAN (TRUE) as required by the Reports formula interface.

Tables Accessed

• FND_CONCURRENT_REQUESTS — Read by BEFOREREPORT to retrieve the CONCURRENT_PROGRAM_ID and ENABLE_TRACE flag for the current request ID, allowing the package to determine whether diagnostic tracing was requested for this submission.
• FND_CONCURRENT_PROGRAMS — Referenced to anchor the %TYPE declarations V_PROGRAM_ID and V_ENABLE_TRACE. The cursor in the documented source selects CONCURRENT_PROGRAM_ID and NVL(ENABLE_TRACE,'N') from FND_CONCURRENT_REQUESTS, with FND_CONCURRENT_PROGRAMS providing the datatype basis.

Both tables are accessed through APPS synonyms. No other tables, and no DML, are documented. P_ACCT_NATUREVALIDTRIGGER performs no database access at all.

Usage Notes

• The package is bound to the JA_JAINRACT report definition, where BeforeReport and AfterReport are registered as report-level formula triggers.
• P_ACCT_NATUREVALIDTRIGGER is wired as the validation trigger for the P_ACCT_NATURE report parameter, so it fires when the user submits the concurrent request and selects an accounting nature value.
• ETRM records zero other packages referencing this object, confirming it is a leaf-level report support package rather than a shared API.
• Because parameter derivation depends on the literal values 'MODVAT' and 'Expense', customizations or new accounting nature values require corresponding code amendments; likewise, tracing relies on a valid ENABLE_TRACE profile/flag on the concurrent program.
• The embedded ALTER SESSION tracing is diagnostic only and should not be enabled in normal production submissions due to trace file overhead.