Results for “excise_inv_num”

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

Overview

The view APPS.JAI_PO_REC_MTL_AEL_V is a reporting and integration object delivered with the JA – Asia/Pacific Localizations product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to fetch accounting entries for the Deliver event with Source 'Inventory India' and Category 'MTL'. In other words, the view surfaces the subledger accounting (SLA) data that the Asia/Pacific localization logic creates when inventory material transactions associated with receipt delivery are accounted for under the India inventory regime.

The view is owned by the APPS schema and is documented as VALID. It is not a base transaction table but a denormalized projection that joins receiving, purchasing, inventory, and general ledger accounting entities. Its principal role is to present accounting entry detail — journal header, journal line, code combination, currency conversion, and the originating receipt and shipment context — in a single flattened structure suitable for reporting, reconciliation, and downstream localization interfaces. Because it carries a fixed APPLICATION_ID of 7000 and constant literals such as EVENT_TYPE = 'DELIVERY', TRX_CLASS = 'JAI PO REC DELIVERY', and TRX_CLASS_NAME = 'JAI PO REC', it functions as an accounting event extraction view rather than a general-purpose transactional view.

Underlying Base Objects

The documented base objects underpinning the view span several functional areas. Receiving data is supplied by JAI_RCV_TRANSACTIONS and JAI_RCV_HEADERS (localization synonyms), which provide the transaction type, shipment header reference, organization, quantity, item, excise and VAT invoice details, receipt number and date, and shipment number and date. RCV_SHIPMENT_LINES contributes the receipt line number and the destination subinventory.

Purchasing entities come from PO_VENDORS (a view), PO_VENDOR_SITES_ALL (a view), and HR_LOCATIONS (a view), supplying party name, party number, party site, and location description. Inventory information is drawn from MTL_MATERIAL_TRANSACTIONS and MTL_UNITS_OF_MEASURE_VL for unit of measure resolution.

The accounting side is defined over the GL accounting entities GL_JE_HEADERS, GL_JE_LINES, GL_JE_CATEGORIES, GL_JE_SOURCES, GL_DAILY_CONVERSION_TYPES, and GL_IMPORT_REFERENCES, which together provide ledger, journal category, journal source, currency, entered and accounted amounts, conversion rate and date, and code combination identifiers. Package references FND_GLOBAL and HR_GENERAL are also declared among the base objects, typically used for session and organizational context resolution.

Key Columns

The view exposes accounting identifiers such as JE_HEADER_ID, JE_LINE_NUM, SET_OF_BOOKS_ID (ledger), JE_CATEGORY with USER_JE_CATEGORY_NAME, and JE_SOURCE with USER_JE_SOURCE_NAME. Monetary detail appears through ENTERED_CURRENCY, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, and ACCOUNTED_CR, complemented by CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_USER_CONVERSION_TYPE. ACCOUNT_ID (code combination) and ACCOUNTING_DATE complete the accounting projection.

The user search term receipt_line_number maps directly to the column RECEIPT_LINE_NUMBER, sourced from RCV_SHIPMENT_LINES.LINE_NUM. This is the line-level identifier on the receipt, and it is the natural join key back to receiving and inspection data. Adjacent transactional columns include TRX_TYPE, TRX_HDR_ID (shipment header id), INVENTORY_ORG_ID, ITEM_ID, UOM, QUANTITY, SUB_INVENTORY, and LOCATION. Localization-specific attributes are carried as EXCISE_INV_NUM, EXCISE_INVOICE_DATE, VAT_INV_NUM, and VAT_INVOICE_DATE. Party context is represented by PARTY_NAME, PARTY_NUMBER, and PARTY_SITE, while receipt and shipment identifiers are provided by RECEIPT_NUM, RECEIPT_DATE, SHIPMENT_NUM, and SHIPMENT_DATE. Standard audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY are also included.

Common Use Cases and Queries

Typical uses include reconciling India receipt delivery accounting entries to the General Ledger, tracing a specific receipt line to its journal entry, and feeding localization reporting on excise and VAT references. A representative query retrieving accounting for a given receipt line is shown below.

• Reconcile delivery accounting to GL by receipt line.
• Trace journal lines for a receipt or shipment header.
• Report excise and VAT invoice references by vendor and subinventory.
• Audit entered versus accounted amounts and conversion rates.

SELECT RECEIPT_NUM, RECEIPT_LINE_NUMBER, TRX_TYPE, JE_HEADER_ID, JE_LINE_NUM, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR, ACCOUNTING_DATE FROM APPS.JAI_PO_REC_MTL_AEL_V WHERE RECEIPT_LINE_NUMBER = :p_line AND RECEIPT_NUM = :p_receipt;

Because the view joins a large number of base objects, queries should be filtered by receipt, organization, or accounting date to keep execution efficient.