C_C4H56I_34 Sample Questions Answers

 In SAP Service Cloud Version 2, "Installed Base" and "Measurements" are two of the services that can be added to a business role. The Installed Base service allows for the management and tracking of a customer's installed products or equipment, enabling service agents to have a comprehensive view of the customer's assets for better service and support. The Measurements service, on the other hand, enables the tracking and recording of various metrics or performance indicators related to the installed base or service processes. This service is crucial for monitoring performance, ensuring quality, and making informed decisions based on empirical data.

According to the SAP Service Cloud Version 2 documents and learning resources, the following are required to grant business user access:

• User ID. A user ID is a unique identifier for a business user, which is used to log on to the system and to assign a business role. A user ID can be created manually or automatically, and it can be based on the employee ID, the email address, or a custom format.
• Employee. An employee is a master data object that represents a person who works for your company and performs a specific role or function. An employee can be assigned to one or more organizational units, and can have one or more business users associated with them.

The other options are not correct because:

• Access restriction. Access restriction is a way to control the visibility and editability of data for business users based on their business roles and organizational assignments. Access restriction is not required to grant business user access, but it can be used to refine the access level after the business user is created and assigned a business role.
• Assignment to an organizational unit. An organizational unit is a master data object that represents a structural element of your company, such as a department, a team, or a branch. An organizational unit can be assigned to one or more employees, and can be used as an attribute for access restriction. Assignment to an organizational unit is not required to grant business user access, but it can be used to define the scope of the business user’s responsibility and visibility. References = Creating Business Users and Business Roles, Creating Business Roles, Set Up Guide for SAP Service Cloud Version 2, SAP Service Cloud Version 2 | SAP Help Portal

To give service agents access to knowledge base articles in SAP Service Cloud Version 2, administrators need to perform specific configurations within the system. This involves maintaining the settings for the knowledge base provider, which could be an internal solution or a third-party service integrated with SAP Service Cloud. By properly configuring these settings, the system can connect to the knowledge repository and retrieve relevant articles. Additionally, setting up the knowledge base articles within SAP Service Cloud is essential. This setup includes defining article structures, content, and access permissions to ensure that agents can efficiently find and utilize the information to assist customers, thereby enhancing the quality and speed of service

 According to the SAP Service Cloud Version 2 documents and learning resources, the following actions can be executed by a Service Agent from the case “More Action” button:

• Summary. This action allows the Service Agent to create a summary of the case, which is a concise and informative description of the case details, such as the subject, the priority, the status, the category, the resolution, and the next steps. The summary can be used to communicate the case progress to the customer or to other stakeholders.
• Mark as unread. This action allows the Service Agent to mark the case as unread, which means that the case will appear as new in the Agent Desktop and will require the Service Agent’s attention. This action can be used to remind the Service Agent to follow up on the case or to delegate the case to another Service Agent.
• Escalate. This action allows the Service Agent to escalate the case to a higher level of authority or expertise, such as a manager or a specialist. The escalation can be triggered manually by the Service Agent or automatically by the system based on predefined criteria, such as the case priority, the SLA, or the customer satisfaction. The escalation can also involve sending notifications, changing the case status, or reassigning the case to another team or employee.

The other options are not correct because:

• Delete. This action is not available from the case “More Action” button. Deleting a case is a permanent action that removes the case and all its related data from the system. Deleting a case can only be done by an administrator or a user with the appropriate authorization in the Cases work center.
• Handover. This action is not available from the case “More Action” button. Handing over a case is a temporary action that transfers the ownership and responsibility of the case to another Service Agent for a specific period of time. Handing over a case can be done by the Service Agent or by the system based on predefined rules in the Settings > Cases > Case Handover view. References = Using Agent Desktop with SAP Service Cloud, Creating a Case Type, Configuring Case Escalation, Configuring Case Handover

In SAP Service Cloud Version 2, you can use case routing rules to automatically assign cases to a team or a responsible employee based on various attributes of the case, such as subject, priority, channel, or category. You can also use master data such as account, contact, product, or organization as attributes for case routing rules. However, account hierarchy is not a valid attribute for case routing, as it is not a master data object but a relationship between accounts. Contact is also not a valid attribute for case routing, as it is not directly related to the case but to the account or individual customer. References = Configuring Case Routing Rules, Master Data

When you create or edit an installed base, you can assign different objects to it at item level. The objects that you can assign are:

• Product: This is a generic product that is not serialized or tracked individually. You can assign a product to an installed base to indicate the type or category of the product that is installed at the customer site. For example, you can assign a product called “Laptop” to an installed base to represent any laptop that belongs to that installed base.
• Registered product: This is a serialized product that has a unique identifier and can be tracked individually. You can assign a registered product to an installed base to indicate the specific product that is installed at the customer site. For example, you can assign a registered product with a serial number “123456789” to an installed base to represent a particular laptop that belongs to that installed base. A registered product can also have warranty and maintenance plan information associated with it.
• Functional location: This is a logical or physical location where the products are installed or used. You can assign a functional location to an installed base to create a hierarchical structure of the installed base. For example, you can assign a functional location called “Office A” to an installed base to represent a sub-location within the installed base where some products are located. A functional location can also have other functional locations, products, or registered products assigned to it as sub-items.
• Maintenance plan: This is a plan that defines the schedule and scope of the maintenance activities for the products. You cannot assign a maintenance plan to an installed base at item level. A maintenance plan can only be assigned to a registered product as a sub-item. For example, you can assign a maintenance plan called “Annual Service” to a registered product to indicate the frequency and type of service that the product requires.
• Warranty: This is a contract that defines the terms and conditions of the warranty coverage for the products. You cannot assign a warranty to an installed base at item level. A warranty can only be assigned to a registered product as a sub-item. For example, you can assign a warranty called “Standard Warranty” to a registered product to indicate the duration and scope of the warranty that the product has. References = Using an Installed Base; Using Installed Bases and Registered Products

To create a registered product in SAP Service Cloud Version 2, you need the following objects:

• Product: This is the generic definition of the product that you want to register. It contains the basic information such as the name, description, category, and price of the product. You can create products in the Products work center, under the Products view.
• Customer: This is the individual or organization that owns the registered product. It can be either an account or an individual customer. You can create customers in the Customers work center, under the Accounts or Individual Customers view.

The other objects are not mandatory for creating a registered product, but they can be used to provide additional information or functionality. For example:

• Installed base: This is a collection of registered products that belong to the same customer and are located at the same site. It can be used to group and manage related registered products more easily. You can create installed bases in the Installed Base work center, under the Installed Base view.
• Contract: This is an agreement between the customer and the service provider that defines the terms and conditions of the service delivery. It can be used to determine the service entitlements and pricing for the registered product. You can create contracts in the Contracts work center, under the Contracts view.

References =

• Creating a Registered Product - SAP Learning, slide 3-4
• Solution Guide for SAP Service Cloud Version 2, page 31-32

 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

To control the access rights of a user, you can use the following options:

• Assign employee to organizational unit: By assigning an employee to an organizational unit, you can define the scope and responsibility of the user within the organizational structure. The organizational unit determines the access rights of the user to the data and transactions related to that unit, such as cases, service orders, contracts, and products. For example, you can assign a service agent to a specific service team or region, and restrict their access to the cases assigned to that team or region.
• Assign restriction rules: By assigning restriction rules to a business role, you can further limit the access rights of the user to the data and transactions based on certain criteria, such as status, priority, category, or territory. Restriction rules can be applied to read and write access, and can be defined for different business objects, such as cases, service orders, contracts, and products. For example, you can assign a restriction rule to a business role that allows the user to read only the cases with high priority, or to write only the cases with open status.

References = Setting up user access rights and restrictions, Org Structure

To control the access rights of a user in SAP Service Cloud Version 2, one can "Assign an employee to an organizational unit," which sets the user's access level based on their role within the organizational structure. This ensures that users have access only to the information and functions relevant to their position. Another method is to "Assign restriction rules," which allows for the specification of detailed access controls based on various criteria, further refining what users can see and do within the system, ensuring data security and compliance with business policies.

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 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

To utilize registered products, you need to activate the service in the business role and create an installed base. The service activation enables you to access the registered products work center view and perform actions such as creating, editing, and deleting registered products. The installed base is a hierarchical structure that represents the customer’s physical or logical assets, such as equipment, software, or services. You can assign registered products to an installed base to track their location, status, and warranty information. References = Solution Guide for SAP Service Cloud Version 2, section “Registered Products” and “Installed Base”

A determination is a rule that assigns a value to a field based on the value of another field or a calculation. For example, you can create a determination that sets the priority of a case based on the urgency and impact fields. A page layout, a workflow, and an autoflow are not used for field calculations. References = [Solution Guide for SAP Service Cloud Version 2 - SAP Online Help], [SAP Service Cloud Version 2 Feature Scope]

The Timeline tabstrip in the Customer Hub of SAP Service Cloud Version 2 is designed to provide a chronological view of significant interactions and milestones related to a customer. Among the various objects that can be displayed in this timeline, Cases and Contracts are pivotal. Cases represent individual customer inquiries or issues that have been logged, tracked, and resolved over time. Contracts, on the other hand, document the formal agreements between the service provider and the customer, outlining the scope of services, terms, and conditions. These elements are crucial for a comprehensive view of the customer's history, enabling service agents to deliver informed, contextual, and efficient support

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.

In SAP Service Cloud Version 2, you use categories to capture and organize the services that your company wants to offer to create a hierarchical structure called a catalog. SAP Service Cloud Version 2 also uses the service categories that you create as attributes for Cases and Registered Products, meaning that you can have the system automatically match and direct incoming service requests (Cases) to the specific services in your catalog and supporting service teams. You can also maintain the service category determinations of Cases and Registered Products currently in process. References = Configuring Categories, Solution Guide for SAP Service Cloud Version 2

To control the reaction times of a case, you could take the following actions:

• Change the priority: The priority of a case determines the urgency and importance of resolving it. By changing the priority, you can affect the due date, next response date, and completion date of the case, as well as the visibility and notification of the case. For example, you can increase the priority of a case if the customer issue is critical or time-sensitive, or decrease the priority if the issue is minor or low-impact.
• Adjust the SLA: The SLA (Service Level Agreement) of a case defines the initial response and completion due time and date for the resolution of issues, based on the service level objectives (SLOs) agreed with the customer. By adjusting the SLA, you can modify the expected reaction times of the case, as well as the consequences of missing the deadlines. For example, you can extend the SLA of a case if the issue is complex or requires more investigation, or shorten the SLA if the issue is simple or urgent.
• Escalate the case: Escalating a case means raising the attention and priority of the case to a higher level of authority or responsibility. By escalating a case, you can involve more senior or specialized agents, managers, or experts to handle the case, as well as notify the customer and other stakeholders of the escalation. For example, you can escalate a case if the issue is beyond your scope or expertise, or if the customer is dissatisfied or angry.

References = Configuring a Service Level Agreement, Configuring Case Routing Rules, SAP Service Cloud Version 2 Feature Scope

Routing is the feature that can help with automatically assigning employees to a case based on relevant attributes, such as channel, subject, priority, or account. Routing rules enable companies to handle a high volume of messages and deliver the case to the right team or person. SAP Service Cloud Version 2 includes a flexible, easy-to-configure routing rule definition engine1.

Escalation, prioritization settings, and process for cases are not features that can help with automatic case assignment. Escalation is a feature that allows agents or managers to escalate a case to a higher level of authority or expertise when needed2. Prioritization settings are a feature that allows administrators to define how cases are prioritized based on urgency and impact3. Process for cases is a feature that allows administrators to define the steps and tasks that need to be completed for a case based on its type and category4.

References = 1: Configuring Case Routing Rules - SAP Learning, 2: Escalation - SAP Online Help, 3: Prioritization Settings - SAP Online Help, 4: Process for Cases - SAP Online Help

• Option A is correct because the administrator must obtain API token credentials from the CTI provider in order to configure the phone integration in Agent Desktop1.
• Option D is correct because the administrator must integrate with a third-party CTI provider in order to enable the phone channel in Agent Desktop2. SAP Service Cloud Version 2 doesnot have native CTI, so a CTI widget adapter is used to connect the CTI provider with the Agent Desktop3.
• Option B is incorrect because the administrator does not need to add a mashup service in Agent Desktop to enable the phone channel. A mashup service is used to integrate external applications or web pages into the Agent Desktop, but it is not required for the phone channel.
• Option C is incorrect because the administrator does not need to add the phone channel to the live interaction widget to enable the phone channel. The live interaction widget is used to display the incoming and ongoing interactions from various channels, but it does not control the activation of the phone channel. References =
• Configuring Phone - SAP Learning
• SAP Service Cloud Version 2 Integration - Sinch
• Agent Console Add-On for SAP Service Cloud - SAP Online Help
• [Mashup Services - SAP Online Help]
• [Live Interaction Widget - SAP Online Help]

Enabling the phone channel in Agent Desktop within SAP Service Cloud Version 2 requires integration with external telephony solutions to facilitate voice communication capabilities. This integration is achieved through collaboration with a Computer Telephony Integration (CTI) provider. The essential steps involve obtaining API token credentials from the chosen CTI provider, which are necessary for authenticating and establishing a secure connection between the SAP Service Cloud and the telephony system. Additionally, the integration process involves configuring the necessary settings and parameters within the Agent Desktop to ensure seamless communication flow and functionality, leveraging the capabilities and services offered by the CTI provider

 You can assign maintenance plans and registered products to an installed base. A maintenance plan defines the schedule and scope of service activities for an installed base or a registered product. A registered product is an instance of a product that is associated with a specific customer. You can create and assign maintenance plans and registered products using the Installed Base work center. References = Using an Installed Base, page 4 and 7.

When you create a user in SAP Service Cloud Version 2, you can assign two objects: a business role and an employee role. A business role defines the access rights and the user interface layout for a user. An employee role defines the organizational unit and the reporting line for a user. You cannot assign a security policy or a user profile when you create a user. A security policy defines the password rules and the login restrictions for a user. A user profile defines the personal settings and preferences for a user. These objects are either assigned automatically or configured by the user themselves. References = Creating Business Roles; Set Up Guide for SAP Service Cloud Version 2, page 9