Results for “okc_xprt_questions_b”

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

Overview

The OKC_XPRT_QUESTIONS_B table resides in the OKC (Contracts Core) schema and forms part of the Oracle E-Business Suite Contracts expert/rule-based question infrastructure. As its description states, this entity stores user questions, constants, and expert variables that drive the conditional logic used during contract authoring and clause selection. In EBS, expert systems allow business users to answer a guided set of questions, and the responses determine which clauses, terms, or conditions are applied to a contract. This table is the master definition of those question objects.

From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies this object as standalone. The table is referenced by dependent child tables (notably OKC_XPRT_QUESTION_ORDERS) rather than participating in a hub/link/satellite chain within its own right. Where a modeling suggestion is useful, OKC_XPRT_QUESTIONS_B can be treated as a reference/dimension-style entity in which QUESTION_ID behaves as a stable business key, with descriptive attributes forming an implicit satellite context.

Key Information Stored

The documented physical schema contains 20 columns. The most significant are summarized below.

• QUESTION_ID — The surrogate primary key, enforced by OKC_XPRT_QUESTIONS_B_PK, and additionally backed by the unique index OKC_XPRT_QUESTIONS_B_U1. It uniquely identifies each question, constant, or expert variable.
• QUESTION_TYPE — Distinguishes whether the record is a user question, a constant, or an expert variable.
• QUESTION_INTENT — Captures the intended behavior of the question in the expert flow.
• QUESTION_DATATYPE — The data type expected for the answer (for example text, number, or date).
• VALUE_SET_NAME — References the value set that supplies permitted or list-based answers.
• DEFAULT_VALUE, MINIMUM_VALUE, MAXIMUM_VALUE — Default answer, and the lower and upper bounds for numeric or comparable responses.
• DISABLED_FLAG — Indicates whether the question is inactive and withheld from the expert flow.
• QUESTION_SYNC_FLAG — Governs synchronization behavior for the question record.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/ADF framework for concurrent update control.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE record who created and last changed each row and which concurrent program touched it.

The surrogate key is QUESTION_ID. No separate business-key column set is documented beyond this unique identifier, so QUESTION_ID effectively serves both roles.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include enumerating active questions, inspecting default and range settings, and tracing which questions belong to a particular ordering sequence.

• List enabled questions with their data types and value sets.
• Find constants and expert variables versus interactive user questions.
• Audit recent changes for governance or reconciliation.
• Join to OKC_XPRT_QUESTION_ORDERS to determine question sequencing or grouping.

Representative SQL patterns:

• SELECT question_id, question_type, question_datatype, value_set_name FROM okc.okc_xprt_questions_b WHERE disabled_flag = 'N';
• SELECT * FROM okc.okc_xprt_questions_b WHERE question_type = 'CONSTANT';
• SELECT q.question_id, q.default_value, o.order_id FROM okc.okc_xprt_questions_b q, okc.okc_xprt_question_orders o WHERE q.question_id = o.question_id;
• SELECT question_id, last_updated_by, last_update_date FROM okc.okc_xprt_questions_b WHERE last_update_date > SYSDATE - 30;

Related Objects

The dominant documented relationship is the child table that inherits the primary key as a foreign key:

• OKC_XPRT_QUESTION_ORDERS — References OKC_XPRT_QUESTIONS_B via OKC_XPRT_QUESTION_ORDERS.QUESTION_ID, ordering questions within the expert flow.

Additional OKC Contracts expert/rule tables and the Contracts Core APIs generally operate alongside this table when evaluating expert logic, but OKC_XPRT_QUESTION_ORDERS is the principal dependent object explicitly documented through the FK definition.