Search Results aid_def_rec_settle_option_code

Overview

AP_ZX_DEF_TAX_EXTRACT_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Payables (AP). It is registered as a VALID database object in both EBS 12.1.1 and 12.2.2. The view is part of the E-Business Tax (EBTax / ZX) extraction framework that supplies Payables with the definitive tax distribution data required for posting, accounting, and downstream reconciliation.

The view does not function as an independent data source; rather, it is a thin projection layered over the EBTax view ZX_AP_DEF_TAX_EXTRACT_V. Its stated purpose within the ETRM documentation is to expose the definitive tax extract for Payables with a stable column naming convention (AID_*), which is typically consumed by the Oracle Payables open interface, the Subledger Accounting (SLA) engine, or customer-built extracts. Because the object is a view and not a table, it carries no storage of its own and imposes no additional materialization cost; its performance is inherited from the underlying EBTax view and the base transaction tables that feed it.

The AID_ prefix is significant. In Oracle's extraction architecture, AID denotes an "Application Interface Definition" identifier — a surrogate key that shields downstream consumers from primary-key changes in the source schemas. This makes the view suitable as a contract boundary between Payables and EBTax.

Underlying Base Objects

The documented metadata identifies exactly one referenced base object: ZX_AP_DEF_TAX_EXTRACT_V, itself a view in the EBTax product family. There are no direct table references in the view text supplied in the ETRM record. All columns exposed by AP_ZX_DEF_TAX_EXTRACT_V are drawn from that single upstream view, renamed with the AID_ prefix. Consequently, the object hierarchy is:

• AP_ZX_DEF_TAX_EXTRACT_V (APPS view, this object)
• → ZX_AP_DEF_TAX_EXTRACT_V (EBTax view)
• → EBTax base tables (e.g., ZX_LINES, ZX_LINES_DET_FACTORS, ZX_REC_NREC_DIST) reached through the EBTax view definition.

Because the dependency is view-to-view, any change to ZX_AP_DEF_TAX_EXTRACT_V (a patch, an EBTax upgrade, or a customization) propagates directly into this object. Administrators should therefore treat the upstream EBTax view as the effective source of truth and verify it after each EBS patch set or one-off tax patch.

Key Columns

The view text returns eight columns, each mapped to its EBTax counterpart via the AID_ alias. The principal columns are:

• AID_REC_NREC_TAX_DIST_ID — identifier of the recoverable/non-recoverable tax distribution line; the central key linking a tax amount to its accounting distribution.
• AID_SUMMARY_TAX_LINE_ID — identifier of the summarized tax line used for aggregation and reporting.
• AID_TAX_LINE_ID — identifier of the detailed tax line.
• AID_TRX_LINE_DIST_ID — identifier of the transaction line distribution to which the tax applies.
• AID_RECOVERABLE_FLAG — indicates whether the tax amount is recoverable.
• AID_DEF_REC_SETTLE_OPTION_CODE — the default recoverability settlement option code.
• AID_TAX_ACCOUNT_CCID — the accounting flexfield (CCID) for the tax account.
• AID_ORG_ID and AID_LEDGER_ID — the operating unit and ledger context of the extract.

Common Use Cases and Queries

The view is typically queried to reconcile tax distributions against AP invoices, validate recoverability treatment, or drive custom accounting extracts. A straightforward selection is:

• SELECT AID_REC_NREC_TAX_DIST_ID, AID_TAX_LINE_ID, AID_RECOVERABLE_FLAG, AID_TAX_ACCOUNT_CCID, AID_ORG_ID, AID_LEDGER_ID FROM APPS.AP_ZX_DEF_TAX_EXTRACT_V;
• Restricting by ledger: add WHERE AID_LEDGER_ID = :p_ledger_id.
• Isolating recoverable tax for a period: add WHERE AID_RECOVERABLE_FLAG = 'Y'.

Because the view exposes no transaction date or amount column directly, consumers generally join the returned IDs back to EBTax or AP distribution tables for amounts, dates, and invoice context.