Search Results cm_rlup_ctl




Overview
Explore in AI Chat

Overview

The CM_RLUP_CTL table is a core control and communication mechanism within the Process Manufacturing Financials (GMF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is specifically designed to manage the Cost Rollup Process, a critical operation in OPM (Oracle Process Manufacturing) for calculating rolled-up costs of manufactured items through the product structure. The table functions as an interface between the user and the background rollup engine, enabling users to initiate runs, monitor their status in real-time, review historical execution details, and, if necessary, issue commands to abort an in-progress rollup. Its existence is pivotal for ensuring the cost rollup, a resource-intensive batch process, can be managed and audited effectively.

Key Information Stored

The table stores metadata and control parameters for each rollup execution. The primary key, ROLLUP_ID, uniquely identifies each run. Critical columns include the COST_MTHD_CODE, which links to the costing method (CM_MTHD_MST), and the CALENDAR_CODE and PERIOD_CODE, which together identify the accounting period for the cost calculation and reference the calendar details table (CM_CLDR_DTL). Other essential columns would typically encompass status flags (e.g., process phase, completion status), timestamps for start and end times, the user who initiated the run, and control flags that allow a user to signal the process to stop. The structure facilitates tracking the rollup from submission through to completion or failure.

Common Use Cases and Queries

The primary use case is monitoring and controlling active or recent cost rollup jobs. A common query involves checking the status of recent runs to identify any that are stalled or have errors. For example:

  • SELECT rollup_id, cost_mthd_code, calendar_code, period_code, status, requested_by, start_date FROM gmf.cm_rlup_ctl WHERE status NOT IN ('COMPLETE', 'CANCELLED') ORDER BY start_date DESC;

Another critical operation is forcing an abort by updating a specific control column in the table for a given ROLLUP_ID, which the background process polls. Reporting on historical rollup performance and frequency for specific cost methods or periods is also a standard practice, aiding in period-end closing analysis and process auditing.

Related Objects

CM_RLUP_CTL sits at the center of a network of related cost rollup tables. It has a direct foreign key relationship with CM_MTHD_MST (costing methods) and CM_CLDR_DTL (calendar periods). Furthermore, it is referenced as a parent table by several key detail tables: CM_RLUP_ITM stores the individual items processed in each rollup, CM_RLUP_MSG likely holds process messages or logs for the run, and CM_CMPT_DTL (component details) links to it via the ROLLUP_REF_NO column to associate component costs with a specific rollup execution. This hierarchy ensures all data generated by a cost rollup is traceable back to a single control record.