Search Results import_projects_taxes




Overview

APPS.JAI_AR_IMPORT_POPU_PKG is a localized Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the "OTHER" API category. It is part of the Oracle Financials for India (JAI) product family and operates in the Accounts Receivable (AR) transaction line context. The package header carries the AUTHID CURRENT_USER clause, meaning it executes with the privileges of the calling user rather than the package owner, and its source header identifies revision 120.4.12020000.1 dated 12-March-2013. The change history notes that the package was originally copied from jai_ar_rctla_t.pls, indicating its lineage in India-localized AR receipt and transaction processing. Broadly, the package provides India-specific localization logic for AR transaction lines, including the handling of Modvat recovery, supplementary invoicing, tax deduction at source (TDS) thresholds, and the determination of project-related tax contexts. Because the package is declared as an "OTHER" API, it is not a formally published public API but is instead an internal helper package referenced by other India localization packages, with one documented dependent package in the metadata.

Key Procedures and Functions

  • POP_JAI_INV_AND_SUPPL — Populates India-localized invoice and supplementary invoice data for a given RA_CUSTOMER_TRX_LINES_ALL row. It takes old and new row images plus an action code, and returns a return code and return message by reference. This supports supplementary invoicing scenarios within AR transactions.
  • POP_JAI_RMACM — Populates RMACM-related India localization data (associated with the Modvat Recovery constant declared at package level) for AR transaction lines, accepting old/new row images and an action and returning status code and message.
  • IMPORT_PROJECTS_TAXES — Imports project-related tax information for an AR transaction line, accepting old and new row images and an action, and returning an error message and error flag. This is the procedure directly associated with project context handling in the package.
  • IS_THIS_PROJECTS_CONTEXT — A boolean function that accepts a context value and determines whether that context corresponds to a projects context. This is typically used internally by IMPORT_PROJECTS_TAXES and related logic to decide whether project-specific tax treatment applies to a transaction line.
  • GET_SERVICE_TYPE — Returns a service type string based on a party identifier, party site identifier, and party type. It supports India GST/service classification determination for AR transactions.
  • GET_LEGAL_ENTITY_ID — Returns the legal entity identifier associated with a given customer transaction identifier, supporting India localization rules that are driven by legal entity registration and GSTIN configuration.

Tables Accessed

The package reads and writes AR transaction data primarily through RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL, which supply the transaction header and line context, including bill-to and ship-to customer and site identifiers retrieved by the c_get_address_details cursor. India localization tables include the supplementary header, line, and tax tables (JAI_AR_SUP_HDRS_ALL, JAI_AR_SUP_LINES, JAI_AR_SUP_TAXES), the India transaction and transaction line tables (JAI_AR_TRXS, JAI_AR_TRX_LINES, JAI_AR_TRX_TAX_LINES), the interface lines table JAI_AR_TRX_INS_LINES_T, the India TDS threshold slab and tax tables (JAI_AP_TDS_THHOLD_SLABS, JAI_AP_TDS_THHOLD_TAXES), and India common tables for customer addresses and document taxes (JAI_CMN_CUS_ADDRESSES, JAI_CMN_DOCUMENT_TAXES). Customer site information is validated against HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL.

Usage Notes

This package is invoked from India-localized AR processing logic, typically within the transaction line validation or population flow, rather than directly by end users. It is referenced by one other package in the ETRM metadata, indicating it is an internal dependency of the India AR localization feature set. The IS_THIS_PROJECTS_CONTEXT function, which corresponds to the user's search, is used to evaluate whether a given context should be treated as a projects context so that project-linked tax handling is applied during AR transaction import. Because the package uses AUTHID CURRENT_USER, callers must have appropriate execute privileges on the package and on any underlying objects referenced. Oracle recommends caution when invoking "OTHER" classified packages from custom code, since their signatures and behavior are not part of a formally guaranteed public API and may change across patch levels or releases, including between 12.1.1 and 12.2.2.