Search Results get_rule_info

Overview

JL_ZZ_TAX is a Latin American localization (JL schema) tax calculation package owned by APPS and classified in the ETRM as an OTHER-style API. It supports Oracle EBS Receivables tax processing for localization regions that rely on the JL_ZZ_ module family, typically Latin American countries using Latin Tax and related legal reporting. The package embodies the tax determination logic that associates transaction attributes — tax category, transaction type, ship-to and bill-to site uses, inventory item, group tax, memo line, customers, transaction date, application, warehouse, fiscal classification, and transaction nature — with tax codes and rule definitions. It also performs the arithmetic foundation of localized tax: computing taxable base amounts, applying rates, calculating charged and calculated tax, and deriving the legal message text that describes the tax outcome. The package declares package-level global state (for example g_first_tax_line, g_prev_header_id, and several associative array globals) that holds intermediate tax groups and per-line amounts during a calculation run, which indicates it is designed to be called iteratively across transaction lines while retaining context across calls.

Key Procedures and Functions

• GET_CATEGORY_TAX_CODE — Determines the applicable tax code for a transaction line given the full set of transaction context inputs (tax category, transaction type, site uses, item, group tax, memo line, customers, transaction date, application, warehouse, level, fiscal classification, inventory organization, location structure and segment, set of books, transaction nature, base amount, establishment type, contributor type, warehouse location, and transaction nature class). It is the primary tax code resolution entry point.
• GET_CATEGORY_TAX_RULE — Retrieves the tax rule associated with a resolved tax category, establishing which rates or conditions apply.
• GET_RULE_INFO — Returns detailed information about a tax rule, supplying the attributes needed to evaluate the rule during calculation.
• GET_TAX_BASE_RATE — Derives the base rate to be applied against the taxable base amount for the resolved category or rule.
• CALCULATE — The main tax calculation driver that ties together category resolution, rule lookup, base rate, and amount computation for the transaction.
• CALCULATE_TAX_AMOUNT — Computes the tax amount for a given line, producing charged and calculated tax values used on the transaction.
• CALCULATE_LATIN_TAX — Performs Latin American specific tax computation, accommodating multi-level and category-dependent tax logic.
• GET_LEGAL_MESSAGE — Returns the legal message text associated with a calculated tax result. This is the function most directly relevant to the search term "get_legal_message" and is used to surface legally required wording on tax output.

Tables Accessed

The package reads and writes a focused set of Receivables and Trading Community foundation tables through APPS synonyms. Customer and geography data come from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_GEOGRAPHIES, and HR_LOCATIONS_ALL, supporting ship-to/bill-to resolution. Receivables configuration and tax data come from AR_SYSTEM_PARAMETERS, AR_SYSTEM_PARAMETERS_ALL, AR_VAT_TAX, and AR_MEMO_LINES. The localization control tables JL_ZZ_AR_TX_CATEG, JL_ZZ_AR_TX_CAT_ATT, JL_ZZ_AR_TX_ATT_CLS, and JL_ZZ_AR_TX_ATT_VAL hold tax category definitions, category attributes, attribute classes, and attribute values that drive rule and code resolution.

Usage Notes

JL_ZZ_TAX is invoked during Receivables transaction entry and tax calculation, typically behind AutoInvoice, the Transactions form, and localization tax concurrent processes, rather than being called by end users directly. Its package-level variables imply sequential invocation within a calculation session, so callers should not assume stateless behavior between line calls. Two other packages reference it. Custom code should call the documented functions only, never manipulate the global variables, and should expect AUTHID CURRENT_USER privileges to require appropriate grants to the invoking schema.