Expand +



A validated tip for your ChaRM implementation

by Scott Priest, Editorial Director

July 14, 2011

Back at IT 2011, I attended as many sessions as I could from the writers of the knowledgebases I edit, Solution Manager Expert and SAP Professional Journal. I was new to the work, having moved over from Financials Expert and GRC Expert a couple of months before, and in many cases was meeting some of the authors and members of the technical advisory boards for the first time.

One such session, "10 Must-Have Tips to More Efficiently Implement, Optimize, and Go Live with ChaRM," was delivered by Nathan Williams of Enowa Consulting, who has written a number of articles for us. I talked to him afterwards and said he should think about writing another article when he found the time. In the following weeks we talked over a few ideas, and finally Nathan recommended we take the same principles of the session and turn them into an article.

It was a great recommendation, and as you can see here, turned into a great article. Nathan collects these tips from more than 20 full-scale implementations -- so you know they're reliable. Here's a sample of one of his tips:

7. Copy Standard SAP Transaction Types into Your Own Z Customer Namespace

ChaRM is driven by SAP Customer Relationship Management (SAP CRM)-based documents. Rather than modifying the standard document types, you should make a copy into your own customer namespace (i.e., create a Z or Y transaction). Establishing Z transaction types allows you to scale efficiently should new requirements come into scope.

In addition, if a potential bug is discovered in your SAP Solution Manager system and must be escalated to SAP Support, it is easier to reach resolution if the standard SAP transaction types are preserved. SAP Support often requests that you temporarily revert back to the standard SAP transaction type to repeat the error. If the standard transaction type is modified, then support becomes an issue.

Finally, significant modification of standard SAP transaction types may mean an upgrade nightmare down the line. If you’ve customized the standard transaction types and then later apply a Support Package, your customization is overwritten. Creating Z transaction types ensures that your customization is preserved during the upgrade.

Table 3 provides examples o f standard transaction types and their descriptions, along with how they can be copied to a customer namespace. The values for standard transaction types in Table 3 are based on transaction types delivered with Support Package 26 of SAP Solution Manager 7.0. Transaction types for SAP Solution Manager 7.1 will be different, but the practice to copy them to the Z customer namespace will still apply.

For the full article, Solution Manager Expert subscribers can go here. For more information about obtaining a license, go here.

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!