Search Results source_phone

Overview

CAC_CAL_RESOURCES is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product family and carries a VALID status in the ETRM data dictionary. The view presents a consolidated, calendar-oriented projection of resource (person) information drawn from the CRM/JTF resource foundation. Its purpose is to expose a flattened, denormalized row per resource that combines identity attributes (user and resource identifiers), resource classification, organizational placement, contact details, and standard audit columns.

Because the view name is prefixed "CAC_CAL_", it is associated with calendar and scheduling functionality, where a caller needs a single, stable source of resource records suitable for populating or resolving calendar entries, appointment owners, and resource assignments. Rather than requiring consumers to join resource, user, and extension tables directly, CAC_CAL_RESOURCES returns a ready-to-use projection with a synthesized resource type token, making it convenient for reporting, concurrent programs, and integration extracts that must remain decoupled from the underlying CRM schema.

Underlying Base Objects

The view is defined over a single documented base object: JTF_RS_RESOURCE_EXTNS_VL, itself a view (the "_VL" suffix indicating a translated, language-sensitive view) within the JTF Resource Manager schema. CAC_CAL_RESOURCES selects from this view without joins, aggregations, or filters, so its cardinality and lifecycle are governed entirely by the rows returned by JTF_RS_RESOURCE_EXTNS_VL. No WHERE clause is documented, meaning all active and inactive resources present in the base view are surfaced, with active-date columns available for the consumer to apply its own filtering. The dependency is read-only; the view introduces no base tables of its own and is safe for query-only access.

Key Columns

• USER_ID / USER_NAME — the FND user account associated with the resource, enabling linkage to user-based security and responsibility contexts.
• RESOURCE_ID / RESOURCE_NAME — the primary resource identifier and display name from the resource foundation.
• RESOURCE_TYPE — a derived column formed as 'RS_'||CATEGORY, producing a prefixed type token (for example, RS_<category>) for downstream classification and filtering.
• BUSINESS_GROUP — sourced from SOURCE_BUSINESS_GRP_NAME, indicating the operating business group of the resource.
• JOB_TITLE, PHONE, EMAIL, MANAGER — contact and organizational attributes projected from the corresponding SOURCE_ columns.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that determines whether a resource is currently active.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns supporting traceability and incremental extraction.

Common Use Cases and Queries

Typical scenarios include resolving resource records for calendar and scheduling processing, building resource directories, feeding downstream reporting extracts, and validating resource-to-user mappings. The RESOURCE_TYPE token is particularly useful when consumers must filter resources by category without decoding the base view. The following examples illustrate standard access patterns.

• List currently active resources: SELECT resource_id, resource_name, resource_type, business_group FROM cac_cal_resources WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Retrieve contact details for a named resource: SELECT resource_name, job_title, phone, email, manager FROM cac_cal_resources WHERE resource_name = :p_name;
• Join to FND_USER for security-scoped reporting: SELECT c.resource_name, u.user_name FROM cac_cal_resources c, fnd_user u WHERE c.user_id = u.user_id;
• Incremental extraction by audit trail: SELECT * FROM cac_cal_resources WHERE last_update_date >= :p_since;

Because the view is a thin projection of JTF_RS_RESOURCE_EXTNS_VL, query performance is governed by that base view; consumers should apply the START_DATE_ACTIVE/END_DATE_ACTIVE predicates and, where relevant, the RESOURCE_TYPE token to limit result sets.