2012 Dec 05 7:08 PM
Hi,
We have got a z program in which we do material avialaibility check using BAPI_ALM_ORDER_MAINTAIN.
When we run this program in batch we got a the job cancelled with error 'Communication_Failure'.
This came on a Z RFC FM to create WBS which is written in a BADI and this FM is parallel processed using keyword starting in new task
So can anyone tell me what could be the possible reason and how can i avoid it in future.
Thanks
Hi,
We have got a z program in which we do material avialaibility check using BAPI_ALM_ORDER_MAINTAIN.
When we run this program in batch we got a the job cancelled with error 'Communication_Failure'.
This came on a Z RFC FM to create WBS which is written in a BADI and this FM is parallel processed using keyword starting in new task
So can anyone tell me what could be the possible reason and how can i avoid it in future.
Thanks
2012 Dec 05 7:33 PM
According to the help on STARTING NEW TASK you need to use the DESTINATION IN GROUP <group> addition, where group defines a group of your application servers. The communication failure might be due to the fact that it doesn't know what server to use.
I hope this helps.
Regards.
2012 Dec 06 6:40 AM
Hi Steve,
We have used destination none as we call this FM on the same system.
We have actually created this z fm as RFC as it is called in work order save badi and we have to set some user status on the WBS which we have to commit.
Any other thing you can suggest.
Regards
Atrinandan
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |