Search Results okc_rep_con_actions




Overview
Explore in AI Chat

Overview

The OKC_REP_CON_ACTIONS table resides in the OKC schema and belongs to the Contracts Core module of Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). It functions as a seed data table that defines which contractual Actions are permitted for a given page mode combined with a specific contract status. In effect, it acts as an authorization and navigation matrix: for each combination of a repository page mode (for example, a creation, update, or query page) and a contract lifecycle status (such as Draft, Active, or Expired), the table enumerates the action codes that the user interface and APIs should expose as valid operations.

Because this is seeded rather than transactional configuration, the row set is generally static within a release and is delivered by Oracle as part of the OKC setup. Administrators extend or restrict behavior primarily through the DISABLED_FLAG rather than by inserting new business rows, preserving the integrity of the seeded control matrix.

From a data modeling perspective, the metadata classifies this object heuristically as standalone. In Data Vault terms it does not participate in the mined foreign-key lattice, so it is best regarded as a reference or lookup entity rather than a hub, link, or satellite. Its 11 documented columns and composite business key support its role as an enabling reference table for the contract actions engine.

Key Information Stored

The table is keyed by a three-part business key, exposed through the unique index OKC_REP_CON_ACTIONS_U1 (PAGE_MODE, ACTION_CODE, STATUS_CODE, ZD_EDITION_NAME) and the primary key constraint OKC_REP_CON_ACTIONS_PK (PAGE_MODE, STATUS_CODE, ACTION_CODE). The most significant columns are:

  • PAGE_MODE — identifies the UI or API context in which the action is evaluated (part of the primary key).
  • STATUS_CODE — the contract status for which the action is valid (part of the primary key).
  • ACTION_CODE — the identifier of the permissible action (part of the primary key).
  • DISABLED_FLAG — an enable/disable switch that suppresses a normally valid action without deleting the seeded row.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the framework for concurrent update protection.
  • ZD_EDITION_NAME — editioning column supporting EBS Online Patching in 12.2.x, part of the unique business key.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row provenance and change history.

The ZD_EDITION_NAME column is significant because it allows multiple editions of the seeded configuration to coexist during the patching cycle.

Common Use Cases and Queries

Typical usage centers on determining which actions a contract should present for its current state, validating user requests before execution, and auditing the seeded configuration after an upgrade or patch.

  • Listing all actions available for a contract status: 
    SELECT page_mode, action_code
FROM   okc.okc_rep_con_actions
WHERE  status_code = :p_status
AND    disabled_flag = 'N';
  • Auditing disabled actions introduced by configuration: 
    SELECT status_code, action_code, last_updated_by, last_update_date
FROM   okc.okc_rep_con_actions
WHERE  disabled_flag = 'Y';
  • Comparing editions after a 12.2.2 patch: 
    SELECT zd_edition_name, COUNT(*)
FROM   okc.okc_rep_con_actions
GROUP  BY zd_edition_name;

Reporting use cases include entitlement matrices, UI behavior documentation, and upgrade impact analysis where seeded action availability may change.

Related Objects

As a standalone reference entity, OKC_REP_CON_ACTIONS has no mined foreign-key parents, but it is functionally referenced by the following significant objects that join on its business key columns: