Results for “sts_code_from”

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

Overview

OKC_K_HISTORY_B is a core table within the OKC (Contracts Core) schema of Oracle E-Business Suite, documented as VALID across release levels 12.1.1 and 12.2.2. The table stores contract status change history together with a record of actions performed throughout the contract life cycle. Every time a contract header or line transitions between statuses, or an operation is executed against a contract, a row is inserted here to preserve an auditable trail of that event.

Following the Data Vault classification heuristically mined from its foreign key structure, OKC_K_HISTORY_B is best modeled as a link table. It does not hold descriptive contract attributes of its own; instead it associates a contract header, an optional contract line, an operation, and a pair of statuses (from and to), forming a many-to-many style junction between these business entities. The presence of the CHR_ID, CLE_ID, OPN_CODE, STS_CODE_FROM, and STS_CODE_TO foreign keys, combined with the event-oriented nature of the data, supports this interpretation.

Key Information Stored

The table contains 21 documented columns at the 12.2.2 schema level. The most significant are:

• ID — the surrogate primary key, enforced by OKC_K_HISTORY_PK and reinforced by unique index OKC_K_HISTORY_B_U1. This is the single business-key candidate documented for the table.
• CHR_ID — foreign key to OKC_K_HEADERS_B, identifying the contract header whose history is recorded.
• CLE_ID — foreign key to OKC_K_LINES_B, identifying the specific contract line when the event is line-level rather than header-level.
• OPN_CODE — foreign key to OKC_OPERATIONS_B, naming the operation or action that triggered the history record.
• STS_CODE_FROM and STS_CODE_TO — foreign keys to OKC_STATUSES_B, capturing the prior and resulting status codes of the transition.
• CONTRACT_VERSION — the version of the contract at the time the event occurred.
• REASON_CODE — a coded reason associated with the status change.
• TRN_CODE — an associated transaction code.
• MANUAL_YN — indicates whether the action was performed manually by a user or automatically by the system.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework for concurrent update control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns recording who created and last touched the row and when.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request context identifying the batch job or request that produced the record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / security group access isolation.

Common Use Cases and Queries

Typical uses focus on audit reporting, contract life-cycle analytics, cycle-time measurement, and troubleshooting unexpected status changes.

• Contract audit trail — retrieve the full transition history for a contract header:

  SELECT h.ID, h.CHR_ID, sf.MEANING status_from, st.MEANING status_to, h.CREATION_DATE, h.CREATED_BY
FROM OKC_K_HISTORY_B h, OKC_STATUSES_B sf, OKC_STATUSES_B st
WHERE h.STS_CODE_FROM = sf.CODE(+) AND h.STS_CODE_TO = st.CODE(+)
AND h.CHR_ID = :p_chr_id ORDER BY h.CREATION_DATE;

• Distinguishing manual from system-driven activity using MANUAL_YN for governance reporting.
• Identifying which concurrent request or program (REQUEST_ID, PROGRAM_ID) produced each event, useful when reconciling automated status updates.
• Cycle-time analysis — interval between successive CREATION_DATE values for the same CHR_ID to measure approval or signature turnaround.
• Reconstructing the status of a contract at a historical point in time using CONTRACT_VERSION and ordered history rows.

Related Objects

The following objects are the most significant relatives, based on documented foreign key relationships:

• OKC_K_HEADERS_B — joined on OKC_K_HISTORY_B.CHR_ID = OKC_K_HEADERS_B.ID; the parent contract header.
• OKC_K_LINES_B — joined on CLE_ID; the contract line for line-level events.
• OKC_OPERATIONS_B — joined on OPN_CODE; the operation that initiated the event.
• OKC_STATUSES_B — joined twice, on STS_CODE_FROM and STS_CODE_TO, supplying status meanings.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for access control context.
• OKC_K_HISTORY_PK / OKC_K_HISTORY_B_U1 — primary key and unique index on ID, enforcing row uniqueness.