Search Results set_mo_org_id

Overview

JL_ZZ_AR_TX_LIB_PKG is a tax library package owned by the APPS schema in Oracle E-Business Suite. Its name follows the JL_ZZ naming convention associated with Oracle's localizations framework, indicating that it supplies shared tax utility logic rather than a business-facing API. In practice, the package functions as a reusable library for Oracle Receivables tax processing, particularly for Latin American and other regional localizations where the standard E-Business Tax engine requires supplemental country-specific treatment. It exposes a set of public functions and procedures that callers use to resolve tax category identifiers, determine tax-inclusive pricing behavior, attribute fiscal transaction nature codes to inventory and memo lines, and evaluate contributor classification data. The package also maintains session context through a module-level organization identifier, which callers set before invoking other routines. Approximately seventeen other packages reference it, confirming its role as a low-level dependency in the Receivables tax stack.

Key Procedures and Functions

The user's search term, GET_TAX_CATEGORY_ID, corresponds to a public function that accepts a VAT tax identifier and returns the associated tax category identifier. A companion function, GET_TAX_INCLUSIVE_FLAG, takes a tax category identifier and returns the tax-inclusive indicator used to determine whether tax is embedded in the transaction price.

• GET_ITEM_FSC_TXN_NAT_CODE — derives fiscal transaction nature codes for an inventory item, populating item organization, fiscal type, federal, and state tributary attributes through IN OUT parameters.
• GET_MEMO_FSC_TXN_NAT_CODE — performs the equivalent fiscal nature code derivation for a memo line.
• GET_TAX_BASE_RATE_AMOUNT — calculates the tax base rate and tax base amount for a customer transaction line at a given organization.
• GET_TAX_METHOD — returns the applicable tax method for the supplied organization.
• CONTRIBUTOR_CLASS_EXISTS and CONTRIBUTOR_CLASS_CHECK — boolean functions that test whether a contributor classification code applies to a given address.
• POPULATE_CUS_CLS_DETAILS — populates customer classification details for an address and contributor class code.
• GET_LOOKUP_MEANING — resolves a lookup code and lookup type pair to its descriptive meaning.
• SET_MO_ORG_ID and GET_MO_ORG_ID — set and retrieve the session-level organization identifier held in the package state variable.

The documented interface also includes VALIDATE_LOC_CLASSIFICATION, exposed in the package body and metadata.

Tables Accessed

The package operates against both Receivables and reference data through APPS synonyms. It reads AR_VAT_TAX to resolve tax identifiers and categories, and AR_SYSTEM_PARAMETERS_ALL for Receivables system option defaults. Transaction and memo detail is sourced from RA_CUSTOMER_TRX_LINES_ALL and AR_MEMO_LINES. Customer and address classification data comes from HZ_CUST_ACCT_SITES and HZ_GEO_STRUCTURE_LEVELS, with contributor classification stored in JL_ZZ_AR_TX_CUS_CLS. Item fiscal attributes are retrieved from MTL_SYSTEM_ITEMS. E-Business Tax configuration and product options are read from ZX_PRODUCT_OPTIONS and ZX_PRODUCT_OPTIONS_ALL. Writes, where they occur, are limited to the JL_ZZ_AR_TX_CUS_CLS classification table populated by POPULATE_CUS_CLS_DETAILS.

Usage Notes

Because the package is classified as OTHER rather than a supported public API, it should be treated as an internal library. It is typically invoked indirectly by Receivables tax routines, localization packages, and country-specific extensions during transaction entry, tax calculation, and invoice validation. Forms-based flows trigger it when users create or update transactions requiring fiscal nature codes or contributor classification checks. Concurrent programs that extract or validate tax data may call it in batch, provided SET_MO_ORG_ID is invoked first so that organization-sensitive functions such as GET_TAX_METHOD resolve correctly. Custom code should call the documented functions rather than replicating their logic, and developers upgrading between 12.1.1 and 12.2.2 should be aware that the package header references patch 120.6 and internal bug fixes, indicating that behavior is subject to change without public API guarantees.