Search Results rlm_cust_item_terms_all




Overview
Explore in AI Chat

Overview

The RLM_CUST_ITEM_TERMS_ALL table is a core data structure within the Oracle E-Business Suite Release Management (RLM) module, introduced in the R12 release. It represents a significant architectural evolution, centralizing customer-specific item attributes that are contingent upon the ship-from organization and customer item relationship. Its primary role is to store detailed terms and conditions governing how specific items are supplied to specific customers from specific shipping locations. This table is critical for enabling complex release management, scheduling agreements, and customer-specific fulfillment logic within the supply chain. As indicated in the documentation, it supersedes the legacy VEH_MTL_CUSTOMER_ITEMS table, with key attributes being migrated forward as part of a phased implementation strategy, ultimately eliminating the predecessor object.

Key Information Stored

The table stores attributes that define the commercial and logistical terms for a customer item sourced from a particular organization. While the full column list is not detailed in the provided excerpt, the structure is anchored by the primary key column CUST_ITEM_TERMS_ID. Based on its functional description, typical data stored would include identifiers for the inventory item (ITEM_ID), customer (CUSTOMER_ID), ship-from organization (SHIP_FROM_ORG_ID), and potentially the customer's item number. It likely holds terms such as release horizon days, acceptable over/under shipment tolerances, shipping instructions, packaging requirements, and other customer-item-organization-specific parameters that drive the release generation and order management processes.

Common Use Cases and Queries

This table is primarily accessed to retrieve the governing terms for a customer's item release. Common operational and reporting use cases include validating release quantities against agreed tolerances, determining the applicable shipping instructions for an order line, and auditing customer-item agreements. A fundamental query pattern involves joining to inventory, customer, and organization tables to resolve IDs into meaningful names.

  • Sample Query for Item Terms:
    SELECT ctt.*, msi.segment1 item_code, hp.party_name customer_name
    FROM rlm_cust_item_terms_all ctt,
        mtl_system_items_b msi,
        hz_cust_accounts hca,
        hz_parties hp
    WHERE ctt.inventory_item_id = msi.inventory_item_id
    AND ctt.ship_from_org_id = msi.organization_id
    AND ctt.customer_id = hca.cust_account_id
    AND hca.party_id = hp.party_id
    AND hca.account_number = '&CUSTOMER_NUMBER';

Related Objects

The table's primary integration is through its defined primary key relationship. It serves as a master source for customer item terms, with other RLM and Order Management tables likely referencing it via foreign keys to CUST_ITEM_TERMS_ID. Based on the documented metadata:

  • Primary Key: CUST_ITEM_TERMS_PK on column CUST_ITEM_TERMS_ID. This unique identifier is the point of reference for all dependent foreign key relationships.
  • Predecessor Object: VEH_MTL_CUSTOMER_ITEMS. This was the Phase 1 table from which attributes were carried forward during the migration to the R12 RLM_CUST_ITEM_TERMS_ALL structure.
  • Logical Dependencies: The table inherently relates to foundational EBS entities such as MTL_SYSTEM_ITEMS_B (for items), HZ_CUST_ACCOUNTS (for customers), and HR_ORGANIZATION_UNITS (for ship-from organizations), though these are typically joined via business key columns rather than documented foreign keys.