Results for “date_assigned”

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

Overview

ZOKL_CSE_PTY_ROLES_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It exposes the contents of the underlying party-role assignment table OKL_CSE_PTY_ROLES, which stores the association between leasing case parties and the roles they hold within a contract, customer, or case-processing context. In EBS 12.1.1 and 12.2.2, OKL is delivered as part of the Oracle Financials family, and views prefixed "Z" typically denote customer-extension or generated wrapper objects layered over seeded OKL tables. This view provides a stable, denormalized read interface over the base table so that concurrent programs, reports, and integrations can retrieve party-role assignments without directly binding to the physical table structure.

Per the ETRM documentation, the object is described only as a "View for table OKL_CSE_PTY_ROLES" and is noted as "Not implemented in this database" in the documented environment, meaning the DDL was not instantiated at the time of documentation. Nonetheless, its view text is captured and fully defines the projection it would expose.

Underlying Base Objects

The view is defined over a single underlying object: the table ZOKL_CSE_PTY_ROLES, aliased as CPRB in the view text. The ETRM metadata lists "Referenced base objects: none documented," reflecting that no dependencies were formally registered against the environment. Functionally, ZOKL_CSE_PTY_ROLES is the extension-side counterpart of the seeded OKL_CSE_PTY_ROLES table, and the view presents a column-for-column projection of it, including ROWID exposed as ROW_ID. Because the definition is a direct SELECT over one table, the view is updatable in principle (subject to the absence of joins, DISTINCT, or aggregates) and inherits the base table's constraints, indexes, and DFF (descriptive flexfield) segments.

Key Columns

• ROW_ID — the ROWID of the underlying base row, useful for row identification and locking.
• ID — primary identifier of the party-role assignment record.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OKL framework.
• IPV_ID — the identifier that users frequently search for; it links the role assignment to the related in-process validation or interface processing record.
• OKL_CC_VD_ID, CLR_ID, CAC_ID — foreign keys to the contract, customer/legal-role, and case-processing entities respectively.
• PTY_ID — the party (customer, vendor, or contact) assigned to the role.
• SEQUENCE_NUMBER — ordering of roles for a given case.
• DATE_ASSIGNED — effective date the role was granted.
• CPR_CASE_NUMBER — human-readable case reference.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield context and segments.
• ORG_ID — multi-org operating unit identifier, essential for operating-unit-secured queries.
• Audit columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes reporting all parties and their roles on a leasing case, resolving the party behind a given IPV record, and validating role assignments during data conversion or interface processing. A representative query filtering on the commonly searched IPV_ID follows:

SELECT row_id, id, ipv_id, pty_id, okl_cc_vd_id, clr_id, cpr_case_number, sequence_number, date_assigned, org_id FROM zokl_cse_pty_roles_v WHERE org_id = :p_org_id AND ipv_id = :p_ipv_id ORDER BY sequence_number;

Because the view exposes ORG_ID, all queries should be constrained by operating unit to respect MOAC security. For integrations, the view can substitute for direct table access to insulate custom code from future column changes on the base table.