Results for “cm_rlup_msg”

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

Overview

CM_RLUP_MSG is a table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the error and diagnostic messages generated by the OPM Cost Rollup Process. The Cost Rollup Process recalculates item costs across the process manufacturing organization, and CM_RLUP_MSG captures the list of inconsistencies encountered during each run so that users can evaluate the performance and accuracy of the process and take corrective action. Each row represents one message tied to a specific rollup execution, identified by ROLLUP_ID, and to a specific line within that execution, identified by LINE_NO.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is assessed as satellite-leaning. In modeling terms, this suggests CM_RLUP_MSG behaves primarily as a descriptive satellite attached to the rollup control entity (CM_RLUP_CTL, itself the parent of ROLLUP_ID), holding non-key descriptive context about each rollup run rather than acting as a standalone hub or a link between two business entities. Its composite primary key makes it a dependent child record rather than an independent master.

Key Information Stored

The table has 13 documented columns. The most important are:

• ROLLUP_ID — the identifier of the cost rollup execution that produced the message; part of the composite primary key and the foreign key to CM_RLUP_CTL.
• LINE_NO — the sequence number of the message within the rollup; the second component of the primary key. Together, ROLLUP_ID and LINE_NO form the business-key candidate CM_RLUP_MSG_PK.
• MESSAGE_COMMENT — the actual message text describing the inconsistency or diagnostic detail encountered during the rollup.
• CREATION_DATE, CREATED_BY — standard who-columns recording when and by whom the message row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns capturing the most recent modification.
• DELETE_MARK — the OPM soft-delete flag; rows are logically removed rather than physically deleted.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the concurrent request and program context that identifies the specific concurrent manager run which generated the messages.

The primary key is a composite surrogate key (CM_RLUP_MSG_PK), while the unique index serves as the business-key candidate. The standard concurrent-program columns allow the messages to be reconstructed and traced back to a specific submission.

Common Use Cases and Queries

The primary use case is post-run analysis of the Cost Rollup Process. Users and support staff query CM_RLUP_MSG to diagnose why a rollup completed with warnings or errors, and to review which items or cost elements failed.

A typical query retrieves messages for a specific rollup:

• SELECT rollup_id, line_no, message_comment FROM cm_rlup_msg WHERE rollup_id = :rollup_id AND delete_mark = 0 ORDER BY line_no;

To correlate messages with the controlling rollup record and its status:

• SELECT m.rollup_id, m.line_no, m.message_comment, c.* FROM cm_rlup_msg m JOIN cm_rlup_ctl c ON m.rollup_id = c.rollup_id WHERE m.delete_mark = 0;

To trace messages back to the concurrent request that produced them — useful for auditing a scheduled cost rollup — filter on the standard concurrent columns:

• SELECT rollup_id, line_no, message_comment, request_id FROM cm_rlup_msg WHERE program_id = :program_id AND request_id = :request_id;

Reporting use cases include counting errors per rollup execution to trend process quality over time, exporting exceptions to a spreadsheet for cost accountants, and building dashboards that flag rollups exceeding a threshold of messages. Because the table is OPM-specific and written by the cost rollup program, it is generally read-only from an end-user perspective.

Related Objects

The most significant related objects are:

• CM_RLUP_CTL — the parent control table for cost rollup executions; CM_RLUP_MSG.ROLLUP_ID is the foreign key referencing CM_RLUP_CTL. This is the primary join for contextualizing messages.
• CM_RLUP_MSG_PK — the composite primary key index on (ROLLUP_ID, LINE_NO), enforcing uniqueness of each message line.
• CM_RLUP_MSG_N1 (if defined) — secondary index for lookup performance; in practice, queries typically pivot on ROLLUP_ID.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID, used to attribute messages to a specific concurrent run.
• CM_RLUP_CTL related OPM costing tables such as CM_ITEM_COST and the item master (CM_ITEM / MTL_SYSTEM_ITEMS) — referenced indirectly by the rollup process when messages describe item-level cost failures.

Because the foreign key relationship is limited, direct reporting should always join CM_RLUP_MSG to CM_RLUP_CTL to obtain the rollup-level attributes needed for meaningful analysis.