Search Results okc_del_messages




Overview

The OKC_DEL_MESSAGES table is a metadata repository within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for releases 12.1.1 and 12.2.2. Its primary function is to store predefined message templates used for constructing due date notifications related to contract deliverables. This table acts as a central lookup, enabling the system to generate consistent, user-defined textual messages that describe deliverable due dates, which are then referenced by the main deliverables table. It is a foundational component for the deliverable tracking and communication features of the Contracts module.

Key Information Stored

The table's structure is designed to catalog message definitions by a unique identifier. The most critical column is MESSAGE_NAME, which serves as the table's primary key. This column stores the unique code or name identifying a specific due date message template. While the provided ETRM metadata does not list all columns, the table's description implies it contains the necessary attributes to define the message's format and logic. This typically includes columns for the message text itself, potentially with placeholders for dynamic date or deliverable information, and possibly indicators controlling its application or language.

Common Use Cases and Queries

The primary use case is the dynamic generation of due date descriptions on contract deliverable reports and forms. When a user assigns a due date message to a deliverable, the system references this table to retrieve the template. A common administrative query would be to list all available message templates for setup or audit purposes. For example:

  • SELECT message_name FROM okc.okc_del_messages ORDER BY 1;

To see which deliverables are using a specific message template, a join with the OKC_DELIVERABLES table is necessary. This is crucial for impact analysis before modifying or obsoleting a message definition.

Related Objects

OKC_DEL_MESSAGES has a direct, documented relationship with the core deliverables table. The primary key (MESSAGE_NAME) is referenced by the following foreign key:

  • Table: OKC_DELIVERABLES
  • Foreign Key Column: OKC_DELIVERABLES.PRINT_DUE_DATE_MSG_NAME
  • Relationship: This foreign key constraint ensures that any value populated in the PRINT_DUE_DATE_MSG_NAME column of a deliverable must exist as a MESSAGE_NAME in the OKC_DEL_MESSAGES table. This enforces data integrity for deliverable message assignments.

This relationship is central to the object's purpose, making OKC_DELIVERABLES the primary consumer of the metadata stored within OKC_DEL_MESSAGES.

  • Table: OKC_DEL_MESSAGES 12.1.1

    owner:OKC,  object_type:TABLE,  fnd_design_data:OKC.OKC_DEL_MESSAGES,  object_name:OKC_DEL_MESSAGES,  status:VALID,  product: OKC - Contracts Coredescription: OKC_DEL_MESSAGES stores the metadata for building various combinations of due date messages for deliverables. ,  implementation_dba_data: OKC.OKC_DEL_MESSAGES

  • Table: OKC_DEL_MESSAGES 12.2.2

    owner:OKC,  object_type:TABLE,  fnd_design_data:OKC.OKC_DEL_MESSAGES,  object_name:OKC_DEL_MESSAGES,  status:VALID,  product: OKC - Contracts Coredescription: OKC_DEL_MESSAGES stores the metadata for building various combinations of due date messages for deliverables. ,  implementation_dba_data: OKC.OKC_DEL_MESSAGES

  • Table: OKC_DELIVERABLES 12.1.1

    owner:OKC,  object_type:TABLE,  fnd_design_data:OKC.OKC_DELIVERABLES,  object_name:OKC_DELIVERABLES,  status:VALID,  product: OKC - Contracts Coredescription: This table stores Deliverables and amendments to deliverables. ,  implementation_dba_data: OKC.OKC_DELIVERABLES

  • Table: OKC_DELIVERABLES 12.2.2

    owner:OKC,  object_type:TABLE,  fnd_design_data:OKC.OKC_DELIVERABLES,  object_name:OKC_DELIVERABLES,  status:VALID,  product: OKC - Contracts Coredescription: This table stores Deliverables and amendments to deliverables. ,  implementation_dba_data: OKC.OKC_DELIVERABLES