Results for “cm_cupd_msg”

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

Overview

CM_CUPD_MSG is a GMF (Process Manufacturing Financials) table that captures error messages generated during the OPM Cost Update process. It resides in the GMF schema and is documented as VALID in ETRM 12.2.2. The table functions as a diagnostic log: each row records a distinct problem encountered when the Cost Update concurrent program runs, and the table is deliberately deduplicated so that a recurring condition is not written repeatedly. OPM users consult these rows to assess the performance and accuracy of a cost update run and to determine whether corrective action — most commonly reprocessing after a data fix — is required.

Because Cost Update materializes cost changes that flow into inventory valuation, subledger accounting, and period-close balances, this table is a primary troubleshooting surface for costing analysts and support teams. It has no transactional role of its own; it is purely a process-audit and exception record.

The heuristic Data Vault classification derived from its foreign-key structure is satellite-leaning. In Data Vault terms, CM_CUPD_MSG reads most naturally as a satellite hanging off the cost update control hub identified by CUPROC_ID, with LINE_NO supplying sequence within each process run. Modeling it as a hub or link would misrepresent its dependent, descriptive nature.

Key Information Stored

The table contains 13 documented columns in 12.2.2. The most significant are:

• CUPROC_ID — The cost update process identifier. This is the leading column of the composite primary key and the foreign key to CM_CUPD_CTL. It is the attribute most often used in ad hoc searches, and is the column returned by the user's "cuproc_id" query.
• LINE_NO — Sequence number of the message within a given process run. Together with CUPROC_ID it forms the primary key CM_CUPD_MSG_PK, which is also the only unique index and therefore the business-key candidate.
• MESSAGE_COMMENT — The human-readable error text. This is the payload of the table and the field users read to understand what failed.
• DELETE_MARK — Standard OPM logical-delete flag indicating whether the row has been soft-deleted.
• REQUEST_ID — Concurrent request identifier, allowing the message set to be tied back to a specific submission of the Cost Update program.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent Manager audit attributes identifying the concurrent program that last touched the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns providing insert and update auditability.

The primary key is composite and surrogate in effect: CUPROC_ID plus LINE_NO. No separate single-column surrogate key is documented, and no alternate unique index exists beyond CM_CUPD_MSG_PK.

Common Use Cases and Queries

The dominant scenario is post-run diagnosis. After a Cost Update completes with warnings, the analyst lists all messages for that run:

• SELECT LINE_NO, MESSAGE_COMMENT FROM GMF.CM_CUPD_MSG WHERE CUPROC_ID = :cuproc_id ORDER BY LINE_NO;
• Joining to the control table to obtain run context and status: SELECT m.LINE_NO, m.MESSAGE_COMMENT, c.* FROM GMF.CM_CUPD_MSG m, GMF.CM_CUPD_CTL c WHERE m.CUPROC_ID = c.CUPROC_ID AND m.CUPROC_ID = :cuproc_id ORDER BY m.LINE_NO;
• Correlating messages to a concurrent request using REQUEST_ID to confirm which submission produced them.
• Trend reporting on recurring error text, grouping by MESSAGE_COMMENT across recent runs to identify systemic data issues.
• Period-close checklists that require zero unaddressed messages before the costing period is closed.
• Excluding soft-deleted rows with DELETE_MARK = 0 in all production queries.

Related Objects

• CM_CUPD_CTL — The cost update control table. Its primary key is referenced by CM_CUPD_MSG.CUPROC_ID, forming the only documented foreign key. Every query joining this table uses CUPROC_ID.
• CM_CUPD_MSG_PK — The unique index on (CUPROC_ID, LINE_NO) that enforces one message per line per process.
• CM_CUPD_* process tables — The broader OPM Cost Update family (control, detail, and item-level tables) sharing the CUPROC_ID key and consumed together when analyzing a run.
• FND_CONCURRENT_REQUESTS — Joined on REQUEST_ID to retrieve program name, phase, and completion status.
• FND_USER — Joined on CREATED_BY or LAST_UPDATED_BY to attribute the run or a manual correction to an operator.