|
Your SAP Resource » Publications » SAP Experts » Solution Manager Expert Online |
|
|
SAP Solution Manager
|
Part of the
|
|
|
|
|
|
|
|
Knowledgebase » Volume 3 (2010) » Update 1 Quick Tip:
|
|
Learn a fast, but effective, configuration setting that can help prevent redundant gaps between support notifications, change requests, and Change Request Management (ChaRM) identification numbers. |
Categories: Administration, Change Request Management, Issue Management, Service Desk, Solution Manager
When you open a business transaction in the Service Desk, you may notice that an identification number is immediately issued for you. You also may not have intended to save the transaction, but there is now an irreversible numerical gap between your actual business transactions. Either of the following scenarios can create a business transaction identification number that results in this gap:
Consequently, the total business transaction count across Issue Management, Service Desk, and Change Request Management (ChaRM) is inaccurate during reporting. Regardless of your intent, the next identification number in line is now taken and a gap exists between your actual Service Desk messages. In this article, I walk you through the steps to prevent these unnecessary gaps and avoid erroneous reporting data.
Would you like to see the full version of this article?If you are an electronic license holder to Solution Manager Expert, please click here to log in. If you would like information about becoming an electronic license holder — and having 24/7 unrestricted access to all articles and content in the Solution Manager Expert online knowledgebase — click here to see the available subscription options. Or call 1-781-751-8799 to speak directly with a subscription and licensing specialist about customized access for you and your team. Isn't your SAP implementation worth world-class information support? |
|
Copyright © 2010 Wellesley Information Services. All rights reserved. Email: customer.service@solutionmanagerexpert.com.
|
