Q

RFC error message without raising exception

Some RFCs actually issue error messages without raising an exception. When calling such functions from VB it seems...

as though the connection is broken when the error message is issued. Consequently, we cannot check the error message via the connection object. In ABAP we can cater for this type of issue by coding an additional exception "ERROR_MESSAGE" which will allow for trapping the message. How can we deal with such RFC calls from VB? One such RFC is L_TO_CREATE_MULTIPLE.


In theory, RFMs should not do this. L_TO_CREATE_MULTIPLE, on the other hand, is not released for customer use officially. Please report this behavior to SAP as a bug, but since the RFM is not released, they may tell you that they are not going to fix it. Worth a try, anyhow...


This was last published in January 2002

Dig Deeper on SAP Basis administration and NetWeaver administration

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close