FAQs Opportunity Management SAP Hybris Cloud for Customer PUBLIC

FAQs Opportunity Management SAP Hybris Cloud for Customer PUBLIC

TABLE OF CONTENTS FAQS OPPORTUNITY MANAGEMENT...3 1. You want to create forecast based in set of opportunities, however you are unsure in what is basic settings you need inside an opportunity to make it work...3 2. You want to start working with Revenue split, what is the criteria you need to make it work:...3 3. You noticed that Revenue schedule is not automated when you change an amount for example...3 4. You don t want homeless opportunities to be seen by everyone in the company, you would like to have it only for unrestricted access for opportunities instead...3 5. You have restricted an opportunity access for a user, however, they are still able to see the data...3 Even after modifying an access for a user, please make sure to do a dummy change in the object you don t them to see anymore, this will allow the system to retrigger the determination access context and remove it from the list... 3 6. You want to activate Buying center in SAP Hybris Cloud for customer...3 7. You are trying to delete a custom opportunity status; however, you still have data consuming it...4 8. If you are replicating opportunities from ERP to C4C, the requirement is to exclude one involved party from C4C as well as from a Realignment run for example...4 9. Your users are complaining that they can see opportunities that they are not the owner...4 10. You noticed that the field probability is not working per the Sales Cycle defined in the business configuration Sample Question... 4 11. You want to have reject word in the approval process for Opportunities...4 www.sap.com/contactsap 2017 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

FAQS OPPORTUNITY MANAGEMENT 1. You want to create forecast based in set of opportunities, however you are unsure in what is basic settings you need inside an opportunity to make it work In order to make the forecast working, please make sure inside an opportunity you have set the following criteria: Publish to Forecast: this flag needs to be checked in the opportunity; Owner: ONLY if you are the owner, the opportunity; Sales Unit: this should match the forecast sales unit, only then will the system pulled it up - this needs to be linked to the owner; Time Period: start and end-date of the opportunity need to match the forecast period. 2. You want to start working with Revenue split, what is the criteria you need to make it work: Revenue split of an opportunity can be split by the sales team; however, a BC question needs to be marked, please check the question below: BC Question: Do you want to split revenue between sales employees; 3. You noticed that Revenue schedule is not automated when you change an amount for example This is the system behavior, in case you have modified the deal for example, you will need to create a new Revenue split to make the data consistency, however, they are PSM released so you can enhance it from your side. 4. You don t want homeless opportunities to be seen by everyone in the company, you would like to have it only for unrestricted access for opportunities instead. To achieve the desired scenario, you will need to make the following BC question: Do you want the access context 1015- sales area restriction to be effective only for objects with employee or territory assignment? 5. You have restricted an opportunity access for a user, however, they are still able to see the data. Even after modifying an access for a user, please make sure to do a dummy change in the object you don t them to see anymore, this will allow the system to retrigger the determination access context and remove it from the list 6. You want to activate Buying center in SAP Hybris Cloud for customer Buying center will help you understanding the relationship within the partners involved in the buying process. To make it available in the system, you need to decide what type of relationship you would like to have. Formal relationship: the question will be Do you want to enable buying center based on buying center relationships? 3

Informal relationships> Do you want to enable buying center based on Business Partner relationship? 7. You are trying to delete a custom opportunity status; however, you still have data consuming it The system will not allow you to delete a custom status from the business configuration while you have data being consumed, this is because you have subsequent documents that consumes the same data. Depending on the status, you can remove the object directly from the in the cogwheel and delete. 8. If you are replicating opportunities from ERP to C4C, the requirement is to exclude one involved party from C4C as well as from a Realignment run for example SAP Hybris Cloud for Customer allows you to define which involved party you do want to exclude from an inbound integration scenario as well as from realignment run, the configuration can be found in the following steps: Go to Business configuration. Implementation projects. Open activity list. Search for Opportunities. Click on Involved parties. Check the inbound integration Colum. 9. Your users are complaining that they can see opportunities that they are not the owner SAP Hybris Cloud for Customer will show to the user in the filter all the opportunities they are the owner plus the ones the user is assigned as a sales employee. 10. You noticed that the field probability is not working per the Sales Cycle defined in the business configuration Sample Question The probability will stop if the user is defined manually in an opportunity for example, the system will not retrigger the probability in case manual change is done. 11. You want to have reject word in the approval process for Opportunities There are two selections while working with approvals: Approved Send back for revision 4

You can have a reject button via PDI implementation, or as an alternative you can use Language adaptation to change label to reject instead of send back for revision. 5