Skip to Content

F4 Help Restriction using Std BAdi not start with VBA in AFO


I have implementd the F4 Help restriction with a BAdi.

I have created an AFO with several sources, for performance, the options for update at first are unchecked and i refresh sheet by sheet with vba code with the setences

lResult = Application.Run("SAPExecuteCommand", "Restart", X)
lResult = Application.Run("SAPExecuteCommand", "Refresh", X)

but at first execution the F4 Help restriction is no trigger (i have put a break-point and the system doen't stop).

IF i cancel the input window and refresh the AFO the evet is started.

Do you know some setence in VBA to force the F4 event.

Kind regards.

Add a comment
10|10000 characters needed characters exceeded

Related questions

0 Answers

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.