Results for “intorders_processed”

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

Overview

CM_ACPR_CTL is the Actual Cost Process Control table owned by the GMF schema within the Process Manufacturing Financials (OPM Financials) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the communication and status channel between the OPM user and the Actual Cost Process (ACPR) as that concurrent program executes in the background. Through this table, users can monitor the progress of an in-flight cost rollup and cost update run, review the outcomes of past runs, and, when necessary, signal the process to abort.

Each row in CM_ACPR_CTL represents a single execution instance of the Actual Cost Process, identified by the surrogate primary key ACPROC_ID (defined by the unique index CM_ACPR_CTL_PK). The table is the parent or "hub" of a small family of dependent detail tables that record ledger entries, component-level cost detail, and error messages generated during the run. From a Data Vault modeling perspective, the FK topology suggests a hub-leaning classification: ACPROC_ID is a stable, non-repeating business key that anchors several satellite-style children (CM_ACST_LED, CM_CMPT_DTL, CM_ACER_MSG), while COST_TYPE_ID and LEGAL_ENTITY_ID act as foreign references to reference hubs. This classification is heuristic and should be treated as a modeling suggestion rather than a documented design standard.

Key Information Stored

The table comprises 38 documented columns. The most operationally significant are:

• ACPROC_ID — surrogate primary key and the foreign-key anchor for all dependent tables.
• CALENDAR_CODE, PERIOD_CODE, PERIOD_ID — identify the accounting calendar and period being costed.
• COST_MTHD_CODE, COST_TYPE_ID — the costing method and cost type applied to the run (COST_TYPE_ID references CST_COST_TYPES).
• RUNNING_IND, ACPROC_STAGE — indicate whether the process is active and which processing stage it has reached.
• STARTED_BY, STARTED_ON, ENDED_ON, SCHEDULED_ON — execution timestamps and the user who launched the run.
• ITEMS_PROCESSED, RECEIPTS_PROCESSED, BATCHES_PROCESSED, INTORDERS_PROCESSED, INVOICES_PROCESSED, MISCRCPT_PROCESSED — throughput counters for each transaction class.
• ERRORS_FOUND, ERRORS_POSTED, ERRORS_LIMIT — error tracking and the threshold at which the process halts.
• ABORT_IND, ABORT_BY, ABORT_REASON — user-driven termination controls and audit trail.
• LEGAL_ENTITY_ID, OPERATING_UNIT_ID — the legal entity and operating unit context (LEGAL_ENTITY_ID references FV_LEGAL_ENTITIES).
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — concurrent request linkage for the background job.
• DELETE_MARK, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard OPM audit and logical-delete columns.

Common Use Cases and Queries

Typical usage includes monitoring active runs, reviewing historical run performance, and diagnosing failures. A simple status query might be:

SELECT acproc_id, period_code, running_ind, acproc_stage, items_processed, errors_found
FROM   gmF.cm_acpr_ctl
WHERE  running_ind = 'Y'
ORDER BY started_on DESC;

Historical throughput reporting can aggregate counters per period, while error triage joins CM_ACER_MSG on ACPROC_ID. Users may also issue an UPDATE to set ABORT_IND = 'Y' with an ABORT_REASON to force the background process to terminate gracefully. Care must be taken with ABORT_IND updates, as they directly influence concurrent process behaviour.

Related Objects

• CM_ACST_LED — cost ledger entries produced by the run, joined on ACPROC_ID.
• CM_CMPT_DTL — component-level cost detail, joined on ACPROC_ID.
• CM_ACER_MSG — error messages logged during processing, joined on ACPROC_ID.
• CST_COST_TYPES — cost type definition referenced by COST_TYPE_ID.
• FV_LEGAL_ENTITIES — legal entity referenced by LEGAL_ENTITY_ID.