Search Results crcc_control_id_unq

Overview

CST_REVENUE_COGS_CONTROL is a control and bookkeeping table owned by the BOM schema in Oracle E-Business Suite, classified under the Bills of Material product family. Its documented purpose is narrow and administrative: it maintains a record of the last successful execution of the Generate COGS Events concurrent request. In the Oracle EBS costing architecture, COGS (Cost of Goods Sold) event generation is the process that recognizes revenue and associated cost of goods sold for eligible transactions. Because incremental COGS processing depends on knowing the point up to which prior runs have already processed data, this table acts as a watermark or checkpoint store rather than a transactional ledger.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it does not participate in a conventional hub/link/satellite pattern with other tables in the mined FK structure. The table is best regarded as a lightweight operational state store whose single row (or few rows) drives idempotent, restartable concurrent processing.

Key Information Stored

The table is compact, with 11 documented columns. The most significant are:

• CONTROL_ID — the surrogate primary key, enforced by the unique constraint CRCC_CONTROL_ID_UNQ. This is the only documented key column and serves as the row identifier.
• LAST_PROCESS_UPTO_DATE — the critical business column; it records the date up to which COGS events have been successfully generated, forming the processing watermark for subsequent runs.
• REQUEST_ID — the concurrent request identifier of the last successful Generate COGS Events run, enabling traceability back to the specific submission.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — identify the concurrent program and its application, confirming which program produced the watermark.
• PROGRAM_UPDATE_DATE — the timestamp associated with the program run.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard Oracle EBS "WHO" audit columns tracking insert and update activity.

No business-key unique index beyond CRCC_CONTROL_ID_UNQ is documented, so CONTROL_ID is the sole documented key candidate.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting the COGS generation process. A common query retrieves the current watermark and the last run details:

• SELECT control_id, last_process_upto_date, request_id, program_id, last_update_date FROM bom.cst_revenue_cogs_control;
• Comparing LAST_PROCESS_UPTO_DATE against the current accounting period to verify whether COGS events are current.
• Joining REQUEST_ID to FND_CONCURRENT_REQUESTS to inspect the outcome, phase, and status of the referenced run.
• Reporting that identifies whether recent revenue transactions post-date the recorded watermark, indicating a pending backlog.

Related Objects

The mined FK structure indicates that numerous AMW (Application Monitoring / control framework) tables reference CONTROL_ID, though these are heuristic and largely unrelated to the costing function. Documented referencing objects include AMW_CONTROL_AP, AMW_CONSTRAINTS_B, AMW_AUDIT_PROCEDURE_INTERFACE, AMW_CTRL_EXT_TL, AMW_CONTROL_ASSOCIATIONS, AMW_CONTROLS_B, AMW_PROCESS_RISK_CONTROLS, AMW_CONTROL_REPORTS, AMW_FIN_ITEM_ACC_CTRL, AMW_CTRL_EXT_B, and RCI_ORG_CERT_CTRLS_F, each joining on CONTROL_ID. Functionally, the table is most tightly coupled to the Generate COGS Events concurrent program and the COGS event tables it drives.