cancel
Showing results for 
Search instead for 
Did you mean: 

Status Changes in CHARM

Former Member
0 Kudos

Hi Everyone,

I am currently working with CHARM in solman. I use the transaction 'CRMD_DNO_MONITOR' . Here there are two status system status and user status. The user status is set by the user like in development , to be tested , successfully tested etc., My problem now is i need to find out whether the user status is changed or not ... searching in sdn i got the idea of using the badi 'ORDER_SAVE'. I checked this badi, while debugging this i found out the status is changed (using CRM_ORDER_READ FM). This gives me the current status . But i need to find out whether my status is changed r not .Can anyone suggest me a way to find out whether the status of a particular change document is changed r not .

Thanks & Regards,

Kevin.

Accepted Solutions (1)

Accepted Solutions (1)

khalil_serrhini
Contributor
0 Kudos

Hey kevin

i ve already faced this problem and found a solution to it. The difference is that it was on the subject field change and not on user status. But the algorithm is the same

Each time a change is done on a ticket (before saving) a badi is called. According to the field different badi are called (like ...order*adm_h, ...activity_h, ...) - I don t know which one is called when status changes BUT there is definitely a badi that is called (u can use debugging on CL_exithandler to find out which one)

in this badi you have as a parameter the first value that you ll export thanks to an EXPORT MEMORY ID. Once you ll be in Badi ORDER_SAVE you import parameter and then compare old a new values.

You ll then know if a change occured or not !

PS: don t have a solman system available or i could have seached for the badi concerning user status change

Good luck !

Khalil

Former Member
0 Kudos

Hi,

Thank u all for ur replies . I will find which one is apt and let u know whether it works r not

Thanks & Regards,

Kevin

Answers (3)

Answers (3)

khalil_serrhini
Contributor
0 Kudos

Hello Kevin

use Badi CRM_ORDER_STATUS

called twice: before and after status change !!

Regards

Former Member
0 Kudos

Hi Everyone,

I am still unable to find the correct way to get the status change....So if any one knows the exact way to find out the status change please let me know......

Thanks & Regards,

Kevin.

Former Member
0 Kudos

Hi,

you can create an own automatic action which is executed every time a ticket is saved (BADI EXEC_METHODCALL_PPF).

It has to be executed after the action which changes the status, so i would recommend to give your automatic action a very high sort number like 999.

In the action, you can get the new status with function module CRM_ORDER_READ_OW and the old status with CRM_STATUS_READ.

Hope this helps,

Christoph

Former Member
0 Kudos

hi christoph,

Thanks for ur quick reply.

I checked those FMs , but i gives the same output. When i changed a particular ticket and checked these FMs , it returned the same status. No difference between these FMs output. And also i am not using ACTIONS .

Thanks & Regards.

Kevin.

Former Member
0 Kudos

Hi Kevin,

in Badi ORDER_SAVE you can not get the new and old status because the status change has not been executed at this time.

I fear you will have to implement an action to realize that.

Greetings,

Christoph

Former Member
0 Kudos

Hi Christoph,

I knew that the status change has not been executed at this time in badi 'ORDER_SAVE' . Only new(current status) is only found there. Actually what i am expecting is whether can we find out that the status has been changed r not in that badi....if so how...or else is there any other way to find out that there was a status change in the ticket(change request).

Thanks & Regards,

Kevin.

fernando_rocha1
Participant
0 Kudos

Hi Kevin,

We can see the status change in the CRM document.

1 Go to CRM_DNO_MONITOR

2 Choose an correction e.g. 800000123 and open it

3 Go to menu Extras -> Change Documents

Here, you will be able to see if the status was changed, who changed it, time, etc.

I hope this helps.

best regards,

Fernando Rocha