Search Results use_comm_services

Overview

APPS.CS_SYSTEM_PARAMETERS is a valid Oracle E-Business Suite view in the Service (CS) product family. It exposes the implementation options that govern the behavior of Oracle Service across a given operating unit and business group. Because Service functionality is highly configurable, these parameters determine operational rules such as whether systems may be created automatically, whether a service contract is mandatory, whether partial product specifications are permitted, and which service-related events are audited.

From a reporting and integration standpoint, the view is the operational (run-time) face of the setup data held in the underlying table. The WHERE clause applies an organization-level filter using USERENV('CLIENT_INFO'), comparing the first ten characters of the client information string against ORG_ID, with a sentinel value of -99 when no organization is set. This means queries executed through the standard EBS application context return only the parameter row for the currently selected operating unit, while a null client-info value falls back to the sentinel comparison. Developers integrating with Service or building custom reports therefore treat this view as the authoritative, multi-org-secured source for Service system parameters.

Underlying Base Objects

The documented metadata identifies a single referenced base object: the synonym CS_SYSTEM_PARAMETERS_ALL. The view is defined as a direct projection of that table, selecting every functional column plus the standard EBS WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN). The _ALL suffix on the base object confirms that the table stores parameters for all operating units, spanning the multi-org model. The view narrows that full set to the active organization through the ORG_ID predicate described above. No joins, aggregations, or derived columns are introduced, so column-level characteristics such as data type and length are inherited directly from the base table.

Key Columns

• ORG_ID and BUSINESS_GROUP_ID — identify the operating unit and business group context of the parameter row and drive the view's filtering logic.
• SYSTEM_TYPE_CODE — classifies the system configuration type used by Service; this is the column most frequently referenced when distinguishing parameter sets.
• SERVICE_ENTITY_ID — links the parameters to the service entity (for example, a service organization) they apply to.
• CREATE_SYSTEMS_FLAG, REQUIRE_SERVICE_CONTRACT_FLAG, PARTIAL_PRODUCT_SPEC_FLAG — core behavioral switches controlling system creation, contract enforcement, and product specification tolerance.
• MANUFACTURING_ORG_ID — the manufacturing organization associated with service processing.
• AUDIT_FLAG and the AUDIT_*_FLAG family — control whether changes to service entities, incident status, type, urgency, severity, responsible group, owner, inventory item, component item, expected resolution date, and expected revision are written to the audit trail.
• USE_ACCESS_CONTROL_FLAG and ACCESS_TEMPLATE_ENTITY_CODE — govern access control behavior and the template entity applied.
• USE_DEPOT_REPAIR_FLAG, USE_CONTRACTS_FLAG, USE_MOBILE_FLD_SRV_FLAG, USE_CUSTOMER_CARE, USE_COMM_SERVICES — feature enablement flags affecting depot repair, contracts, mobile field service, customer care, and communications services.
• WHO columns and ATTRIBUTE1–ATTRIBUTE15 plus CONTEXT — provide standard audit stamping and descriptive flexfield support.

Common Use Cases and Queries

Typical scenarios include verifying Service setup for a given operating unit, auditing which behaviors are enabled before an upgrade or configuration change, and joining parameter values to incident or contract logic in custom reporting.

To inspect all parameters for the current operating unit:

SELECT org_id, system_type_code, create_systems_flag, require_service_contract_flag, audit_flag FROM apps.cs_system_parameters;

To review audit-related configuration:

SELECT org_id, audit_service_entity_flag, audit_incident_status_flag, audit_incident_owner_flag FROM apps.cs_system_parameters;

Because the view is organization-secured, cross-organization comparisons generally require querying the base synonym CS_SYSTEM_PARAMETERS_ALL directly rather than the view.