Search Results awt_success

Overview

JL_ZZ_AP_WITHHOLDING_PKG is a localization package owned by APPS that implements extended withholding tax (AWT) processing logic for the Oracle E-Business Suite Payables module. Its header comment (jlzzpwhb.pls 120.30) confirms that it belongs to the JL localization layer, and the presence of the JL_ZZ_AP_AWT_TYPES and JL_ZZ_AP_SUPP_AWT_TYPES tables indicates it is used in jurisdictions where withholding tax is governed by country-specific extensions rather than the standard Payables withholding functionality.

The package is classified as OTHER in the EBS Technical Reference Manual, meaning it is not a public API intended for external integration. It is an internal engine that supports the withholding option validation, taxable base computation, withholding rate determination, cumulative-to-date tracking, and proration logic required when invoices are validated and accounted. The debug flag uses FND_PROFILE.value('AFLOG_ENABLED') so runtime tracing can be toggled through standard profile options.

Key Procedures and Functions

The package exposes nineteen documented program units. Their purposes are:

• GET_WITHHOLDING_OPTIONS – Determines which withholding options apply for a supplier, tax, or invoice context.
• GET_GL_PERIOD_NAME – Resolves the corresponding GL period name for a withholding transaction date.
• GET_BASE_CURRENCY_CODE – Returns the functional/base currency used for withholding calculations.
• INITIALIZE_WITHHOLDING_TABLE, INITIALIZE_WITHHOLDING_TYPE, and INITIALIZE_WITHHOLDING_NAME – Set up internal working structures before withholding processing begins.
• GET_TAXABLE_BASE_AMOUNT – Computes the taxable base against which withholding is applied.
• STORE_TAX_NAME, PROCESS_WITHHOLDING_NAME, and PROCESS_WITHHOLDING_TYPE – Sequence the capture and evaluation of withholding names and types.
• PRORATE_WITHHOLDINGS and STORE_PRORATED_WITHHOLDINGS – Allocate withholding amounts across invoice lines or distributions when multiple bases apply.
• STORE_INTO_TEMPORARY_TABLE – Persists intermediate results for subsequent processing.
• PRINT_TAX_NAMES – Outputs diagnostic or reporting detail of the tax names processed.
• JL_ZZ_AP_EXTENDED_MATCH and JL_ZZ_AP_EXT_INSERT_DIST – Perform extended matching and distribution insertion for withholding lines.
• VALIDATE_MULTIPLE_BAL_SEG, VALIDATE_MULT_BS_GATEWAY, and DYNAMIC_CALL_GET_BALSEG – Validate and dynamically resolve balancing segment values (bal_seg) so that withholding accounting entries post to the correct balancing segment.

Tables Accessed

The package reads and writes a defined set of APPS synonyms that span the Payables and General Ledger schemas:

• AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, AP_AWT_BUCKETS, AP_AWT_TAX_RATES, AP_TAX_CODES – source invoice, distribution, and withholding rate data.
• AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE – used when withholding is applied during Payables Open Interface import.
• JL_ZZ_AP_AWT_TYPES, JL_ZZ_AP_SUPP_AWT_TYPES, JL_ZZ_AP_SUP_AWT_CD, JL_ZZ_AP_INV_DIS_WH, JL_ZZ_AP_INV_DIS_WH_S – localization setup and withholding result tables.
• GL_PERIOD_STATUSES, AP_OTHER_PERIODS, AP_SYSTEM_PARAMETERS – period and system-level defaults for accounting date derivation.

Usage Notes

The package is invoked internally during invoice validation, Payables Open Interface import, and Accounting events where withholding must be computed and posted. It is also referenced by four other packages within APPS, indicating a shared dependency within the localization stack. It is not intended for direct invocation by customer code; the recommended integration point remains the standard Payables APIs, which in turn call this package.

Because of the presence of VALIDATE_MULTIPLE_BAL_SEG, VALIDATE_MULT_BS_GATEWAY, and DYNAMIC_CALL_GET_BALSEG, administrators should verify that balancing segment configuration and Security Rules are correctly defined before enabling extended withholding; the package dynamically resolves balancing segment values, and misconfiguration will produce validation errors during invoice validation rather than at setup time.