on 05-04-2012 5:30 PM
Hello!
we are defining our own application to release transport request via RFC and we
are using BAPI_CTREQUEST_RELEASE trough SOAP-RFC service.
Unfortunately we are getting the following error:
-<TYPE>E</TYPE>
<ID>TP</ID>
<NUMBER>608</NUMBER>
<MESSAGE>Could not start transport control program
tp</MESSAGE>
<LOG_NO/>
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>4</MESSAGE_V1>
<MESSAGE_V2>connection closed (no data)</MESSAGE_V2>...
If we call the BAPI directly trough SE37, the functionallity is working and also
release functionallity is fine in transaction SE09-10...
It seems that the second jump via RFC (the first jump is our RFC call to the BAPI) to the CALL FUNCTION 'RFC_TP' is not allowed. The only workaround that I founded is to create a RFC and call the BAPI in background mode using a submit via job...... and it works.
Any idea about this? Do you think is not possible to do this or do we have a problem in our system tp configuration?
Thanks to all!
Fernando.
I was looking for other solutions but didn´t find anything..... I will call a job.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.