Search Results excise_taxformula

Overview

The APPS.JA_JAINSITR_XMLP_PKG package is a report-logic PL/SQL package associated with the Oracle E-Business Suite India Localization (JA schema) supplementary invoice register. It is a generated XML Publisher (XMLP) package, as indicated by the _XMLP_PKG suffix, and encases the PL/SQL formulae and reporting hooks required by an Oracle Reports / XML Publisher concurrent program that produces the India Supplementary Invoice Statement (JAINSITR). The package is owned by APPS and declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the defining schema, a standard convention for EBS report packages that must respect the calling responsibility and security model.

The business purpose of this package is to compute and supply reporting values for supplementary invoices—tax documents used in India for excise, customs, service tax, and other statutory reporting. Package-level state (customers, supplementary type, invoice number, site use ID, process date, and the concurrent request ID) is populated at report execution, and formula functions derive the amounts and identifiers displayed on the report layout.

Key Procedures and Functions

The package exposes eight documented functions, structured to satisfy the data model and formula columns demanded by the XML Publisher template:

• SERIAL_FFORMULA — Returns a serial or running sequence value used in the report output (for example, a serialized count of records on the register).
• EXCISE_TAXFORMULA — Returns the excise tax amount associated with a given customer transaction and supplementary invoice type.
• CF_5FORMULA — A generic "column formula" placeholder (the CF_5 naming reflects the fifth computed column in the generated report). It returns a computed amount for the given customer transaction and supplementary invoice type; the exact business meaning is defined within the report definition itself.
• CSTFORMULA — Computes the Central Sales Tax (CST) amount for the transaction and supplementary invoice type.
• OTHERS_FORMULA — Returns the aggregate of all other tax or charge components not covered by excise or CST.
• BEFOREREPORT — The standard Oracle Reports before-report trigger, returning a BOOLEAN to signal successful initialization (typically loading the concurrent request ID and setup values).
• AFTERREPORT — The after-report trigger, returning a BOOLEAN; used for cleanup or terminating report processing.
• SERIAL_NUMBER_P — Accessor function returning the current serial number held in package state.

Note that the tax formula functions share a common signature accepting a customer transaction ID and a supplementary invoice type, allowing the report to resolve the correct tax basis per invoice line. Parameter lists are not reproduced here to avoid inventing arguments; only the documented structure is described.

Tables Accessed

The package references six objects through APPS synonyms:

• JAI_AR_SUP_HDRS_ALL — Stores supplementary invoice headers; used to identify the invoice and supplementary type.
• JAI_AR_SUP_LINES — Supplementary invoice lines, providing line-level tax and amount detail.
• JAI_AR_SUP_TAXES — Supplementary invoice tax records, the primary source for excise, CST, and other tax amounts.
• JAI_CMN_TAXES_ALL — Common tax setup (tax types/regimes) used to resolve tax codes and rates.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — Standard concurrent manager tables, used to retrieve run-time parameters and request context.

Usage Notes

This package is not invoked directly by users. It is registered as the PL/SQL package attached to the JAINSITR concurrent program, and is called by the Oracle Reports runtime when the report is submitted. The BEFOREREPORT and AFTERREPORT functions fire automatically around report processing, while the formula functions are called by the report layout to populate individual fields. Because ETRM records zero dependent packages, the object is a leaf report package with no downstream dependents; modification should therefore be treated as a report-level customization. The 2007 header reference (120.1) indicates this package has been stable across 12.1.1 and 12.2.2, with the source remaining functionally consistent in both releases.