Results for “csr_spares_source”

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

Overview

CSR_RULES_TRANSLATED_V is a reporting view owned by the APPS schema in Oracle EBS. It is part of the CSR (Scheduler) product family and presents scheduling rule definitions from the underlying rule tables in a fully translated, display-ready form. The view is documented in ETRM 12.2.2 and is valid in both EBS 12.1.1 and 12.2.2.

The view's primary purpose is to resolve code values into user-visible meanings. It wraps CSR_RULES_TL (the translatable rule table) and joins to FND_APPLICATION_TL, FND_RESPONSIBILITY_TL, FND_USER, JTF_TERR_ALL, JTF_RS_ALL_RESOURCES_VL, and JTF_OBJECTS_VL so that application, responsibility, user, territory, resource, and resource-type identifiers are returned as names rather than numeric IDs. In addition, numerous columns — such as ENABLED_FLAG, SP_ENFORCE_PLAN_WINDOW, SP_SPARES_SOURCE, and the various SP_PICK_* flags — are decoded using scalar subqueries against FND_LOOKUPS, with LOOKUP_TYPE values including YES_NO, CSR_ENFORCE_PLAN_WINDOW, CSR_CONSIDER_STANDBY_SHIFTS, and CSR_SPARES_SOURCE.

Because it surfaces translated meanings, the view is suited to operational reports, BI Publisher data models, and integration extracts where downstream consumers require human-readable rule metadata rather than raw lookup codes. The lookup_type construct is central to its design: many columns are effectively driven by FND_LOOKUPS filtering on a specific LOOKUP_TYPE.

Underlying Base Objects

The documented base objects for the view are: CSR_RULES_TL and CSR_RULES_EXPLODED_V, CSF_DC_QUERIES_VL, FND_APPLICATION_TL, FND_GLOBAL, FND_LOOKUPS, FND_RESPONSIBILITY_TL, FND_USER, HR_GENERAL, HR_SECURITY, JTF_OBJECTS_VL, JTF_RS_ALL_RESOURCES_VL, JTF_TASK_STATUSES_VL, JTF_TERR_ALL, and the collection type WINDOW1532_COLL.

• CSR_RULES_TL — the primary rule table supplying rule name, description, rank, planning scope, and the SP_* scheduling parameters.
• CSR_RULES_EXPLODED_V — supplies the exploded rule structure referenced by the view.
• FND_LOOKUPS — the source of all decoded meaning columns, filtered by LOOKUP_TYPE and LOOKUP_CODE.
• FND_APPLICATION_TL, FND_RESPONSIBILITY_TL, FND_USER — resolve ownership and security context to names.
• JTF_TERR_ALL, JTF_RS_ALL_RESOURCES_VL, JTF_OBJECTS_VL — resolve territory, resource, and resource-type names.
• FND_GLOBAL, HR_GENERAL, HR_SECURITY — provide session and security context used during query execution.
• WINDOW1532_COLL — a collection type used internally in the view's SQL.

Key Columns

• RULE_ID, OBJECT_VERSION_NUMBER — primary key and optimistic locking column for each rule.
• RULE_NAME, DESCRIPTION, BASE_RULE_NAME — rule identity and its base rule reference.
• APPLICATION_NAME, RESPONSIBILITY_NAME, USER_NAME — resolved ownership context.
• TERRITORY_NAME, RESOURCE_NAME, RESOURCE_TYPE_NAME — resolved territory, resource, and object type.
• ENABLED_FLAG — decoded via LOOKUP_TYPE = 'YES_NO', normalizing the enabled status to Y/N.
• RULE_RANK — priority ranking used by the scheduler.
• SP_PLAN_SCOPE, SP_MAX_PLAN_OPTIONS, SP_MAX_RESOURCES, SP_MAX_CALC_TIME, SP_MAX_OVERTIME, SP_WTP_THRESHOLD — core scheduling planning parameters.
• SP_ENFORCE_PLAN_WINDOW, SP_CONSIDER_STANDBY_SHIFTS, SP_SPARES_SOURCE — decoded via their respective CSR_* LOOKUP_TYPE values.
• SP_SPARES_MANDATORY, SP_DIST_LAST_CHILD_EFFORT, SP_PICK_CONTRACT_RESOURCES, SP_PICK_IB_RESOURCES, SP_PICK_TERRITORY_RESOURCES — boolean flags decoded via LOOKUP_TYPE = 'YES_NO'.
• SP_MIN_TASK_LENGTH, SP_DEFAULT_SHIFT_DURATION — numeric scheduling constraints.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard auditing columns.

Common Use Cases and Queries

Typical scenarios include reviewing which rules are enabled, auditing scheduling parameters, and feeding rule data into planning dashboards. The following query retrieves enabled rules with their decoded planning flags:

• SELECT RULE_ID, RULE_NAME, ENABLED_FLAG, SP_ENFORCE_PLAN_WINDOW, SP_PICK_CONTRACT_RESOURCES FROM APPS.CSR_RULES_TRANSLATED_V WHERE ENABLED_FLAG = 'Y' ORDER BY RULE_RANK;
• SELECT RULE_NAME, RESOURCE_TYPE_NAME, SP_SPARES_SOURCE, SP_SPARES_MANDATORY FROM APPS.CSR_RULES_TRANSLATED_V WHERE SP_SPARES_MANDATORY = 'Y';
• SELECT RULE_NAME, TERRITORY_NAME, SP_MAX_RESOURCES, SP_MAX_OVERTIME FROM APPS.CSR_RULES_TRANSLATED_V WHERE TERRITORY_NAME IS NOT NULL;

Because decoded columns are sourced from FND_LOOKUPS, filtering on the translated meanings (for example, SP_ENFORCE_PLAN_WINDOW = 'Yes') is preferred over comparing raw codes. Joining this view back to CSR_RULES_TL on RULE_ID allows access to any code columns not exposed by the view itself.