Results for “factor_discount_amount”

44 results




Overview
Explore in AI Chat

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

Overview

ARFV_RECEIPT_HISTORIES is an Oracle E-Business Suite Receivables (AR) view owned by the APPS schema, carrying VALID status in both 12.1.1 and 12.2.2. It presents the audit and status history of cash receipts, exposing the transactional narrative recorded in AR_CASH_RECEIPT_HISTORY alongside descriptive attributes resolved from the receipt, its batch, and the operating unit. The view is a reporting and integration artifact: it flattens a normalized history table into a denormalized, read-only result set suitable for concurrent programs, Oracle Discoverer workbooks, BI Publisher data templates, and inbound or outbound interfaces requiring receipt lifecycle information without joining multiple tables.

The view text is declared WITH READ ONLY, guaranteeing that consumers cannot perform DML through it. It also embeds Oracle Application Framework-style lookup resolution through the _LA: prefixed columns, which map coded values in the base table to their decoded meanings via AR_LOOKUPS. This design allows reporting tools that understand the _LA: convention to render user-facing labels while preserving the underlying code for programmatic consumers.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over four referenced objects, all resolved through APPS synonyms:

  • AR_CASH_RECEIPT_HISTORY — the driving table (alias CRH); each row represents one history event for a cash receipt.
  • AR_CASH_RECEIPTS — inner-joined on CASH_RECEIPT_ID to supply the receipt number and receipt-level context.
  • AR_BATCHES — outer-joined on BATCH_ID to provide the receipt batch name where a batch exists.
  • HR_ALL_ORGANIZATION_UNITS — outer-joined on ORG_ID to resolve the operating unit name.

The joins are deliberately asymmetric: AR_CASH_RECEIPTS and HR_ALL_ORGANIZATION_UNITS are outer-joined (the (+) operator appears on AOU and BAT), while AR_CASH_RECEIPT_HISTORY is the mandatory side. The DISTINCT-style /* UNIQUE ATTRIBUTES */ hint comment indicates the view was generated by Oracle's metadata/ETRM tooling rather than hand-authored, which explains the internal column naming conventions.

Key Columns

The exposed columns fall into several logical groups:

CURRENT_RECORD_FLAG is particularly significant: it identifies the active history row for a receipt, enabling point-in-time reconstruction of receipt state without scanning the full history.

Common Use Cases and Queries

Typical scenarios include receipt audit trails, status-change analysis, and reconciliation of receipt amounts in functional versus entered currency. A representative query returning the current state of receipts for an operating unit is:

  • SELECT h.receipt_number, h.operating_unit, h."_LA:RECEIPT_STATUS" status, h.functional_amount, h.currency_exchange_rate FROM arfv_receipt_histories h WHERE h.org_id = :p_org_id AND h."_LA:CURRENT_RECORD_FLAG" = 'Yes';

For batch-oriented reporting, filtering on RECEIPT_BATCH_NAME and grouping by status produces batch-level summaries suitable for period-end close. For integration, the view supplies a stable, read-only interface for extracting receipt history into a downstream data warehouse without granting direct access to AR base tables. Because ORG_ID is exposed, queries must respect Multi-Org security, and consumers should note that batch and operating unit are outer-joined, so NULL values are expected where those relationships do not exist.