Search Results cs_service_responsibility




Overview
Explore in AI Chat

Overview

CS_SERVICE_RESPONSIBILITY is a Service (CS) module table in the Oracle E-Business Suite, owned by the CS schema. Its documented purpose is to store Service Request (SR) Type access information whenever service security is enabled. In practice, the table acts as the authorization matrix that determines which responsibilities are permitted to create, view, or update service requests belonging to particular SR Types. When the Service Security profile option is turned on, Oracle Service uses this table to constrain the set of SR Types that a given user, operating through an assigned responsibility, can work with.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table carries a composite primary key (RESPONSIBILITY_ID, APPLICATION_ID) and references descriptive/classification attributes such as ACCESS_TYPE and BUSINESS_USAGE, which behave like satellite attributes describing the relationship context rather than a pure transactional hub. This classification should be treated as a heuristic modeling suggestion, not a mandated design, since the table is a native OLTP entity in the CS schema.

Key Information Stored

The table contains eleven documented columns. The most significant are:

  • RESPONSIBILITY_ID — part of the composite primary key (CS_SERVICE_RESPONSIBILITY_PK) and the identifier of the responsibility granted access.
  • APPLICATION_ID — the second component of the composite primary key, identifying the application that owns the responsibility; foreign key to FND_APPLICATION.
  • ACCESS_TYPE — defines the nature of access granted to the responsibility for the associated SR Type.
  • BUSINESS_USAGE — indicates the business context or usage designation for the access record.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org and security-group scoping.
  • CREATION_DATE, CREATED_BY — standard audit columns recording record creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent change.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle EBS framework.

The surrogate-style primary key is the composite (RESPONSIBILITY_ID, APPLICATION_ID); there is no separate single-column unique index documented, so these two columns together represent the business-key candidates for uniqueness.

Common Use Cases and Queries

The primary use case is administering and auditing service security. Administrators configure SR Type access per responsibility, and developers or support analysts query the table to diagnose why a user cannot see or create a particular SR Type. A typical query joins this table to CS_SR_TYPE_MAPPING to enumerate the SR Types accessible to a responsibility:

  • Determine which SR Types a responsibility can access: select from CS_SERVICE_RESPONSIBILITY joined to CS_SR_TYPE_MAPPING on RESPONSIBILITY_ID and APPLICATION_ID.
  • Validate access configuration: filter by ACCESS_TYPE to list responsibilities with a specific access level.
  • Audit changes: use LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent security modifications.
  • Security-group reporting: join to FND_SECURITY_GROUPS via SECURITY_GROUP_ID for multi-org analysis.
  • Resolve responsibility names: join APPLICATION_ID to FND_APPLICATION and the responsibility to FND_RESPONSIBILITY for readable labels.

Related Objects

The following objects are most significant to this table based on documented FK/PK relationships:

  • CS_SR_TYPE_MAPPING — references CS_SERVICE_RESPONSIBILITY through RESPONSIBILITY_ID and APPLICATION_ID; this is the central join for SR Type access resolution.
  • FND_APPLICATION — referenced by APPLICATION_ID, providing the owning application of each responsibility.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security-group scoping.
  • FND_RESPONSIBILITY — commonly joined for responsibility name and description details.
  • CS_SERVICE_RESPONSIBILITY_PK — the primary key constraint enforcing uniqueness on RESPONSIBILITY_ID and APPLICATION_ID.