Results for “cm_rlup_ctl”

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

Overview

CM_RLUP_CTL is the Cost Rollup Process Control table owned by the GMF schema within the Process Manufacturing Financials (OPM) product family. It functions as the communication and reconciliation layer between an OPM user and the Cost Rollup Process while that process executes in the background. Because cost rollups in process manufacturing can be long-running and computationally intensive, this table provides the persistent state that lets a user monitor an active run, review the outcome of historical runs, and, when required, force an in-flight process to terminate.

The Data Vault classification mined from the foreign-key topology is hub-leaning. As a modeling suggestion, this indicates that CM_RLUP_CTL behaves primarily as a central entity whose surrogate identity (ROLLUP_ID) is referenced by surrounding detail and message tables, with its own foreign keys pointing outward to descriptive dimensions such as calendars, cost methods, cost types, and legal entities. The 46 documented columns in the 12.2.2 physical schema reflect a control-record design: identity, scheduling, status, progress counters, abort controls, and standard EBS audit/WHO columns.

Key Information Stored

The surrogate primary key is ROLLUP_ID, enforced by the unique index CM_RLUP_CTL_PK. This identifier is the single business-key candidate documented for the table and is the value propagated to dependent tables.

• ROLLUP_ID — Surrogate primary key uniquely identifying each cost rollup run.
• CALENDAR_CODE and PERIOD_CODE — Costing calendar and period the rollup is scoped to; these form a foreign key to CM_CLDR_DTL.
• COST_MTHD_CODE — Costing method used, foreign key to CM_MTHD_MST.
• COST_TYPE_ID — Cost type associated with the run, foreign key to CST_COST_TYPES.
• LEGAL_ENTITY_ID — Legal entity context, foreign key to FV_LEGAL_ENTITIES.
• ROLLUP_STAGE — Current processing stage of the rollup.
• RUNNING_IND, IN_USE, ABORT_IND — Status flags controlling whether the run is active, locked, or flagged for termination.
• SCHEDULED_ON, STARTED_ON, ENDED_ON — Scheduling and execution timestamps.
• STARTED_BY, ABORT_BY, ABORT_REASON — Operator and rationale trail for manual intervention.
• FORMULA_CNT, PRODUCTS_CALC, BURDENS_CALC, COST_ROWS_CALC — Progress counters reporting workload completed.
• ERRORS_FOUND, ERRORS_POSTED, ERRORS_LIMIT — Error accounting and the threshold governing run tolerance.
• RANGE_TYPE, FROM_RANGE, TO_RANGE, FROM_ORGN_CODE, TO_ORGN_CODE, ITEM_ID — Scope selection criteria for the rollup.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — Concurrent program context for tracing the submitted request.
• Standard audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, DELETE_MARK, and DEFAULT_LANGUAGE.

Common Use Cases and Queries

Operational monitoring is the most frequent use case. Administrators query the table to determine whether a rollup is still executing and to inspect abort state.

• Locating currently active runs: SELECT ROLLUP_ID, ROLLUP_STAGE, STARTED_ON, STARTED_BY FROM GMF.CM_RLUP_CTL WHERE RUNNING_IND = 'Y';
• Reviewing historical runs by period: SELECT ROLLUP_ID, CALENDAR_CODE, PERIOD_CODE, ENDED_ON, ERRORS_FOUND FROM GMF.CM_RLUP_CTL WHERE PERIOD_CODE = :period;
• Forcing an abort by setting ABORT_IND and recording ABORT_BY and ABORT_REASON for the identified ROLLUP_ID.
• Progress reporting on products and burdens calculated versus formula counts for long-running jobs.
• Reconciliation to the concurrent manager via REQUEST_ID when a rollup request appears stalled.

Related Objects

CM_RLUP_CTL sits at the center of a small cluster of rollup tables. The documented relationships are:

• CM_RLUP_ITM — references CM_RLUP_CTL.ROLLUP_ID; holds per-item rollup results.
• CM_RLUP_MSG — references CM_RLUP_CTL.ROLLUP_ID; stores process messages and errors.
• CM_CMPT_DTL — references CM_RLUP_CTL via CM_CMPT_DTL.ROLLUP_REF_NO; component-level cost detail.
• CM_CLDR_DTL — referenced by CALENDAR_CODE and PERIOD_CODE.
• CM_MTHD_MST — referenced by COST_MTHD_CODE.
• CST_COST_TYPES — referenced by COST_TYPE_ID.
• FV_LEGAL_ENTITIES — referenced by LEGAL_ENTITY_ID.

Together these tables supply both the control metadata and the resulting costing detail that downstream reporting and inquiry forms consume.