Search Results ja_jaincini_xmlp_pkg




Overview
Explore in AI Chat

Overview

JA_JAINCINI_XMLP_PKG is a report-support PL/SQL package body owned by APPS and classified under ETRM as OTHER. It belongs to the Oracle E-Business Suite India Localization (JA/JAI schema) and backs an XML Publisher (XMLP) concurrent report — the naming convention JA_INCINI (India excise invoice / inclusive initialization report) combined with the _XMLP_PKG suffix confirms this is the generated report logic package for a BI Publisher template.

The package's operational core is number-to-words conversion for Indian statutory documents. Function CONVERT_NUMBER translates a numeric amount into its spelled-out English (or NLS-translated) representation, which is then wrapped by CF_2FORMULA to produce a label such as "sum of Rs. (in words)". This pattern is typical of Indian tax invoices and excise reports where the invoice total must legally appear both numerically and in words.

Key Procedures and Functions

  • CONVERT_NUMBER — The principal conversion routine, and the object the user searched for. It accepts a numeral and returns a VARCHAR2 word representation. It enforces a maximum of 12 digits (raising a NUMBER_TOO_LARGE exception above that), works on the absolute value, and decomposes the number using Indian numbering units — CRORE (10^7), LAKH (10^5), and THOUSAND (10^3). Unit names are not hard-coded; they are fetched at runtime from JA_LOOKUPS under the lookup type JAI_NLS_TRANSLATION, giving multilingual output. An overloaded variant of CONVERT_NUMBER converts a numeric segment to words via TO_CHAR with the 'Yyyysp' (spelled) date/number format.
  • CF_2FORMULA — Report formula function that formats the sum-of-duty value, prefixing the words from CONVERT_NUMBER with a currency label.
  • CF_3FORMULA through CF_7FORMULA — Additional XML Publisher formula columns that compute and format display values for the report layout.
  • BEFOREREPORT — Standard XMLP pre-execution hook used to initialize package state and report parameters before data retrieval.
  • AFTERREPORT — Standard post-execution hook, typically used to reset state or release resources after the report completes.
  • M_1FORMATTRIGGER, M_2FORMATTRIGGER, M_3_GRPFR1FORMATTRIGGER — Conditional formatting triggers that fire in the report template to apply formatting to specific fields or repeating groups.

Tables Accessed

The package references the following tables through APPS synonyms:

  • JA_LOOKUPS — Read at runtime by CONVERT_NUMBER to resolve the CRORE, LAKH, THOUSAND, and ZERO unit labels from lookup type JAI_NLS_TRANSLATION, enabling NLS-specific word output.
  • RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL — Receivables transaction headers and lines, the primary data source for the invoice figures being converted and printed.
  • JAI_CMN_INVENTORY_ORGS — India localization common inventory organization definition, used to scope the report by operating unit / inventory organization.
  • WSH_NEW_DELIVERIES — Shipping delivery information, supplying dispatch details associated with the transaction.
  • FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — Concurrent Manager metadata, used to identify the program definition and its request parameters.

Usage Notes

This package is not an application programming interface and is not referenced by any other package (referenced by 0 packages per the ETRM metadata). It is invoked exclusively through its associated XML Publisher concurrent program, which the Concurrent Manager calls during report execution. BEFOREREPORT and AFTERREPORT fire automatically at the start and end of each run; the CF_* formula functions and M_* format triggers are invoked by the report template engine at layout time. The overloading of CONVERT_NUMBER means callers should be aware that an INTEGER argument routes to the full Indian-unit word conversion, while a numeric segment argument routes to the date-style spelled conversion. Customers extending the report can reuse CONVERT_NUMBER conceptually, but because the package is generated and carries a "noship" header, direct modification is not supported and changes are lost on patch application; the supported extension point is customizing the JA_LOOKUPS JAI_NLS_TRANSLATION entries to change wording per language.