Results for “okc_del_resp_parties_b”

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

Overview

OKC_DEL_RESP_PARTIES_B is a Contracts Core (OKC) application table that stores responsible party codes associated with Contract Deliverables. The suffix "B" designates the base (or "B" entity) table in the standard Oracle EBS multi-table naming pattern, indicating that a corresponding translation or "_TL" table may exist for language-dependent descriptive attributes, while this base table holds the operational, entity-level definition itself. Each row in the table defines an intent-striped responsible party code — meaning the same party concept can be recorded under distinct intent qualifiers, so that a single responsible party may carry different meanings or behaviors depending on the deliverable context in which it is referenced.

Functionally, this object serves as a lookup and reference table used during Contract Deliverables setup and processing. It allows the Contracts application to constrain and validate the party that owns or is accountable for a given deliverable, and to distinguish parties by intent so that reporting and workflow logic can separate, for example, the party expected to perform versus the party expected to receive or approve a deliverable. Because the metadata classifies this object as standalone under a heuristic Data Vault analysis, it is best modeled as an independent reference or lookup entity rather than as a hub, link, or satellite; no foreign-key-driven relationships to other entities were mined from the database structure.

Key Information Stored

The documented metadata identifies a single primary-key column of significance:

• RESP_PARTY_CODE — The responsible party code. This is the column constrained by primary key OKC_DEL_RESP_PARTIES_B_PK and represents the principal business attribute of the row: an identifier for the responsible party, striped by intent.

In the Oracle EBS convention, a "_B" table of this type typically also carries an internal surrogate key (commonly an ID column) and standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). However, because the metadata provided documents only RESP_PARTY_CODE as the primary key and does not enumerate an internal ID or a named unique index distinct from the primary key, additional columns should not be assumed without direct inspection of the ALL_TAB_COLUMNS dictionary view for the specific release. The distinction here is important: the documented business-key candidate and the primary key are the same column, RESP_PARTY_CODE, with no separately documented surrogate identifier.

The metadata notes that the table is not implemented in this database, meaning it may not be present in every OKC deployment or may be created conditionally depending on the installed Contracts functionality and patch level.

Common Use Cases and Queries

Typical usage centers on validating and reporting responsible party definitions for Contract Deliverables. A basic lookup to enumerate all defined responsible party codes is:

• SELECT resp_party_code FROM okc_del_resp_parties_b;

More practical scenarios include joining this reference data to deliverable instances to report which party is responsible, or filtering the list to build a value set or LOV used in the Contract Deliverables setup forms. Because the table is intended to be striped by intent, reporting queries commonly group by the responsible party code to surface coverage or duplication across intent categories:

• Responsible-party LOV population: SELECT resp_party_code FROM okc_del_resp_parties_b ORDER BY resp_party_code;
• Setup/validation query confirming that a specific party code is defined before it is referenced on a deliverable.
• Migration and audit scripts that extract the complete set of defined party codes for comparison across environments.

Reports and interfaces that externalize Contract Deliverables configuration should treat this table as the authoritative source of allowable responsible party values, and should first verify existence via the data dictionary before assuming the table is available, given the "not implemented" note.

Related Objects

The mined relationship classification is standalone, so no foreign-key dependencies were documented in the metadata. Related objects that reference or depend on this table are therefore inferred from the OKC Contracts Core domain rather than from explicit FK data:

• OKC_DELIVERABLES (and its base/translation forms) — the primary consumer, referencing responsible party codes against individual deliverables.
• OKC_DEL_RESP_PARTIES_TL — the presumed translation table for language-dependent attributes associated with the "_B" base rows.
• OKC_DEL_RESP_PARTIES_B_PK — the primary key constraint, enforcing uniqueness of RESP_PARTY_CODE.
• OKC_DELIVERABLE_TEMPLATES — template definitions that may default responsible party assignments.
• OKC_CONTRACTS / OKC_K_HEADERS — contract header entities in whose context deliverables and their responsible parties are evaluated.
• FND_LOOKUP_VALUES — frequently used alongside this table when responsible party values are surfaced through descriptive or extensible lookup mechanisms.

Because the metadata does not document foreign keys, join columns beyond RESP_PARTY_CODE should be confirmed against the live schema before being relied upon in production SQL.