Results for “blanket_number”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RLM_BLANKET_RSO is a table in the RLM (Release Management) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the association between blanket release sales orders and customer items, effectively recording which customer item a blanket release number is tied to within a given effective date range. The RLM module governs the movement of consignment inventory and release-order processing for customers, and RLM_BLANKET_RSO provides the linkage that allows a user to tie a specific customer item (from MTL_CUSTOMER_ITEMS) to a blanket release sales order header.

From a heuristic Data Vault modeling perspective, this table is classified as standalone, meaning it is not part of a broader hub/link/satellite hierarchy and functions as an independent reference data set keyed by its own composite unique index.

Key Information Stored

The documented schema lists six columns. The most important include:

  • RSO_HDR_ID — Release sales order header identifier, part of the business-key unique index.
  • CUSTOMER_ITEM_ID — Foreign key to MTL_CUSTOMER_ITEMS, identifying the customer item associated with the blanket release.
  • CUSTOMER_ID — The customer party for whom the blanket release is defined.
  • BLANKET_NUMBER — The blanket agreement or release number forming the business reference.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — The date range during which the blanket-to-customer-item relationship is valid.

The unique index RLM_BLANKET_RSO_U1 is defined on (RSO_HDR_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE), making this the business-key candidate. The table is standalone, so no surrogate primary key column is separately documented; the unique composite key effectively serves as the primary identifier.

Common Use Cases and Queries

Typical usage involves validating which customer item a blanket release sales order header applies to, and within which effective period. A representative query joins to the customer items table:

  • Reporting blanket releases per customer and item for consignment fulfillment.
  • Identifying active blanket relationships as of a given date by filtering on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
  • Reconciling blanket release headers (RSO_HDR_ID) to their associated customer item records.

Sample pattern: SELECT b.BLANKET_NUMBER, b.CUSTOMER_ID, b.CUSTOMER_ITEM_ID FROM RLM.RLM_BLANKET_RSO b WHERE SYSDATE BETWEEN b.EFFECTIVE_START_DATE AND b.EFFECTIVE_END_DATE;

Related Objects

The principal referenced object is:

  • MTL_CUSTOMER_ITEMS — joined on CUSTOMER_ITEM_ID, providing customer item descriptive and cross-reference data.
  • Release sales order header tables in the RLM schema (referenced via RSO_HDR_ID) supply order-level context.
  • Customer master (HZ_CUST_ACCOUNTS / RA_CUSTOMERS) — joined on CUSTOMER_ID for customer name and account details.
  • RLM blanket and release processing views/APIs that consume this mapping for consignment release generation.

Because the table is standalone with a single documented foreign key, its dependency footprint is narrow; joins center on CUSTOMER_ITEM_ID and RSO_HDR_ID.