Search Results vat_action

Overview

JAI_RCV_RTV_LINES_V is a reporting view owned by the APPS schema within the JA (Asia/Pacific Localizations) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes Return-to-Vendor (RTV) receipt transaction lines enriched with Asia/Pacific tax attributes — specifically the excise and VAT tracking elements required by regional localization requirements, notably for India and other APAC legislative regimes. The view consolidates transactional receipt data from Receiving with localization-specific attributes held in the JAI tax extension tables, producing a single denormalized row per RTV line suitable for tax reporting, statutory extracts, and downstream integration.

The view carries a VALID status in the data dictionary and is intended primarily for read-only reporting. It is not a transactional entity; it does not support DML. Its principal value lies in surfacing the VAT_ACTION and EXCISE_ACTION columns alongside standard receiving identifiers, allowing localization tax logic and audit queries to join directly against return-to-vendor activity.

Underlying Base Objects

The view is defined as a three-way join over the following documented base objects, all referenced via APPS synonyms:

• JAI_RCV_TRANSACTIONS — the JA localization extension table holding tax-specific attributes per receiving transaction, aliased as JRT and serving as the driving table.
• RCV_TRANSACTIONS — the core Receiving transaction table, aliased as RT, supplying vendor, pricing, and source document quantity information.
• RCV_SHIPMENT_LINES — the receiving shipment line table, aliased as RCL, supplying item and line-level descriptors.

The join predicates are: RT.TRANSACTION_ID = JRT.TRANSACTION_ID, JRT.SHIPMENT_LINE_ID = RCL.SHIPMENT_LINE_ID, and the filter JRT.TRANSACTION_TYPE = 'RETURN TO VENDOR', which restricts output to RTV transactions only. The JAI_RCV_TRANSACTIONS table holds the localization attributes (excise invoice, VAT invoice, excise/VAT action codes and batch numbers) that are not present in the standard Receiving tables.

Key Columns

• TRANSACTION_ID / PARENT_TRANSACTION_ID — identifies the receiving transaction and its parent, enabling lineage tracing.
• ORGANIZATION_ID, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID — inventory organization and shipment context.
• RECEIPT_NUM, LINE_NUM — human-readable receipt and line references.
• VENDOR_ID, VENDOR_SITE_ID — supplier and supplier site being returned to.
• QUANTITY, SOURCE_DOC_QUANTITY, PO_UNIT_PRICE — returned quantity and originating document quantity with purchase order pricing.
• ITEM_ID, ITEM_DESCRIPTION — the item being returned.
• EXCISE_INVOICE_NO, VAT_INVOICE_NO — localization tax document references.
• EXCISE_ACTION, VAT_ACTION — the localization action codes indicating the tax treatment applied to the return (the column most directly relevant to a search on "vat_action").
• EXCISE_BATCH_NUM, VAT_BATCH_NUM — batch/register references for tax posting.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE4 — descriptive flexfield context and segments.
• CREATION_DATE, TRANSACTION_DATE — audit and business-effective timestamps.
• RMA_REFERENCE — reference to the return material authorization.

Common Use Cases and Queries

Typical scenarios include statutory VAT/excise return reporting, reconciliation of RTV tax postings, and integration extracts feeding external tax filing engines. A representative query follows:

SELECT receipt_num, line_num, vendor_id, item_description, quantity,
  vat_invoice_no, vat_action, excise_action, transaction_date
FROM apps.jai_rcv_rtv_lines_v
WHERE vat_action IS NOT NULL
  AND transaction_date BETWEEN :p_from AND :p_to;

Because the view already filters to TRANSACTION_TYPE = 'RETURN TO VENDOR', consumers need not join RCV_TRANSACTIONS directly. Tuning should account for the join to JAI_RCV_TRANSACTIONS and filtering on ORGANIZATION_ID and TRANSACTION_DATE, the most selective predicates in typical reporting workloads.