Search Results update_additional_info

Overview

ZX_GL_EXTRACT_PKG is an Oracle E-Business Tax (EBTax) internal PL/SQL package owned by the APPS schema. It supports the extraction of tax reporting data from E-Business Tax into the General Ledger interface, forming part of the reporting infrastructure that moves tax detail into accounting. The package operates on a set of global variable records defined in the sibling package ZX_EXTRACT_PKG, using the shared record type TRL_GLOBAL_VARIABLES_REC_TYPE to carry transaction, ledger, and registration context between extraction steps. Its header carries the revision marker zxrigextractpvts.pls 120.1, indicating it is a private (non-public-API) packaged component within the tax reporting subsystem. In EBS 12.1.1 and 12.2.2, the package participates in the flow that populates the ZX_REP_ACTG_EXT_T and ZX_REP_TRX_DETAIL_T reporting tables, which underpin tax accounting extracts consumed by General Ledger.

Key Procedures and Functions

• INSERT_TAX_DATA — The primary data-population routine. It accepts the shared TRL_GLOBAL_VARIABLES_REC_TYPE record as an IN OUT NOCOPY parameter and inserts extracted tax data into the reporting tables. Use of NOCOPY indicates a performance-oriented design in which the potentially large record is passed by reference rather than copied.
• UPDATE_ADDITIONAL_INFO — As the name implies, this procedure augments previously inserted extraction rows with additional reporting attributes. This is the object targeted by the update_additional_info search term. Like INSERT_TAX_DATA, it receives the TRL_GLOBAL_VARIABLES_REC_TYPE record IN OUT NOCOPY, allowing it to read the current extraction context and persist supplementary values before the record proceeds through the extraction pipeline.
• PRORATED_TAX — A function returning a NUMBER and accepting a substantial parameter set covering the transaction, ledger, document sequence, tax code, code combination, tax document date, tax class, tax document identifier, customer name, customer reference, registration number, sequence name, and column name. It computes a prorated tax amount, apportioning tax across lines or accounts according to the document sequence and column context supplied. This supports reporting scenarios where a single tax amount must be distributed across multiple accounting distributions.

Tables Accessed

The documented table references (through APPS synonyms) reflect the package's dual role of reading source tax and accounting data and writing reporting output:

• ZX_REP_ACTG_EXT_T / _S and ZX_REP_TRX_DETAIL_T / _S — the tax reporting extract tables (and their _S shadow/interface counterparts) that receive the inserted and updated rows.
• ZX_REGISTRATIONS — supplies tax registration details for the transaction parties involved in the extract.
• GL_JE_HEADERS and GL_JE_LINES — provide General Ledger journal context for reconciling tax amounts to accounting entries.
• GL_CODE_COMBINATIONS — resolves the accounting flexfield combinations used to classify and distribute tax amounts.
• FND_DOCUMENT_SEQUENCES — supplies document sequence information used by the proration logic.
• DUAL and PLITBLM — infrastructure references; DUAL supports scalar evaluation, while PLITBLM is the standard PL/SQL table (index-by table) backing type used by Oracle's packaged code.

Usage Notes

ZX_GL_EXTRACT_PKG is a private reporting utility rather than a public integration API. It is invoked from within the E-Business Tax extraction flow, typically by the parent ZX_EXTRACT_PKG and related extract driver packages (the metadata records it as referenced by one other package). It is not intended to be called directly from forms; UI-driven tax reporting actions reach it through the standard concurrent programs that generate tax accounting extracts and reporting data for General Ledger. Because it manipulates the shared TRL_GLOBAL_VARIABLES_REC_TYPE record, any custom invocation must first initialize that record consistently with the ZX_EXTRACT_PKG contract. The procedures should be treated as internal and version-sensitive; the 120.1 header indicates the sequential revision lineage typical of Oracle's packaged code. Customizations should prefer supported reporting APIs and concurrent programs over direct calls to INSERT_TAX_DATA, UPDATE_ADDITIONAL_INFO, or PRORATED_TAX, since signatures and internal behavior may change across patch levels in both 12.1.1 and 12.2.2.