Results for “csr_tests_b”

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

Overview

The CSR_TESTS_B table is a core definition table within the CSR (Scheduler) product module of Oracle E-Business Suite. Per the ETRM reference documentation, it stores Timing Scenario Definitions at the base-table level, as indicated by the _B suffix. The object resides in the CSR schema, is flagged with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2, and contains 24 documented columns. Its purpose is to persist the operational parameters that a scheduler simulation or performance test run consumes when exercising field service scheduling logic — including route topology, resource trips, spares, and territory constraints. Because the CSR Scheduler module drives the assignment of field service tasks to technicians, the scenario records in this table act as the input configuration for repeatable timing and load exercises, which is directly relevant to users searching for guidance on creating Tricentis Enterprise performance testing virtual machines against EBS Scheduling workloads.

Under the heuristic Data Vault classification mined from the foreign-key structure, this table is assessed as a standalone object. In Data Vault modeling terms, that assessment suggests treating it as a hub-like or reference construct rather than a link table bridging multiple hubs. The single documented foreign key attaches to FND_SECURITY_GROUPS, which is a common pattern for a secured reference table rather than a transactional intersection.

Key Information Stored

The table separates its surrogate identity from its business key and then stores a broad set of scheduler configuration attributes. The most significant columns are:

• TEST_NUMBER — the business-key candidate. A unique index, CSR_TESTS_B_U1, is documented on this column, making it the natural identifier of a timing scenario.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking token, incremented on each update to prevent lost updates.
• SECURITY_GROUP_ID — the documented foreign key to FND_SECURITY_GROUPS, scoping the scenario to a security group.
• TASK_NUMBER — identifies the schedule task associated with the scenario.
• PLANNED_START and PLANNED_END — the nominal time window for the scenario.
• PLAN_MODE — the planning mode governing how the scheduler resolves the scenario.
• SPARES, TRIPS, and SKILLS — capacity and qualification parameters that drive resource assignment.
• TDS_ROUTE, TDS_LOC, and TDS_DFLT — route, location, and default values used by the time-distance engine.
• TERRITORIES, CONTRACTS, and IB — territory, contract, and install-base scope flags.
• TIMESTAMP, STOPWATCH, and DESCRIPTION — run-timing markers and the human-readable scenario description.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS Who columns providing audit lineage.

The metadata does not document a named surrogate primary key constraint distinct from the unique index, so TEST_NUMBER should be treated as the authoritative business identifier.

Common Use Cases and Queries

Typical use cases include auditing scenario definitions, extracting configuration for performance-test baselines, and validating that scenarios are complete before a scheduler run. A representative query by scenario number is:

• SELECT t.test_number, t.description, t.plan_mode, t.planned_start, t.planned_end, t.spares, t.trips FROM csr.csr_tests_b t WHERE t.test_number = :n;
• Joining to security groups: SELECT t.test_number, g.security_group_name FROM csr.csr_tests_b t JOIN fnd_security_groups g ON t.security_group_id = g.security_group_id;
• Reporting recently modified scenarios: SELECT test_number, last_updated_by, last_update_date FROM csr.csr_tests_b WHERE last_update_date > SYSDATE - 30 ORDER BY last_update_date DESC;

Because the table is widely read during scheduler execution, queries should be predicated on TEST_NUMBER or the security group to exploit the unique index.

Related Objects

• FND_SECURITY_GROUPS — referenced via CSR_TESTS_B.SECURITY_GROUP_ID; the only documented foreign-key relationship and the primary join target.
• CSR_TESTS_TL — the translation (TL) companion table that holds language-specific text for a base _B record, joined on the shared identifier.
• FND_APPLICATION / FND_PRODUCT_GROUPS — product registration context for the CSR module.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to operator identities for audit reporting.
• FND_LOGINS — resolves LAST_UPDATE_LOGIN to the session that performed the update.
• CSR Scheduler concurrent programs and public APIs that consume timing scenario definitions to drive assignment and routing runs.