Search Results g_level_procedure

Overview

ZX_TAX_VERTEX_PKG is a tax-engineering PL/SQL package in the Oracle E-Business Tax (EBTax) module. Its specific responsibility is to validate and normalize the address and geocode data that Oracle passes to Vertex, the third-party tax calculation engine used by EBS for jurisdiction determination. Vertex derives sales, use, and value-added tax results from a combination of geocode, city, county, and postal address elements; if those inputs are malformed, Vertex either returns an error or, worse, silently resolves the wrong taxing jurisdiction. ZX_TAX_VERTEX_PKG acts as a pre-flight gate that confirms these inputs satisfy the format rules Vertex expects before the tax service is invoked.

The package follows the standard EBS PL/SQL logging pattern. It declares a package constant G_PKG_NAME set to 'ZX_TAX_VERTEX_PKG', a G_MODULE_NAME of 'ZX.PLSQL.ZX_TAX_VERTEX_PKG.', and mirrors the FND_LOG runtime levels into local constants. The excerpt confirms the presence of G_LEVEL_PROCEDURE, along with G_LEVEL_UNEXPECTED, G_LEVEL_ERROR, G_LEVEL_EXCEPTION, G_LEVEL_EVENT, and G_LEVEL_STATEMENT. The g_level_procedure search term that led to this object refers to that constant, which is compared against G_CURRENT_RUNTIME_LEVEL to decide whether a procedure-level trace line should be emitted to FND_LOG.

Key Procedures and Functions

• IS_GEOCODE_VALID — Confirms that a supplied geocode is well formed. Based on the source excerpt, the function accepts a geocode value and returns BOOLEAN. It returns TRUE when the value falls within the range '000000000' through '999999999'; otherwise it returns FALSE and raises a formatted error through FND_MESSAGE using the ZX message GENErIC_MESSAGE with the token GENERIC_TEXT. The function brackets its body with .BEGIN and .END log entries at procedure level and writes a 'Geocode is Valid.' or 'Geocode is invalid.' statement at statement level.
• IS_CITY_LIMIT_VALID — Validates the city limit value associated with the address being submitted to Vertex. By analogy with IS_GEOCODE_VALID, it performs a format and range check and signals a message when the input fails.
• INSTALLED — The conventional EBS installation-verification function. It returns a Boolean or status value indicating whether the package is present and callable in the current instance, allowing calling code to degrade gracefully when the Vertex integration is not licensed or not yet installed.

All three are documented as belonging to the APPS schema with an API classification of OTHER, meaning they are internal utilities rather than published public APIs.

Tables Accessed

The only documented table reference is ZX_TAX_VERTEX_QSU, accessed through an APPS synonym. The suffix QSU indicates a QuickCode/Sales-Use lookup set value table belonging to the Vertex integration. It is used to store or retrieve the setup values that govern Vertex address validation, including which validation levels, geocode ranges, and city-limit rules apply for the operating unit or legal entity being processed.

Usage Notes

ZX_TAX_VERTEX_PKG is invoked indirectly rather than by end users. Typical call paths include the EBS Tax calculation routines that build the address payload before calling the Vertex Tax Service, and any concurrent program or forms-based tax setup screen that validates Vertex configuration. It is referenced by one other package in the documented metadata; that caller should be treated as the primary entry point. Only a small number of custom extensions call these routines directly, and such code should invoke IS_GEOCODE_VALID and IS_CITY_LIMIT_VALID before submitting an address to Vertex, honoring the Boolean return and the associated FND_MESSAGE error tokens.