proxy call restriction

[Former Member]

hi experts,

i am using JMS to proxy async scenario. in the proxy i am using call transactions to update one transaction. the scenario is my message can contain multiple records which needs to be updated in a transaction. now lets say i have sent one message with 100 records and the proxy takes 5 min to update the transaction with all the records. meanwhile another message with 50 records has come to SAP system and opens another proxy session. As the first proxy session is updating that transaction, second session update will fail saying " the transaction is locked by so and so user". How do i eliminate this problem. is there any way i can make the proxy session wait until the previous session got completed?

thanks

[Former Member]

not answered

[former_member187339]

Hi,

I dont know whether you got a solution for your problem.

But can't we go for EOIO processing in Proxy side. Something similar as shown in this blog:

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417200%29ID1124433650DB1059249387145227120...

Regards

Suraj

[Former Member]

please use call transaction plus batch input.

Like if call transaction gets fails you create session for it and later on you can exucute them.

For help here is one example:-

http://www.erpgenie.com/sap-technical/abap/batch-input-and-call-transaction

Regards,

Sunil

[Former Member]

hi

unfortunately batch input sessions i can not use as i need to send the succ/failure status back to XI in real time