Skip to Content
0

SAP GUI 7.50 and Excel VBA

Jun 14, 2017 at 07:41 AM

1.5k

avatar image
Former Member

Hi all,

I have upgraded SAP GUI for Windows version 7.40 patch 14 to version 7.50.

but when I run Excel VBA that content BDC Recording to update data on SAP, the script does not work, message error : "Start screen does not exist in batch input data".

when I downgrade SAP GUI to version 7.40 again, Excel VBA scripting can run successfully.

any one can help me?

thank's

Lukman

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Stefan Schnell
Jun 14, 2017 at 10:48 AM
0

Hello Lukman,

I assume you use the ActiveX libraries wdtfuncU.ocx etc. for your BDC recording. In a few cases it seems that the new ActiveX libraries are not working correctly, e.g. you can find here an example and explanation. The best solution seems at the moment in your case to work with the SAP GUI for Window version 7.40.

Cheers
Stefan

Show 6 Share
10 |10000 characters needed characters left characters exceeded
Former Member

hello Stefan,

thank you for your reply, on your other post you are mention about CCo - the COM connector for SAP.

can we use CCo COM for excel VBA ?

Cheers,

Lukman

0
Former Member

Hello Stefan,

Like Lukman, I am having issues trying to run VBA with SAP GUI 7.50.
We have applied patch level 2 and it seemed to have helped a little bit but I am still getting an error after trying to extract the second table.
When I logon to SAP via VBA I manage to extract to Excel the first table (T001P); when it tries to extract the next table I get "Call to RFC_READ_TABLE failed!" and then "No T500P entries found! Execution cancelled."

Note: As an interim measure, I have kept GUI 7.40 on a separate desktop, as there are no issues with it.

It seems to lose the connection between tables. Any ideas?

Cheers!

Rob

0

Hello Rob,

thanks for your reply.

Unfortunately I don't can help you to solve your problem. As Frank Krause wrotes here are these components only available for compatibility reasons. And as I wrote here have these components in a few cases a different behaviour towards to their predecessors. With all respect to the developers of this components, these components are deprecated. You shouldn't use it. There are alternatives like NCo or CCo. It's not nice to say that, but the effort to adapt your programs comes sooner or later up to you, do it now.

Cheers
Stefan

0
Former Member

Hi Stefan,

Thank you for your quick reply. I will look into CCo for VBA. Any guidance you can provide would be much appreciated.

Have a great weekend.

Rob

0

Hello Rob,

thanks for your reply.

You can find a lot of VBA examples into the help file of CCo. If you use the x64 of Office it is not possible to reference CCo in the VBA IDE, so you must renounce code completion, but it works. CCo needs the SAP NetWeaver RFC library in the same directory as itself. You can download the RFC library from the SAP Service Marketplace or you can collect the files from your SAP GUI for Windows 7.50 installation. These are

  • C:\Windows\SysWOW64\sapnwrfc.dll
  • C:\Program Files (x86)\Common Files\SAP Shared\NCo\NET40\libicudecnumber.dll
  • C:\Windows\SysWOW64\icudt50.dll
  • C:\Windows\SysWOW64\icuin50.dll
  • C:\Windows\SysWOW64\icuuc50.dll

Best regards
Stefan

0
Former Member

Hi Stefan,

Thanks for the additional information.

Cheers!

Rob

0