Results for “cac_task_rs_teams_sec”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CAC_TASK_RS_TEAMS_SEC is a security-aware database view belonging to the JTF – CRM Foundation product family within Oracle E-Business Suite. It exposes team definition data drawn from the Resource Manager schema, presenting a curated column list that includes standard WHO audit columns, team descriptors, and the security-related attributes required for row-level access control. The view is used primarily in reporting and integration contexts where CRM task assignments, resource teams, and territory-related team structures must be queried without directly touching the underlying transactional table.
The "_SEC" suffix indicates that this view is a security variant. Views of this type typically apply a security predicate or expose SECURITY_GROUP_ID so that only teams visible to the current operating unit or security profile are returned. This makes the view suitable for concurrent programs, Oracle Reports, OAF-based pages, and custom SQL that must enforce multi-org or CRM security semantics.
Underlying Base Objects
Per the documented view text, CAC_TASK_RS_TEAMS_SEC is defined over a single base object: JTF_RS_TEAMS_B. No additional tables, joins, or inline subqueries appear in the documented definition. The ETRM metadata records no other referenced base objects and notes that the view is "Not implemented in this database" in the source environment, meaning the definition is supplied for reference and may be created selectively depending on the module configuration.
JTF_RS_TEAMS_B is the base table for resource teams in CRM Foundation. It stores team headers used by Resource Manager and related modules such as Tasks, Territories, and Sales. Because the view performs a straightforward projection with no joins, it inherits the row cardinality and partitioning behavior of the base table, and updates directed through the view would map back to that table where key-preserved.
Key Columns
- TEAM_ID – Primary identifier for the team; the primary key of JTF_RS_TEAMS_B.
- TEAM_NUMBER – User-facing team number or code used for lookup and reporting.
- EXCLUSIVE_FLAG – Indicates whether a resource may belong exclusively to this team.
- START_DATE_ACTIVE / END_DATE_ACTIVE – Effective dating range controlling the active window of the team.
- EMAIL_ADDRESS – Contact email associated with the team header.
- OBJECT_VERSION_NUMBER – Optimistic locking column used by the framework for concurrent updates.
- SECURITY_GROUP_ID – Security grouping used by CRM row-level security to isolate data across groups or operating units.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield context and segment values.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.
Common Use Cases and Queries
Typical scenarios include reporting on active teams for a given security group, validating team effective dates before assignment, and exporting team headers to downstream systems. Because the view adds the security dimension, it is commonly used in CRM dashboards and in Resource Manager inquiries where the operating user must only see teams within their security context.
Sample query listing active teams:
SELECT team_id, team_number, email_address,
start_date_active, end_date_active
FROM cac_task_rs_teams_sec
WHERE exclusive_flag = 'Y'
AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
AND NVL(end_date_active, SYSDATE + 1);
Sample query joining to assignments by security group:
SELECT t.team_id, t.team_number, a.resource_id
FROM cac_task_rs_teams_sec t,
jtf_rs_team_members a
WHERE t.team_id = a.team_id
AND t.security_group_id = :p_security_group;
When querying, note that no filters beyond those in the view definition are applied automatically; consumers must still supply effective-date and security-group predicates appropriate to their reporting requirement. Performance is generally equivalent to a base-table scan with an index on TEAM_ID or TEAM_NUMBER.
-
View: CAC_TASK_RS_TEAMS_SEC 12.1.1
Not implemented in this database·Explore JTF module →
-
View: CAC_TASK_RS_TEAMS_SEC 12.2.2
Not implemented in this database·Explore JTF module →
-
VIEW: JTF.JTF_RS_TEAMS_B# 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
TABLE: JTF.JTF_RS_TEAMS_B 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel