Search Results scheduled_date




Overview
Explore in AI Chat

Overview

The Oracle E-Business Suite view APPS.JAI_RCV_RGM_INSTALLMENT_V is a reporting and integration construct in the ETRM (Enterprise Tax and Receivables Management) family of objects, specifically associated with the localization functionality for Receiving and Returnable Goods Management (RGM). The view presents a summarized, installment-level picture of claim recoveries tied to receiving shipments. Its role is to aggregate amounts recorded in the underlying claims table so that scheduled installment data can be reported and consumed by downstream processes without requiring callers to perform their own GROUP BY aggregation.

Because the view pre-aggregates amounts, it typically serves as a read-only source for inquiries, dashboards, and integration interfaces that need to see how much is recoverable and how much has been claimed for a given shipment header, line, and scheduled installment. The naming convention (the JAI_ prefix) indicates it belongs to the Oracle EBS localization layer rather than the core Oracle Receiving schema.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined with the owner APPS and references a single documented base object: the synonym JAI_RCV_RGM_CLAIMS. The view text selects from this object, aliased as A:

  • SELECT shipment_header_id, shipment_line_id, installment_no, scheduled_date, NVL(SUM(a.installment_amount),0) recoverable_amount, NVL(SUM(a.claimed_amount),0) claimed_amount FROM jai_rcv_rgm_claims a GROUP BY shipment_header_id, shipment_line_id, installment_no, scheduled_date

The parenthesized synonym reference shown in the metadata (JAI_RCV_RGM_CLAIMS (SYNONYM)) indicates that callers resolve the underlying physical table through the APPS synonym layer. The grouping keys — shipment_header_id, shipment_line_id, installment_no, and scheduled_date — define the level of granularity at which recoverable and claimed amounts are rolled up.

Key Columns

  • SHIPMENT_HEADER_ID — Identifier of the receiving shipment header that the claim installment relates to; part of the grouping key.
  • SHIPMENT_LINE_ID — Identifier of the specific shipment line; narrows the claim to a line-level entity.
  • INSTALLMENT_NO — The installment sequence number, indicating which scheduled installment the aggregated amounts belong to.
  • SCHEDULED_DATE — The date on which the installment is scheduled; a grouping key and the column most commonly used for date-range filtering and aging.
  • RECOVERABLE_AMOUNT — The sum of INSTALLMENT_AMOUNT across matching claim rows, coalesced to zero via NVL(...,0) so that null sums are never returned.
  • CLAIMED_AMOUNT — The sum of CLAIMED_AMOUNT across matching claim rows, likewise coalesced to zero.

Common Use Cases and Queries

The view is most often queried when reconciling what has been scheduled against what has actually been claimed for a shipment. A typical query filters on the scheduled date to isolate an accounting or reporting period:

  • SELECT shipment_header_id, shipment_line_id, installment_no, scheduled_date, recoverable_amount, claimed_amount FROM apps.jai_rcv_rgm_installment_v WHERE scheduled_date BETWEEN :p_from AND :p_to ORDER BY scheduled_date;
  • To identify outstanding balances, compare the two aggregated measures: ... WHERE recoverable_amount > claimed_amount.
  • To drill into a single shipment line: ... WHERE shipment_header_id = :p_header AND shipment_line_id = :p_line.

Because the view already groups by installment number and schedule date, it is suitable for aging reports, installment schedules, and integration extracts that feed downstream recovery or reconciliation programs. Filters on SCHEDULED_DATE, header, or line identifiers are the most efficient access paths given the view's GROUP BY structure.