Results for “jai_rcv_cenvat_claims”

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

Overview

The JAI_RCV_CENVAT_CLAIMS table is a core data object within the JA - Asia/Pacific Localizations product family of Oracle E-Business Suite. It stores the Central Value Added Tax (CENVAT) percentage and related amounts claimed against a receipt for a Manufacturing Organization. CENVAT is the Indian indirect tax regime that allows manufacturers to offset excise duty paid on input materials against the duty payable on finished goods; this table records the claimable portion associated with each receiving transaction so that the localization engine can compute the eligible credit precisely.

The table resides in the JA schema and is marked VALID in both the 12.1.1 and 12.2.2 releases. Its documented primary key is JAI_RCV_CENVAT_CLAIMS_PK, defined on the TRANSACTION_ID column.

From a dimensional modeling perspective, the FK topology suggests this object behaves as a link table: it connects receiving transactions, shipment lines, vendors, and vendor sites while also carrying its own descriptive CENVAT attributes. This is offered as a heuristic Data Vault suggestion rather than an Oracle-documented classification, and it aligns with the table's role as an associative intersection between the receiving event and the party/tax claim context.

Key Information Stored

The table contains 26 documented columns. The most business-significant are outlined below.

• TRANSACTION_ID — surrogate primary key and the join to RCV_TRANSACTIONS; uniquely identifies each CENVAT claim record.
• SHIPMENT_LINE_ID — links the claim to the specific receipt line in RCV_SHIPMENT_LINES.
• CENVAT_AMOUNT and CENVAT_CLAIMED_AMT — the assessed and actually claimed tax amounts.
• CENVAT_CLAIMED_PTG — the percentage of CENVAT claimed on the receipt, central to the table's purpose.
• CENVAT_SEQUENCE — ordering attribute for multiple claims against the same receipt.
• VENDOR_ID and VENDOR_SITE_ID — parties referencing HZ_PARTIES and HZ_PARTY_SITES.
• UNCLAIM_CENVAT_FLAG, UNCLAIM_CENVAT_DATE, and UNCLAIMED_CENVAT_AMOUNT — reverse or reversal-of-claim tracking.
• PARTIAL_CENVAT_CLAIM and QUANTITY_FOR_2ND_CLAIM — support staged or split claims across deliveries.
• OTHER_CENVAT_AMT and OTHER_CENVAT_CLAIMED_AMT — secondary tax components.
• VENDOR_CHANGED_FLAG and NON_BONDED_DELIVERY_FLAG — status indicators affecting claim eligibility.
• OBJECT_VERSION_NUMBER — concurrency control for the OAF/ADF layer.

The TRANSACTION_ID is the surrogate key; no separate business-key unique index beyond the primary key is documented.

Common Use Cases and Queries

Typical scenarios include reconciliation of claimed versus unclaimed CENVAT, vendor-wise credit analysis, and reversal reporting.

• Retrieving claim percentages for a receipt line:
  SELECT cenvat_claimed_ptg, cenvat_claimed_amt FROM ja.jai_rcv_cenvat_claims WHERE shipment_line_id = :line_id;
• Joining to receiving transactions for audit trails:
  SELECT c.transaction_id, t.transaction_date, c.cenvat_amount FROM ja.jai_rcv_cenvat_claims c, rcv_transactions t WHERE c.transaction_id = t.transaction_id;
• Identifying unclaimed balances: filter rows where UNCLAIM_CENVAT_FLAG = 'Y'.
• Vendor-wise CENVAT summaries grouped by VENDOR_ID.

Related Objects

The documented foreign keys define the principal dependencies:

• RCV_TRANSACTIONS — joined on TRANSACTION_ID; parent receiving transaction.
• RCV_SHIPMENT_LINES — joined on SHIPMENT_LINE_ID; receipt line detail.
• HZ_PARTIES — joined on VENDOR_ID; vendor master.
• HZ_PARTY_SITES — joined on VENDOR_SITE_ID; vendor site.
• PO_HEADERS_ALL / PO_LINES_ALL — indirectly reachable via shipment lines for sourcing context.