Master SAP Sales Cloud V2 with Free C_C4H47_2601 Questions 2026

Step-by-Step Execution:

1. Navigate to Holiday Calendars and click the plus (+) button to create a new entry.
2. Enter the Name, Code, and Validity (Valid From/Valid To years), select the required holidays, and save.
3. Navigate to Working Day Calendars and click the plus (+) button to create a new working calendar.
4. Enter the Working Calendar Name, Code, and validity period.
5. Select the appropriate countries/regions, define the specific working days using the toggle switches, and set the first day of the week.
6. Link the newly created Holiday Calendar to this Working Day Calendar and click Finish.

Example Values:

• Holiday Calendar Name: DE_Public_Holidays
• Working Calendar Name: Germany_Standard_Week
• First day of the week: Monday

Expected Result: A new working day calendar integrated with regional holidays is established, allowing the system to correctly calculate business hours, visit dates, and task deadlines for users in the assigned region.

Quick Mistakes:

• Attempting to create the Working Day Calendar before the Holiday Calendar, leaving you unable to link the region's specific holidays during the setup process.
• Forgetting to assign the sap.crm.service.holidayCalendarService and sap.crm.service.workingDayCalendarService business services to the administrator role prior to beginning configuration.

Exam Insight:

• Tests the sequence of calendar creation, establishing that Holiday Calendars act as prerequisites for comprehensive Working Day Calendars.
• Validates your understanding of the specific business services required for administrators to manage regional calendar settings.

Step-by-Step Execution:

1. Access the Forecast Tracker and select the desired fiscal period.
2. Under the Opportunities section, locate the specific deal you wish to adjust for the simulation.
3. Click the Edit icon in the field and select Override to make changes to the amount or forecast category.
4. Review the Live Rollup view to see how the simulation changes the Forecast Tracker chart in real time.
5. Click Submit to finalize the new forecast numbers, adding an optional comment explaining the submission.

Example Values:

• Override Amount: Update from $50,000 to $40,000
• Forecast Category Override: Change to "Best Case"

Expected Result: The forecast is submitted with the overridden "what-if" scenario values, and the Live Rollup reflects the simulated changes.

Quick Mistakes:

• Confusing Forecast Figures (submitted totals) with Live Figures (real-time pipeline totals).
• Assuming override changes permanently alter the opportunity for all users, whereas they are strictly for simulation purposes and visible only to the sales manager and assigned representative.

Exam Insight:

• Tests the understanding of the Forecast Tracker's What-If simulation capabilities.
• Important because overriding opportunities allows sales managers to accurately simulate outcomes and submit refined forecasts without disrupting live master data.

Step-by-Step Execution:

1. Navigate to the Generative AI settings and open the Email Drafter tab.
2. Toggle the Activate Email Drafter switch to enable the feature for business users.
3. Go to Configure and use the switches to enable the Email Draft Recommendation for the needed entities.
4. Enable standard prompts from the Available Prompts list.
5. Click the add (+) button to create and include custom prompts.
6. Complete the settings and save the changes.

Example Values:

• Entities: Lead, Opportunity

Expected Result: The Email Draft Recommender is active, providing sales representatives with AI-generated email responses based on standard and custom prompts for the selected entities.

Quick Mistakes:

• Activating the Email Drafter but failing to select specific entities under the Configure menu, making the tool unavailable on object records.
• Forgetting to save the changes after adding custom prompts.

Exam Insight:

• Tests the configuration workflow for Gen AI features in SAP Sales Cloud Version 2.
• Highlights the administrator's responsibility to not only activate AI features globally but also map them to specific entities and tailor the prompts for specific business contexts.

Step-by-Step Execution:

1. Navigate to the Document Types settings for sales orders and create a new entry.
2. Enter a custom document type code starting with the identifier Z.
3. Provide a description for the new document type.
4. Select Internal from the Maintenance Mode drop-down menu.
5. Turn on the Internal Pricing switch to enable native pricing capabilities based on your pricing master data.
6. Save the new document type configuration.

Example Values:

• Document Type Code: ZDOM
• Description: Domestic Sales Order
• Maintenance Mode: Internal
• Internal Pricing: On

Expected Result: A new custom sales order document type is successfully created, allowing users to process internal sales orders using native pricing configurations without integration to external systems.

Quick Mistakes:

• Creating a custom document type code that does not start with the required identifier "Z".
• Selecting the "External" maintenance mode, which makes the orders read-only and prevents users from editing them in SAP Sales Cloud Version 2.
• Forgetting to toggle the Internal Pricing switch, which disables native price calculations for the document type.

Exam Insight:

• Tests your knowledge of Sales Order Maintenance Modes, specifically understanding the difference between Internal, External, and Internal & External modes.
• Demonstrates the functional limitations of "Internal" mode, specifically that these orders cannot be integrated with external SAP systems and do not support the Simulate and Transfer features.

Step-by-Step Execution:

1. Navigate to the My Network landing page to view the automatically generated list of interacted accounts and contacts.
2. Review the Hugrank score for your target account to determine the current relationship strength.
3. Open the Account Quick View and check the Colleagues section to identify who can provide a warm introduction.
4. Navigate to the Interactions tab and locate a specific contact you wish to keep confidential.
5. Toggle the Private flag to restrict visibility of this contact.

Example Values:

• Target Hugrank: Green (70-100 score indicating good engagement)
• Interaction Type: Private

Expected Result: The user successfully identifies relationship strengths and warm introduction paths, and successfully restricts visibility for a sensitive contact using the privacy toggle.

Quick Mistakes:

• Assuming Hugrank evaluates interactions across all email providers, whereas it only integrates with Office 365 and does not support Gmail or MS Exchange.
• Forgetting that marking a contact as private makes all interactions with that contact unavailable to other SAP Sales Cloud Version 2 users, which could hinder team collaboration if used incorrectly.

Exam Insight:

• Tests the understanding of Relationship Intelligence, Hugrank scoring indicators, and privacy controls.
• Important because Relationship Intelligence builds a smart network based on Office 365 communications to uncover hidden relationships, accelerate business development, and protect sensitive contact data.