Search Results okc_rep_con_approvals




Overview
Explore in AI Chat

Overview

The OKC_REP_CON_APPROVALS table is a Contracts Core (OKC) repository object in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores a contract's approval data. Each row captures an approval-related action performed against a contract during its lifecycle, recording who acted, what action was taken, and when. Because approval routing and sign-off are integral to contract authoring and execution, this table provides the audit trail that establishes which user approved, rejected, or forwarded a contract and at which version.

In Data Vault modeling terms, the metadata's heuristic classification places this object as satellite-leaning. Its structure — a foreign key to OKC_REP_CONTRACTS_ALL plus descriptive attributes such as action code, user, date, and notes — resembles a satellite attached to the contract hub, capturing time-stamped descriptive history rather than representing an independent business entity or an association between two hubs. This classification should be treated as a modeling suggestion rather than a definitive design statement.

Key Information Stored

The table comprises 13 documented columns. Its most significant columns include:

  • CONTRACT_ID — Foreign key to OKC_REP_CONTRACTS_ALL, identifying the contract to which the approval action belongs. This is the primary linkage and is the leading column of the unique index.
  • CONTRACT_VERSION_NUM — The contract version against which the approval action was recorded, enabling version-aware audit of approvals.
  • ACTION_CODE — The approval action performed (for example, approve, reject, or forward), central to understanding the approval outcome.
  • USER_ID — The user who performed the action, providing accountability and personnel attribution.
  • ACTION_DATE — The timestamp of the approval action; together with USER_ID and ACTION_CODE it forms the business-key candidate.
  • NOTES — Free-text commentary accompanying the action, frequently used for rejection reasons or approver remarks.
  • FORWARD_USER_ID — The user to whom the contract was forwarded, supporting routing and delegation analysis.
  • OBJECT_VERSION_NUMBER — Optimistic locking version, used by the framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording row creation and modification metadata.

The unique index OKC_REP_CON_APPROVALS_U1 on (CONTRACT_ID, USER_ID, ACTION_CODE, ACTION_DATE) functions as the documented business-key candidate, while no separate surrogate primary key column is documented beyond the natural composite. The table references OKC_REP_CONTRACTS_ALL via CONTRACT_ID.

Common Use Cases and Queries

Typical uses include approval audit reporting, bottleneck analysis, and integration extracts. A representative query retrieves the approval history for a contract:

  • SELECT contract_id, contract_version_num, action_code, user_id, action_date, notes FROM okc.okc_rep_con_approvals WHERE contract_id = :p_contract_id ORDER BY action_date;
  • Join to contract headers for descriptive context: SELECT a.contract_id, c.contract_number, a.action_code, a.user_id, a.action_date FROM okc.okc_rep_con_approvals a, okc.okc_rep_contracts_all c WHERE a.contract_id = c.contract_id;
  • Approver workload analysis: group by USER_ID and ACTION_CODE over a date range to measure approval throughput.
  • Forwarding/delegation tracking using FORWARD_USER_ID to identify reassigned approvals.

Related Objects

  • OKC_REP_CONTRACTS_ALL — Referenced through CONTRACT_ID; supplies contract header and number context.
  • OKC_REP_CON_VERSIONS / contract version objects — Correlate with CONTRACT_VERSION_NUM for version-level approval tracking.
  • OKC_REP_CON_APPROVAL_STEPS — Where present, links approval steps to these action records.
  • FND_USER — Resolves USER_ID and FORWARD_USER_ID to user names.
  • OKC_CONTRACT_PUB / OKC contract APIs — Application programming interfaces that create and update approval records.
  • OKC_REP_CON_ACTIONS / action-code lookups — Describe ACTION_CODE values.

Together these objects support end-to-end contract approval auditing within the OKC module.