Results for “jai_nls_translation”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.JA_JAINITCR_XMLP_PKG package body is a report logic package that supports the Oracle E-Business Suite (EBS) India Localization (JA) tax reporting suite. Its name derives from the concurrent program XML Publisher report JAINITCR — the India "Certificate under Section 203 of the Income-Tax Act" style report, formatted as a Tax Deducted at Source (TDS) certificate. This package acts as the PL/SQL execution layer for that XML Publisher/BI Publisher report template.

Two responsibilities dominate the package. First, it generates localized, in-words narration of monetary amounts, including the India-specific denominations Crore, Lakh, and Thousand, using the lookup type JAI_NLS_TRANSLATION. This enables the printed certificate to express totals both numerically and as translated text (a bilingual output requirement for Indian statutory documents). Second, it exposes the standard Oracle Reports XML Publisher integration hooks — BEFOREREPORT, AFTERREPORT, and AFTERPFORM — together with a set of report column formulas and a handful of parameter lookup utilities that supply paginated, row-level and page-level values to the template.

The package is owned by APPS and is classified as OTHER (not a documented public API). It is invoked exclusively by the concurrent program infrastructure, not by application forms or by other PL/SQL packages; the metadata confirms zero references from other packages. The full suite comprises 20 documented procedures and functions. The header identifies the source as JAINITCRB.pls, version 120.3, last revised 2008/02/19, confirming an unmodified, pre-12.0.4 code line carried forward through 12.1.1 and 12.2.2.

Key Procedures and Functions

The package can be grouped into four functional families:

• Number-to-words conversion. CONVERT_NUMBER is overloaded. One variant accepts an integer and returns the translated descriptive text, breaking the value into Crore, Lakh, Thousand, and unit segments and validating against a maximum digit threshold with the NUMBER_TOO_LARGE exception. The other variant accepts a numeric segment and formats it using the Yyyysp date-to-text mask to produce spelled-out year text. This is the direct consumer of the JAI_NLS_TRANSLATION lookup.
• Report lifecycle hooks. BEFOREREPORT, AFTERREPORT, and AFTERPFORM are standard XML Publisher report triggers. BEFOREREPORT initializes session and report state; AFTERPFORM runs after each page format section; AFTERREPORT performs end-of-report cleanup.
• Template formulas. A large set of column formulas supplies derived values to the report layout: CF_1FORMULA, CF_2FORMULA, CF_3FORMULA, CP_1FORMULA, BANK_BRANCHFORMULA, CF_VEN_PAN_NOFORMULA, CF_CHECK_DEP_DATEFORMULA, CF_TDS_AMTFORMULA, and CF_BSR_CODEFORMULA. These correspond to the certificate's key data fields: vendor Permanent Account Number (PAN), bank branch, cheque deposit date, TDS amount, and Bankers' Serial/Reconciliation (BSR) code.
• Tax calculation helpers and parameters. CP_CESS_AMT_P, CP_SURCHARGE_AMT_P, CP_SH_CESS_AMT_P, and CP_1_P compute cess, surcharge, and shared-cess amounts. F_SELECTED_CERT_DATE, F_SELECTED_CERT_ID, and F_SELECTED_VENDOR are parameter/select-value functions that return the certificate date, certificate identifier, and vendor selection passed from the concurrent program parameter set.

Tables Accessed

The package reads from and writes to the following documented APPS tables:

• AP payment and banking tables: AP_CHECKS_ALL, AP_INVOICE_PAYMENTS_ALL, AP_BANK_ACCOUNTS_ALL, AP_BANK_ACCOUNT_USES_ALL, and AP_BANK_BRANCHES supply payment, cheque, bank account, and branch details printed on the certificate.
• India TDS tables: JAI_AP_TDS_F16_HDRS_ALL, JAI_AP_TDS_INV_PAYMENTS, JAI_AP_TDS_PAYMENTS, JAI_AP_TDS_VENDOR_HDRS, and JAI_CMN_TAXES_ALL provide the statutory TDS header, invoice-payment, payment, vendor, and tax rate/authority data required to reconcile and format each certificate.
• Concurrent program metadata: FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS resolve the running request's identity and parameters.
• Database/session views: V$DATABASE, V$SESSION, and V$PROCESS are referenced, typically for logging, session context, or diagnostic stamping within the report run.

The lookups JAI_NLS_TRANSLATION (via the JA_LOOKUPS table, connected under synonyms as LC1–LC4) are not listed in the table summary but are read directly in CONVERT_NUMBER.

Usage Notes

This package is not designed for direct invocation. It is instantiated by the XML Publisher engine when the India TDS certificate concurrent program runs, and it is normally executed as the packaged logic bound to the report data definition. The translation behavior is critical: JAI_NLS_TRANSLATION lookup rows must exist for the codes CRORE, LAKH, THOUSAND, and the zero/unit code, for each operating language required. If the concerned translation rows are missing in the target language, the SELECT in CONVERT_NUMBER raises NO_DATA_FOUND, causing the certificate to fail. Implementers troubleshooting a "JAI_NLS_TRANSLATION" search result should therefore first verify that the lookup type JAI_NLS_TRANSLATION contains complete, language-specific rows in JA_LOOKUPS. Because the package carries no database-write operations in its documented logic, runtime failures are typically data- or translation-related rather than transactional.