Results for “receipt_source_code”

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

Overview

The JAI_RCV_CLAIM_MODVAT_V view is a reporting object 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 consolidates receipt transaction data with India-specific Modified Value Added Tax (MODVAT) and Central Value Added Tax (CENVAT) claim information, allowing localization users to reconcile excise-related claims against receiving activity. The view joins receiving transactions to shipment lines, shipment headers, JAI receiving headers and lines, item setup records, and CENVAT claim records, producing a single denormalized result set suitable for reporting, reconciliation, and downstream integration. For users searching on item_modvat_flag, the view surfaces this attribute as ITEM_MODVAT_FLAG, sourced from the item setup table, making it one of the primary entry points for identifying items eligible for MODVAT treatment.

Underlying Base Objects

The view is defined over the following documented base objects:

• RCV_TRANSACTIONS — receiving transaction lines, supplying transaction_ID, transaction_type, destination_type_code, transaction_date, quantity, location_id, and vendor identifiers.
• RCV_SHIPMENT_LINES — shipment line detail, providing to_organization_id and item_id.
• JAI_RCV_HEADERS (SYNONYM) — localization receipt header, contributing excise_invoice_no, excise_invoice_date, online_claim_flag, and receipt_source_code.
• JAI_RCV_LINES (SYNONYM) — localization receipt line, supplying claim_modvat_flag, excise invoice attributes, and online_claim_flag at line level.
• JAI_INV_ITM_SETUPS (SYNONYM) — item setup, source of MODVAT_FLAG (alias ITEM_MODVAT_FLAG) and ITEM_CLASS.
• JAI_RCV_CENVAT_CLAIMS (SYNONYM) — CENVAT claim amounts and percentages, including cenvat_amount, cenvat_claimed_amt, other_cenvat_amt, and second-claim amounts.
• JAI_CMN_INVENTORY_ORGS (SYNONYM) — organization-level manufacturing/trading classification used to derive the CATEGORY column.
• JAI_INV_SUBINV_DTLS (SYNONYM) and HR_LOCATIONS (VIEW) — subinventory and location resolution for the category derivation logic.
• HR_GENERAL (PACKAGE) — referenced supporting package.

Key Columns

• ROW_ID, RECEIPT_NUM, TRANSACTION_ID — row and receipt identifiers for joining and traceability.
• ITEM_ID, ITEM_MODVAT_FLAG, ITEM_CLASS — item identity and its MODVAT eligibility flag from the item setup record.
• CLAIM_MODVAT_FLAG — line-level claim indicator from JAI_RCV_LINES.
• VENDOR_ID, VENDOR_SITE_ID — resolved using the VENDOR_CHANGED_FLAG to select either transaction-level or claim-level vendor.
• CENVAT_AMOUNT, CENVAT_CLAIMED_AMT, CENVAT_CLAIMED_PTG — CENVAT amounts and claimed percentages.
• OTHER_CENVAT_AMT, OTHER_CENVAT_CLAIMED_AMT, CENVAT_AMT_FOR_2ND_CLAIM — supplementary and second-claim amounts.
• ATTRIBUTE1–3 and SHIP_ATTRIBUTE1–3 — excise invoice number/date and online claim flags at line and shipment level respectively.
• CATEGORY — derived from JAI_CMN_INVENTORY_ORGS manufacturing/trading flags, defaulting to 'NN'.
• QUANTITY, CURRENCY_CONVERSION_RATE, TO_ORGANIZATION_ID — transaction quantity, rate, and destination organization.

Common Use Cases and Queries

Typical scenarios include auditing MODVAT-eligible receipt lines, reconciling CENVAT claims to excise invoices, and reporting by item or organization. A representative query filtering on the MODVAT flag is:

• SELECT RECEIPT_NUM, ITEM_ID, ITEM_MODVAT_FLAG, CENVAT_AMOUNT, CENVAT_CLAIMED_AMT FROM JAI_RCV_CLAIM_MODVAT_V WHERE ITEM_MODVAT_FLAG = 'Y' AND CLAIM_MODVAT_FLAG = 'Y';
• SELECT TO_ORGANIZATION_ID, ITEM_CLASS, SUM(CENVAT_CLAIMED_AMT) FROM JAI_RCV_CLAIM_MODVAT_V GROUP BY TO_ORGANIZATION_ID, ITEM_CLASS;
• SELECT RECEIPT_NUM, ATTRIBUTE1, ATTRIBUTE2, ONLINE_CLAIM_FLAG FROM JAI_RCV_CLAIM_MODVAT_V WHERE ONLINE_CLAIM_FLAG = 'Y';

Because the view consolidates multiple localization and standard receiving tables, it is best used for read-only reporting and integration extracts rather than transactional updates.