Results for “ap_tax_derivations”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_TAX_DERIVATIONS is a table in the AP (Payables) schema of Oracle E-Business Suite. The ETRM documentation classifies it with the description "No longer used," which is the single most important fact about this object. In Oracle EBS 12.1.1 and 12.2.2, this table is a legacy artifact retained in the database for backward compatibility with the Oracle 11i E-Business Tax predecessor model. It holds the vendor-level tax derivation rules that were formerly used to compute withholding or invoice tax based on the vendor's country and state configuration.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is satellite-leaning. The table describes attributes (tax rule identifiers, country, state, tax code) attached to a business entity — the vendor — rather than representing a transaction or a many-to-many relationship. That makes it a candidate for modeling as a satellite keyed on the vendor hub, not as a hub or link. This classification is a modeling suggestion only; the definitive record lies in the Oracle EBS data model.

Key Information Stored

The table is documented with 10 columns. The surrogate primary key is TAX_RULE_ID, enforced by the constraint AP_TAX_DERIVATIONS_PK. This identifier is system-generated and carries no business meaning; it exists solely to uniquely identify each derivation rule row.

The business-key candidate is defined by the unique index AP_TAX_DERIVATIONS_U1 over the column combination (VENDOR_ID, RECEIVING_COUNTRY, RECEIVING_STATE). This triplet establishes the natural uniqueness of a derivation rule: one tax rule per vendor, per receiving country, and per receiving state combination.

• TAX_RULE_ID — surrogate primary key, system-generated.
• VENDOR_ID — foreign key to PO_VENDORS; identifies the supplier to which the derivation rule applies.
• RECEIVING_COUNTRY — the destination country used as a derivation criterion.
• RECEIVING_STATE — the destination state or province used as a derivation criterion.
• TAX_CODE — the tax classification applied when the derivation criteria match.
• CREATED_BY, CREATION_DATE — standard EBS audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording the most recent modification and session.

Common Use Cases and Queries

Because Oracle replaced this derivation mechanism with the E-Business Tax (EBTax) regime in Release 12, no seeded application logic in 12.1.1 or 12.2.2 reads from AP_TAX_DERIVATIONS. Practical use is therefore confined to legacy research, data migration verification, and historical reconciliation after an 11i to R12 upgrade.

A typical historical lookup joins the table to the supplier master to resolve the vendor name:

• Query derivations for a specific vendor: SELECT * FROM ap.ap_tax_derivations WHERE vendor_id = :vendor_id;
• Join to supplier for reporting: SELECT d.tax_rule_id, v.vendor_name, d.receiving_country, d.receiving_state, d.tax_code FROM ap.ap_tax_derivations d, po.po_vendors v WHERE d.vendor_id = v.vendor_id;
• Audit extraction of rules created before a cutoff date using creation_date.
• Row-count and uniqueness validation against AP_TAX_DERIVATIONS_U1 during upgrade testing.

Reporting use cases are limited to historical tax rule documentation and migration audit evidence. No current tax calculation should depend on this table.

Related Objects

The documented foreign-key relationship ties this table to the supplier master:

• PO_VENDORS — joined on AP_TAX_DERIVATIONS.VENDOR_ID = PO_VENDORS.VENDOR_ID; the only documented foreign key.
• AP_SUPPLIERS — the R12 supplier entity that superseded PO_VENDORS; relevant when reconciling legacy vendor identifiers.
• AP_TAX_DERIVATIONS_PK — primary key constraint on TAX_RULE_ID.
• AP_TAX_DERIVATIONS_U1 — unique index on (VENDOR_ID, RECEIVING_COUNTRY, RECEIVING_STATE), the business-key constraint.
• EBTax regime tables such as ZX_REGIMES and ZX_RULES — the functional successors that replaced vendor tax derivation logic in Release 12.

Because the object is documented as no longer used, integrators should treat it as read-only archival data and avoid building new dependencies upon it.