Search Results p_org_where

Overview

JA_JAINRGCR_XMLP_PKG is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified as OTHER. It serves as the report logic container for the JAINRGCR concurrent program, a report in the Oracle Financials for India (JA) module that produces a Register of Credit / Credit Register (RGCR) — a tax credit register tracking service tax credit taken and utilized against closing and opening balances. The package follows the standard Oracle Reports XML Publisher (XMLP) integration pattern, in which report-level data logic and formula columns are encapsulated in a PL/SQL package body invoked by the report's After Parameter Form, Before Report, and After Report triggers. No other package references this object, confirming it is a leaf-level report implementation package rather than a shared API. The source header indicates version 120.1, last modified 2007/12/25, with the designation "noship," meaning the file is not shipped as part of the standard standalone product but is distributed through the applicable patch or product family delivery.

Key Procedures and Functions

The package exposes ten documented program units:

• BEFOREREPORT — The Before Report trigger function. It resolves the concurrent request ID via FND_GLOBAL.CONC_REQUEST_ID, reads the concurrent program ID and enable-trace flag from FND_CONCURRENT_REQUESTS, and, when tracing is enabled, dynamically alters the session to generate a trace file. It also derives formatted from/to dates (CP_FROM_DATE, CP_TO_DATE) from the report parameters.
• AFTERPFORM — The After Parameter Form trigger, used to validate or derive parameter values once the report parameter form is submitted.
• AFTERREPORT — The After Report trigger, responsible for cleanup and post-processing after report output completes.
• CF_CREDIT_TAKENFORMULA — A formula column returning the credit taken amount for the register.
• CF_CREDIT_UTILIZEDFORMULA — A formula column returning the credit utilized amount.
• CF_OPENING_BALFORMULA — A formula column returning the opening balance of credit.
• CF_CLOSING_BALFORMULA — A formula column returning the closing balance of credit.
• CF_SERVICE_TYPEFORMULA — A formula column resolving the service type description.
• CF_VALUEFORMULA — A formula column deriving the taxable or credit value.
• CF_DESCRIPTIONFORMULA — A formula column resolving the descriptive text for the register line.

Tables Accessed

The package queries three categories of tables. Concurrent processing metadata is read from FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS in BEFOREREPORT to obtain the program ID and trace flag. Session diagnostics use V$SESSION, V$PROCESS, and V$DATABASE to locate the audit session ID, OS process ID, and database name for trace file naming. The India service tax credit data is drawn from JAI_RGM_TRX_RECORDS, JAI_RGM_TRX_REFS, JAI_RGM_DIS_SRC_HDRS, JAI_RGM_DIS_SRC_TAXES, JAI_RGM_DIS_DES_HDRS, and JAI_RGM_DIS_DES_TAXES, which hold transaction records, references, and distribution source/destination header and tax lines. Supporting lookups include AP_PAYMENT_SCHEDULES_ALL for payment schedule and credit utilization data, HR_ALL_ORGANIZATION_UNITS for the operating unit or organization context (relevant to the p_org_where parameter), and MTL_SYSTEM_ITEMS for item descriptions.

Usage Notes

This package is invoked exclusively by the JAINRGCR Oracle Reports definition through the standard XML Publisher trigger mechanism; it is not intended for direct invocation from forms or custom code. The report is submitted as a concurrent program, and the p_org_where parameter supplied by the user restricts the organization context used to filter the credit register data, tying into HR_ALL_ORGANIZATION_UNITS. Because the package is marked "noship" and referenced by no other package, customizations and diagnostics must be applied within the report definition and its parameter form. Trace file generation is controlled by the Enable Trace flag on the concurrent program definition, which the BEFOREREPORT function honors when constructing the ALTER SESSION statement. On EBS 12.1.1 and 12.2.2 the object resides in the APPS schema, so all referenced tables are accessed through APPS synonyms.