Search Results ap_tax_codes




Overview

PO_TAX_SHIPMENTS_DETAIL_V is a Purchasing (PO) module reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates tax shipment detail across the three procurement document types: purchase orders, purchase order releases, and requisitions. It is documented under the ETRM reference for the PO product and is classified as a view rather than a base table. The view is not implemented as a database object in the reference environment, meaning it is supplied as a shipped Oracle view definition whose availability depends on the installed product set and patch level.

The central purpose of the view is to expose, for each shipment line, the applicable tax code name and the computed recoverable and non-recoverable tax amounts. Because tax recovery in EBS is derived at query time rather than stored on the shipment, the view invokes the PO_TAX_SUMMARY_PKG API functions GET_RECOVERABLE_TAX and GET_NONRECOVERABLE_TAX to calculate these values dynamically. This makes the view a convenience layer for tax reporting and reconciliation rather than a transactional store.

Underlying Base Objects

The view is defined as a three-branch UNION over shipment-level sources, joined to lines, headers, and tax codes. The documented referenced objects are:

ETRM records no referenced base objects for this view in its metadata, so the join structure above is drawn from the shipped view text rather than from a documented dependency list.

Key Columns

  • A literal document-type discriminator ('PO', 'REL', 'REQ') as the first column, identifying which procurement document produced the row.
  • PO_HEADER_ID / PO_RELEASE_ID / REQUISITION_HEADER_ID and the corresponding line identifiers, providing the primary keys needed to trace the row back to source.
  • LINE_LOCATION_ID and SHIPMENT_NUM, the shipment-level identifiers used by the tax summary package calls.
  • CANCEL_FLAG and CLOSED_CODE, indicating shipment status.
  • SHIP_TO_LOCATION_CODE and DEST_ORGANIZATION, the receiving destination.
  • Currency code, resolved with NVL from line level to header level.
  • The tax code NAME from AP_TAX_CODES.
  • Recoverable and non-recoverable tax amounts, computed by PO_TAX_SUMMARY_PKG for document type 'PO'/'REL' or requisition with ship/shipment granularity.
  • Calculated extended amount, derived via DECODE on ORDER_TYPE_LOOKUP_CODE: amount less cancelled amount for fixed price, or quantity less cancelled quantity multiplied by unit price (or PRICE_OVERRIDE) for rate-based lines.
  • PLL.QUANTITY, PLL.QUANTITY_CANCELLED, PLL.AMOUNT, and PLL.AMOUNT_CANCELLED.

Common Use Cases and Queries

The view is typically used for tax recovery analysis, accrual reconciliation, and shipment-level tax reporting. Because it references AP_TAX_CODES, it is a natural starting point for queries that begin from a tax code context, such as the search term "ap_tax_codes". A representative query filters by tax code name and document type:

  • Listing all purchase order shipments bearing a given tax code: SELECT * FROM PO_TAX_SHIPMENTS_DETAIL_V WHERE name = :tax_code AND ROWNUM <= 100.
  • Summarising recoverable versus non-recoverable tax by tax code: SELECT name, SUM(recoverable_tax), SUM(nonrecoverable_tax) FROM PO_TAX_SHIPMENTS_DETAIL_V GROUP BY name.
  • Extracting only requisition-branch rows for requisition tax analysis by filtering on the document-type literal.

Performance is a consideration: the package functions execute per row, so the view should be filtered aggressively before aggregation.