Search Results acceptance_date

Overview

The ORACLE EBS view APPS.OKC_CHANGE_PARTY_ROLE_V belongs to the OKC – Contracts Core product family and functions as a reporting and integration layer over the base table OKC_CHANGE_PARTY_ROLE. In Oracle EBS 12.1.1 and 12.2.2, the view is defined in the APPS schema and carries a VALID status in the ETRM repository. Its purpose is to expose party-role rows associated with contract change requests, including the acceptance date recorded against each party role. Users searching for the term acceptance_date will find this view particularly relevant because ACCEPTANCE_DATE is one of its exposed columns and mirrors the identically named column on the underlying base table.

The view is typically consumed by reporting tools, concurrent programs, and integration interfaces that need to read change party role data without directly querying the base table. Because the view is a simple projection over a single synonym, it introduces no aggregation and behaves predictably for query tuning and row-level filtering.

Underlying Base Objects

The documented base object referenced by the view is OKC_CHANGE_PARTY_ROLE, accessed through a synonym. The view text aliases this source as CPRB and selects columns directly from it. No joins, unions, or derived expressions appear in the documented definition; the view is a straight column projection. This means every row returned by OKC_CHANGE_PARTY_ROLE_V corresponds one-to-one with a row in OKC_CHANGE_PARTY_ROLE.

• Source object: OKC_CHANGE_PARTY_ROLE (synonym)
• Owner: APPS
• Object type: VIEW
• Status: VALID

Key Columns

The view exposes the following columns, each mapped directly from the base table:

• ROW_ID – the ROWID of the underlying OKC_CHANGE_PARTY_ROLE row, useful for direct row addressing.
• CRT_ID – identifier linking the party role to a contract change request.
• CPL_ID – identifier for the contract party line associated with the role.
• OBJECT_VERSION_NUMBER – optimistic locking column used by the framework to detect concurrent updates.
• ACCEPTANCE_DATE – the date on which the party role was accepted; central to queries searching for acceptance timing.
• CREATED_BY, CREATION_DATE – audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – audit columns recording the most recent modification and session.

Common Use Cases and Queries

Typical scenarios include reporting on acceptance of party roles for a change request, identifying roles accepted within a date range, and feeding integration processes that synchronize contract change data. The following examples illustrate practical usage.

• List all party roles for a change request with their acceptance dates:

SELECT crt_id, cpl_id, acceptance_date
FROM   apps.okc_change_party_role_v
WHERE  crt_id = :p_crt_id;

• Find roles accepted within a period:

SELECT crt_id, cpl_id, acceptance_date
FROM   apps.okc_change_party_role_v
WHERE  acceptance_date BETWEEN :p_start AND :p_end;

• Retrieve full audit context for a specific row:

SELECT row_id, crt_id, cpl_id, acceptance_date,
       created_by, creation_date,
       last_updated_by, last_update_date
FROM   apps.okc_change_party_role_v
WHERE  row_id = :p_rowid;

Because the view is a direct projection, these queries can be extended with standard EBS security predicates and joined to related contract change tables using CRT_ID and CPL_ID as needed. Performance characteristics mirror those of the base table, so indexing on the base columns remains the primary tuning consideration.