Search Results entered_transaction_amount

Overview

PO_ACCRUAL_RECONCILE_TEMP is a Purchasing (PO) module view in Oracle E-Business Suite, documented in ETRM for the 12.1.1 and 12.2.2 releases. Within the accrual reconciliation workflow, it presents the interim, transaction-level detail used to compare period-end purchasing accruals against the invoices, receipts, and adjustments that ultimately clear them. The view is a filtered projection over the PO_ACCRUAL_RECONCILE_TEMP_ALL table, and its row scope is deliberately restricted by the organization of the current session.

That restriction is implemented in the view's WHERE clause through a decode of USERENV('CLIENT_INFO'), which reads the leading characters of the client information string and resolves them to an operating unit (ORG_ID). Rows are therefore returned only for the organization currently set in the user's session, which is the standard mechanism by which multi-org secured views in Purchasing isolate data by operating unit. The ETRM record carries the note "Retrofitted" and "Not implemented in this database," indicating that the object exists as part of the documented repository but was not physically created in the source environment from which the metadata was captured.

Underlying Base Objects

The only documented base object is PO_ACCRUAL_RECONCILE_TEMP_ALL, from which every column is selected. Because the view is a single-table projection with an ORG_ID predicate, no joins are performed internally; the enrichment of accrual lines with vendor, item, invoice, and receipt attributes is already materialized in the base table. The _ALL suffix and the ORG_ID filter together confirm that the base table is the multi-organization variant, while PO_ACCRUAL_RECONCILE_TEMP serves as the operating-unit-scoped access path typically consumed by forms, reports, and concurrent programs. ETRM documents no additional referenced objects, and no base-table ownership is recorded for the view itself.

Key Columns

• PRIMARY_UNIT_OF_MEASURE and PO_UNIT_OF_MEASURE: The primary (inventory) unit of measure and the purchasing unit of measure for the item, enabling quantity comparison across differing purchase and stocking conventions. These directly answer the searched term "primary_unit_of_measure."
• TRANSACTION_QUANTITY, NET_PO_LINE_QUANTITY, TRANSACTION_UNIT_PRICE, AVG_RECEIPT_PRICE: Quantity and price drivers used to recompute accrual values.
• TRANSACTION_AMOUNT, ENTERED_TRANSACTION_AMOUNT, NET_PO_LINE_AMOUNT, INVOICE_PRICE_VARIANCE: Monetary amounts in functional and entered currency.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE: Currency context for amount columns.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_NUM, PO_NUM, PO_DISTRIBUTION_ID, LINE_LOCATION_ID, PO_TRANSACTION_ID, INV_TRANSACTION_ID, WIP_TRANSACTION_ID: Identifiers linking accrual rows to purchase orders, distributions, inventory and WIP transactions.
• INVOICE_ID, INVOICE_NUM, INVOICE_LINE_NUM, LINE_MATCH_ORDER, RECEIPT_NUM, VENDOR_ID, VENDOR_NAME, VENDOR_NAME_ALT: Invoice, receipt, and supplier context.
• ACCRUAL_ACCOUNT_ID, ACCRUAL_CODE, PERIOD_NAME, AGING_DATE, TRANSACTION_DATE: Accounting and timing attributes for reconciliation and aging.
• WRITE_OFF_FLAG, WRITE_OFF_ID, REASON_ID, COMMENTS, ADJUSTMENT_TRANSACTION, DESTINATION_TYPE_CODE, TRANSACTION_SOURCE_CODE, PO_TRANSACTION_TYPE: Status and classification of each accrual line.
• ORG_ID, TRANSACTION_ORGANIZATION_ID, ITEM_MASTER_ORGANIZATION_ID, INVENTORY_ITEM_ID, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID: Organization, item, and concurrent request identifiers.

Common Use Cases and Queries

The view supports period-end accrual reconciliation, accrual aging analysis, write-off processing, and correspondence between received-not-invoiced balances and payables activity. A typical retrieval filters by period and purchase order:

SELECT po_num, po_line_num, inventory_item_id, PRIMARY_UNIT_OF_MEASURE, TRANSACTION_QUANTITY, TRANSACTION_AMOUNT, CURRENCY_CODE, PERIOD_NAME, AGING_DATE FROM PO_ACCRUAL_RECONCILE_TEMP WHERE PERIOD_NAME = :period AND PO_NUM = :po_num ORDER BY PO_LINE_NUM, TRANSACTION_DATE;

Accrual aging and write-off review are equally common:

SELECT VENDOR_NAME, PO_NUM, PO_UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE, NET_PO_LINE_AMOUNT, INVOICE_PRICE_VARIANCE, WRITE_OFF_FLAG, AGING_DATE FROM PO_ACCRUAL_RECONCILE_TEMP WHERE NVL(WRITE_OFF_FLAG,'N') = 'N' AND AGING_DATE < SYSDATE - 90 ORDER BY AGING_DATE;

Because ORG_ID is derived from CLIENT_INFO, callers must initialize the multi-org context before querying, or the predicate will not resolve correctly.