Results for “cm_alpr_ctl”

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

Overview

CM_ALPR_CTL is a Process Manufacturing Financials (GMF) control table that governs the cost allocation process within Oracle E-Business Suite. It records process-level metadata such as the cost allocation run's fiscal year and period, the costing calendar, and the costing period, along with execution status indicators. In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the GMF schema and holds 14 documented columns. It functions as the authoritative state record for cost allocation processing, ensuring that period-driven allocations are performed exactly once per calendar/period/fiscal combination and providing auditability over who initiated and completed each run.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. Its attributes are descriptive and period-scoped rather than purely transactional or purely intersectional, which supports treating it as a satellite attached to a calendar/period-driven hub. This is a heuristic suggestion, not a normative design.

Key Information Stored

The primary key, CM_ALPR_CTL_PK, is a composite business key rather than a generated surrogate. It comprises CALENDAR_CODE, PERIOD_CODE, GL_FISCAL_YR, and GL_PERIOD. This composite uniquely identifies a cost allocation control record and enforces period uniqueness.

• CALENDAR_CODE – Costing calendar identifier; the leading PK column and the FK into CM_CLDR_DTL.
• PERIOD_CODE – Costing period within the calendar; second PK column and part of the FK to CM_CLDR_DTL.
• GL_FISCAL_YR – General Ledger fiscal year of the allocation run; third PK column.
• GL_PERIOD – GL period number; fourth PK column completing the composite key.
• PERIOD_ID – Surrogate period identifier used for internal period resolution.
• STARTED_ON / STARTED_BY – Timestamp and user who initiated the allocation process; supports audit and concurrency control.
• ENDED_ON – Completion timestamp; null indicates an in-progress or aborted run.
• RUNNING_IND – Status flag indicating whether the allocation is currently executing; critical for preventing overlapping runs.
• CREATION_DATE / CREATED_BY – Standard EBS who-columns for row creation.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN – Standard EBS audit columns tracking the most recent modification and session.

Common Use Cases and Queries

Typical uses include determining whether a cost allocation has already been run for a given period, monitoring the status of an active run, and reporting period-by-period allocation history. A common check is:

• SELECT running_ind, started_on, ended_on FROM gmf.cm_alpr_ctl WHERE calendar_code = :cal AND period_code = :per AND gl_fiscal_yr = :yr AND gl_period = :glp;

• Detecting stalled runs: query rows where RUNNING_IND = 'Y' and ENDED_ON IS NULL.
• Period completion reporting: join to CM_CLDR_DTL on CALENDAR_CODE and PERIOD_CODE to translate period codes into descriptive calendar dates.
• Audit reporting: extract STARTED_BY/STARTED_ON and LAST_UPDATED_BY/LAST_UPDATE_DATE for user accountability.

Related Objects

The most significant related object is CM_CLDR_DTL, referenced by the FK from CM_ALPR_CTL.CALENDAR_CODE and PERIOD_CODE. Joining these tables resolves costing calendar and period descriptions. Other GMF cost allocation and period-close programs read and update CM_ALPR_CTL to enforce run-once semantics per period. The standard EBS audit columns integrate with FND_USER for user resolution. Because the FK surface is limited in the documented metadata, dependent views and concurrent programs that maintain RUNNING_IND and completion timestamps should also be treated as related operational objects.