According to the SAP Sales Cloud Version 2 Solution Guide1, surveys are used to collect feedback from customers or prospects on various topics, such as product satisfaction, service quality, or marketing campaigns. Surveys can be created and assigned to different categories, which help to organize and filter them. The default survey categories that are pre-delivered with the SAP Sales Cloud Version 2 tenant are Checklist and Call Script1. These categories are suitable for the sales team to use in a new call list, as they allow them to follow a predefined set of questions or actions during a phone call with a customer or prospect. Checklist surveys can be used to verify certain information or requirements, while call script surveys can be used to guide the conversation and capture the responses2. Promotion and Sentiment Score are not default survey categories, but they can be created as custom categories if needed1. References = 1 Solution Guide for SAP Sales Cloud | SAP Help Portal 2 Creating Surveys - SAP Sales Cloud Version 2 - openSAP Microlearning

Learn more

SAP Sales Cloud Version 2 is a cloud native sales solution that offers several advantages over the previous version, such as:

• Monthly releases that will help fill gaps faster: SAP Sales Cloud Version 2 follows a monthly release cycle that allows for faster delivery of new features, enhancements, and bug fixes. This helps customers to keep up with the changing market demands and customer expectations1.
• Fresh new User Experience with dynamic layouts and faster screen loading: SAP Sales Cloud Version 2 provides a more intuitive and responsive user interface that adapts to different devices and screen sizes. The user interface also leverages the latest web technologies to improve the performance and loading time of the screens2.
• Modern platform that delivers higher speeds, higher availability, and higher agility: SAP Sales Cloud Version 2 is built on a modern cloud platform that leverages microservices, containers, and Kubernetes to provide higher scalability, reliability, and flexibility. The platform also enables faster innovation and integration with other SAP and non-SAP solutions3. References = Introducing SAP Sales Cloud Version 2, What’s New in SAP Sales Cloud Version 2, Solution Guide for SAP Sales Cloud Version 2, SAP Sales Cloud Version 2 - openSAP Microlearning

MS Teams integration in SAP Sales Cloud Version 2 enables the following use cases:

• Share Workspaces and Deal Rooms: You can create and share Teams and Channels to collaborate with your colleagues and customers on sales opportunities and deals. You can also access the SAP Sales Cloud context information from the Teams app.
• Create Appointments with MS Teams collaboration: You can create SAP Sales Cloud appointments and visits with MS Teams as a collaboration channel. You can also access the SAP Sales Cloud application and reference objects from the side panel during the Teams meeting.
• Make outbound calls: You can set MS Teams as the default channel for outbound calls from SAP Sales Cloud. You can also see the call details and outcomes in the SAP Sales Cloud activity timeline. References = Microsoft Teams Integration in SAP Cloud for Customer, Scope and Configure section; SAP Sales and Service Cloud V2 – Integration with Microsoft Teams, Integration Features section; Improve SAP seller productivity with Microsoft Teams and Power Platform, Enable Teams for SAP Sales Cloud section.

 You can perform the following configurations for Leads as an Administrator of the SAP Sales Cloud Version 2 system:

• Create and manage custom Statuses: You can define custom statuses for Leads to reflect your business process and track the progress of each Lead. You can also specify the default status for new Leads and the status that indicates a qualified Lead1
• Maintain Routing Rules: You can create and assign routing rules for Leads to automatically distribute them to the appropriate sales representatives based on criteria such as territory, product, or source. You can also define the priority and validity of each rule2

You cannot perform the following configurations for Leads as an Administrator of the SAP Sales Cloud Version 2 system:

• Create and manage Forecast Categories: Forecast Categories are used to classify Opportunities based on their likelihood of closing and their impact on the sales pipeline. They are not applicable for Leads, which are potential customers who have not yet expressed interest in buying3
• Maintain Probability: Probability is a percentage value that indicates the chance of winning an Opportunity. It is calculated based on the Forecast Category and the Sales Methodology. It is not applicable for Leads, which are not yet Opportunities.

References = 1: Maintaining Lead Statuses 2: Maintaining Routing Rules for Leads 3: Maintaining Forecast Categories : [Maintaining Probability]

 Lead scoring is a feature of SAP Service Cloud Version 2 that uses machine learning to predict the probability of a deal based on past sales data. Lead scoring prioritizes leads based on the propensity to win. According to the SAP Service Cloud Version 2 documentation, the considerations used for lead scoring are:

• Lead source: The origin of the lead, such as a campaign, a referral, or a website. Different lead sources may have different conversion rates and influence the lead score.
• Lead status: The current stage of the lead in the sales pipeline, such as new, qualified, or closed. The lead status reflects the progress and readiness of the lead and affects the lead score.
• Lead priority: The level of urgency or importance assigned to the lead by the sales representative, such as low, medium, or high. The lead priority indicates the potential value and attractiveness of the lead and impacts the lead score.

References = View Lead Scoring Predictions

 Workspaces are collaborative spaces where you can share and discuss objects from SAP Service Cloud Version 2 with your team members using Microsoft Teams. You can share the following objects with Workspaces: Sales Quotes, Leads, Opportunities, Accounts, Contacts, Activities, and Tickets. Appointments and Tasks are not shareable objects with Workspaces. References = Workspaces, Collaborate with Microsoft Teams

A Call List is a list of entities that you want to contact for a specific purpose, such as a marketing campaign or a follow-up call. You can create a Call List from the Home Page or the Agent Desktop. You can add the following entities as participants to a Call List:

• Leads: These are potential customers who have shown interest in your products or services, but have not yet been qualified or converted to an opportunity. You can add leads to a Call List to nurture them and move them along the sales funnel.
• Contacts: These are individuals who are associated with an account or an individual customer. You can add contacts to a Call List to maintain relationships, provide service, or cross-sell or upsell products or services.
• Target Groups: These are groups of leads, contacts, or accounts that share certain characteristics, such as industry, location, or buying behavior. You can add target groups to a Call List to segment your audience and tailor your communication accordingly.

You cannot add the following entities as participants to a Call List:

• Opportunities: These are sales deals that have been qualified and have a high probability of closing. You cannot add opportunities to a Call List because they are already in the pipeline and require a different approach than cold calling or prospecting.
• Accounts: These are organizations or individuals that have a business relationship with your company. You cannot add accounts to a Call List because they are already customers and require a different level of service and engagement than leads or contacts. References = Solution Guide for SAP Service Cloud Version 2, Creating a Call List, Adding Participants to a Call List

 The standard out-of-the-box forecast categories for Opportunities in SAP Sales Cloud Version 2 include Expected, Pipeline, and Committed. These categories are used to classify the opportunities based on their likelihood of closing, which helps in sales forecasting

https://help.sap.com/docs/SAP_CLOUD_FOR_CUSTOMER/24765b551a014b779b95c7b07d8e90 79/98d8f276bece401ebe00bed3d9722712.html

 To tag Leads using a dedicated filterable and searchable field called “Early Adopters”, and automatically notify the Sales Manager about it, you need to use the following features:

• Extension Field: You can create a custom field called “Early Adopters” in the Lead object and set its data type as Boolean. This will allow you to mark the Leads that belong to this category and filter or search them easily.
• Auto flow Rule: You can create a rule that triggers when a Lead is created or updated, and checks the value of the “Early Adopters” field. If the value is true, you can use an action to send an email notification to the Sales Manager with the Lead details.
• Field Attributes: You can configure the visibility and editability of the “Early Adopters” field for different user roles. For example, you can make it visible and editable only for the Lead Owner and the Sales Manager, and hide it from other users.

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

• Solution Guide for SAP Service Cloud Version 2, pages 19-20, 28-29, 34-35
• SAP Service Cloud Version 2 - openSAP Microlearning, videos “Creating Extension Fields” and “Creating Auto flow Rules”

To create a new Business User, you need to have an existing Employee and a unique Email ID for the Business User. The Employee is the person who will use the system and the Email ID is the login credential for the Business User. The Organizational Structure and the security policy are not required for creating a new Business User, but they can be assigned later to define the roles and authorizations of the Business User. References = Version 2 Onboarding Guide for SAP Service Cloud, page 9-10. User Management in SAP Service Cloud Version 2, 0:40-1:20.

Functions are attributes that describe the role of an organizational unit in the organizational structure. They can be used to determine the responsible organizational unit for a business transaction or activity. Functions can also be used to filter and group organizational units in reports and queries. Some of the predefined functions in SAP Service Cloud Version 2 are:

• Distribution Channel: This function represents the path through which goods and services reach the customer. It can be structured regionally or according to products. A distribution channel can be assigned to one or more sales organizations.
• Sales Office: This function represents a local sales unit within a sales organization. It can be used to differentiate between different sales regions or areas. A sales office can be assigned to one or more sales groups.
• Division: This function represents a grouping of the products or services to be sold. It can be used to segment the market according to product lines or customer groups. A division can be assigned to one or more sales organizations.

These functions can be assigned to organizational units in SAP Service Cloud Version 2 by using the Organizational Management work center. There, you can create or edit an organizational unit and select the functions from the drop-down list in the General tab. You can also assign more than one function to an organizational unit, for example, a sales office and a sales group.

References = Organizational Unit, Describing and Displaying the Organizational Structure, Explain the Organizational Structures

 A pricing determination rule defines how the system determines the pricing procedure for a sales document. The pricing procedure is a set of condition types that are used to calculate the prices and discounts for a sales document. The pricing determination rule can use the following data as criteria: document type, product, and sales organization. The document type specifies the type of sales document, such as opportunity, quote, or order. The product specifies the product ID or category of the item. The sales organization specifies the organizational unit responsible for selling the product. The system uses these data to find the most specific and accurate pricing procedure for the sales document. References = Setting up Pricing, section “Sales Cloud Version 2 PricingComponents”; Determining Different Pricing Options, section “Calculating Customer Pricing”; Validation, Determination, Service Cloud v2, Sales Cloud v2, section “Using Code Blocks”.

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

 To create a robust mobile scenario for your business users, you need to perform the following administration tasks during mobile application setup:

• Ul screen adaptation: You can adapt the user interface of the mobile app to suit your business needs and preferences. You can change the layout, visibility, and behavior of fields, sections, and actions on the app screens. You can also create custom fields and logic using the key user tools1.
• Mobile User creation: You need to create and assign mobile users to enable them to access the mobile app. You can create mobile users manually or automatically, and assign them to the relevant business roles and catalogs. You can also manage the mobile user lifecycle, such as activating, deactivating, locking, and unlocking users2.

References =

• 1: Adapt the User Interface of the Mobile App
• 2: Create and Assign Mobile Users

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. 

The Guided Selling Score is a feature of SAP Sales Cloud Version 2 that helps sales representatives to prioritize and manage their opportunities. The score is calculated based on various factors, such as sales phase, opportunity score, lead score, and probability. Administrators can configure which of these factors are displayed in the Guided Selling Score by using the fine-tuning activity Configure Score Type for Opportunities. In this activity, administrators can select one of the following options for the score type:

• Sales Phase: The score is based on the sales phase of the opportunity. The higher the sales phase, the higher the score. For example, an opportunity in the Decision phase has a higher score than an opportunity in the Discovery phase.
• Opportunity Score: The score is based on the opportunity score of the opportunity. The opportunity score is a custom score that can be defined by administrators using the fine-tuning activity Configure Opportunity Scoring. The opportunity score can be calculated based on various attributes, such as products, contacts, activities, notes, and so on.The higher the opportunity score, the higher the score.
• Lead Score: The score is based on the lead score of the opportunity. The lead score is a score that is assigned to the account or contact associated with the opportunity. The lead score can be defined by administrators using the fine-tuning activity Configure Lead Scoring. The lead score can be calculated based on various attributes, such as industry, revenue, number of employees, and so on.The higher the lead score, the higher the score.
• Probability: The score is based on the probability of the opportunity. The probability is a percentage that indicates the likelihood of winning the opportunity. The probability can be manually entered by sales representatives or automatically calculated by the system based on the sales phase.The higher the probability, the higher the score.

By default, the score type is set to Sales Phase. However, administrators can change it to any of the other options, or select a combination of two options. For example, administrators can choose to display both the Sales Phase and the Opportunity Score in the Guided Selling Score. In this case, the score is calculated as the average of the two scores. For example, if an opportunity has a sales phase score of 80 and an opportunity score of 60, the Guided Selling Score is 70.

References = Scope and Configure Guided Selling, How to use Guided Selling - SAP Sales Cloud