Results for “scheduled_date”

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

Overview

The JAI_RCV_RGM_INSTALLMENT_V view is a reporting and integration object owned by the APPS schema and shipped as part of the JA — Asia/Pacific Localizations product family in Oracle EBS 12.1.1 and 12.2.2. Its name derives from the Receiving (RCV) and Regime (RGM) functional areas, and it presents a consolidated, installment-level summary of recoverable and claimed amounts tracked against the underlying claims data. In practice, the view abstracts the raw claims ledger into a grouped schedule that can be consumed directly by localization reports, reconciliation inquiries, and downstream integrations without the caller needing to replicate the aggregation logic.

The object is a standard (non-materialized) database view. In the documented ETRM metadata for 12.2.2 its status is VALID, so it will be returned by dictionary queries such as ALL_VIEWS and ALL_DEPENDENCIES and can be safely referenced in custom SQL, BI Publisher data models, and Oracle Reports concurrent programs.

Underlying Base Objects

The view is defined over a single documented base object, the synonym JAI_RCV_RGM_CLAIMS. The view text aggregates that source table and therefore inherits the transactional grain of an individual claim record, collapsing it to a unique combination of shipment, line, installment, and scheduled date.

The defining query is:

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

Because the view performs no joins to receiving headers, lines, or lookup tables, it cannot supply descriptive attributes such as item, supplier, or currency. Callers requiring those fields must join back to the appropriate receiving or purchasing tables on SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID.

Key Columns

• SHIPMENT_HEADER_ID — Foreign key to the receiving shipment header. Part of the grouping key and the primary join path to RCV_SHIPMENT_HEADERS.
• SHIPMENT_LINE_ID — Foreign key to the receiving shipment line. Combined with the header it identifies the specific receipt line against which the installment is claimed.
• INSTALLMENT_NO — The installment sequence number within the shipment line's recovery schedule.
• SCHEDULED_DATE — The due date on which the installment is expected to be recoverable.
• RECOVERABLE_AMOUNT — The sum of INSTALLMENT_AMOUNT from the source claims, defaulted to zero via NVL where no amount exists.
• CLAIMED_AMOUNT — The sum of amounts already claimed, also defaulted to zero. The difference between this and RECOVERABLE_AMOUNT yields the open balance per installment.

Common Use Cases and Queries

A frequent requirement is to report the outstanding recoverable balance per shipment line and scheduled date. The following query selects that information for a given shipment:

SELECT v.shipment_header_id,
       v.shipment_line_id,
       v.installment_no,
       v.scheduled_date,
       v.recoverable_amount,
       v.claimed_amount,
       v.recoverable_amount - v.claimed_amount outstanding_amount
FROM   jai_rcv_rgm_installment_v v
WHERE  v.shipment_header_id = :p_shipment_header_id
ORDER BY v.shipment_line_id, v.installment_no;

Other typical scenarios include aging analysis by SCHEDULED_DATE, reconciliation between claimed and recoverable totals, and driving installment-based recovery reports in the Asia/Pacific localization set. When descriptive context is required, join to RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES on the identifier columns. Because the view aggregates at runtime, performance depends on the volume of JAI_RCV_RGM_CLAIMS; filtering by shipment identifiers or date ranges is recommended.