Search Results source_mgr_name

Overview

CS_JTF_RS_RESOURCE_EXTNS_SEC is a security-enabled view owned by the APPS schema within the Service (CS) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as the "Main resource view that stores all resource data," and functions as the primary read interface through which Oracle Service, Field Service, and related modules expose information about service resources. The suffix "SEC" denotes that this view is designed to enforce row-level security, so that a session only returns resource records the current user is authorized to see based on the resource security model configured for the deployment.

Because the view consolidates identifying, organizational, costing, and contact attributes of a resource into a single projection, it is widely used in reporting, integrations, and concurrent programs that need a flattened, secured representation of resource data. The inclusion of the SOURCE_JOB_TITLE column, along with a full set of SOURCE_* attributes, makes the view particularly valuable when the resource originates from an external source such as an HR or third-party system, since the source-side descriptive fields are preserved alongside the canonical resource identifier.

Underlying Base Objects

The documented definition of CS_JTF_RS_RESOURCE_EXTNS_SEC is a straight projection over a single view:

• JTF_RS_RESOURCE_EXTNS_VL — the base object referenced by the definition.

The query selects from JTF_RS_RESOURCE_EXTNS_VL (aliased B) and returns every documented column, including attributes and the SOURCE_* descriptive fields, without joins, unions, or computed expressions. In practice this means CS_JTF_RS_RESOURCE_EXTNS_SEC inherits the column list and datatypes of the base view and adds the security filtering layer that distinguishes the _SEC view from its non-secured counterparts. Because the base object is itself a view (the _VL designation indicates a translated view with language-dependent columns resolved), the effective lineage traces back to the underlying resource extension tables such as JTF_RS_RESOURCE_EXTNS.

Key Columns

• ROW_ID / RESOURCE_ID — the primary identifier of the resource record and its foreign key to the resource entity.
• RESOURCE_NUMBER / RESOURCE_NAME — the human-readable resource number and name used for display and lookup.
• CATEGORY / SOURCE_CATEGORY / SOURCE_STATUS — classification and lifecycle state of the resource.
• SOURCE_JOB_TITLE — the job title of the resource as recorded at the source; the column most frequently used for filtering and reporting on resource role.
• SOURCE_ID / SOURCE_NAME / SOURCE_NUMBER — identifiers and descriptive name of the originating source record.
• SOURCE_EMAIL / SOURCE_PHONE / SOURCE_MOBILE_PHONE / SOURCE_PAGER — contact details captured from the source system.
• SOURCE_ADDRESS1–4, SOURCE_CITY, SOURCE_STATE, SOURCE_POSTAL_CODE, SOURCE_COUNTRY, SOURCE_OFFICE, SOURCE_LOCATION, SOURCE_MAILSTOP — address and location attributes.
• SOURCE_MGR_ID / SOURCE_MGR_NAME — the resource manager reference.
• SOURCE_ORG_ID / SOURCE_ORG_NAME / SOURCE_BUSINESS_GRP_ID / SOURCE_BUSINESS_GRP_NAME — organizational context of the source.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range of the resource record.
• MANAGING_EMPLOYEE_ID / CONTACT_ID / SUPPORT_SITE_ID / USER_ID — linkage keys to employees, contacts, sites, and application users.
• ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY — the descriptive flexfield columns available for deployment-specific extensions.

Common Use Cases and Queries

A typical reporting requirement is to list active resources by job title, which is the column implied by the search term "source_job_title." The following query returns active resources ordered by job title:

• SELECT resource_id, resource_number, resource_name, source_job_title, source_name, start_date_active, end_date_active FROM cs_jtf_rs_resource_extns_sec WHERE source_job_title IS NOT NULL ORDER BY source_job_title;
• SELECT resource_id, resource_name, source_job_title, source_org_name FROM cs_jtf_rs_resource_extns_sec WHERE category = 'EMPLOYEE';
• SELECT resource_id, resource_name, source_job_title, source_email, source_mgr_name FROM cs_jtf_rs_resource_extns_sec WHERE source_job_title LIKE 'Field%';
• SELECT resource_id, resource_name, source_job_title FROM cs_jtf_rs_resource_extns_sec WHERE source_org_id = :org_id AND trunc(sysdate) BETWEEN start_date_active AND nvl(end_date_active, sysdate);

Because the security predicate is embedded in the view, reports built directly on CS_JTF_RS_RESOURCE_EXTNS_SEC automatically restrict returned resources to those the running user is permitted to view, which is the principal reason integrations and Oracle Service reporting components standardize on the _SEC variant rather than querying the underlying resource extension tables directly.