CRM module in a business suite
CRM; actual close date, structured lost reasons, calendar sync unresolved
Core objects
In full
SAP's administrator training for Version 2 lists B2B accounts, individual contacts and B2C individual customers as separate customer records an administrator maintains, alongside employees and products. The opportunity carries contact roles, described as "the different individuals or stakeholders involved in the decision-making process". Activities are their own records - appointments and tasks - and their party schema defines the roles on an appointment including organizer, owner, account and contact. Activities attach to the opportunity: SAP's knowledge base article on the "Opportunity Won Status" toggle states that when it is switched on a user must "finish all mandatory activities before they can move an Opportunity to Won status".
Source: https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/identifying-core-responsibilities-and-tools-for-administrators_a296949c-50d8-4897-8905-770f01e74d8b, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/setting-up-opportunity-management_fe41caff-df24-4309-89af-5647e9998eff, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/configuring-sales-activities, https://userapps.support.sap.com/sap/support/knowledge/en/3531149
Verification: Verified
Pipeline stages
In full
An opportunity runs against a sales cycle, and SAP's configuration training tells administrators they can "create a whole new Sales Cycle" and set the stages and duration within it, giving managers "clear visibility into the progress of each opportunity". Movement across that sequence is stored rather than merely displayed: Pipeline Flow reports on "how opportunities move through the pipeline over time" between the start and end of a fiscal period, and its accuracy depends on an administrator-set date "from which historical changes are competent for pipeline flow inspection".
Source: https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/setting-up-opportunity-management_fe41caff-df24-4309-89af-5647e9998eff, https://learning.sap.com/courses/exploring-sap-sales-cloud-version-2/streamlining-pipeline-and-process-flow-with-trends-analytics, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/configuring-pipeline-and-sales-forecasting
Verification: Verified
Status
In full
Status is a field on the opportunity, held separately from the sales cycle and its phases. SAP's configuration training has administrators build status schemas and status codes and attach a schema to an opportunity document type - "create a new set of statuses for an Opportunity Document Type" - with sales cycles configured separately. SAP's knowledge base confirms the field in use on Version 2: a General Settings toggle called "Opportunity Won Status" makes mandatory activities a precondition of moving an opportunity to "Won" status, and SAP notes that the restriction "applies only to the Won status - other status changes remain unaffected". A second article covers setting a status as the initial status in a status schema.
Source: https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/setting-up-opportunity-management_fe41caff-df24-4309-89af-5647e9998eff, https://userapps.support.sap.com/sap/support/knowledge/en/3531149, https://userapps.support.sap.com/sap/support/knowledge/en/3379057
Verification: Verified
Resolution
In part
Won and lost are values of the same status field rather than a separate outcome attribute. SAP documents "Won" as an opportunity status and describes a "Reason for Status" list that records why a status changed. Pipeline Flow sorts opportunities at the end of a period into buckets SAP names as "unchanged, progressed, won, or lost", so the outcome is read from the status the opportunity settled in.
Source: https://userapps.support.sap.com/sap/support/knowledge/en/3531149, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/setting-up-opportunity-management_fe41caff-df24-4309-89af-5647e9998eff, https://learning.sap.com/courses/exploring-sap-sales-cloud-version-2/streamlining-pipeline-and-process-flow-with-trends-analytics
Verification: Verified
Value
In full
SAP ships two monetary amounts on the opportunity. Expected Value is "the estimated or tentative revenue expected from the Opportunity", entered by the user in the opportunity header. Total Negotiated Value is "calculated automatically based on the sum of all line items" and cannot be edited directly. Pipeline aggregation is configured to run on one or the other.
Source: https://userapps.support.sap.com/sap/support/knowledge/en/3534352, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/configuring-pipeline-and-sales-forecasting
Verification: Verified
Scope of work
In full
Products attach to the opportunity as line items. SAP states that Total Negotiated Value "aggregates automatically from product line items, specifically pulling the Product Negotiated Value assigned to each product within the opportunity", so what is being sold is held as priced items on the record rather than as a description.
Source: https://userapps.support.sap.com/sap/support/knowledge/en/3534352
Verification: Verified
Expected close date
In full
A Close Date field ships on the opportunity. SAP's configuration training has an administrator choose which date drives the opportunity progress bar - "select the date that will show as the last marker on an Opportunity progress bar. Either the Close Date or the Revenue Start Date" - so the field is the vendor's own and marks the end point the opportunity is running towards.
Verification: Verified
Actual close date
No verdict
Whether Version 2 records the date an opportunity actually settled could not be established. The Close Date field is documented, but no reachable SAP material states whether the platform stamps a settlement date when the status moves to Won or Lost, whether Close Date is overwritten at that point, or whether a second date field exists for it.
Source: https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/setting-up-opportunity-management_fe41caff-df24-4309-89af-5647e9998eff, https://userapps.support.sap.com/sap/support/knowledge/en/3534352
Searched: Searched SAP's Version 2 training and knowledge base for a closing date stamped at status change; the articles that describe close-date behavior on won or lost opportunities are all written against the earlier SAP Cloud for Customer generation. help.sap.com and api.sap.com both refuse automated retrieval, so the SAP Help Portal documentation set for SAP Sales Cloud Version 2 and the Opportunity Service API reference on the SAP Business Accelerator Hub could not be read.
Verification: Pending vendor verification
Opportunity owner
In full
The opportunity carries an owner. SAP's configuration training walks an administrator through routing rules that "assign opportunities to employees automatically" and lists the columns those rules work on as Owner, Owner Role, Sales Employee and Sales Employee Role.
Verification: Verified
Linked buyer
In full
Contact roles link the opportunity to named people. SAP's configuration training states that "tracking contact roles for opportunities is essential for the sales process" and that contact roles "refer to the different individuals or stakeholders involved in the decision-making process", with the role set maintained by an administrator.
Verification: Verified
Record preservation
In full
Closed opportunities stay in the system and stay reportable. Trends Analytics lets a manager "view all successful closed opportunities for a given quarter" and compares success rates across the last five quarters, and Pipeline Flow reports won and lost opportunities at the end of a fiscal period with their quantities and values, all of which require settled records to persist and remain queryable.
Verification: Verified
Structured lost reasons
No verdict
SAP ships a structured Reason for Status list on the opportunity - administrators "create new entries to manage extra reasons for status based on business needs", and the codes are validated on import - so the reason a deal was lost can be recorded against the record as a coded value. What could not be established is whether those reasons can be counted in the platform's own reporting, which is the test this feature turns on.
Source: https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/setting-up-opportunity-management_fe41caff-df24-4309-89af-5647e9998eff, https://userapps.support.sap.com/sap/support/knowledge/en/3450592
Searched: Searched SAP's Version 2 training and knowledge base for a report, data source or analytics table exposing Reason for Status; SAP's published list of Embedded Analytics tables sits on a community page closed to automated retrieval, and help.sap.com and api.sap.com both refuse automated retrieval, so the SAP Help Portal documentation set for SAP Sales Cloud Version 2 and the Opportunity Service API reference on the SAP Business Accelerator Hub could not be read.
Verification: Pending vendor verification
Email sync
In part
SAP documents a mailbox connection for Version 2 and restricts it to one kind: "SAP Sales and Service Cloud v2 do not support client side groupware integration, only Server Side Integration". A groupware add-in runs inside the mail client on top of that connection, and a user can search accounts from it. What the reachable material does not state is which direction mail moves - whether mail sent from the mail client is captured onto the record, whether mail can be sent from inside the CRM, or both.
Source: https://userapps.support.sap.com/sap/support/knowledge/en/3422870, https://userapps.support.sap.com/sap/support/knowledge/en/3570131, https://userapps.support.sap.com/sap/support/knowledge/en/3530742
Verification: Pending vendor verification
Calendar sync
No verdict
Version 2 has an Activity Manager that manages appointments through calendars inside the product, and a server-side groupware integration exists for Microsoft mail clients. No reachable SAP material states whether appointments synchronize with an external calendar, or in which direction.
Source: https://userapps.support.sap.com/sap/support/knowledge/en/3530742, https://userapps.support.sap.com/sap/support/knowledge/en/3422870, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/configuring-sales-activities
Searched: Searched SAP's Version 2 knowledge base and training for appointment or calendar synchronization; the configuration article is login-gated and its public preview names only the keywords Outlook, Server Side, Add-In, Configuration and Groupware. help.sap.com and api.sap.com both refuse automated retrieval, so the SAP Help Portal documentation set for SAP Sales Cloud Version 2 and the Opportunity Service API reference on the SAP Business Accelerator Hub could not be read.
Verification: Pending vendor verification
Schedulable activity types
In full
Activities are typed and the types are extensible. Appointments ship with Meeting and Outbound Phone Call, which cannot be deleted, and administrators can add their own appointment categories; tasks ship with categories including Text Message, External Channel, General Task, Email and Outbound Phone Call, and administrators can add custom task categories provided "their code must start with a Z and be at least 5 characters long to be saved". Appointments are scheduled through the Activity Manager's calendar, and a party schema sets the organizer, owner, account and contact on each one.
Source: https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/configuring-sales-activities
Verification: Verified
Opportunity reporting
In part
Two of the three reports are native. Win rate is covered by Trends Analytics, which lets a manager "understand historical success rates by forecast category" and "check whether the team's success rates increase or decrease over a period" across the last five quarters. Forecasting is native: administrators define forecast categories, choose whether pipeline aggregates as a sum by forecast category or a cumulative sum across them, pick Expected Value or Total Negotiated Value as the amount, and roll the result up a territory or sales unit hierarchy, with sales targets uploaded from a CSV template. Stage-to-stage conversion is the gap. Pipeline Flow does report movement between stages, showing which opportunities were unchanged, progressed, won or lost between the start and end of a period, but SAP describes the output as the quantity and monetary value of opportunities in each transition rather than as the proportion that advanced.
Source: https://learning.sap.com/courses/exploring-sap-sales-cloud-version-2/streamlining-pipeline-and-process-flow-with-trends-analytics, https://learning.sap.com/courses/configuring-sap-sales-cloud-version-2/configuring-pipeline-and-sales-forecasting, https://learning.sap.com/courses/exploring-sap-sales-cloud-version-2/understanding-the-daily-tasks-of-sales-managers
Verification: Verified