Results for “jai_ap_st_forms_dtl_grprcpt_v”

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

Overview

The JAI_AP_ST_FORMS_DTL_GRPRCPT_V view is a reporting and integration object owned by the APPS schema within the JA – Asia/Pacific Localizations product family of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). It consolidates detail lines from the regional Sales Tax / Withholding Tax statutory forms infrastructure that is used extensively across Asia/Pacific country localizations (notably India, where the JAI_ tables support excise, VAT, CST, and related statutory reporting).

Specifically, this view aggregates tax target amounts and matched amounts at the goods receipt (GR) level, filtered to customer-type parties (PARTY_TYPE_FLAG = 'C') and receipt-related detail rows (ISSUE_RECEIPT_FLAG = 'R'). Its primary role is to expose consolidated tax amount figures per statutory form header, invoice, and transaction, enabling downstream reporting, reconciliation, and extraction for statutory returns. The column alias INV_TAX_TARGET_AMT is the aggregation of the underlying TAX_TARGET_AMOUNT, which is the target tax amount expected to be recovered or matched against issued receipts — the object a user searching for "inv_tax_target_amt" would typically be seeking.

Underlying Base Objects

The view is defined over three documented base objects, all exposed to the APPS schema as synonyms:

• JAI_CMN_STFORM_HDRS_ALL (aliased A) — the statutory form header table, supplying ST_HDR_ID, FORM_TYPE, and PARTY_TYPE_FLAG.
• JAI_CMN_ST_FORM_DTLS (aliased B) — the statutory form detail table, supplying receipt flags, order/transaction identifiers, and the amounts TAX_TARGET_AMOUNT and MATCHED_AMOUNT.
• JAI_CMN_TAXES_ALL (aliased C) — the tax setup table, joined to enforce the relationship between tax, form type, and party type.

The join predicates bind A.ST_HDR_ID = B.ST_HDR_ID, B.TAX_ID = C.TAX_ID, and A.FORM_TYPE = C.STFORM_TYPE, restricting rows to those where the header party type is a customer and the detail line is a receipt. Because the underlying objects are the "ALL" multi-org and detail variant tables, the view inherits their transactional scope and is normally queried through the standard reporting responsibilities.

Key Columns

• ST_HDR_ID — Identifier of the statutory form header from which the detail line originates; the primary grouping key.
• FORM_TYPE — The statutory form classification (from both the header and tax setup join).
• INVOICE_ID — The AP invoice associated with the detail line, enabling link-back to the payables transaction.
• ISSUE_RECEIPT_FLAG — Indicates whether the line relates to an issue or a receipt; the view filters to 'R' (receipt).
• ORDER_FLAG / ORDER_NUMBER — Order-level identifiers for the associated purchase order or transaction order.
• TRX_TYPE_ID / TRX_NUMBER — Transaction type and number, supporting traceability to the originating transaction.
• INV_TAX_TARGET_AMT — The aggregated (SUM of NVL(TAX_TARGET_AMOUNT, 0)) target tax amount for the grouped detail rows. This is the column most commonly referenced when searching for "inv_tax_target_amt".
• INV_MATCHED_AMT — The aggregated (SUM of NVL(MATCHED_AMOUNT, 0)) matched amount, allowing comparison of target versus actually matched tax.

Common Use Cases and Queries

Typical scenarios include reconciling statutory tax targets against matched amounts for issued receipts, feeding statutory form extracts, and diagnosing variances between expected and matched tax at the goods-receipt level.

A representative query to retrieve the consolidated target and matched amounts per form and invoice is:

• SELECT st_hdr_id, form_type, invoice_id, trx_number, inv_tax_target_amt, inv_matched_amt FROM apps.jai_ap_st_forms_dtl_grprcpt_v WHERE invoice_id = :invoice_id;

To isolate variances where the matched amount falls short of the target:

• SELECT st_hdr_id, form_type, invoice_id, trx_number, inv_tax_target_amt, inv_matched_amt FROM apps.jai_ap_st_forms_dtl_grprcpt_v WHERE inv_tax_target_amt <> inv_matched_amt ORDER BY st_hdr_id, invoice_id;

Because the view performs GROUP BY aggregation and inner joins across header, detail, and tax setup, queries should always be filtered by meaningful keys (invoice, form type, or header) to avoid full-scan performance penalties on the large JAI_CMN detail tables.