Results for “jai_rcv_costing_v”

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

Overview

JAI_RCV_COSTING_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Asia/Pacific Localizations product (JA). The object has a status of VALID and is documented against ETRM metadata for releases 12.1.1 and 12.2.2. It exposes receiving-related journal entry lines that were previously captured in the JAI_RCV_JOURNAL_ENTRIES table, filtered to focus specifically on costing and delivery accounting activity.

The view is designed to present a compact, query-friendly projection of receipt accounting information. Rather than exposing every journal entry generated by receiving transactions, it filters the underlying data to rows where ACCT_NATURE contains "COSTING" or "DELIVER" (case-insensitive). This makes the view particularly useful for period-end cost analysis, receipt accrual reconciliation, and localization reporting specific to Asia/Pacific installations.

Because the column list includes ORGANIZATION_CODE, TRANSACTION_ID, ACCT_TYPE, PERIOD_NAME, and amounts (ENTERED_DR / ENTERED_CR), the view can be used both for operational reporting and as an integration source for downstream extracts.

Underlying Base Objects

The view is defined over a single documented base object: JAI_RCV_JOURNAL_ENTRIES, which is exposed in the APPS schema as a synonym. The view text selects from that table and applies a WHERE clause filtering on ACCT_NATURE, using UPPER() and LIKE patterns to match any nature value containing "COSTING" or "DELIVER".

The view does not perform joins, aggregations, or grouping. It is a straightforward filtering and projection layer. Date handling is notable: TRUNC() is applied to TRANSACTION_DATE and CREATION_DATE, so the view returns date-only values, which simplifies period grouping and reporting joins. All other columns are passed through unchanged from the base table.

Because the dependency is a single synonym, query performance and data freshness track the base table directly. No materialization or scheduling is involved.

Key Columns

• ORGANIZATION_CODE — the inventory organization identifier for the receipt transaction.
• TRANSACTION_ID — the unique receipt transaction identifier; the primary link back to receiving transactions.
• TRANSACTION_DATE — truncated date of the original transaction.
• CREATION_DATE — truncated date the journal entry row was created.
• ACCT_TYPE — the accounting type associated with the journal line. This is the column central to the user's "acct_type" search interest.
• ACCT_NATURE — the accounting nature, used as the view's filter. Values containing "COSTING" or "DELIVER" are retained.
• SOURCE_NAME — the source of the transaction, typically RCV (Receiving).
• CATEGORY_NAME — the receiving category associated with the line.
• CODE_COMBINATION_ID — the general ledger account combination key; joinable to GL_CODE_COMBINATIONS.
• PERIOD_NAME — the accounting period of the journal entry.
• ENTERED_DR — entered debit amount in the transaction currency.
• ENTERED_CR — entered credit amount in the transaction currency.

Common Use Cases and Queries

A typical use case is reconciling receiving costing journals for a given period and organization. Analysts frequently group by ACCT_TYPE and PERIOD_NAME to review debits and credits, or join CODE_COMBINATION_ID to GL_CODE_COMBINATIONS for account descriptions.

• Costing journal review: SELECT ORGANIZATION_CODE, PERIOD_NAME, ACCT_TYPE, ACCT_NATURE, SUM(ENTERED_DR), SUM(ENTERED_CR) FROM JAI_RCV_COSTING_V GROUP BY ORGANIZATION_CODE, PERIOD_NAME, ACCT_TYPE, ACCT_NATURE;
• Drill-down by transaction: SELECT TRANSACTION_ID, TRANSACTION_DATE, ACCT_NATURE, ENTERED_DR, ENTERED_CR FROM JAI_RCV_COSTING_V WHERE TRANSACTION_ID = :txn_id;
• Period comparison: SELECT PERIOD_NAME, SUM(NVL(ENTERED_DR,0)) - SUM(NVL(ENTERED_CR,0)) FROM JAI_RCV_COSTING_V WHERE ORGANIZATION_CODE = :org GROUP BY PERIOD_NAME ORDER BY PERIOD_NAME;
• Account-level detail: SELECT CODE_COMBINATION_ID, ACCT_TYPE, ENTERED_DR, ENTERED_CR FROM JAI_RCV_COSTING_V WHERE PERIOD_NAME = :period;

Because amounts are stored as entered values, currency is not explicitly exposed; users needing currency conversion should join to the base table or related localization objects. The view is read-only, so it is safe to reference in reports without risk of data modification.