Results for “action_sequence”

2 results




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

Overview

OKE_APPROVAL_HISTORY is a transactional table in the OKE (Project Contracts) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the contract document approval history, recording each approval action performed against a contract header or a change request as the document moves through its configured approval workflow. Every time an approver acts on a contract or change request — approving, rejecting, or otherwise advancing the process — a corresponding row is written here, producing an auditable trail of who acted, when, and under which approval path.

The heuristic Data Vault classification mined from the foreign key structure is link. This suggests modeling the table as an associative entity connecting contract headers, change requests, and approval paths, rather than as a standalone hub or a pure descriptive satellite. The table carries both the relationship keys and descriptive action attributes, so in practice it straddles the link and satellite roles.

Key Information Stored

The physical schema documented for 12.2.2 contains 15 columns. The most business-significant are:

The surrogate primary key is OKE_APPROVAL_HISTORY_UK01 (K_HEADER_ID, CHG_REQUEST_ID, ACTION_SEQUENCE). A unique index OKE_APPROVAL_HISTORY_U1 exists on (K_HEADER_ID, ACTION_SEQUENCE, CHG_REQUEST_ID), representing the business-key candidate. There is no separate generated surrogate column; the approval history is keyed by its natural business components.

Common Use Cases and Queries

Typical scenarios include reconstructing the approval audit trail for a contract, determining pending or completed approvers on a change request, and reporting on approval cycle times. A representative pattern joins the history to the header and change request:

  • Contract approval audit: select ACTION_CODE, ACTION_DATE, PERFORMER from OKE_APPROVAL_HISTORY where K_HEADER_ID = :header_id order by ACTION_SEQUENCE.
  • Change request approval status: join CHG_REQUEST_ID to OKE_CHG_REQUESTS to list all actions taken against a specific change request.
  • Cycle-time analysis: compare ACTION_DATE values across APPROVAL_SEQUENCE entries to measure elapsed approval durations.
  • Role-based reporting: aggregate APPROVER_ROLE_ID to see which roles perform the most approval actions.

Related Objects

  • OKE_K_HEADERS — joined via OKE_APPROVAL_HISTORY.K_HEADER_ID; the parent contract header.
  • OKE_CHG_REQUESTS — joined via OKE_APPROVAL_HISTORY.CHG_REQUEST_ID; the change request under approval.
  • OKE_APPROVAL_PATHS — joined via OKE_APPROVAL_HISTORY.APPROVAL_PATH_ID; the approval path definition.
  • OKE_APPROVAL_PATH_MEMBERS — the members configured for the referenced approval path, useful when mapping APPROVER_ROLE_ID to expected approvers.
  • OKE_K_HEADER_APPROVALS — the current approval state of the header, complementary to the historical record held here.

These related objects are consistent with the documented foreign keys from OKE_APPROVAL_HISTORY to OKE_K_HEADERS, OKE_CHG_REQUESTS, and OKE_APPROVAL_PATHS.