Search Results supplier_shp_calendar_cd




Overview
Explore in AI Chat

Overview

RLM_CUST_SHIPTO_TERMS_UNIQUE is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, defined within the Order Management / Advanced Supply Chain Planning (ASCP) domain. It exposes shipping and receiving terms configured at the customer ship-to level, including cumulative (CUM) management attributes, planning calendar windows, shipment scheduling rules, and trading-partner attributes. The view is a projection over the underlying ship-to terms data and prefixes every row with a ROWID alias (row_id), exposing the full physical row identity alongside the functional attributes.

Its principal reporting role is to supply planning and order management processes with ship-to-specific terms used to drive cumulative quantity calculations, shipment scheduling cutoffs, transit-time expectations, and demand tolerances. Because it surfaces CUM start dates and cumulative control settings, the view is frequently referenced when users search for terms such as "cum_previous_start_date" — the prior cumulative period start date that governs how shipments are attributed to cumulative windows. The view therefore acts as a stable, application-facing access point for ship-to terms used in concurrent programs, integrations, and analytics.

Underlying Base Objects

The view is defined over a single base object, documented as RLM_CUST_SHIPTO_TERMS, presented through a synonym in the APPS schema. In practice, the synonym resolves to the underlying transactional table that stores customer ship-to terms records, keyed by CUST_SHIPTO_TERMS_ID. The view selects all functional columns from this base object and maps the physical ROWID as row_id, giving consumers a direct handle to the underlying row.

Because the view is a one-to-one projection of the base object with no joins, aggregations, or filtering predicates documented, it behaves as a denormalized read interface over the base table. Reporting and integration code can reference the view without knowledge of the underlying table name, while the ROWID exposure supports downstream update or correlation logic in custom extensions.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing cumulative period boundaries, validating scheduling horizons, and feeding external planning engines. A representative query retrieving cumulative start dates for a customer:

  • SELECT cust_shipto_terms_id, address_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;
  • SELECT row_id, customer_id, address_id, ship_method, intransit_time, time_uom_code FROM apps.rlm_cust_shipto_terms_unique WHERE inactive_date IS NULL;
  • SELECT cust_shipto_terms_id, pln_firm_day_from, pln_firm_day_to, shp_frozen_day_from, demand_tolerance_above FROM apps.rlm_cust_shipto_terms_unique WHERE agreement_id = :p_agreement_id;

Because the view mirrors the base terms table without transformation, it is suitable both for read-only reporting and for correlation back to the source record via row_id when custom logic must reconcile or update ship-to terms.