Search Results rlm_cust_shipto_terms_u1

Overview

RLM.RLM_CUST_SHIPTO_TERMS_ALL is a transactional configuration table in the Oracle E-Business Suite Release 12 (12.1.1 and 12.2.2) Process Manufacturing / Oracle Supply Chain module. It stores customer address attributes that are dependent on the ship-from/ship-to relationship. In the R-12 data model, several attributes previously carried forward from VEH_RA_ADDRESSES (which was eliminated in Phase 2 of the redesign) were relocated into this table, giving it a distinct role from generic address masters such as RA_ADDRESSES.

The table holds one row for each ship-from location associated with a ship-to address. In Data Vault terms, the documented physical structure suggests this object is best modeled as a standalone structure — a hub-like entity keyed on the ship-to terms identifier, surrounded by dependent ship-from/ship-to attribute satellites. The heuristic classification (mined from FK structure) is "standalone," with no documented parent-child FK relationships to other objects. Its physical storage resides in the APPS_TS_TX_DATA tablespace with PCT Free 10.

Key Information Stored

The surrogate primary key is CUST_SHIPTO_TERMS_ID, backed by the primary key constraint CUST_SHIPTO_TERMS_PK. The business-key candidate is defined by unique index RLM_CUST_SHIPTO_TERMS_U1 on the composite columns (CUSTOMER_ID, ADDRESS_ID, SHIP_FROM_ORG_ID, ORG_ID). A non-unique index, RLM_CUST_SHIPTO_TERMS_U2, supports the CUST_SHIPTO_TERMS_ID column. This table carries 119 documented columns; the most significant include:

• CUST_SHIPTO_TERMS_ID — Surrogate unique identifier for the ship-to terms row.
• CUSTOMER_ID — Customer identifier; conceptually a FK to RA_CUSTOMERS.
• ADDRESS_ID — Ship-to address identifier; conceptually a FK to RA_ADDRESSES.
• SHIP_FROM_ORG_ID — Ship-from organization identifier; conceptually a FK to MTL_PARAMETERS.
• ORG_ID — Operating unit / organization context for multi-org partitioning.
• CUM_CONTROL_CODE — Determines whether CUM Management is performed by Purchase Order or by Record Keeping Year; validated against FND_LOOKUPS lookup type RLM_CUM_CONTROL_CODE.
• CUM_CURRENT_RECORD_YEAR, CUM_PREVIOUS_RECORD_YEAR, CUM_CURRENT_START_DATE, CUM_PREVIOUS_START_DATE — CUM management cycle definitions.
• CUM_ORG_LEVEL_CODE, CUM_SHIPMENT_RULE_CODE, CUM_YESTERD_TIME_CUTOFF — CUM processing rules and cutoff timing.
• SHIP_METHOD — Shipment method; conceptually a FK to MTL_INTERORG_SHIP_METHODS.
• INTRANSIT_TIME, TIME_UOM_CODE, INTRANSIT_CALC_BASIS — In-transit lead time and its unit of measure.
• SHIP_DELIVERY_RULE_NAME — Default shipment/delivery rule.
• DEMAND_TOLERANCE_ABOVE, DEMAND_TOLERANCE_BELOW — Demand tolerance thresholds.
• DEFAULT_SHIP_FROM — Flags the default ship-from location for the ship-to address.
• INACTIVE_DATE — Date after which the terms row is considered inactive.
• PRICE_LIST_ID, AGREEMENT_ID, BLANKET_NUMBER — Commercial sourcing and agreement references.

Standard EBS audit columns are present (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) along with descriptive flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) and TP_ATTRIBUTE1–15. The ORG_ID column is critical because the table is organization-partitioned, consistent with other RLM_ALL tables.

Common Use Cases and Queries

This table supports planning, order promising, and shipping configuration queries. Typical usage includes retrieving the configured ship-from location(s) for a given ship-to address, determining the applicable CUM control rules, and resolving the in-transit lead time for transportation planning.

Retrieve all ship-from locations for a customer ship-to address with effective dates:

SELECT cst.ship_from_org_id, cst.ship_method, cst.intransit_time,
       cst.cum_control_code, cst.inactive_date
  FROM rlm.rlm_cust_shipto_terms_all cst
 WHERE cst.customer_id = :customer_id
    AND cst.address_id = :address_id
    AND cst.org_id = :org_id
    AND NVL(cst.inactive_date, SYSDATE+1) > SYSDATE;

Another frequent scenario is joining to RA_CUSTOMERS and RA_ADDRESSES to enrich a ship-to report with CUM configuration. Reporting queries typically filter on CUM_CONTROL_CODE to audit which customers have CUM management enabled, or join to MTL_PARAMETERS on SHIP_FROM_ORG_ID to resolve the inventory organization name.

Related Objects

Although the metadata classifies this object as standalone, the following related entities are referenced conceptually in accordance with the documented comments and join conventions:

• RA_CUSTOMERS — joined on CUSTOMER_ID.
• RA_ADDRESSES — joined on ADDRESS_ID to resolve ship-to address details.
• MTL_PARAMETERS — joined on SHIP_FROM_ORG_ID to obtain organization information.
• MTL_INTERORG_SHIP_METHODS — joined on SHIP_METHOD for shipping method definitions.
• FND_LOOKUPS — source of validation for lookup type RLM_CUM_CONTROL_CODE.
• ORG_ORGANIZATION_DEFINITIONS — resolves ORG_ID to the operating unit.
• VEH_RA_ADDRESSES — legacy source object from Phase 1, now replaced in Phase 2.

Developers should treat RLM_CUST_SHIPTO_TERMS_ALL as the authoritative ship-from/ship-to terms store within the RLM schema, and reference RA_ADDRESSES and RA_CUSTOMERS for master data rather than duplicating it.