cancel
Showing results for 
Search instead for 
Did you mean: 

SO not triggering updated idoc

Former Member
0 Kudos

I have a vendor PO that updates the customer SO. In my case, when any change is made to the SO, it has to trigger an idoc.

If I go manually into the sales order and make any changes, it will trigger the idoc immediatley with no problem. But if the PO makes changes to the SO, the SO gets updated but does not trigger an idoc with the updates.

How can I fix this? thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Vaz - I am assuming that you have a customized routine to update the sales order from the IDOC generated out from PO. While you are posting the IDOC onto the sales order and you want it (sales order) to generate another IDOC, you can code to Submit the condition type associated with the IDOC you are expecting. The way I know we can trigger an output condition from a sales doc is to SUBMIT RSNAST00 with KSCHL as the condition type, application V1, object key as the sales order #. Your ABAPer should be able to code it perfectly (I am a functional, sorry for trying ABAP here !).

Hope this helps !!

Thanks

Nikhil

Former Member
0 Kudos

thanks for the quick reply. I am functional as well, but a newbie at that. Thats why I'm not able to solve these problems completely.

The idoc is already being triggered from the sales order, but only when it is saved manually. I'm going to have to speak to the abaper and see how this coding is exactly done and try to get it fixed.

thanks

Answers (1)

Answers (1)

Former Member
0 Kudos

In this case did you checked the change log.

Did change log shows all the changes.

If shows all changes then you have implement logic in requirement routine.

Get all change log information(CDHDR/Item table) and trigger output .

Let me know if you are not clear.

Thanks,

Narayan

Former Member
0 Kudos

I am not sure of how to check the change logs.

But I was doing a trace on to find which programs (if any z fm) were being called. And since I did that, the idoc was being triggered with no problem.

After a couple of times trying to get that checked out, the problem has seemed to fix itself.

I still need to pass a few more test files thru it just to make sure.

Former Member
0 Kudos

How to check change log.

VA02>From Menu ba>Click Environment-->Changes

Thanks,

Narayan