Results for “csr_rules_vl”

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

Overview

The CSR_RULES_VL view is a translated (VL, "view language") reporting object owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the CSR — Scheduler product, which is the resource-scheduling engine used by modules such as Field Service, Depot Repair, and TeleService. The view presents scheduler rule definitions in a language-aware manner, joining the base rule table to its translation table so that rule names and descriptions are returned in the session’s language (USERENV('LANG')). Because it is a VL view, it is the correct object to query for user-facing reporting and integration rather than the underlying _B and _TL tables, which expose only internal identifiers or individual translations. The object is documented with a status of VALID in the ETRM metadata, confirming that it is a supported, queryable view.

Underlying Base Objects

The view is defined over two synonym-referenced tables — CSR_RULES_B and CSR_RULES_TL — joined on RULE_ID. CSR_RULES_B holds the non-translated rule attributes (identifiers, ownership, flags, rank, and document content), while CSR_RULES_TL stores the translated rule name and description for each installed language. The documented base objects additionally include WINDOW1532_COLL (a collection type), the STANDARD package, and XMLTYPE, reflecting the Oracle Forms/HTML infrastructure and XML rule-document handling associated with the scheduler rule maintenance UI. When a user searches for csr_rules_b, that synonym is in fact the base table behind this view; the VL view is the intended access point for rule names and descriptions.

Key Columns

• RULE_ID — Primary key of the scheduling rule, shared between the base and translation tables.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework during updates.
• BASE_RULE_ID — Reference to the source/base rule when a rule is derived from a seeded definition.
• APPL_ID, RESP_ID, USER_ID — Application, responsibility, and user scoping for the rule’s applicability.
• TERR_ID — Territory identifier to which the rule applies.
• RESOURCE_TYPE, RESOURCE_ID — The resource category and specific resource governed by the rule.
• ENABLED_FLAG — Indicates whether the rule is active (Y/N).
• RULE_RANK — Priority/ranking used by the scheduler when resolving competing rules.
• RULE_DOC — XML document containing the rule definition logic.
• RULE_NAME, DESCRIPTION — Translated name and description from CSR_RULES_TL, filtered to the session language.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes reporting enabled scheduling rules by territory or resource, auditing rule rank and precedence, and extracting RULE_DOC XML for integration or migration. Because the view filters translations automatically, it is preferred over direct joins to CSR_RULES_TL.

List enabled rules with translated names:

SELECT rule_id, rule_name, rule_rank, enabled_flag
FROM   apps.csr_rules_vl
WHERE  enabled_flag = 'Y'
ORDER  BY rule_rank;

Inspect rules scoped to a specific resource type and territory:

SELECT rule_id, rule_name, terr_id, resource_id, rule_doc
FROM   apps.csr_rules_vl
WHERE  resource_type = :p_resource_type
AND    terr_id = :p_terr_id;

Retrieve the XML definition for a given rule in the current language:

SELECT t.rule_name, t.rule_doc.getClobVal()
FROM   apps.csr_rules_vl t
WHERE  t.rule_id = :p_rule_id;

These queries return only the rows whose translation matches the caller’s language, ensuring consistent, locale-correct reporting across EBS 12.1.1 and 12.2.2 environments.