Results for “amendment_notes”

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

Overview

OKC_DELIVERABLES is a core transactional table in the Contracts Core (OKC) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores deliverable definitions and amendments to those deliverables that are attached to contracts and other business documents managed within EBS. A deliverable represents a discrete obligation, milestone, or event-driven action associated with a contract — for example, a submission, a payment milestone, a renewal notice, or a recurring reporting duty — together with its scheduling rules, responsible parties, and notification behavior.

The table is documented as VALID in the OKC schema and contains 99 columns in the 12.2.2 physical schema. Per the heuristic Data Vault classification mined from its foreign key structure, OKC_DELIVERABLES is best modeled as a link entity: it associates a business document (the contract) with deliverable metadata, notification messages, and event definitions, rather than functioning as a standalone hub. This classification is a modeling suggestion only; the table is natively a conventional EBS transactional entity.

Amendments are handled in-table. Columns such as AMENDMENT_OPERATION, ORIGINAL_DELIVERABLE_ID, and SUMMARY_AMEND_OPERATION_CODE allow amended versions of a deliverable to be stored alongside the original, supporting contract versioning without a separate amendment table.

Key Information Stored

The primary key is OKC_DELIVERABLES_PK, defined on DELIVERABLE_ID, which is a surrogate identifier. A second unique index, OKC_DELIVERABLES_U1, is also defined on DELIVERABLE_ID; it does not expose a separate natural business key, so DELIVERABLE_ID serves as the effective join key throughout the module.

• DELIVERABLE_ID — surrogate primary key and the principal foreign key target for dependent tables.
• BUSINESS_DOCUMENT_ID / BUSINESS_DOCUMENT_TYPE / BUSINESS_DOCUMENT_NUMBER / BUSINESS_DOCUMENT_VERSION / BUSINESS_DOCUMENT_LINE_ID — identify the owning contract (or other business document), its version, and optionally the line to which the deliverable belongs.
• DELIVERABLE_TYPE, DELIVERABLE_NAME, DESCRIPTION, COMMENTS, DELIVERABLE_STATUS, DISPLAY_SEQUENCE — classify, name, describe, and sequence the deliverable; DELIVERABLE_STATUS tracks its lifecycle state.
• FIXED_DUE_DATE_YN, ACTUAL_DUE_DATE, COMPLETION_DATE, FIXED_START_DATE, FIXED_END_DATE — fixed and actual date scheduling attributes.
• RELATIVE_ST_DATE_DURATION/UOM/EVENT_ID and RELATIVE_END_DATE_DURATION/UOM/EVENT_ID — event-relative scheduling, where the start and end are computed from business document events plus an offset.
• RECURRING_YN, RECURRING_DEL_PARENT_ID, REPEATING_DAY_OF_MONTH, REPEATING_DAY_OF_WEEK, REPEATING_FREQUENCY_UOM, REPEATING_DURATION — recurring deliverable definition and the parent recurrence record.
• RESPONSIBLE_PARTY, INTERNAL_PARTY_ID, INTERNAL_PARTY_CONTACT_ID, EXTERNAL_PARTY_ID, EXTERNAL_PARTY_SITE_ID, EXTERNAL_PARTY_ROLE, REQUESTER_ID — party and contact assignment.
• NOTIFY_PRIOR_DUE_DATE_*, NOTIFY_COMPLETED_YN, NOTIFY_OVERDUE_YN, NOTIFY_ESCALATION_*, ESCALATION_ASSIGNEE, PRINT_DUE_DATE_MSG_NAME, DISABLE_NOTIFICATIONS_YN — notification and escalation configuration, including the message template referenced in OKC_DEL_MESSAGES.
• AMENDMENT_OPERATION, ORIGINAL_DELIVERABLE_ID, AMENDMENT_NOTES, LAST_AMENDMENT_DATE, SUMMARY_AMEND_OPERATION_CODE — amendment lineage and history.
• ORIG_SYSTEM_REFERENCE_CODE, ORIG_SYSTEM_REFERENCE_ID1, ORIG_SYSTEM_REFERENCE_ID2 — external system cross-reference for integration scenarios.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard audit and optimistic locking columns. The additional columns PAY_HOLD_*, COMPLETION_DATE, RAISE_COMPLETION_EVENT_YN, DEL_CATEGORY_CODE, EXHIBIT_CODE, DATA_ITEM_NUMBER, PRICE_GROUP, ESTIMATED_PRICE, UDA_TEMPLATE_ID, and SCHEDULE_TYPE extend 12.2 functionality around pricing, exhibits, and scheduling.

Common Use Cases and Queries

Typical reporting includes listing all deliverables for a contract, identifying overdue or incomplete deliverables, and reviewing amendment history. A representative query joining the contract structure is:

SELECT d.deliverable_id, d.deliverable_name, d.deliverable_status,
       d.actual_due_date, d.completion_date, d.responsible_party
FROM   okc_deliverables d
WHERE  d.business_document_id = :contract_id
AND    d.deliverable_status <> 'COMPLETE'
ORDER  BY d.display_sequence;

Amendment tracking uses ORIGINAL_DELIVERABLE_ID to trace successor rows, while recurring obligations are identified through RECURRING_YN and RECURRING_DEL_PARENT_ID. Notification configuration is validated against OKC_DEL_MESSAGES via PRINT_DUE_DATE_MSG_NAME, and event-relative scheduling is resolved through RELATIVE_ST_DATE_EVENT_ID and RELATIVE_END_DATE_EVENT_ID against OKC_BUS_DOC_EVENTS_B, with the computed dates available in START_EVENT_DATE and END_EVENT_DATE.

Related Objects

• OKC_DEL_MESSAGES — joined on OKC_DELIVERABLES.PRINT_DUE_DATE_MSG_NAME; supplies the notification message template.
• OKC_BUS_DOC_EVENTS_B — referenced twice, via RELATIVE_ST_DATE_EVENT_ID and RELATIVE_END_DATE_EVENT_ID; defines the business document events that anchor relative scheduling.
• OKC_DELIVERABLES (self-reference) — ORIGINAL_DELIVERABLE_ID and RECURRING_DEL_PARENT_ID link amendments and recurrence children back to their parent rows.
• OKC_CONTRACTS (OKC_K_HEADERS_B / OKC_K_HEADERS_TL) — the contract header master referenced through BUSINESS_DOCUMENT_ID for contract-type documents.
• OKC_K_LINES_B / OKC_K_LINES_TL — contract lines referenced by BUSINESS_DOCUMENT_LINE_ID where a deliverable is line-specific.
• OKC_NOTIFICATIONS / OKC_DEL_NOTIFICATIONS — notification instances generated from the notification columns on this table.
• OKC_DELIVERABLES_V — the standard descriptive view over the deliverable table used for reporting.
• OKC_DELIVERABLE_API / OKC_DELIVERABLE_PUB — the public APIs used to create, amend, and complete deliverables programmatically.

These relationships confirm the link role of OKC_DELIVERABLES: it anchors contract documents, events, messages, and notification processes into a single deliverable obligation record.