As far as I understand your problem, there is nothing wrong with using RFC. It is apparently the called RFC function that is not made for batch processing. If you use a proper BAPI, no messages should ever popped up, rather the messages are collected in a response table for you to analyze.
If the called RFC does in turn execute a batch input (BTCI), then the typical cause for failure is missing data, that causes to display a screen which is not foreseen in your processing scenario. If the RFC is a self-written one, let it execute with BTCI mode A and watch for screens, where the OK-Code is "blank". This is then a screen, which is not in the expected sequence. You may circumvent the malfunction by adding additional logic to catch these cases. Also, you should execute the BTCI in mode N to catch all messages in a table (CALL TRANSACTION ... MESSAGES bdcmesstab).
If the RFC is a standard function, you may have chance in providing additional data or changing the customizing for your application.
Dig Deeper on SAP application integration
Related Q&A from Axel Angeli
An SAP user wants to know how to upload data into SAP R/3 when SAP Scripting is not enabled. Continue Reading
An SAP user is receiving an error message while integrating SAP iDoc PORDCR1 for a purchase order. Continue Reading
An SAP user is having difficulty with PERNR iDoc while transporting data from SAP to an external system. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.