Search Results q_first_party




Overview
Explore in AI Chat

Overview

JE_IL_TAX_PKG is a PL/SQL package body owned by APPS within the Oracle E-Business Suite, classified under the OTHER API category. The package supports Israeli withholding tax and local tax reporting requirements, principally by supplying the data extraction and validation logic that drives a corresponding Oracle Reports data template. The "IL" designation reflects its regional scope: it produces the deduction file number validation, taxpayer identifier checks, and withholding amount calculations that Israeli statutory tax reporting demands for accounts payable transactions. The package body carries a header revision marker (120.11.12010000.2, dated 2008/08/04), indicating it belongs to the mature 12.x code line that spans 12.1.1 and 12.2.2. Unlike callable public APIs, this package is a report-support object: its functions are invoked as report triggers and as formula columns or group filters inside the data template, and it is not referenced by any other package in the EBS codebase.

Key Procedures and Functions

The package exposes seven documented program units, each serving the report execution model:

  • BEFOREREPORT — Called as the Before Report trigger. Per the embedded comments, its responsibility is to populate data into a global temporary table and to construct the dynamic WHERE clause consumed by the data template queries through lexical references. In the documented excerpt the function returns TRUE.
  • IS_NUMBER — Called from the Q_FIRST_PARTY and Q_VENDOR_SITE queries of the data template. It validates the Deduction File Number, the company's Taxpayer Id, and the supplier's Taxpayer Id by attempting a numeric conversion on the supplied string. On failure it raises a localized message (JE_IL_INVALID_DFN, JE_IL_INVALID_TAXPAYER_ID, or JE_IL_INVALID_SUP_TAXPAYER_ID with the vendor number as token), writes the message to the report log, and re-raises the exception.
  • GET_GROSS_AMOUNT — Returns the gross invoice amount used as the basis for withholding tax computation. This is the value most commonly referenced by report formula columns, making it the focal point of "get_gross_amount" searches.
  • GET_AWT_AMOUNT — Returns the calculated amount withheld at source (AWT) for the transaction under evaluation.
  • GET_INVOICE_ID — Resolves and returns the invoice identifier associated with the report row, used to join report output back to detail data.
  • GET_AWT_AMT — An alternate or context-specific accessor for the withheld amount, typically applied where a different derivation path or currency context applies.
  • GET_AWT_BANK_AMT — Returns the withheld amount as it pertains to bank payment records, reconciling withholding to actual disbursements.

Tables Accessed

The package reads from the core payables, subledger accounting, and ledger tables through APPS synonyms: AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL for invoice header and distribution amounts; AP_CHECKS_ALL and AP_INVOICE_PAYMENTS_ALL for payment and disbursement detail required by GET_AWT_BANK_AMT; XLA_AE_HEADERS, XLA_AE_LINES, and XLA_DISTRIBUTION_LINKS for subledger accounting entries and their linkage to distributions; GL_LEDGERS and GL_LEDGER_RELATIONSHIPS for ledger and secondary-ledger context; and PLITBLM for the financials-style temporary storage used during report processing. These accesses are read-oriented, consistent with a reporting package, with the possible exception of temporary-table population performed in BEFOREREPORT.

Usage Notes

JE_IL_TAX_PKG is not an application programming interface in the conventional sense. It is invoked exclusively through the Israeli withholding tax report data template: BEFOREREPORT fires once at report start, and IS_NUMBER, GET_GROSS_AMOUNT, GET_AWT_AMOUNT, GET_INVOICE_ID, GET_AWT_AMT, and GET_AWT_BANK_AMT execute per row within group queries. No other EBS package references it, so upgrade impact is confined to the report definition and the package itself. Developers extending Israeli tax reporting should call these functions from within the associated data template rather than from standalone custom code, since the functions assume report-session context such as FND message logging and the temporary-table state established by BEFOREREPORT.