Search Results arp_tax_view_vertex

Overview

ARP_TAX_VIEW_VERTEX is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM as an "OTHER" API. It resides in the Oracle Receivables (AR) product family, where the ARP prefix denotes Receivables-related database objects. The package functions as a tax view vertex holder, meaning it encapsulates the tax-relevant attributes of a transaction or entity — the "vertices" — that Oracle's E-Business Tax (EBTax) engine evaluates when determining applicable tax rules and rates. In EBS 12.1.1 and 12.2.2, tax determination in Receivables is driven by the tax services layer, and the ARP_TAX_VIEW_VERTEX package provides the Receivables-side representation of those vertex attributes so that the tax engine can process them correctly.

The package is documented as VALID in both releases and depends on SYS.STANDARD only, indicating it is a lightweight, self-contained construct that does not itself query application tables directly. It is referenced by ZX_VTX_USER_PKG, the E-Business Tax user-defined vertex package, confirming its role in the tax vertex framework.

Key Procedures and Functions

The ETRM documents sixteen procedures and functions within this package. Their purpose is to expose individual transaction and party attributes as discrete vertex values to the tax engine:

• PRODUCT_CODE — returns the inventory product code used to classify the item being taxed.
• VENDOR_CONTROL_EXEMPTIONS — supplies vendor-controlled exemption information relevant to tax exemption processing.
• COMPANY_CODE and DIVISION_CODE — provide organizational classification attributes used in tax rule qualification.
• TRX_LINE_TYPE — identifies the line type of the transaction line under evaluation.
• CUSTOMER_CLASS and CUSTOMER_CODE — supply customer classification and customer identifier attributes used to match tax rules.
• GET_EXEMPTIONS — retrieves exemption status or exemption details applicable to the current transaction.
• POO_ADDRESS_CODE and POA_ADDRESS_CODE — return "Point of Order Origin" and "Point of Order Acceptance" address codes, two of the standard EBTax address vertices.
• SHIP_FROM_ADDRESS_CODE and SHIP_TO_ADDRESS_CODE — return the ship-from and ship-to location codes central to place-of-supply determination.
• AUDIT_FLAG — indicates whether tax audit information should be captured for the transaction.
• TOTAL_TAX — exposes the total tax amount calculated for the transaction.
• TRANSACTION_DATE — supplies the transaction date used to select effective-dated tax rates and rules.
• OVERRIDE_PARAMETERS — permits certain tax parameter values to be overridden during determination.

Parameter lists are not documented in the ETRM; only the procedural names and their semantic roles are published.

Tables Accessed

The ETRM metadata for ARP_TAX_VIEW_VERTEX does not list any tables referenced via APPS synonyms, and its only dependency is SYS.STANDARD, which is the PL/SQL standard package. This indicates that the package itself does not directly query or modify application tables. Instead, it collects and returns vertex attribute values supplied by its caller — typically the E-Business Tax tax-determination engine or the ZX_VTX_USER_PKG integration layer — which in turn reads the underlying transaction, customer, and address data from Receivables and EBTax tables. Any data access occurs in the calling context rather than within this package.

Usage Notes

The package is invoked indirectly through the E-Business Tax vertex framework rather than being called by end users. When a Receivables transaction is saved, or when the tax engine is invoked during invoice entry, the tax services layer requests vertex values; ARP_TAX_VIEW_VERTEX supplies the Receivables-specific values from the documented functions, and the returned attributes feed tax rule qualification and rate determination. Because ZX_VTX_USER_PKG references this package, it is part of the user-extensible vertex mechanism within EBS 12.1.1 and 12.2.2. Customizations and extensions that require additional tax attributes should generally be implemented through the supported EBTax configuration and user-defined vertex packages rather than by modifying this seeded package. Direct calls from custom PL/SQL are possible but not recommended, as the seeded API signature is not published as a public interface in the ETRM.