Search Results start_date_commitment




Overview
Explore in AI Chat

Overview

The view SO_COMMITMENTS_V is a reporting construct within the Oracle E-Business Suite Order Entry (OE) module. It exposes active customer commitments — specifically deposits and guarantees — recorded as receivables transactions that are still within their commitment validity window as of the current system date. The view joins transactional receivables data with customer and agreement information to present a consolidated, query-ready result set suitable for reporting, reconciliation, and integration scenarios.

In the context of ETRM 12.1.1 and 12.2.2, the view is registered under the OE – Order Entry product. Its primary purpose is to surface commitments whose start and end dates bracket the current date, allowing users to identify which deposits or guarantees remain in force. The presence of START_DATE_COMMITMENT as a directly exposed column reflects the user's search term and underscores the view's role in date-driven commitment analysis.

Underlying Base Objects

Although the ETRM metadata does not document the underlying base objects, the view text reveals its definition over five core Receivables and Order Entry tables:

  • RA_CUSTOMER_TRX (alias RATRX) — the transaction header, supplying transaction number, commitment start/end dates, customer identifiers, currency, and the agreement reference.
  • RA_CUSTOMER_TRX_LINES (alias RATRL) — transaction line detail, providing extended amount and inventory item.
  • RA_CUSTOMERS (alias RACST) — customer master data, providing the bill-to customer name.
  • SO_AGREEMENTS (alias OEAGR) — agreement information, outer-joined to the transaction to supply the agreement name.
  • RA_CUST_TRX_TYPES (alias RACTT) — transaction type lookup, restricting results to commitment-bearing types.

The join predicates enforce that the transaction type is either DEP (deposit) or GUAR (guarantee), the transaction is complete (COMPLETE_FLAG = 'Y'), and the current date falls between the commitment start and end dates, with NVL defaults to SYSDATE when either date is null.

Key Columns

Common Use Cases and Queries

Typical uses include identifying active deposits and guarantees for a given customer, auditing commitments nearing expiry, and feeding downstream integrations. A representative query follows:

SELECT TRX_NUMBER,
       CUSTOMER_NAME,
       START_DATE_COMMITMENT,
       EXTENDED_AMOUNT,
       INVOICE_CURRENCY_CODE
FROM   SO_COMMITMENTS_V
WHERE  BILL_TO_CUSTOMER_ID = :customer_id
ORDER BY START_DATE_COMMITMENT;

Because the view already filters on SYSDATE against the commitment dates, callers do not need to add date predicates to restrict results to currently active commitments. Note that the ETRM metadata indicates the view is "Not implemented in this database," so availability must be confirmed in each target instance before reliance.