Search Results ap_extended_withholding_option
Overview
APPS.AP_EXTENDED_WITHHOLDING_PKG is a regional extension wrapper package within the Oracle E-Business Suite Payables module. Its principal business function is to provide a stable, region-neutral entry point through which country-specific extended withholding tax logic can be invoked. The package itself does not implement regional tax rules; instead, it acts as a dispatcher. When invoked, it verifies whether the corresponding regional extended package (JG_EXTENDED_WITHHOLDING_PKG) is installed and, if so, executes the regional routine dynamically. This architecture allows Oracle Payables to ship a single code path for extended withholding while permitting localization teams to supply jurisdiction-specific calculations, reversals, and distribution handling without modifying the base application. The header revision ($Header: apexawts.pls 120.6) confirms the package has been stable since the 11i/12.0 era and remains available in both 12.1.1 and 12.2.2.
Key Procedures and Functions
The package exposes ten documented procedures and functions, several of which are the wrapper/dummy routines described above:
- AP_DO_EXTENDED_WITHHOLDING — Primary driver. Verifies installation of the regional extended package and dynamically executes the extended withholding routine for a given invoice, withholding date, calling module, and amount, returning a success indicator.
- AP_UNDO_EXTENDED_WITHHOLDING — Counterpart to the above, dynamically invoking the regional reversion routine to undo previously applied extended withholding.
- AP_UNDO_TEMP_EXT_WITHHOLDING — Reverses temporary extended withholding entries, typically used during recalculation or invoice adjustment.
- AP_EXT_WITHHOLDING_DEFAULT — Derives or applies default extended withholding attributes for an invoice or distribution.
- AP_EXTENDED_MATCH — Supports matching of extended withholding amounts against invoice distributions.
- AP_EXTENDED_INSERT_DIST — Inserts withholding-related distribution lines into the invoice distribution structure.
- AP_EXTENDED_WITHHOLDING_ACTIVE — Determines whether extended withholding is active for the given context.
- AP_EXTENDED_WITHHOLDING_OPTION — Evaluates and returns the applicable extended withholding option, controlling whether and how extended withholding is applied. This is the procedure most closely associated with the search term ap_extended_withholding_option.
- AP_EXT_WITHHOLDING_PREPAY — Handles extended withholding treatment for prepayment invoices and their application.
- CHECK_WITH_DIS — Validates withholding against distributions, confirming consistency between withheld amounts and distribution lines.
Tables Accessed
Through APPS synonyms the package references several core and localization tables:
- AP_INVOICE_DISTRIBUTIONS / AP_INVOICE_DISTRIBUTIONS_ALL — Read and written to retrieve invoice distribution lines and to insert or adjust withholding distributions.
- AP_TAX_CODES — Consulted to resolve withholding tax code definitions and associated rates.
- JL_ZZ_AP_INV_DIS_WH — The regional (JL/ZZ) invoice distribution withholding table storing jurisdiction-specific withholding detail.
- JL_ZZ_AP_SUP_AWT_CD — The regional supplier withholding code table, used to determine applicable extended withholding codes for a supplier.
Usage Notes
The package is not typically called directly by end users. It is invoked from Payables forms (notably the invoice and payment workbenches), from concurrent programs such as Payables Open Interface, Invoice Validation, and payment processing, and from surrounding PL/SQL APIs that need to apply, reverse, or validate extended withholding. Because it is referenced by sixteen other packages, it forms part of the internal Payables dependency chain. Custom code should call the wrapper rather than the regional JG_ package so that installation checks and dynamic dispatch are honored. When the regional package is absent, the wrapper routines degrade gracefully — this is why they are described as "dummy" procedures. In 12.1.1 and 12.2.2 the package behavior is consistent; the same revision level applies to both releases.