Results for “csr_spares_source”

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

Overview

APPS.CSR_RULES_TRANSLATED_V is a reporting view in the Oracle E-Business Suite (EBS) Service / Field Service module, specifically within the e-Technical Resource Management (eTRM) or Scheduler component. The view presents scheduling rules defined in the CSR_RULES tables in a fully denormalized, human-readable, and translated form. Rather than exposing raw foreign-key identifiers and lookup codes, the view resolves each code to its descriptive meaning using subqueries against FND_LOOKUPS, and it joins across user, responsibility, application, territory, and resource objects to present a complete rule definition in a single row.

The view is owned by APPS and is intended primarily for reporting, ad-hoc queries, and integration scenarios where an external or downstream process must consume scheduling rule definitions without performing the same translation logic. Because the view exposes the lookup meaning for controlled columns such as the plan-window enforcement flag, it is the authoritative source for interpreting the semantics of a given rule.

Underlying Base Objects

The view is defined over a set of documented base objects: CSR_RULES_TL (the translatable rules table, accessed via synonym), FND_APPLICATION_TL, FND_RESPONSIBILITY_TL, FND_USER, FND_LOOKUPS, JTF_OBJECTS_VL, JTF_RS_ALL_RESOURCES_VL, JTF_TASK_STATUSES_VL, JTF_TERR_ALL, CSF_DC_QUERIES_VL, and CSR_RULES_EXPLODED_V. Supporting packages include FND_GLOBAL, HR_GENERAL, and HR_SECURITY, the latter used to enforce security on the resource and user data returned. A collection type, WINDOW1532_COLL, also participates in the definition.

The primary driving table is CSR_RULES_TL, from which rule identity, ranking, scope, and all scheduler planning parameters (the sp_* columns) originate. Descriptive attributes such as application name, responsibility name, user name, territory name, resource type name, and resource name are joined in from their respective master views and synonyms. The view also references CSR_RULES_EXPLODED_V, indicating that rule hierarchies (via base_rule_id and base_rule_name) are resolved to surface parent-child rule relationships.

Key Columns

Identity and descriptive columns include RULE_ID, RULE_NAME, DESCRIPTION, and OBJECT_VERSION_NUMBER. The BASE_RULE_ID and BASE_RULE_NAME columns expose the parent rule when a rule is derived or inherited. Contextual columns include APPLICATION_NAME, RESPONSIBILITY_NAME, USER_NAME, TERRITORY_NAME, RESOURCE_TYPE_NAME, and RESOURCE_NAME, each resolved through the corresponding base object.

Scheduler planning parameters form the core of the view. SP_PLAN_SCOPE, SP_MAX_PLAN_OPTIONS, SP_MAX_RESOURCES, SP_MAX_CALC_TIME, SP_MAX_OVERTIME, and SP_WTP_THRESHOLD carry raw numeric or code values. Several columns are explicitly translated against FND_LOOKUPS: SP_ENFORCE_PLAN_WINDOW (lookup type CSR_ENFORCE_PLAN_WINDOW), SP_CONSIDER_STANDBY_SHIFTS (CSR_CONSIDER_STANDBY_SHIFTS), SP_SPARES_MANDATORY and other YES_NO flags, and SP_SPARES_SOURCE (CSR_SPARES_SOURCE). The ENABLED_FLAG is also returned as a translated YES_NO meaning. Rule ordering is provided by RULE_RANK, and audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are exposed for traceability.

Common Use Cases and Queries

The most common use is to determine whether a scheduling rule enforces the planning window. Since the user search term was "csr_enforce_plan_window," a typical query is:

• SELECT rule_name, sp_enforce_plan_window, sp_plan_scope FROM apps.csr_rules_translated_v WHERE sp_enforce_plan_window IS NOT NULL;
• SELECT rule_name, sp_consider_standby_shifts, sp_spares_mandatory, sp_spares_source FROM apps.csr_rules_translated_v ORDER BY rule_rank;
• SELECT rule_name, base_rule_name, territory_name, resource_name, enabled_flag FROM apps.csr_rules_translated_v WHERE enabled_flag = 'Yes';
• SELECT rule_name, sp_max_resources, sp_max_overtime, sp_wtp_threshold FROM apps.csr_rules_translated_v WHERE sp_plan_scope = :scope;

Because the view returns lookup meanings rather than codes, reports and integration extracts can be generated without additional FND_LOOKUPS joins, ensuring consistent interpretation of plan-window enforcement and related scheduler behavior across Oracle EBS 12.1.1 and 12.2.2.