SAP C_C4H56I_34 SAP Certified Application Associate - SAP Service Cloud Version 2 Exam Practice Test

Business roles are used to assign work centers and views to users, and also to define access restrictions and authorizations for each view. By using business roles, you can control which views are visible and editable for different users or groups of users. For example, you can restrict access to certain accounts, products, or tickets based on the user’s organizational unit, territory, or other criteria. References = Apply Access Contexts and Restriction Rules, Restricting access the right way in SAP Cloud for Customer

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

Access restriction types are used to define the level of access that a business role has for a business service. There are three access restriction types available in SAP Service Cloud Version 2:

• Unrestricted: This means that the business role has full access to all the data related to the business service, regardless of the ownership or the organizational unit.
• Define specific restriction: This means that the business role has access to the data related to the business service based on certain criteria, such as the employee responsible, the territory, the account team, or the service organization. You can define the specific restriction rules for each business service in the business role details.
• Restricted: This means that the business role has no access to the data related to the business service. The business service is not visible or editable for the business role. References = Set Up Guide for SAP Service Cloud Version 2, page 10; Solution Guide for SAP Service Cloud Version 2, page 11

With the integration of Microsoft Teams into SAP Service Cloud Version 2, service agents gain the ability to enhance collaboration around case management. The Share Workspace icon, a key feature of this integration, allows agents to initiate shared workspaces directly from a case or within the Agent Desktop environment. This functionality facilitates real-time collaboration and communication among team members, making it easier to discuss case details, share insights, and collectively work towards resolutions, all within the familiar interface of Microsoft Teams

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.

E-mail templates are used to define the fixed content (such as subject or disclaimer) andvariable parts (such as the form of address) of the email responses that service agents send to customers. E-mail templates can also be customized to include the corporate branding, such as logos, colors, fonts, and signatures, according to the needs of the service organization. E-mail templates can be created and maintained using the Configuring Email app in SAP Service Cloud Version 2. References = Configuring Email - SAP Learning, Maintain Email Templates | SAP Help Portal, Configuring Email Templates - SAP Customer Data Cloud, Configuring Email Templates | SAP Help Portal

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

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

 One of the main uses for warranty management in SAP Service Cloud Version 2 is to associate a warranty with a registered product. This allows the service agent toautomatically determine the warranty coverage and validity when creating a case for a customer who owns the registered product. The warranty can include information such as the duration, the coverage option, and the start date. The warranty is created in the Products work center and then assigned to the registered product in the Registered Products work center. References = Managing Warranties - SAP Learning, Creating a Warranty - SAP Learning, Solution Guide for SAP Service Cloud Version 2, page 88

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

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.

• 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

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

The due dates defined in Service Level Agreements are calculated based on the following elements:

• Working calendar: This is a calendar that defines the working days and hours for a specific country or region. It also includes the public holidays and other non-working days for that location. The working calendar is used to determine the actual duration of a service level objective, excluding the non-working time12.
• Operating hours: This is a time interval that defines the availability of a service team or an individual employee. It specifies the start and end time of the working hours for each dayof the week. The operating hours are used to determine the actual response time of a service level objective, excluding the time when the service team or employee is not available3 .

The service contract and the maintenance plan are not elements that are used to calculate the due dates defined in Service Level Agreements. The service contract is an agreement between a service provider and a customer that defines the scope, terms, and conditions of the service delivery. The maintenance plan is a schedule that defines the frequency and type of maintenance activities for an installed base object.

References = 1: Working Calendar - SAP Online Help, 2: Configuring a Service Level Agreement - SAP Learning, 3: Operating Hours - SAP Online Help, : [Using Service Level Agreements - SAP Learning], : [Service Contract - SAP Online Help], : [Maintenance Plan - SAP Online Help]

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

When creating a new business user in SAP Service Cloud Version 2, it is mandatory to maintain certain key elements. "Employee" information is crucial as it links the user account to an individual's employee record within the organization, providing context and defining the user's position and role within the company. Additionally, assigning a "Business role" is essential as it determines the access levels, permissions, and functionalities available to the user based on their responsibilities and tasks within the organization.

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

 You cannot access cases in SAP Service Cloud Version 2 if you do not have the appropriate access rights or permissions. There are two possible reasons for this: either access to the Case app is not enabled for the business user, or the employee is not assigned to the correct business role. Access to the Case app is enabled by adding the Case work center and the relevant work center views to the business role assigned to the business user. The business role defines the functional scope and access rights of the user for specific tasks and operations. If the business user does not have the Case work center or the necessary work center views in their business role, they will not be able to access cases in SAP Service Cloud Version 2. Alternatively, the employee may have the Case work center and work center views in their business role, but they may not be assigned to the correct business role in the first place. The business role assignment is done in the Employee work center, where the administrator can assign one or more business roles to each employee. If the employee is not assigned to the business role that has the Case work center and work center views, they will not be able to access cases in SAP Service Cloud Version 2. References = Creating Business Roles, section “How to Add a Work Center to a Business Role” and “How to Add a Work Center View to a Business Role”; Assigning Business Roles to Employees, section “How to Assign a Business Role to an Employee”

• Dates: You can specify the start date and end date of the warranty, or choose to calculate them automatically based on the registered product’s purchase date or installation date. You can also define grace periods before and after the warranty period.
• Duration: You can define the duration of the warranty in days, months, or years, and choose whether to include or exclude weekends and holidays. You can also set up recurrence rules for warranties that renew periodically.
• Non-covered categories: You can exclude certain service categories from the warranty coverage, such as damage, misuse, or wear and tear. You can also specify the non-covered charges, such as labor, parts, or travel expenses, that the customer has to pay in case of a non-covered service request.
• Registered products: You can assign the warranty to one or more registered products, either manually or automatically based on product attributes, such as product ID, serial number, or product group. You can also assign the warranty to a registered product’s parent or child products, such as components or accessories.

References = Creating a Warranty, Warranty Attributes

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

For service levels in SAP Service Cloud Version 2, the "Initial review date" is a significant milestone that can be used to track and manage service commitments. This milestone marks the scheduled date for an initial evaluation or review of the service provided, ensuring that service level agreements (SLAs) are being met and that any issues are identified and addressed in a timely manner. This helps in maintaining high service standards and customer satisfaction.

In the Related Objects facet of a case, you can maintain the following information:

• Registered products: You can add registered products that are related to the case, such as the product that caused the issue, the product that needs to be repaired, or the product that needs to be replaced. You can also view the product details, such as the serial number, the warranty, the reading value, and the status.
• Installed bases: You can add installed bases that are related to the case, such as the location where the product is installed, the configuration of the product, or the hierarchy of the product components. You can also view the installed base details, such as the ID, the description, the account, and the status.
• Products: You can add products that are related to the case, such as the product that needs to be ordered, the product that needs to be delivered, or the product that needs to be invoiced. You can also view the product details, such as the ID, the description, the quantity, and the price. References = Solution Guide for SAP Service Cloud Version 2, section Related Objects.