[2024年06月] 100%合格 SAP C-C4H56I-34 試験一発合格保証! [Q12-Q26]

When rolling out SAP Service Cloud Version 2 to multiple countries, it is essential to “Enable country/region” to ensure that the system is tailored to the specific regulatory, linguistic, and cultural requirements of each country. This involves configuring country-specific settings, such as local currencies, date formats, and legal regulations. Additionally, “Maintaining organizational units” for each different country is crucial. This involves setting up the organizational structure, including departments, divisions, and teams, in a way that reflects the operational and management structure in each country. This ensures that the system aligns with local business practices and organizational hierarchies.

In determining the reaction time for Service Level Agreements (SLAs) within SAP Service Cloud Version 2,
“Priority” and “Case types” are key elements. The priority assigned to a case can directly influence the reaction time, with higher priority cases typically requiring faster response times. Case types also play a crucial role, as different types of cases may have varying levels of urgency and complexity, which can affect the expected reaction time. These elements help in setting appropriate response expectations and ensuring that cases are handled according to their significance and requirements.

Existing Cases can be changed, but only by executing the action “Create New Version” from the existing Case Type that has to be modified. For example, if after creating a new Case Type, the Administrator realizes that the Service Catalog is missing, they will have to execute the action Create New Version from the existing Case Type, then enter the service catalog and activate the new version. References = Creating a Case Type

According to the SAP Service Cloud Version 2 documents and learning resources, you can do the following things with Agent Desktop in SAP Service Cloud Version 2:
Create accounts and contacts. Agent Desktop allows you to create and maintain master data for accounts and contacts, which are essential for managing customer relationships and service requests. You can also view and edit the account hierarchy, the contact roles, and the communication preferences of the accounts and contacts.
Use a mashup to execute transactions in other SAP solutions. Agent Desktop enables you to integrate with other SAP solutions, such as SAP S/4HANA Service, SAP Field Service Management, or SAP Marketing Cloud, by using mashups. Mashups are web pages that are embedded in the Agent Desktop and can pass input parameters from the service objects, such as cases, tickets, or registered products, to the external solutions. You can use mashups to perform actions in the external solutions, such as creating a service order, scheduling a service appointment, or launching a marketing campaign, without leaving the Agent Desktop.
The other options are not correct because:
Creating installed bases is not possible with Agent Desktop in SAP Service Cloud Version 2. Installed bases are collections of products that are installed at a customer site and require service or maintenance.
Installed bases are created and managed in the Installed Base work center, which is not part of the Agent Desktop.
Assigning products to existing accounts is not possible with Agent Desktop in SAP Service Cloud Version 2. Products are items that are sold or serviced by your company, and they can be assigned to accounts or contacts as attributes. Products are assigned and maintained in the Products work center, which is not part of the Agent Desktop. References = Introducing Agent Desktop in SAP Service Cloud Version 2, Using Agent Desktop with SAP Service Cloud, Description SAP Service Cloud Version 2 Feature Scope, Agent Console Add-On for SAP Service Cloud Agent Desktop in SAP Service Cloud Version 2 is a versatile tool that enables service agents to perform a variety of tasks efficiently. Among its capabilities, creating accounts and contacts directly from the interface stands out as a fundamental feature, allowing agents to manage customer information seamlessly.
Additionally, the Agent Desktop supports the use of mashups, which are integrations with external applications or web content. These mashups enable agents to execute transactions or access data in other SAP solutions without leaving the Agent Desktop environment, thereby enhancing productivity and providing a unified user experience

In SAP Service Cloud Version 2, there are three types of account to choose from: business or company customer (referred to as Account), individual customer, and contact. Contacts are associated with accounts and can have different roles, such as decision maker, influencer, or end user. Individual customers are accounts that represent a single person, such as a consumer or a sole proprietor. Channel partners are not a separate account type, but a role that can be assigned to an account. Groups are not an account type, but a way to organize accounts into categories, such as industry, region, or segment. References = Creating Customer Account Master Data, SAP Service Cloud Version 2 Feature Scope Description

The Entities facet of the Customer Hub screen can display the following objects: Cases, Registered Products, Installed Bases, and Service Contracts. These objects are related to the customer and can provide useful information for service agents. Cases are requests for support that contain details about the customer issue and the resolution process. Registered Products are items that the customer has purchased or registered with the company. Installed Bases are collections of registered products that are installed at a specific location. Service Contracts are agreements that define the terms and conditions of the service delivery for the customer. References = Creating a Case Type, Explaining the Support for the Customer Service Process

For Service Level Agreements (SLAs) to be correctly derived in cases within SAP Service Cloud Version 2, they need to be properly configured and activated. A common reason for SLAs not being derived could be that they have not been configured in the fine-tuning settings of the system. This setup is crucial for defining the SLAs’ parameters and how they apply to various cases. Another potential issue could be that the determination rules, although configured, were not activated. These rules are essential for the system to automatically apply the correct SLA based on the case’s attributes. Without activation, the system cannot utilize these rules to determine and apply SLAs to cases.

Case routing in SAP Service Cloud Version 2 is a mechanism that automatically directs incoming cases to the appropriate service teams or individuals based on predefined criteria. The “Service Category” is one of the primary criteria used in case routing. It categorizes cases based on the nature of the inquiry or issue, ensuring that they are directed to the team with the relevant expertise. Additionally, the “Service Team” is determined during case routing, which involves assigning cases to specific groups of service agents or teams who are equipped to handle them. This ensures that cases are managed by the most suitable and knowledgeable personnel, facilitating efficient resolution.

To integrate external systems into Agent Desktop, you need to have SAP Event Mesh and SAP Cloud Integration as prerequisites. SAP Event Mesh is a cloud-based event bus that enables applications to communicate with each other using events. SAP Cloud Integration is a cloud-based integration platform that allows you to connect your applications with other SAP and non-SAP cloud and on-premise applications.
These components enable you to create mashups that integrate external system functions into Agent Desktop, such as creating service orders and service quotations in SAP S/4HANA or SAP S/4HANA Cloud Service Management. References = Integrate External SAP Systems into Agent Desktop with Mashups | SAP Help Portal, Introducing Agent Desktop in SAP Service Cloud Version 2 – openSAP Microlearning

According to the SAP Service Cloud Version 2 learning resources, to enable service agents to access and perform actions in an external solution, such as SAP S/4HANA Service, from a specific case type, the administrator has to do the following steps:
Create a mashup to embed the web page of the external solution. A mashup is a way to integrate data or functionality from another web application into SAP Service Cloud Version 2. The mashup can be configured to pass input parameters from the case to the external solution, such as the case ID, the account ID, or the product ID.
Use the web page URL of the external solution for extracting input parameters in the mashup. The web page URL of the external solution is the source of the mashup, and it can be used to define the input parameters that the mashup will send to the external solution. For example, if the web page URL of the external solution is https://s4hana-service.com/create-order?caseId={caseId}&accountId={accountId}, then the mashup can use the placeholders {caseId} and {accountId} to extract the values from the case and pass them to the external solution.
Include a dedicated step pointing to the mashup in one of the phases of the case type. A case type is a template that defines the phases and steps that a case goes through from creation to closure. A step is a specific action that a service agent can perform on a case, such as sending an email, creating a task, or launching a mashup. By including a dedicated step pointing to the mashup in one of the phases of the case type, the administrator can enable the service agents to access the external solution from the case screen.
The other options are not correct because:
Developing a custom business object is not necessary to access an external solution from a case type. A custom business object is a way to extend the data model of SAP Service Cloud Version 2 by creating new entities and fields that are not available in the standard solution.
Defining a custom screen for the mashup is not required to access an external solution from a case type.
A custom screen is a way to create a new user interface for a custom business object or a standard business object that has been extended with custom fields. A mashup does not need a custom screen, as it uses the web page of the external solution as its user interface. References = Integrating SAP Customer Service, Service Operations and Field Service, Solution Guide for SAP Service Cloud Version
2