Results for “deliverable_type_code”

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

Overview

OKC_DEL_BUS_DOC_COMBXNS is a Contracts Core (OKC) setup and validation table in Oracle EBS 12.1.1 and 12.2.2. It stores the set of valid combinations between Business Document Classes and Deliverable Types, acting as a cross-reference or mapping table that constrains which deliverable types may be attached to which business document classes. In practice, the table governs the deliverable configuration that appears when users author contract terms and deliverables against a contract or business document, ensuring that only sanctioned pairings are offered or accepted by the application.

The object is owned by the OKC schema and is reported as VALID. The documented physical schema in ETRM 12.2.2 lists eight columns. The primary key is OKC_DEL_BUS_DOC_COMBXNS_PK, defined over (DOCUMENT_TYPE_CLASS, DELIVERABLE_TYPE), which enforces uniqueness of each class-to-type pairing. A secondary unique index, OKC_DEL_BUS_DOC_COMBXNS_U1, is defined over (DOCUMENT_TYPE_CLASS, DELIVERABLE_TYPE_CODE, ZD_EDITION_NAME); this index is the strongest documented business-key candidate, particularly where the ZD_EDITION_NAME column participates in edition-aware or multi-edition configurations.

Under the heuristic Data Vault classification mined from the foreign-key structure, the table is characterized as satellite-leaning. This is a modeling suggestion rather than a formal designation: the table carries descriptive, configuration-style attributes that qualify or extend the referenced deliverable type master rather than defining an independent business entity or a purely associative link between two hubs.

Key Information Stored

The most significant columns documented for this table are:

• DOCUMENT_TYPE_CLASS — Identifies the business document class in the valid combination. This column is part of both the primary key and the unique business-key index.
• DELIVERABLE_TYPE — The deliverable type participating in the valid combination; also part of the primary key and a foreign-key column referencing OKC_DELIVERABLE_TYPES_B.
• DELIVERABLE_TYPE_CODE — The business-facing code for the deliverable type. It appears in the unique index OKC_DEL_BUS_DOC_COMBXNS_U1 and supports joins and lookups using a user-recognizable identifier.
• ZD_EDITION_NAME — Edition qualifier used in the unique business-key index, enabling edition-specific validity of class/type combinations.
• CREATED_BY, CREATION_DATE — Standard audit columns recording who inserted the combination record and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification of the row, including the login that performed the update.

The surrogate primary key is OKC_DEL_BUS_DOC_COMBXNS_PK, while the documented business-key candidate is the unique index OKC_DEL_BUS_DOC_COMBXNS_U1, which adds DELIVERABLE_TYPE_CODE and ZD_EDITION_NAME beyond the PK columns. Note that the documented column list names DELIVERABLE_TYPE_CODE rather than DELIVERABLE_TYPE; where both appear in different metadata contexts, treat DELIVERABLE_TYPE as the foreign-key target column and DELIVERABLE_TYPE_CODE as the indexed code attribute.

Common Use Cases and Queries

Typical scenarios include validating that a selected deliverable type is permitted for a given business document class, reporting the configured deliverable matrix for a contract type, and troubleshooting why a deliverable type is unavailable during contract authoring. Because rows represent valid combinations, application logic and reports commonly query this table to drive LOVs or to reconcile setup between environments.

A representative query retrieves the valid deliverable types for a class:

• SELECT c.document_type_class, c.deliverable_type, c.deliverable_type_code, c.zd_edition_name FROM okc_del_bus_doc_combxns c WHERE c.document_type_class = :document_type_class;
• Join to the deliverable master for descriptive names: SELECT c.document_type_class, b.deliverable_type_name FROM okc_del_bus_doc_combxns c, okc_deliverable_types_b b WHERE c.deliverable_type = b.deliverable_type;
• Audit recently changed setup: SELECT * FROM okc_del_bus_doc_combxns WHERE last_update_date >= :since_date ORDER BY last_update_date;

Reporting use cases include matrix reports of classes versus deliverable types, gap analysis of missing combinations before an upgrade, and data-migration validation in 12.1.1 to 12.2.2 upgrades where edition-aware indexing affects setup comparison.

Related Objects

The principal related objects are those linked through the documented foreign-key and business-key relationships:

• OKC_DELIVERABLE_TYPES_B — Referenced by OKC_DEL_BUS_DOC_COMBXNS.DELIVERABLE_TYPE; the master table of deliverable type definitions and the primary FK target.
• OKC_DEL_BUS_DOC_COMBXNS_PK — Primary-key constraint over (DOCUMENT_TYPE_CLASS, DELIVERABLE_TYPE), enforcing unique combinations.
• OKC_DEL_BUS_DOC_COMBXNS_U1 — Unique index over (DOCUMENT_TYPE_CLASS, DELIVERABLE_TYPE_CODE, ZD_EDITION_NAME), serving as the business-key candidate.
• OKC Business Document Class definitions — The class side of the mapping; document type class values originate from OKC document class/type setup and are consumed here for validation.
• OKC Contracts authoring and deliverables APIs — Application components that consult the valid combination setup during contract and deliverable entry, using the class/type pairing to constrain user selections.

Collectively, these objects keep the valid combination setup consistent with the deliverable type master and enforce the class-to-deliverable mapping used throughout Contracts Core.