Search Results time_uom_code




Overview
Explore in AI Chat

Overview

RLM_CUST_SHIPTO_TERMS_UNIQUE is an APPS-owned view within the Release Management (RLM) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes customer ship-to trading terms used by Release Management and Supply Chain scheduling functionality, presenting the attributes that govern how releases and shipments are generated for a specific customer ship-to address and ship-from organization combination. The view is registered in ETRM as VALID and is exposed to reporting, interface, and integration components through the standard APPS schema, meaning it can be queried directly by concurrent programs, BI Publisher data models, OAF pages, and custom PL/SQL that operate under APPS credentials.

The "UNIQUE" designation implies that the view returns one representative or deduplicated row per logical ship-to terms key, filtering or ranking the rows of the underlying base object so that downstream consumers receive a single customer/ship-to/ship-from terms record rather than the entire history. Its purpose in reporting and integration is to provide a stable, single-row-per-key interface to the terms configuration that Release Management uses for cumulative (CUM) processing, planning and shipping day windows, and tolerance handling.

Underlying Base Objects

The documented base object referenced by the view is RLM_CUST_SHIPTO_TERMS, accessed through a synonym in the APPS schema. The view's text (as captured in the ETRM excerpt) is a column-projection SELECT over that base table, including a ROWID alias exposed as ROW_ID:

  • RLM_CUST_SHIPTO_TERMS — the base configuration table that stores customer ship-to terms records, including CUM control, calendar, planning/shipping day ranges, tolerances, and descriptive flexfield attributes.
  • ROW_ID — the ROWID of the underlying physical row, surfaced as a pseudo-key for identifying the source record.
  • CUST_SHIPTO_TERMS_ID — the primary key of the terms record, carried through the view.

Because the view is defined over a synonym rather than a fully qualified table name, its resolution depends on the APPS synonym pointing to the correct base table in the same EBS instance. The uniqueness behavior is applied on top of this base object, so any administrative changes to the base table's data (for example, adding a new active terms record) directly affect the row returned by the view.

Key Columns

The view exposes the full set of base table columns. The most functionally significant include:

Common Use Cases and Queries

The view is typically used to retrieve the effective trading terms for a customer ship-to and supplying organization, particularly where CUM processing dates or planning/shipping windows must be reported or validated. Because it is a view over the base table, query performance depends on the base table's indexes and the predicate selectivity.

A representative query returning the cumulative start dates for a given ship-to context:

  • SELECT customer_id, address_id, ship_from_org_id, cum_control_code, cum_current_start_date, cum_previous_start_date FROM apps.rlm_cust_shipto_terms_unique WHERE customer_id = :p_customer_id AND address_id = :p_address_id AND ship_from_org_id = :p_org_id;

Additional scenarios include:

  • Reporting the current and previous cumulative period start dates for a set of ship-to terms to reconcile CUM balances transferred at year-end.
  • Validating that planning and shipping day windows (PLN_FIRM_DAY_FROM/TO, SHP_FIRM_DAY_FROM/TO, and the forecast and frozen equivalents) are consistently populated before running release or scheduling programs.
  • Joining the view to customer and organization reference tables to produce a terms master report for a Release Management implementation or upgrade assessment.

Care should be taken to filter on the appropriate business keys, since the "UNIQUE" view is intended to yield one row per ship-to terms key; callers requiring historical or all source rows should query the base table RLM_CUST_SHIPTO_TERMS directly.