Results for “ota_section_rules_uk2”

14 results




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

Overview

OTA.OTA_SECTION_RULES is a transactional configuration table in the Oracle E-Business Suite (EBS) Oracle Training Administration (OTA) module, available in releases 12.1.1 and 12.2.2. It stores the Question Bank selection rules that determine how many questions are drawn from each question bank when generating a test. The table is only meaningful when the parent test is defined as rule-based or dynamic, that is, when OTA_TESTS.TYPE_FLAG is set to "D". In that mode, the rules in this table, rather than a fixed list of test questions, drive test assembly.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, confirming its role as a transactional data store. The documented physical schema contains 13 columns. Under the heuristic Data Vault classification mined from the foreign-key structure, OTA_SECTION_RULES is best modeled as a link table: it resolves the many-to-many relationships between tests, test sections, and question banks, and carries descriptive payload such as question counts and sequencing. This classification is a modeling suggestion rather than a mandated EBS construct.

Key Information Stored

The surrogate primary key is SECTION_RULE_ID, exposed through the unique index OTA_SECTION_RULES_PK. Two additional unique indexes represent business-key candidates and constrain the combinations of related entities:

The two business-key candidates are OTA_SECTION_RULES_UK1 (SECTION_ID, QUESTION_BANK_ID) and OTA_SECTION_RULES_UK2 (TEST_ID, QUESTION_BANK_ID). The uniqueness enforced by these indexes means a given question bank may appear at most once per section and at most once per test, which is the principle of interest when searching for OTA_SECTION_RULES_UK2.

Common Use Cases and Queries

Typical scenarios include auditing which question banks feed a dynamic test, reconciling the requested question count against actual test content, and reporting test composition by section. A representative query joining the rule to its parent test is:

  • SELECT sr.SECTION_RULE_ID, sr.TEST_ID, sr.SECTION_ID, sr.QUESTION_BANK_ID, sr.NUMBER_OF_QUESTIONS, sr.SEQUENCE FROM OTA.OTA_SECTION_RULES sr WHERE sr.TEST_ID = :test_id ORDER BY sr.SECTION_ID, sr.SEQUENCE;
  • To detect duplicate bank assignments per test, group by TEST_ID and QUESTION_BANK_ID and filter for counts greater than one; the OTA_SECTION_RULES_UK2 index guarantees this should not occur.
  • To aggregate the total number of questions generated for a test, sum NUMBER_OF_QUESTIONS across all section rules for the given TEST_ID.

Because the table is only populated for tests with TYPE_FLAG = "D", reports should join to OTA_TESTS and filter on that flag to avoid returning rows for static tests.

Related Objects

The table is tightly coupled to the following OTA entities through documented foreign keys:

  • OTA.OTA_TESTS — joined on TEST_ID; the parent test definition, including TYPE_FLAG.
  • OTA.OTA_TEST_SECTIONS — joined on SECTION_ID; the test sections to which rules apply.
  • OTA.OTA_QUESTION_BANKS — joined on QUESTION_BANK_ID; the source banks for question selection; this relationship is also carried by the non-unique index OTA_SECTION_RULES_FK1.
  • HR.HR_ALL_ORGANIZATION_UNITS — referenced by BUSINESS_GROUP_ID for organization security.
  • OTA.OTA_QUESTIONS — indirectly related through OTA_QUESTION_BANKS, providing the questions that satisfy the rules.

No PL/SQL API specific to this table is documented in the ETRM metadata; maintenance is normally performed through the OTA test definition forms and concurrent test-generation processes.