Search Results okc_xprt_rule_statuses

Overview

OKC.OKC_XPRT_QUESTION_ORDERS is a transactional intersection table in the Oracle E-Business Suite Contract Expert (OKC) schema. It captures the presentation order and runtime behavior of questions associated with a contract terms template, and it is the definitive source for the sequence in which Contract Expert prompts are rendered to an authoring user during contract creation. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

The ETRM dependency metadata classifies this object heuristically as a link in a Data Vault model. That classification is a modeling suggestion rather than a functional designation: the table resolves a many-to-many relationship between two parent entities — templates and questions — and therefore carries foreign keys to both, which is the defining characteristic of a link table. Its surrogate primary key, QUESTION_ORDER_ID, is generated from a sequence and is enforced by OKC_XPRT_QUESTION_ORDERS_PK. Because the table also stores descriptive attributes such as ordering and status flags, it behaves functionally as an intersection entity that is queried directly at runtime rather than as a pure associative key store.

Key Information Stored

The most significant columns fall into three logical groups: identity, foreign key linkage, and behavioral control.

• QUESTION_ORDER_ID — the surrogate primary key, a sequence-generated NUMBER that uniquely identifies each row and is backed by unique index OKC_XPRT_QUESTION_ORDERS_U1.
• TEMPLATE_ID — FK to OKC_TERMS_TEMPLATES_ALL, identifying the contract terms template to which the question ordering applies.
• QUESTION_ID — FK to OKC_XPRT_QUESTIONS_B, identifying the specific Contract Expert question.
• SEQUENCE_NUM — the ordinal position in which the question is displayed when Contract Expert is invoked during contract authoring.
• MANDATORY_FLAG — indicates whether the question must be answered at runtime.
• QUESTION_RULE_STATUS — status of the rule in which the question participates; where a question appears in multiple rules, the highest-priority status is shown, with priority order ACTIVE, PENDINGPUB, then DRAFT. It is tied to the FND lookup OKC_XPRT_RULE_STATUSES.
• RUNTIME_AVAILABLE_FLAG — null or N at record creation, updated to Y once a template is successfully published in Oracle Configurator; read-only question order regions render "Shown in Runtime" from this value.
• OBJECT_VERSION_NUMBER — optimistic locking value set to 1 on insert and incremented on update for API concurrency control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking row provenance and change history.

The second unique index, OKC_XPRT_QUESTION_ORDERS_U2, covers the column pair (TEMPLATE_ID, QUESTION_ID), making this composite the business-key candidate: a given question may appear only once per template, with QUESTION_ORDER_ID acting purely as the technical surrogate.

Common Use Cases and Queries

Typical reporting and diagnostic queries retrieve the ordered question set for a template, confirm mandatory questions, or audit which questions have become runtime-available after Configurator publishing.

• Retrieve the runtime question sequence for a template: SELECT q.question_id, o.sequence_num, o.mandatory_flag FROM okc_xprt_question_orders o, okc_xprt_questions_b q WHERE o.question_id = q.question_id AND o.template_id = :template_id AND o.runtime_available_flag = 'Y' ORDER BY o.sequence_num;
• List all templates that include a specific question, using the U2 business key: SELECT template_id, sequence_num, mandatory_flag FROM okc_xprt_question_orders WHERE question_id = :question_id;
• Identify questions awaiting publication: SELECT * FROM okc_xprt_question_orders WHERE runtime_available_flag IS NULL OR runtime_available_flag = 'N';
• Audit rule-status distribution and mandatory prompts per template for contract authoring readiness checks.

Related Objects

• OKC.OKC_TERMS_TEMPLATES_ALL — parent template entity; joined via TEMPLATE_ID.
• OKC.OKC_XPRT_QUESTIONS_B — parent question entity; joined via QUESTION_ID.
• OKC.OKC_XPRT_QUESTION_ORDERS_PK — primary key constraint on QUESTION_ORDER_ID.
• OKC_XPRT_QUESTION_ORDERS_U1 / U2 — unique indexes supporting surrogate and business-key access paths.
• FND lookup OKC_XPRT_RULE_STATUSES — validates QUESTION_RULE_STATUS values.
• Contract Expert runtime UI logic and Oracle Configurator publishing routines, which read RUNTIME_AVAILABLE_FLAG and SEQUENCE_NUM to render questions.