Results for “abort_by”

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

Overview

CM_CUPD_CTL is the Cost Update Process Control table owned by the GMF schema in Oracle Process Manufacturing Financials (OPM). It functions as the coordination and control record for the OPM Cost Update Process (often referred to as the Cost Rollup / Cost Update concurrent program). Because the Cost Update Process executes asynchronously in the background, CM_CUPD_CTL provides the persistent control surface through which a user communicates with a running process, reviews the outcome of past runs, and, when required, signals the process to abort. Each row represents a single cost update execution identified by the surrogate primary key CUPROC_ID, defined by the unique index CM_CUPD_CTL_PK.

Under a heuristic Data Vault classification derived from its foreign key structure, CM_CUPD_CTL is satellite-leaning: it carries descriptive and status attributes about a process event rather than acting as a pure hub or a relationship link. This classification is a modeling suggestion only; in native EBS terms the table is a transactional control table.

Key Information Stored

CM_CUPD_CTL contains 33 documented columns. The most significant are:

• CUPROC_ID — the surrogate primary key and unique business-key candidate (CM_CUPD_CTL_PK); the cost update process identifier referenced by dependent tables.
• CALENDAR_CODE and PERIOD_CODE — the cost calendar and period against which the update runs; both participate in the foreign key to CM_CLDR_DTL.
• PERIOD_ID and PERIOD_STATUS — the internal period identifier and the open/closed status context of the run.
• COST_MTHD_CODE — the costing method applied; foreign key to CM_MTHD_MST.
• COST_TYPE_ID — the cost type used; foreign key to CST_COST_TYPES.
• LEGAL_ENTITY_ID — the legal entity in scope; foreign key to FV_LEGAL_ENTITIES.
• FINAL_UPDATE and RUNNING_IND — flags indicating whether this is the final update pass and whether the process is currently executing.
• SCHEDULED_ON, STARTED_ON, ENDED_ON, STARTED_BY — execution timing and the initiating user.
• ERRORS_FOUND, ERRORS_POSTED, ROWS_POSTED — run statistics for monitoring and reconciliation.
• ABORT_IND, ABORT_BY, ABORT_REASON — the abort signaling and audit fields.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — the concurrent request and program context.
• IN_USE, DELETE_MARK — standard OPM logical locking and soft-delete flags.

Common Use Cases and Queries

Typical scenarios include determining whether a cost update is still running, reviewing historical runs for a calendar and period, and issuing an abort. A representative query for the current status of runs is:

• SELECT cuproc_id, calendar_code, period_code, cost_mthd_code, running_ind, abort_ind, errors_found, rows_posted FROM gmf.cm_cupd_ctl WHERE calendar_code = :cal AND period_code = :per ORDER BY started_on DESC;
• Locating active processes: SELECT cuproc_id, started_by, started_on FROM gmf.cm_cupd_ctl WHERE running_ind = 'Y' AND NVL(delete_mark,0) = 0;
• Requesting an abort by setting abort_ind, abort_by, and abort_reason for the target cuproc_id.

Reporting use cases include run-duration analysis (STARTED_ON vs. ENDED_ON), error-rate tracking (ERRORS_FOUND versus ERRORS_POSTED), and audit reporting on who initiated or aborted a run.

Related Objects

• CM_CUPD_MSG — child table linked by CM_CUPD_MSG.CUPROC_ID to CM_CUPD_CTL.CUPROC_ID; holds the messages generated during the run.
• CM_CLDR_DTL — referenced via CALENDAR_CODE and PERIOD_CODE; the cost calendar detail.
• CM_MTHD_MST — referenced via COST_MTHD_CODE; the costing method master.
• CST_COST_TYPES — referenced via COST_TYPE_ID; the cost type definition.
• FV_LEGAL_ENTITIES — referenced via LEGAL_ENTITY_ID; the legal entity master.