Search Results okc_xprt_question_orders




Overview
Explore in AI Chat

Overview

OKC_XPRT_QUESTION_ORDERS is a Contracts Core (OKC) table within Oracle E-Business Suite 12.1.1 and 12.2.2 that governs the display order of questions presented to users at runtime during contract authoring. It functions as an intersection entity between terms templates (OKC_TERMS_TEMPLATES_ALL) and question definitions (OKC_XPRT_QUESTIONS_B), allowing the same question to participate in multiple templates with independent sequencing, mandatory status, and availability rules. From a Data Vault modeling perspective, the documented FK structure suggests classifying this object as a link table, since it resolves a many-to-many relationship between templates and questions and carries descriptive attributes on that relationship.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is QUESTION_ORDER_ID, enforced by OKC_XPRT_QUESTION_ORDERS_PK and the unique index OKC_XPRT_QUESTION_ORDERS_U1. A second unique index, OKC_XPRT_QUESTION_ORDERS_U2, spans TEMPLATE_ID and QUESTION_ID, forming the natural business-key candidate that guarantees a question appears only once per template.

  • QUESTION_ORDER_ID — Surrogate primary key of the ordering record.
  • TEMPLATE_ID — Foreign key to OKC_TERMS_TEMPLATES_ALL, identifying the owning template.
  • QUESTION_ID — Foreign key to OKC_XPRT_QUESTIONS_B, identifying the question being positioned.
  • SEQUENCE_NUM — Display order of the question within the template at runtime.
  • MANDATORY_FLAG — Indicates whether the user must answer the question.
  • RUNTIME_AVAILABLE_FLAG — Controls whether the question is surfaced during contract execution.
  • QUESTION_RULE_STATUS — Tracks the rule processing state associated with the question.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM layer.
  • CREATED_BY, CREATION_DATE — Standard audit columns for record creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns for the most recent modification.

Common Use Cases and Queries

The primary use case is rendering an ordered question list when a contract is authored from a given template. Reporting queries typically join to OKC_XPRT_QUESTIONS_B to resolve question prompts and to OKC_TERMS_TEMPLATES_ALL to resolve template names.

  • Retrieve the runtime question sequence for a template: SELECT q.sequence_num, qb.question_text FROM okc_xprt_question_orders q, okc_xprt_questions_b qb WHERE q.question_id = qb.question_id AND q.template_id = :template_id AND q.runtime_available_flag = 'Y' ORDER BY q.sequence_num;
  • Identify mandatory questions per template using MANDATORY_FLAG = 'Y' for validation or gap analysis.
  • Audit recently modified ordering records via LAST_UPDATED_BY and LAST_UPDATE_DATE to track template configuration changes.
  • Reconcile template-question pairings against OKC_XPRT_QUESTION_ORDERS_U2 to detect duplicate or orphaned assignment attempts.

Related Objects

The table participates in a small, well-defined relationship graph anchored by its two foreign keys.

  • OKC_TERMS_TEMPLATES_ALL — Parent template entity; joined on TEMPLATE_ID.
  • OKC_XPRT_QUESTIONS_B — Parent question definition; joined on QUESTION_ID.
  • OKC_XPRT_QUESTIONS_TL — Translation table supplying language-specific question text for reporting.
  • OKC_XPRT_QUESTION_RULES — Rule definitions that consume QUESTION_RULE_STATUS from this table.
  • OKC_XPRT_QUESTION_ANSWERS — Runtime responses collected for questions positioned here.
  • OKC_TERMS_TEMPLATE_QUESTIONS — Related template-question linkage used by some Contracts flows.
  • OKC_XPRT_QUESTION_ORDERS_PK / _U1 / _U2 — Indexes supporting primary-key and business-key access paths.

Together these objects form the metadata layer that drives the dynamic question-and-answer experience in Oracle Contracts authoring.