Search Results cs_system_options_u1

Overview

CS.CS_SYSTEM_OPTIONS is a Service (CS) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores Service Security Setup information. It functions as the configuration repository for agent-level and responsibility-level security behavior within the Service/TeleService module, defining how service requests, agents, and access policies are constrained at runtime. The table resides in the APPS_TS_SEED tablespace, which is characteristic of seeded setup data rather than high-volume transactional content, and its status is VALID in the ETRM repository. FND Design Data registers it as CS.CS_SYSTEM_OPTIONS.

From a Data Vault modeling perspective, the metadata classifies this object as standalone. This is a heuristic suggestion rather than a mandated design: the table carries its own surrogate primary key and does not participate in a classic hub-and-satellite chain within the documented relationship graph beyond a single outbound dependency on FND_SECURITY_GROUPS. Analysts modeling EBS data into a vault pattern would therefore treat it as an independent reference dimension rather than as a link between business entities.

Key Information Stored

The table's documented physical schema contains 28 columns. The most significant are:

• SYSTEM_OPTION_ID (NUMBER) — the entity identifier and primary key, enforced by constraint CS_SYSTEM_OPTIONS_PK. It is also the leading column of the unique index CS_SYSTEM_OPTIONS_U1.
• SR_AGENT_SECURITY (VARCHAR2, 30) — the service security option governing how agents are validated against service requests.
• SR_SEC_DYNAMIC_POLICY — the dynamic security policy option controlling runtime policy evaluation.
• SS_SRTYPE_RESTRICT — an iSupport security option restricting service request types.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, linking the row to a security group definition.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150 each) — descriptive flexfield segments and their category, available for client-specific extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns providing audit lineage.
• OBJECT_VERSION_NUMBER and ZD_EDITION_NAME — concurrency control and editioning columns, the latter participating in the unique index CS_SYSTEM_OPTIONS_U1 alongside SYSTEM_OPTION_ID.

The surrogate primary key is SYSTEM_OPTION_ID. The documented business-key candidate is the composite unique index CS_SYSTEM_OPTIONS_U1 over (SYSTEM_OPTION_ID, ZD_EDITION_NAME); because ZD_EDITION_NAME is an editioning artifact, SYSTEM_OPTION_ID effectively remains the stable business identifier.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios center on auditing which security posture is active for a given configuration, and on tracing references from downstream modules that point back to this table.

Retrieve the active security configuration:

• SELECT system_option_id, sr_agent_security, sr_sec_dynamic_policy, ss_srtype_restrict, security_group_id FROM cs.cs_system_options;

Inspect client-specific flexfield extensions for a configuration row:

• SELECT system_option_id, attribute_category, attribute1, attribute2 FROM cs.cs_system_options WHERE attribute_category IS NOT NULL;

Trace the security group linkage and audit history:

• SELECT o.system_option_id, g.security_group_name, o.last_update_date, o.last_updated_by FROM cs.cs_system_options o, fnd_security_groups g WHERE o.security_group_id = g.security_group_id;

Identify referencing rows across dependent modules by joining on SYSTEM_OPTION_ID, for example against GCS_SYSTEM_OPTIONS or WIP_PARAMETERS, to determine which subledger or parameter set consumes a given service option.

Related Objects

The documented relationship graph identifies one outbound foreign key and several inbound references:

• FND_SECURITY_GROUPS — referenced by CS_SYSTEM_OPTIONS.SECURITY_GROUP_ID.
• GCS_SYSTEM_OPTIONS — references CS_SYSTEM_OPTIONS.SYSTEM_OPTION_ID.
• WIP_PARAMETERS — references SYSTEM_OPTION_ID, tying service security into Work in Process parameters.
• LNS_SYSTEM_OPTIONS_ALL — references SYSTEM_OPTION_ID from the Loans schema.
• WIP_ACCOUNTING_CLASSES — references SYSTEM_OPTION_ID, linking service security to accounting class derivation.
• FUN_SYSTEM_OPTIONS — references SYSTEM_OPTION_ID from the Financials common schema.

These dependencies indicate that CS_SYSTEM_OPTIONS acts as a shared reference point across Service, Work in Process, Loans, and Financials functionality, and that any change to its seeded rows can propagate into parameter resolution and accounting behavior in those modules.