Search Results get_tax_code

Overview

The APPS.PA_CLIENT_EXTN_OUTPUT_TAX package body is a client extension stub within the Oracle Projects (PA) module of Oracle E-Business Suite. Its purpose is to provide a controlled extension point through which tax determination logic for project-related output tax can be supplied by implementers, without modifying Oracle seeded code. The package belongs to the client extension layer, as indicated by the CLIENT_EXTN naming convention, and carries an API classification of OTHER in the ETRM repository for releases 12.1.1 and 12.2.2.

The delivered source is intentionally minimal. The entire body consists of a single documented procedure, GET_TAX_CODE, whose default implementation immediately assigns NULL to the output parameter and returns without further processing. This design confirms the package functions as a placeholder or hook: production tax logic is expected to be layered in by the customer, typically through a wrapper or site-specific customization, rather than being delivered by Oracle.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure for this package body:

• GET_TAX_CODE — Accepts project, customer, bill-to and ship-to site use, set of books, expenditure item, event, line type, request, and user identifiers, and returns the applicable output tax code through an OUT NOCOPY parameter. The parameter list is defined in the package specification and remains fixed; the body implementation simply sets the returned tax code to NULL. Because the procedure signature is preserved, any customer implementation must honor the same parameter contract to remain compatible with callers already referencing this extension point.

No additional procedures or functions are documented for this object.

Tables Accessed

No tables are referenced through APPS synonyms in the documented metadata. Consistent with a stub implementation whose only statement assigns NULL to the output parameter, the delivered body performs neither reads nor writes against database tables. Any customer extension that implements actual tax logic would introduce its own table access — for example, to Oracle Receivables tax or project billing reference data — but such access is outside the delivered package and is therefore not reflected in the ETRM documentation.

Usage Notes

The package is referenced by one other package, confirming it participates in the standard Oracle Projects output tax derivation flow rather than being intended for ad hoc invocation. In practice, callers within the Projects billing and invoicing processes invoke GET_TAX_CODE when an output tax code must be determined for a project transaction, passing the relevant project, customer, site, and event context so that a customized implementation can resolve the correct code.

From a customization standpoint, this object represents a supported extension point rather than a business API. The recommended pattern is to preserve the delivered signature and replace the body logic with site-specific derivation rules, ensuring the default NULL return does not propagate into downstream tax calculation. Because the fixed parameter list includes expenditure item and event identifiers, implementations can key tax logic to specific transaction granularity. Callers should continue to invoke the package through its existing callers in the Projects tax flow; direct invocation from custom code is possible but should mirror the context values passed by the seeded caller to avoid inconsistent tax results.