Search Results cp_excise_1




Overview

The APPS.JA_JAINTSLS_XMLP_PKG package is a report logic container generated for the Oracle EBS India Localization (JA schema) "India Sales Tax" register report. It is bound to the BI Publisher/XML Publisher concurrent program JAINTSLS, which produces the India Sales Tax register and related statutory output for the Receivables (AR) subledger. The package encapsulates the PL/SQL formula columns, parameter validation triggers, and report-level Before/After Report functions required by the XML Publisher data template.

The header line confirms the object is compiled AUTHID CURRENT_USER and carries the RCS identifier $Header: JAINTSLSS.pls 120.1 2007/12/25 … noship $, indicating it is a "no ship" (non-shipped, internal) source artifact generated by the XML Publisher template builder rather than an application-programming interface. The declared globals (P_START_DATE, P_END_DATE, P_ORGANIZATION_ID, P_LOCATION_ID, P_TAX_NAME, P_TAX_ID, P_TAX_TYPE, P_REPORT_STYLE, P_ORG_ID, P_CONC_REQUEST_ID) map directly to the report's concurrent program parameters and are populated at run time from the concurrent request context.

Key Procedures and Functions

Sixteen documented program units are exposed, all declared in the package specification:

Tables Accessed

All reads are performed through APPS synonyms. Receivables transaction data is drawn from RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL, with payment terms supplied by AR_PAYMENT_SCHEDULES_ALL. India Localization transaction and tax detail is retrieved from JAI_AR_TRXS, JAI_AR_TRX_LINES, and JAI_AR_TRX_TAX_LINES. Supporting master data comes from JAI_CMN_TAXES_ALL (tax definitions) and JAI_CMN_CUS_ADDRESSES (customer/address details used for the report header). Concurrent program metadata and request context are read from FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS.

Usage Notes

This package is not a general-purpose API and is not referenced by any other package. It is invoked exclusively in the context of the JAINTSLS concurrent program: the concurrent manager calls the report entry point, which in turn calls BEFOREREPORT, the XML data template's SQL (which invokes the CF_* formula functions through the package), and finally AFTERREPORT. Parameter validation runs against P_END_DATEVALIDTRIGGER before submission. In 12.1.1 and 12.2.2 the object behaves identically, as its source predates both releases; in 12.2.x it remains compiled against the APPS edition. Customizations should not be applied directly to this generated package, since regeneration by the XML Publisher designer will overwrite modifications; extension points belong in the report template or in a separately named custom package.