Search Results cac_task_rs_extns_sec

Overview

CAC_TASK_RS_EXTNS_SEC is a CRM Foundation (JTF) security view in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes resource-extension data used by the Task Manager and resource scheduling components of CRM Foundation, presenting the columns of the underlying resource-extension table through a secured, reporting-oriented projection. The view is significant because it is one of the primary surfaces through which resource attributes — including the denormalized "source" attributes such as SOURCE_JOB_TITLE — become available to concurrent programs, Discoverer workbooks, OAF pages, and integration extracts.

Because the view name carries the "_SEC" suffix, its intent is to restrict visible rows according to the security context of the querying session. Access is therefore granted only where the resource falls within the caller's security group or resource group. In the database documented by ETRM, this view is recorded as not implemented, meaning the object is delivered by the product's installation scripts but was not created in the specific instance sampled. Implementers upgrading from 12.1.1 to 12.2.2 should validate its existence with a query against ALL_VIEWS before depending on it in custom code.

Underlying Base Objects

The view text is a direct, column-by-column SELECT from a single base table:

• JTF_RS_RESOURCE_EXTNS — the resource-extension table that stores supplemental attributes for records in the JTF_RS_RESOURCE / JTF_RS_RESOURCE_EXTNS resource model.

No joins, unions, or additional source objects are documented in the ETRM metadata: the view is a straight projection with no WHERE clause visible in the stored text. Consequently, the "_SEC" semantics must be enforced either through a synonym/row-level security policy applied to the base table or through the calling application's own WHERE predicates. ETRM lists no other referenced base objects, so dependencies beyond JTF_RS_RESOURCE_EXTNS should not be assumed.

Key Columns

The view exposes the full resource-extension column set. Columns of particular interest include:

• RESOURCE_ID — primary join key back to the resource definition; the anchor for all downstream joins.
• CATEGORY / RESOURCE_NUMBER — classification and human-readable resource identifier.
• SOURCE_ID, SOURCE_NAME, SOURCE_NUMBER, SOURCE_ORG_ID, SOURCE_ORG_NAME — originating record for the resource, commonly a supplier contact, employee, or partner.
• SOURCE_JOB_TITLE — the job title of the source contact or resource, widely used in CRM resource reporting and in agent/queue routing logic.
• SOURCE_EMAIL, SOURCE_PHONE, SOURCE_MOBILE_PHONE, SOURCE_PAGER — contact points propagated from the source record.
• SOURCE_MGR_ID, SOURCE_MGR_NAME, SOURCE_BUSINESS_GRP_ID, SOURCE_BUSINESS_GRP_NAME — supervisory and organizational context.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating for the resource assignment.
• SECURITY_GROUP_ID — the security grouping that governs row visibility.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF columns for client-specific extensions.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY — concurrency and audit columns.

Common Use Cases and Queries

Typical scenarios include resource-directory reporting, agent-skills and job-title analysis, and integration extracts that feed downstream CRM or telephony systems. Because SOURCE_JOB_TITLE is frequently requested, a representative query is:

• SELECT r.resource_id, r.source_name, r.source_job_title, r.source_email FROM cac_task_rs_extns_sec r WHERE r.source_job_title IS NOT NULL AND r.end_date_active IS NULL;
• SELECT category, COUNT(*) FROM cac_task_rs_extns_sec WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active > SYSDATE) GROUP BY category;
• SELECT s.source_org_name, s.source_mgr_name, COUNT(s.resource_id) FROM cac_task_rs_extns_sec s WHERE s.security_group_id = :p_group GROUP BY s.source_org_name, s.source_mgr_name;

When building custom queries, always apply the effective-dating and security-group predicates explicitly, since the documented view text contains neither. If the view is absent (as in the sampled instance), query JTF_RS_RESOURCE_EXTNS directly with the equivalent column list.