Results for “contract_version_num”

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

Overview

The OKC_REP_SIGNATURE_DETAILS table is a Contracts Core (OKC) data object within Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2 releases. It stores the signature details associated with a Contract Party, capturing who signed a given contract version, when the signature was applied, and the routing context around that signature. In the Contracts repository model, a signed contract party record is the auditable evidence that a specific party role on a specific contract version has been executed. The table is owned by the OKC schema and comprises 24 documented columns.

From a heuristic Data Vault classification derived from its foreign-key structure, this object is modeled as a standalone table. In Data Vault terms it behaves most like a satellite attached to the contract-party business key (contract, version, party role, party), recording descriptive and transactional signature attributes rather than defining new hubs or links. This is a modeling suggestion; the physical implementation is a conventional relational table.

Key Information Stored

The table is keyed by OKC_REP_SIGNATURE_DETAILS_PK, a composite primary key spanning CONTRACT_ID, CONTRACT_VERSION_NUM, PARTY_ROLE_CODE, and PARTY_ID. These four columns together form the natural business key and are the primary join path back to the contract repository.

• CONTRACT_ID, CONTRACT_VERSION_NUM — identify the specific contract and version to which the signature belongs; signature data is retained per version, so amendments produce distinct rows.
• PARTY_ROLE_CODE, PARTY_ID — identify which party, in which role, signed or is associated with the signature.
• SIGNED_BY, SIGNED_DATE — the person credited with the signature and the effective signing date; these drive execution and compliance reporting.
• CONTACT_ID — links the signature to the contact record of the signatory.
• USER_ID, FORWARD_USER_ID — the system user who created the signature record and, where applicable, the user to whom the action was forwarded for approval or countersignature.
• ACTION_CODE, SOURCE — denote the action performed and the origin of the signature event, supporting routing and audit analysis.
• RUN_ID, SEQUENCE_LEVEL — support workflow-run and ordering context.
• NOTES — free-text commentary attached to the signature.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework for concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, REQUEST_ID — concurrent program and request audit context identifying the process that wrote the row.

Common Use Cases and Queries

Typical uses include contract execution tracking, signatory audit reports, and integration with workflow-driven signature routing. The most common query pattern joins on the four-column business key:

• Signatures for a contract version — SELECT party_role_code, party_id, signed_by, signed_date FROM okc_rep_signature_details WHERE contract_id = :contract_id AND contract_version_num = :version_num.
• Pending or forwarded signatures — filter on FORWARD_USER_ID or ACTION_CODE to identify signatures awaiting action.
• Signatory history — group by SIGNED_BY and SIGNED_DATE for execution audit and cycle-time reporting.
• Reconciliation — join to contract and party tables to confirm every executed party role has a corresponding signature row.

Related Objects

The composite primary key drives the principal relationships. The most significant related objects are:

• OKC_CONTRACTS / contract repository tables — joined on CONTRACT_ID and CONTRACT_VERSION_NUM to retrieve contract context.
• OKC_PARTIES (contract party tables) — joined on CONTRACT_ID, CONTRACT_VERSION_NUM, PARTY_ROLE_CODE, and PARTY_ID.
• Party/contact master tables — joined via PARTY_ID and CONTACT_ID to resolve signatory names and details.
• FND_USER — joined on USER_ID and FORWARD_USER_ID to resolve application users.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID and PROGRAM_ID for process audit.
• OKC Contracts Core APIs — the contract signature and party APIs that insert and maintain these rows programmatically.