Professional Documents
Culture Documents
Blogs
Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Subscribe
Riccardo Escher Print
Business Card
Company: Osram GmbH Permalink
Posted on Aug. 21, 2009 12:06 AM in SAP Solution Manager
Introduction
Within the German User Group (DSAG) I founded 2007 a customer workforce group which aimed to ehnance the stability and the ergonomics of the Solution Manager Change Request Management
(ChaRM).
During the DSAG technology days in Februay 2008 we consigned our development request to the SAP representatives. But (freely adapted from G. W. F. Hegel) St. Anthony of Padua, as he
sermonized to the fishes, achieved more than I caused with our workforce group and our detailed paper full of screen shots and explanations.
So, after 18 month of waiting for an answer I decided to implement some of the needed enhancements and to share them with you, the SDN folk. May be this will stimulate a couple of developers
to open their treasure box too, so I will have less to code :-).
(the only way to see the user status values (E00*) I know of is to have a
look with SE16 into table TJ30).
Smartform action
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010
SAP Network Blog: Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Page 2 of 7
The action is partner dependent, so we insert the partner function we have created for the security team(s) in our partner schema (ZOSR0002).
It is important that there can be only one unprocessed action at a time.
By the way, we have copied with transaction SMARTFORMS the smartform CRM_SLFN_ORDER_SERVICE_01 (which can be found in the action profile SLFN0001_ADVANCED in the action
SLFN0001_ADVANCED_MAIL) to our name space (ZSV2I_OG_CHARM_SERVICE_06) and then we have adapted this Smartform to our needs (not so interesting in this blog).
Now we maintain the „Processing Types" to insert our smartform informations (Button „New Entries", F4-Help for the action, Selection of "Smart Forms Mail").
Now we mark the new line and press the button „Set Processing":
Now you can insert the technical details of the Smartform action:
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010
SAP Network Blog: Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Page 3 of 7
Conditions
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010
SAP Network Blog: Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Page 4 of 7
In the right screen we press on the button "Create" and we select our newly created action (you may control the details of the action definition in the first two tabs "Overview" and "Processing
Details"):
First we create the schedule condition itself; to do this we go to the tab "Schedule Condition":
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010
SAP Network Blog: Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Page 5 of 7
We press the button "Edit Condition" and we jump into the most popular Condition Editor; we give a name for the new condition (they can be reused for other actions) and, as suggested, we simply
click into the empty "Condition Definition":
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010
SAP Network Blog: Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Page 6 of 7
Result
We have now a mail action which will be scheduled only when the document is in status "In development" but started only when the status has changed to "Critical Authorization Check". You can
save the transaction as many times as you want during development: the e-mail action would keep there as unprocessed (you can see it with the tab "Actions").
Here an example for the Staus E0002 "In development":
Tip
When the action weren't scheduled and you check your customizing on and on without finding an error, you might execute the consistency check of transaction SPPFCADM:
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010
SAP Network Blog: Pep Up Your ChaRM - Part 1: HowTo Create a Smart e-Mail Action Page 7 of 7
Riccardo Escher since 1992 SAP basis developer, always interested in new technologies and without any reluctance in helping SAP to improve their products (messages, user group)
Any comments?
Comment on this weblog
Riccardo,
this is excellent - thank you so very much !
I tried to configure email notification to developer on status change by following note 1275036, and some other document (half in German) - do not work at all.
This your way: short, simple and most importantly - works !!!
Thanks again
Elena
Riccardo
http://weblogs.sdn.sap.com/pub/wlg/15438 3/3/2010