C_C4H56I_34 SAP Certified Application Associate - SAP Service Cloud Version 2 Questions and Answers

According to the SAP Service Cloud Version 2 documents and learning resources, you can use the following options to automatically assign an employee or team to a case:

• Set up rule(s) for case routing to employees. You can configure case routing rules to assign cases to specific employees 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. You can maintain case routing rules for employees in the Settings > Cases > Case Routing to Employees view.
• Set up rule(s) for case routing to teams. You can also configure case routing rules to assign cases to teams based on the same attributes as for employees. You can maintain case routing rules for teams in the Settings > Cases > Case Routing to Team view.

The other options are not correct because:

• Define case types and assign responsible teams and employees. You can define case types to model different types of service workflows based on your business processes. You can add phases, steps, approvals, and automated flows to each case type. However, defining case types and assigning responsible teams and employees does not automatically assign an employee or team to a case. You still need to set up case routing rules to do that.
• Set up rules with BRF+. BRF+ is a tool that allows you to create and maintain business rules in a graphical user interface. You can use BRF+ to define complex rules for various scenarios, such as pricing, output management, or workflow. However, BRF+ is not used to automatically assign an employee or team to a case in SAP Service Cloud Version 2. You need to use case routing rules for that purpose. References = Configuring Case Routing Rules, Creating a Case Type, Business Rule Framework plus (BRFplus)

 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.

Autoflow is a feature that allows you to define rules that trigger actions based on certain conditions and events. You can configure three types of actions for autoflow: send info notifications, send e-mails, and send event notifications. Send info notifications are messages that appear in the user interface of SAP Service Cloud Version 2 to inform users about the status of a process or an entity. Send e-mails are messages that are sent to external recipients, such as customers or partners, using predefined e-mail templates. Send event notifications are messages that are sent to integrated solutions, such as SAP Marketing Cloud or SAP Sales Cloud, using predefined event templates. You cannot configure autoflow to send object updates or event e-mail templates. Object updates are changes that are made to the fields or attributes of an entity, such as a case or a service order. Event e-mail templates are e-mail templates that are used to send event notifications to integrated solutions. To configure object updates, you need to use the administration tool. To configure event e-mail templates, you need to use the event management tool. References = Solution Guide for SAP Service Cloud Version 2, section “Autoflow”, page 34.

 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

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

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 link customer e-mails with cases, you need to do the following configuration steps in SAP Service Cloud Version 2:

• Maintain and activate at least one e-mail channel: You need to create an e-mail channel for each support e-mail address that you want to use to communicate with your customers. You also need to configure the settings for the e-mail channel, such as the technical e-mail address, the sender name, the sender e-mail address, and the reply-to e-mail address. You also need to verify and activate the e-mail channel, so that the incoming e-mails are forwarded from your company’s e-mail server to the tenant’s technical e-mail address.
• Create a case routing rule: You need to create a case routing rule for each e-mail channel, to define how the incoming e-mails are processed and assigned to cases. You can specify the criteria for the case routing rule, such as the e-mail channel, the sender e-mail address, the subject, or the body of the e-mail. You can also specify the actions for the case routing rule, such as creating a new case, updating an existing case, assigning a case type, assigning a team or a processor, or sending an auto-reply e-mail. References = Configuring Email, section Communication Channel Configuration - Email; Providing Expedited Service, section Inbound Email Linked to a Case.

Triggering an event notification based on a specific condition in SAP Service Cloud Version 2 typically involves implementing custom logic through the Software Development Kit (SDK). This approach allows for the creation of tailored functionalities that can respond to very specific conditions or criteria within the system. By utilizing the SDK, developers can write scripts or programs that monitor certain conditions or events within the Service Cloud environment and trigger notifications accordingly. This method provides a flexibleand powerful means to extend the standard capabilities of SAP Service Cloud to meet unique business requirements

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

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

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.

The following configuration activities are part of SAP Service Cloud Version 2:

• Maintain case types: You can maintain case types to define the different categories of cases that you handle in your service organization. You can specify the name, description, priority, status, and other attributes for each case type. You can also assign case types to service categories and service levels.
• Set up Agent Desktop: You can set up Agent Desktop to customize the user interface and the functionality of the solution. You can configure the layout, the navigation, the cards, the widgets, the actions, the timeline, the quick create, and the search options for the Agent Desktop. References = Configuring Case Types, section Maintain Case Types; Configuring Agent Desktop, section Set Up Agent Desktop.

Configuration activities in SAP Service Cloud Version 2 include a range of tasks designed to tailor the system to specific business processes and requirements. "Maintaining case types" is a critical activity that involves defining and configuring the different categories of customer inquiries and issues that can be logged in the system. This configuration is essential for organizing, tracking, and managing cases efficiently. Another important configuration activity is "Setting up Agent Desktop," which involves customizing the user interface and functionalities available to service agents. This setup is crucial for ensuring that agents have access to the necessary tools, information, and workflows to effectively resolve customer cases.

To enable different user groups to have different fields access in the UI in SAP Service Cloud Version 2, you would use the page layout and adaptation functionalities. Page layout allows you to create and assign different layouts for different user groups, which can include or exclude certain fields, sections, and tabs1. Adaptation allows you to make changes to the UI elements, such as labels, visibility, and order, in the adaptation mode2. References = Manage Page Layouts, Adaptation Mode

You can adapt the status schema of a case type by adding or removing statuses in the existing status schema, or by creating a new version of a status schema. Adding or removing statuses allows you to customize the support process for different case types. Creating a new version of a status schema enables you to modify the existing status schema without affecting the cases that are already using it. You cannot copy or change the existing status schema directly, as this would impact the existing cases and their service level agreements. References = Creating the Statuses for Cases, Creating a Case Type

An installed base is a hierarchical arrangement of products that are located or installed at a customer’s location. To use installed bases in cases, you need to perform the following actions:

• Assign a customer to the installed base. This is done by adding the customer as an involved party in the installed base header. The customer is the owner of the installed base and the products within it.
• Assign at least one registered product to the installed base. This is done by adding the registered product as an item in the installed base hierarchy. A registered product is an instance of a product that is associated with a specific customer. You can also assign products and functional locations (also known as installation points) to the installed base hierarchy. References = Using an Installed Base, Using Installed Bases and Registered Products, Explaining How to Provide Expedited Service, Set Up Guide for SAP Service Cloud Version 2

To effectively use installed bases in cases within SAP Service Cloud Version 2, it is necessary that "A customer needs to be assigned to the installed base," which links the installed base to a specific customer account, providing a clear context for service and support activities. Additionally, "At least one registered product must be assigned to the installed base" to define the scope of products or equipment covered under the installed base, enabling targeted and relevant service actions based on the specific products included.

When configuring a new email channel in SAP Service Cloud Version 2, administrators havethe ability to maintain several key parameters to ensure the proper setup and functioning of the email communication channel. The "Channel type" parameter is fundamental, as it defines the nature of the channel being configured, in this case, specifying it as an email channel. The "Channel email ID" is another crucial parameter, identifying the specific email address associated with this channel, through which incoming and outgoing communications are routed. Lastly, the "Default account" parameter is essential for defining the default system account or user that will be associated with emails received through this channel, ensuring that emails are correctly routed and managed within the SAP Service Cloud system

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

• Agent Desktop: This is the main user interface for service agents to manage customer interactions, cases, and tasks. It consists of several components, such as the Communication Panel, the Customer Hub, the Case Hub, and the Task Hub12.
• Templates: These are predefined sets of data that can be used to create or update objects, such as cases, emails, surveys, and reports. Templates can help to standardize and automate processes, as well as save time and effort34.

The following services cannot be activated in SAP Service Cloud Version 2:

• Live activity configuration: This is a feature of SAP Sales Cloud, not SAP Service Cloud. It allows sales representatives to track and record their interactions with customers, such as calls, emails, meetings, and tasks5.
• Initial user: This is not a service, but a user account that is created during the tenant activation process. The initial user has full access to the solution and can perform administrative tasks, such as creating other users, assigning roles, and configuring settings.

References = 1: Agent Desktop - SAP Online Help, 2: SAP Service Cloud Version 2 Feature Scope, 3: Templates - SAP Online Help, 4: SAP Service Cloud Version 2 Feature Scope, 5: Live Activity Configuration - SAP Online Help, : Onboarding Guide for SAP Service Cloud Version 2 - SAP Online Help

Within SAP Service Cloud Version 2, the available user types include "Business" and "Technical" users. Business users typically interact with the system through its front-end functionalities, focusing on tasks such as sales, service, and customer engagement. Technical users, on the other hand, are involved with the back-end aspects of the system, dealing with configuration, customization, and system administration tasks to ensure that the SAP Service Cloud operates smoothly and meets the organization's needs.

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 the Customer Hub in Agent Desktop, a service agent can perform the following actions:

• Edit customer details: The agent can update the customer’s personal and business information, such as name, address, phone number, email, account, and contact person. The agent can also add or remove tags to the customer1.
• View customer details: The agent can see the customer’s basic information, such as name, address, phone number, email, account, and contact person. The agent can also see the customer’s tags, which are keywords that help to categorize and identify the customer1.
• Access interactions and notes in the timeline tab: The agent can view the chronological history of interactions with the customer, such as cases, calls, emails, chats, surveys, and visits. The agent can also see the notes that were added by other agents or by the customer2.

The agent cannot perform the following actions in the Customer Hub in Agent Desktop:

• Create a new e-mail message or a new case from the What Would You like to do? area: This action can only be done from the Communication Panel, which is a separate area in the Agent Desktop that shows the incoming and outgoing communication items, such as emails, calls, chats, and messages3.
• Launch a customer survey: This action can only be done from the Survey tabstrip, which is a separate tabstrip in the Customer Hub that shows the surveys that were sent to or received from the customer. The agent can launch a new survey from this tabstrip by selecting a survey template and a communication channel4.

References = 1: Customer Hub - SAP Online Help, 2: Timeline - SAP Online Help, 3: [Communication Panel - SAP Online Help], 4: [Survey - SAP Online Help]