on 12-11-2009 8:10 AM
Hello,
according to OSS 1275036 I tried to implement email notification in my Charm-process using BADI AGS_SDK_SCHED_ST_CHD in my schedule condition. If a new partner is responible in Charm-process, this partner should be notified by email. The email should be send if user status is changing.
It still works for my change request (notification of change manager) and the first step of my change document (notification of developer). But for all following steps (e.g. notification of tester) no action for email-notification is found in my change document.
In my actions I only use schedule conditions (according to OSS) and no start condition. To use the BADI for several user status, I maintained my user status in field value instead of inital value.
Does anybody know, how to use this BADI for several status changes in my change document?
Thanks,
Laura
Hello together,
I solved my problem by using CRM Standardcustomizing. Forgot SAP note 1275036 and 865619. They are all bad and not sufficient for a complex Charm scenario.
I only used note 1275036 for the first mail in my change document (email to developer). For all following mail notifcations I'm using actions based on workflow conditions instead of BADI.
Just using normal CRM-Customizing and create one schedule and start condition for every used action.
E.g. send mail to tester:
schedule condition:
&Servicevorgang CRM.Anwenderstatus& [*] E0002+DHFHEAD
and &Servicevorgang CRM.ErrorFreeFlag& = X
start condition:
&Servicevorgang CRM.Anwenderstatus& [*] E0004+DHFHEAD
and &Servicevorgang CRM.ErrorFreeFlag& = X
This works perfect, because you won't get several mails for one status if you save your document more than one time, which is a problem with note 865619.
Regards,
Laura Mathes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have tried the same like giving scheduled & start conditions . But i couldn't get any mails delivered. Can u help me out by getting me a screen shot of what u have done.... And also i need to know about what have u done in the work flow for this....i mean how to create a work flow relating or linking the actions to it... Please help me with it.....
Thanks & Regards,
Joe.
Hello ,
for this problem I have done a copy of BADI. And then I have change the implementation to my own.
I Think the best to learn what the BADI doing insert a Break Point.
Regards
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Daniel,
thanks a lot for your answer. Seems as we work at the same things in Charm process
I've also got the idea of copy the BADI. But I thought, that it has to go easier. So I send a support message to SAP. They couldn't help and told me to open a thread inside here. Nice support!!!
So it seems that there's no better way than copy the BADI.
Do you have some further informations how you`'ve changed the BADI? Just copy it a often as you want to send a mail notification so you can use one BADI copy for each status?
Thanks for your help.
Regards,
Laura
Hi Daniel
In this case, don't we also have to enter BERSL values along with the User_Status value? For example, in the table TJ30 there are several entries E0002. How would the Action know which one to pick up? So if i want User_Status for SDCR, shouldn't the value be E0002SDMJHEAD ?
Please advise.
Thank you in advance.
Hello,
you are not able to enter BERSL in Customizing, because there's not enough space (only 5 digits). By the side, if you want SDCR, you have to use SDCRHEAD.
It's no problem, that there are more than one value for every status in TJ30, because you define every action for your action profile, e.g. SDCR_ACTIONS.
A bigger problem is, that the values, that you've entered for one action profile will occur in every other action profile in which you use the same BADI. So today I will try to copy BADI.
Regards,
Laura
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.