Search Results g_level_error

Overview

ZX_TRL_PUB_PKG is the tax repository line public package in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It provides the application programming interface through which ETRM (E-Business Tax) creates, updates, deletes, and cancels transaction tax lines and summary tax lines in the tax repository. It is classified under the ETRM API classification OTHER and is owned by the APPS schema. The package body is identified in source control as zxrwlnrepsrvpubb.pls, version 120.40, last modified 2006/09/22.

The package operates on the tax repository tables ZX_LINES and ZX_LINES_SUMMARY, and it is the principal entry point for line-level tax repository maintenance. It is referenced by three other packages, which indicates that it functions as a lower-level service layer invoked by higher-level ETRM APIs rather than as an end-user-facing interface. The body declares standard FND_LOG runtime-level constants, including g_level_statement, g_level_procedure, g_level_event, g_level_unexpected, and g_level_error. The g_level_error constant, assigned from FND_LOG.LEVEL_ERROR, is the runtime level used to gate error-level diagnostic messages written through FND_LOG.STRING. The global g_current_runtime_level is initialized once per invocation from FND_LOG.G_CURRENT_RUNTIME_LEVEL.

Key Procedures and Functions

The package exposes twelve documented procedures and functions. MANAGE_TAXLINES is the primary create, update, delete, and cancel driver for tax lines and summary tax lines; it accepts an event class record and returns a status. The body shows that it initializes the return status to FND_API.G_RET_STS_SUCCESS, populates a context information record from the event class (application, entity code, event class code, transaction and transaction line identifiers), and emits procedure-level log messages at entry. SYNCHRONIZE_TAXLINES reconciles tax repository lines with their source transactions. DOCUMENT_LEVEL_CHANGES records document-level changes affecting tax lines. MARK_TAX_LINES_DELETE flags tax lines for deletion. MANAGE_TAXDISTRIBUTIONS and FREEZE_TAXDISTRIBUTIONS handle the creation and freezing of tax distributions. UPDATE_TAXLINES updates existing repository lines, while DISCARD_TAX_ONLY_LINES removes lines that contain tax but no associated transaction amount. UPDATE_GL_DATE and UPDATE_EXCHANGE_RATE modify accounting date and currency conversion attributes on tax lines. DELETE_TAX_LINES_AND_DISTS and DELETE_TAX_DISTS perform physical deletion of tax lines together with their distributions, or of distributions alone.

Tables Accessed

The package reads and writes the following tables through APPS synonyms. ZX_LINES and ZX_LINES_SUMMARY are the core tax repository tables holding detail and summarized tax lines. ZX_REC_NREC_DIST stores recoverable and non-recoverable tax distribution amounts. ZX_EVNT_CLS_MAPPINGS supplies the mapping between event classes and tax configuration used to resolve the correct repository behavior. ZX_TRX_HEADERS_GT is a global temporary table carrying transaction header context. AP_INVOICE_DISTRIBUTIONS_ALL and AP_SELF_ASSESSED_TAX_DIST_ALL are Payables tables accessed when tax lines relate to invoice distributions and self-assessed tax. PLITBLM is an Oracle-supplied index-organized table used internally by PL/SQL for associative array and bulk processing support.

Usage Notes

ZX_TRL_PUB_PKG is invoked programmatically by other ETRM packages (three documented referrers) and by ETRM forms and concurrent programs that must persist tax line changes to the repository. It is not intended for direct end-user execution. Callers are expected to supply a fully populated event class record and to inspect the returned status, since the package follows the standard FND_API success, error, and unexpected return-status convention. Because the package writes to core ETRM repository tables, custom code should always call it rather than performing direct DML on ZX_LINES or ZX_LINES_SUMMARY. The FND_LOG gating pattern means that diagnostic output, including error-level messages controlled by g_level_error, is produced only when the current runtime level is at or below the corresponding severity, so debugging typically requires enabling FND logging for the ZX module before reproducing the issue.