Pass the SAP Certified Application Associate C_C4H47I_34 Questions and answers with ExamsMirror

 Payment Terms are part of the Account Sales Data, which can be maintained in the Sales Data tab of the Account master data. Payment Terms specify the conditions under which a vendor completes a sale. They determine when the customer must pay their invoice and the discount they receive for paying early. Payment Terms are assigned to an Account based on the Sales Organization, Distribution Channel, and Division. References = SAP Service Cloud Version 2 for Utilities Integration with SAP S/4HANA, page 9; SAP Service Cloud Version 2, Add-On for Utilities - SAP Online Help, page 13.

 To create a Call List so it can be executed and monitored via the Digital Selling Workspace, you need to follow these steps:

Define Key Objectives of Call List: You need to specify the purpose, target audience, and expected outcome of the Call List. This will help you to measure the effectiveness and ROI of the Call Campaign.

Create Call List: You need to create a new Call List object and fill in the basic details such as name, description, owner, status, and start and end dates.You can also add custom fields if needed.

Add Script to Call List: You need to create or select a Script that contains the questions and answers that the agents will use during the calls. You can also define the branching logic and the disposition codes for the Script.

Add Resources to Call List: You need to add the Leads or Contacts that you want to call as Resources to the Call List. You can also assign them to different agents or teams based on your criteria.

Monitor Call Campaign Progress: You need to use the Digital Selling Workspace to execute and monitor the Call Campaign. You can see the status, progress, and results of each call, as well as the overall performance and analytics of the Call List.

References = You can find more information about these steps in the following resources:

Solution Guide for SAP Service Cloud Version 2, pages 40-43

SAP Service Cloud Version 2 - openSAP Microlearning, videos “Creating Call Lists” and “Using the Digital Selling Workspace”

Embedding custom modules created in SAP Build App is a correct answer because SAP Build App (formerly known as SAP AppGyver) is a no-code development environment that allows users to build business applications without the need for pro-code development knowledge1. SAP Build App is part of the SAP Extension Suite, which enables side-by-side extensibility for SAP Sales Cloud Version 22.

Extending standard delivered applications, Adding custom fields on existing entities, and Enhancing the code baseline without modifying the standard are not correct answers because they are examples of in-app extensibility, not side-by-side extensibility. In-app extensibility allows users to customize and adapt the standard functionality of SAP Sales Cloud Version 2 within the same system, using tools such as fields, layouts, mash-ups, and key user tools3.

References = 1: Design and Develop Extensions on SAP Service and Sales Cloud Version 2 Using SAP AppGyver 2: Getting Familiar with SAP Sales Cloud Version 2 - SAP Learning 3: SAP Help Portal - SAP Online Help

 Inactive users are users who have not logged in to the system for a long time or have never logged in. They pose a security risk as they may have outdated or unauthorized access to the system. To prevent security risks while monitoring inactive users in SAP Sales Cloud Version 2, you can use the following methods:

By using the auto sign out, users are automatically logged off after a specified period of inactivity. This prevents unauthorized access to the system by someone who may use the user’s device or session. You can configure the auto sign out time in the Security Policy settings.

By scheduling the dedicated auto sign out background job, you can automatically deactivate the user accounts that have not logged in for a certain number of days. This reduces the number of inactive users in the system and frees up the licenses for other users. You can schedule the auto sign out background job in the Administrator work center. References = Security Guide for SAP Sales Cloud Version 2, page 15-16. User Management in SAP Sales Cloud Version 2, 1:40-2:00. Inactive User Accounts – Risks and Best Practices.

According to the SAP Cloud for Customer Extension Guide1, mashups are used to integrate data from SAP’s cloud solution with data provided by an online Web service or application. Users can access the content provided by these Web services and applications, and use it in their daily work. Mashups can include Web searches, company or industry business information, or online map searches. There are different types of mashups, such as URL mashups, HTML mashups, and data mashups. However, not all mashups are supported on the mobile application. According to the SAP Cloud for Customer Transition Guide2, data mashups in SAP Cloud for Customer are not supported in both SAP Service Cloud V2 and SAP Sales Cloud V2. It is recommended to use side-by-side extensibility to create richer applications that can work together. HTML Code Mashup is available in SAP Cloud for Customer, but in SAP Service Cloud V2 and SAP Sales Cloud V2, it is recommended to use SAP Build Apps to create mashups and to optimize the implementation. In Version 2, only HTML mashup of type URL, which is rendered in iframe is supported. Therefore, the mashup settings that can be toggled on by the end user in order to use them on their mobile device are the ones that use HTML mashup of type URL. Based on the preconfigured mashups provided in SAP Cloud for Customer1, the ones that use HTML mashup of type URL are Activity mashup and Quote mashup. These mashups allow the user to view and edit activities and quotes from external applications within the SAP cloud solution. Guided Selling mashup and Lead mashup are not supported on the mobile application, as they use data mashups and HTML code mashups respectively. References = 1 Mashups | SAP Help Portal 2 Mashups | SAP Help Portal

The valid Master Data entities for a B2B scenario in SAP Sales Cloud Version 2 are Account and Individual Customer. An Account represents a company or organization that your company has a business relationship with. An Individual Customer represents a single person who is a customer of your company. These entities are crucial for managing customer relationships and sales processes in a B2B scenario. 

Lead Routing to Employee is the setting that allows you to assign Leads to a specific sales employee based on certain attributes, such as the source of the Lead. This feature is part of the Digital Sales Engagement for Business Users capability in SAP Service Cloud Version 21. You can configure Lead Routing to Employee rules in the following path: Settings → Leads → Lead Routing to Employee2. The other options are not related to this setting. Qualifications are the criteria that determine the quality of a Lead3. Status is the current stage of a Lead in the sales process. Party Schema is the structure that defines theparties involved in a Lead, such as the account, contact, or partner. References = 1: SAP Service Cloud Version 2 Features | SAP Help Portal 2: Configuring Lead Routing Rules - SAP Learning 3: Solution Guide for SAP Service Cloud - SAP Online Help : [Lead Status - SAP Online Help] : [Party Schema - SAP Online Help]

 A Source is a field that indicates where a Lead came from, such as a website, an event, or a referral. You can create custom Sources to track Leads from different channels, such as social media. To create a new Source, you need to access the Business Configuration work center, select the Implementation Projects view, and open the Fine-Tune activity list. Then, you need to find and open the Leads activity, and click on Maintain Sources. Here, you can add a new Source with a name and a description, such as “Social Media”. You can also assign a Source Category to group similar Sources together. After saving your changes, you can use the new Source when creating or editing Leads in the system. You can also use the Source field as a filter or a report parameter to analyze the performance of your Leads from different Sources. References = SAP Service Cloud Version 2 | SAP Help Portal, Creating a Lead in SAP Sales Cloud

 To assign a Playbook to Leads based on a specific attribute, such as Lead Source, you need to create a rule for that attribute in the Playbook configuration. In this case, you want to assign the Playbook with Lead Qualification Survey to all the Leads that have Cyclo Clothing as their Lead Source, which indicates that they are potential customers of the newly acquired company. Therefore, you need to create a rule for Lead Source as Cyclo Clothing in the Playbook settings. References = Using Guided Selling to Work with Opportunities, section “Rules for Playbook Assignment”.

Playbooks are a set of activities and actions that guide sales representatives through the sales process. Playbooks can be created for Leads and Opportunities, and they can be grouped by Sales Phases or Status. Sales Phases are the stages of the sales cycle, such as Qualification, Proposal, or Negotiation. Status is the current state of the Lead or Opportunity, such as Open, In Progress, or Won. Playbooks can be grouped by Sales Phases for Opportunities, as each phase may require different actions and tasks. Playbooks can also be grouped by Status for Leads, as each status may indicate the level of interest and readiness of the Lead. Playbooks cannot be grouped by Status for Opportunities or by Sales Phases for Leads, as these are not relevant or meaningful criteria for grouping. References = Introducing SAP Sales Cloud Version 2, 2:00-2:40. Playbooks in SAP Sales Cloud Version 2, 0:20-1:10. Set Up Guide for SAP Service Cloud Version 2, page 28-29.