topic Re: Issue with Batch Input Interface for Vendors in Background running in Application Development and Automation Discussions

Issue with Batch Input Interface for Vendors in Background running

former_member207873 — Wed, 12 Aug 2020 08:21:39 GMT

Hello Experts,

I am running an Zprogram where in i am submitting the program for BI program for Interface for vendors(rfbikr00). But unfortunatly in SM35 it works good in foreground, but not in background. I am getting the error . Account ** is currently blocked by user * . It is understandable that the system is locking for a vendor and changing and at the same time is doing another change for the same vendor . How to rectify this issue.

Best Regards.

Re: Issue with Batch Input Interface for Vendors in Background running

FredericGirod — Wed, 12 Aug 2020 08:26:22 GMT

run your job when nobody work ...

ensure, you are not locking yourself

Re: Issue with Batch Input Interface for Vendors in Background running

former_member207873 — Wed, 12 Aug 2020 08:44:55 GMT

frdric.girod,

Thanks a lot for your answer. I am locking myself. That is the problem. So i am not sure how to prevent it. Normally while working with call transaction we can give a wait up to. But how to do it in a background job ?

Re: Issue with Batch Input Interface for Vendors in Background running

Sandra_Rossi — Wed, 12 Aug 2020 09:37:43 GMT

Most probably you would have the same issue in foreground too. The reason is probably because the locks are retained during the asynchronous update task and so it blocks the anext transaction. With CALL TRANSACTION USING, you may wait the end of the update task (works like adding AND WAIT to any COMMIT WORK) or eventually make the update task local if you prefer.

Re: Issue with Batch Input Interface for Vendors in Background running

Sandra_Rossi — Wed, 12 Aug 2020 11:17:25 GMT

Please, "you should only submit an answer when you are proposing a solution to the poster's problem".

Re: Issue with Batch Input Interface for Vendors in Background running

Sandra_Rossi — Wed, 12 Aug 2020 11:23:42 GMT

Maybe there are several possibilities to run a batch input session with synchronous or local update task, but the only one I know is via the program RSBDCCTU (update mode = S or L).

Re: Issue with Batch Input Interface for Vendors in Background running

former_member207873 — Wed, 12 Aug 2020 12:26:22 GMT

Sandra Rossi,

I still have the same issue even if i run it through RSBDCCTU . (Update Mode = S or L ) and background processing . Account *** is currently blocked by user ***

Re: Issue with Batch Input Interface for Vendors in Background running

Sandra_Rossi — Wed, 12 Aug 2020 12:35:38 GMT

Based on your initial assumption concerning the difference between foreground and background, I initially answered that probably it was about a technical lock, but now I guess it's a functional blocking and so the transaction which produces this error should behave the same in foreground and in background.

If you search the Web, you can see the problem is already discussed (solve by MK05 or FK05, etc.):

"Account" "is currently blocked by user" site:sap.com