Free SAP C_C4H56I_34 Practice Exam with Questions & Answers | Set: 2

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

 The categories in the service catalog can be used for service level determination, a filter option for the case summary, and case responsibility determination. Service level determination is the process of assigning a service level agreement (SLA) to a case based on the category and other attributes. A filter option for the case summary allows the user to view cases by category or subcategory. Case responsibility determination is the process of assigning a case to a service agent or a service team based on the category and other criteria. References = Configuring Categories, Creating the Statuses for Cases, Service Categorization with Machine Learning

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 get a system bug fixed within SAP Service Cloud Version 2, an administrator should create an incident and report the issue to SAP Cloud Support. An incident is a request for support that contains information about the problem, such as the system ID, priority, category, description, and attachments. Creating an incident is the recommended way to contact SAP Cloud Support and get a timely and effective resolution for the bug. SAP Cloud Support will then analyze the incident and provide a solution or a workaround, depending on the severity and complexity of the bug. Alternatively, an administrator can also report an issue via case, which is a similar process but with a different user interface. However, creating an incident is the preferred option as it provides more options and features for managing the support request. References = SAP Service Cloud Version 2 | SAP Help Portal, How are bugs fixed in a cloud system?| SAP Community

To assign employees to multiple organizational units, you need to assign them directly to different organizational objects. This can be done by creating positions that incorporate the organizational units and then assigning the employees to those positions. The Primary flag in the organization unit is used to indicate the main organizational unit for an employee or a manager, but it does not prevent them from being assigned to other organizational units. Acquiring an additional license for the required add-on is not relevant for this scenario. Assigning the employee at company level is not sufficient to assign them to multiple organizational units, as the company level is the root of the organizational structure and does not reflect the specific functions or teams of the employees. References = Setting Up a Service Organization, Create an Org Unit

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

• 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

In SAP Service Cloud Version 2, employees can be assigned to various objects as part of the system's configuration to ensure proper management and allocation of resources. Specifically, employees can be associated with "Accounts" to manage customer relationships and interactions effectively. This allows for a personalized and efficient approach to account management, where specific employees are responsible for certain accounts, ensuring better service and accountability. Additionally, employees can be assigned to "Registered Products," which enables them to manage and oversee specific products that customers have registered or purchased. This assignment is crucial for providing targeted support and services for specific products, enhancing the overall customer service experience.

 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

 To set up an organizational structure for a new implementation, the following options are possible:

• Assign an employee to several organizational units. This is possible by using the Employee Assignment function in the Organizational Management work center. An employee can be assigned to multiple organizational units with different validity periods and functions. For example, an employee can be a sales representative in one unit and a service agent in another unit.
• Use the Reporting Line function for selection. This is possible by using the Reporting Line function in the Organizational Management work center. This function allows the administrator to select an organizational unit and display its reporting line, which shows the hierarchical relationship between the unit and its parent and child units. The administrator can also edit the reporting line by adding, removing, or changing the position of the units. References =
• Setting up an organizational structure - SAP Learning, section Assigning Employees to Organizational Units, slide 8-9
• Set Up Guide for SAP Service Cloud Version 2, section Organizational Structure, page 11-12