Results for “cum_note_text”

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

Overview

RLM_CUST_ITEM_CUM_KEYS_V is a reporting view owned by the APPS schema within the RLM (Release Management) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes the contents of the customer item cumulative key entity, providing a flattened, read-consistent projection of cumulative quantity tracking records that govern how shipment quantities are accumulated against customer items across a defined date range. The object carries a VALID status in the ETRM data dictionary, confirming it is a live, queryable object used by concurrent programs, forms, and external integrations.

Its principal role is to decouple downstream consumers—reporting tools, OAF pages, and interface programs—from the physical column layout of the base table. The view preserves the complete column set of the underlying entity, including the descriptive flexfield segments (ATTRIBUTE1 through ATTRIBUTE15 and TP_ATTRIBUTE1 through TP_ATTRIBUTE15), the WHO audit columns, and the descriptive text field CUM_NOTE_TEXT. Because the search term associated with this object is cum_note_text, the view is commonly accessed by developers searching for the free-text annotation carrying cumulative notes attached to a customer item cumulative key.

Underlying Base Objects

The view is defined over a single referenced base object, RLM_CUST_ITEM_CUM_KEYS, surfaced through an APPS synonym. The view text performs a straightforward projection: SELECT CKEYS.ROWID ROW_ID, CKEYS.CUM_KEY_ID, ... FROM RLM_CUST_ITEM_CUM_KEYS CKEYS. No joins, unions, or filtering predicates are applied, meaning the view is a one-to-one alias layer rather than a transformation object. The ROW_ID column is derived from the base table ROWID, which permits the view to be used as an updatable construct in Oracle Forms or OAF-based maintenance screens where row identification is required.

Since no WHERE clause constrains the result set, consumers must apply their own organizational or date-range predicates. The absence of joins also means the view does not resolve customer names, item descriptions, or address details; those must be obtained separately through the corresponding customer, item, and address entities.

Key Columns

• CUM_KEY_ID — Primary identifier for the cumulative key record; the principal join key to child and audit tables.
• CUSTOMER_ITEM_ID — The customer item against which cumulative quantities are maintained.
• SHIP_FROM_ORG_ID — Warehouse or shipping organization from which accumulation is evaluated.
• CUM_START_DATE and CUST_RECORD_YEAR — Define the accumulation window and the customer record year to which the key belongs.
• CUST_UOM_CODE — Unit of measure in which cumulative quantities are expressed.
• CUM_QTY, CUM_QTY_TO_BE_ACCUMULATED, CUM_QTY_AFTER_CUTOFF — Quantity amounts for accumulated, pending, and post-cutoff measures respectively.
• LAST_CUM_QTY_UPDATE_DATE — Timestamp of the most recent cumulative quantity refresh.
• PURCHASE_ORDER_NUMBER, SHIP_TO_ADDRESS_ID, BILL_TO_ADDRESS_ID, INTRMD_SHIP_TO_ID — Trading-partner and address context for the accumulation.
• CUM_NOTE_TEXT — Free-form note text recorded against the cumulative key; the attribute most frequently targeted by ad hoc queries of this view.
• INACTIVE_FLAG — Indicates whether the cumulative key is logically retired.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1-15 and TP_ATTRIBUTE_CATEGORY / TP_ATTRIBUTE1-15 — Descriptive flexfield context and segments for the record and its trading-partner counterpart.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program audit trail.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns.

Common Use Cases and Queries

Typical usage includes extracting cumulative balances for a customer item during a reporting period, auditing records that carry annotation text, and feeding cumulative data into external EDI or supplier-portal integrations. A representative retrieval for records with notes is:

• SELECT cum_key_id, customer_item_id, cum_start_date, cum_qty, cum_note_text FROM apps.rlm_cust_item_cum_keys_v WHERE cum_note_text IS NOT NULL AND inactive_flag = 'N';
• SELECT v.cum_key_id, v.cust_record_year, v.cum_qty_to_be_accumulated FROM apps.rlm_cust_item_cum_keys_v v WHERE v.customer_item_id = :p_customer_item_id AND v.ship_from_org_id = :p_org_id ORDER BY v.cum_start_date DESC;
• SELECT v.purchase_order_number, v.cum_qty, v.cum_qty_after_cutoff FROM apps.rlm_cust_item_cum_keys_v v WHERE v.ship_to_address_id = :p_ship_to AND v.cust_record_year = :p_year;

Because the view applies no filtering, queries should always constrain by organization, customer item, or record year to avoid full-table scans. Access is normally granted to the APPS schema and responsibility-specific read-only users.