Results for “ar_tax_group_codes”

50+ results




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

Overview

The view APPS.JG_PO_REQ_TAX_LINES_SUMMARY_V is a reporting and integration object within the Oracle E-Business Suite Regional Localizations (JG) product family. It is defined in the APPS schema with a status of VALID and is published as part of the ETRM reference set for releases 12.1.1 and 12.2.2. The view consolidates tax-relevant attributes of purchase requisition lines into a single denormalized structure, joining requisition headers, requisition lines, requisition distributions, supplier and supplier site information, item master data, location data, currency precision, and tax code definitions.

Its principal role is to supply downstream localization and tax reporting processes with requisition tax line detail without requiring callers to reconstruct the multi-table join themselves. Rather than representing a transaction entry screen, it serves as a read-only projection intended for country-specific localization logic, tax extraction routines, and audit reporting where requisition-level tax treatment must be evaluated alongside supplier, location, and currency context.

Underlying Base Objects

The documented ETRM metadata for release 12.2.2 records the owner as APPS and lists DUAL (SYNONYM) among the referenced base objects. This reflects the flattened representation used in the reference repository rather than the full dependency list. The view text itself, as documented, discloses the operative base tables driving the projection:

Because it is a view, no physical storage is consumed; all attributes are derived at query time from the joined base tables.

Key Columns

Common Use Cases and Queries

A frequent requirement is to resolve ship-from and ship-to geography for a requisition — for example, the search term ship_from_city corresponds to supplier site city columns (CITY, PROVINCE) exposed through PO_VENDOR_SITES, while the deliver-to city is surfaced via HRL.TOWN_OR_CITY. A typical query follows:

  • SELECT REQUISITION_HEADER_ID, REQUISITION_LINE_ID, VENDOR_NAME, CITY, PROVINCE, COUNTRY, TAX_RATE, TAX_TYPE FROM APPS.JG_PO_REQ_TAX_LINES_SUMMARY_V WHERE SEGMENT1 = :requisition_number;
  • SELECT DISTRIBUTION_ID, CODE_COMBINATION_ID, RECOVERY_RATE FROM APPS.JG_PO_REQ_TAX_LINES_SUMMARY_V WHERE SET_OF_BOOKS_ID = :sob AND TAX_TYPE = :tax_type;

These patterns support tax auditing, localization extracts, and reconciliation of requisition tax lines against downstream payables documentation.