Search Results ledger_pp_id

Overview

APPS.AP_PREPAY_DEF_TAX_EXTRACT_V is a reporting view in Oracle E-Business Suite (documented for 12.2.2 and applicable to 12.1.1) that exposes prepayment-related deferred tax extract information for Payables. It is a thin projection defined entirely as a SELECT over ZX_AP_DEF_TAX_EXTRACT_V, the E-Business Tax (EBTax) view that supplies deferred tax extract rows for Payables transactions. The AP_PREPAY variant exists to present the same extract data under prepayment-oriented alias names, so that downstream Payables logic, reports, and integrations that operate on prepayments can consume tax distribution, tax line, recoverability, and accounting information using prepayment nomenclature without re-deriving those relationships.

The view carries no business logic of its own; it performs column renaming only. Its value lies in semantic alignment: consumers looking for prepayment deferred tax data can query a purpose-named object rather than interpret a generic tax extract view. The presence of SUMMARY_TAX_LINE_ID is significant—this is the column most commonly used to correlate a deferred tax extract row back to a summary tax line, which is central to reconciliations and to the user search that surfaced this object.

Underlying Base Objects

The view is defined over a single documented base object:

• ZX_AP_DEF_TAX_EXTRACT_V (VIEW) — the sole referenced object, owned by APPS, providing Payables deferred tax extract data.

Because the dependency is a one-to-one view-on-view relationship, all filtering, joins, and security behavior inherited from the EBTax tax extract layer flow directly through AP_PREPAY_DEF_TAX_EXTRACT_V. There are no joins, unions, or aggregations introduced by the AP prepayment view itself; every row returned by ZX_AP_DEF_TAX_EXTRACT_V appears once in AP_PREPAY_DEF_TAX_EXTRACT_V with renamed columns. This also means performance characteristics are governed entirely by the underlying tax extract view and its own base tables. Any row-level security, ledger or org context, or EBTax configuration filtering applied within ZX_AP_DEF_TAX_EXTRACT_V remains in force.

Key Columns

Each column is an alias of a column in ZX_AP_DEF_TAX_EXTRACT_V. The aliases adopt a "PP" (prepayment) suffix to distinguish prepayment usage:

• REC_NREC_PP_TAX_DIST_ID — sourced from REC_NREC_TAX_DIST_ID; identifies the recoverable/non-recoverable tax distribution.
• SUMMARY_TAX_PP_LINE_ID — sourced from SUMMARY_TAX_LINE_ID; the summary tax line identifier, the key correlation point for summary-level tax reporting and the term underlying the user's search.
• TAX_PP_LINE_ID — sourced from TAX_LINE_ID; the detailed tax line identifier.
• TRX_PP_LINE_DIST_ID — sourced from TRX_LINE_DIST_ID; links to the transaction line distribution.
• RECOVERABLE_PP_FLAG — sourced from RECOVERABLE_FLAG; indicates whether the tax is recoverable.
• DEF_REC_PP_SET_OPTION_CODE — sourced from DEF_REC_SETTLEMENT_OPTION_CODE; the deferred recovery settlement option code.
• TAX_PP_ACCOUNT_CCID — sourced from TAX_ACCOUNT_CCID; the tax accounting flexfield combination.
• ORG_PP_ID — sourced from ORG_ID; the operating unit identifier.
• LEDGER_PP_ID — sourced from LEDGER_ID; the ledger identifier.

Common Use Cases and Queries

Typical uses include prepayment deferred tax reconciliation, tax distribution reporting, and integration extracts feeding subledger accounting or external tax systems. Because SUMMARY_TAX_PP_LINE_ID maps to the EBTax summary tax line, a frequent pattern is joining back to EBTax tables on that identifier.

Example—retrieve deferred tax extract rows for a ledger and operating unit:

• SELECT summary_tax_pp_line_id, tax_pp_line_id, trx_pp_line_dist_id, recoverable_pp_flag, tax_pp_account_ccid, org_pp_id, ledger_pp_id FROM apps.ap_prepay_def_tax_extract_v WHERE ledger_pp_id = :p_ledger_id AND org_pp_id = :p_org_id;

Example—filter to recoverable prepayment tax lines:

• SELECT summary_tax_pp_line_id, rec_nrec_pp_tax_dist_id, def_rec_pp_set_option_code, tax_pp_account_ccid FROM apps.ap_prepay_def_tax_extract_v WHERE recoverable_pp_flag = 'Y';

Example—locate rows by summary tax line for reconciliation:

• SELECT summary_tax_pp_line_id, tax_pp_line_id, trx_pp_line_dist_id, tax_pp_account_ccid FROM apps.ap_prepay_def_tax_extract_v WHERE summary_tax_pp_line_id = :p_summary_tax_line_id;

All such queries should be executed against the APPS schema with appropriate EBS responsibility context so that org and ledger access is respected through the underlying tax extract view.