Does anyone here have any experience using VB6 to send data to a SAP ERP system using SAP's "Exchange" functionality? I may be having to develop an app that does this and would like to get some idea of what I'm up against. Thanks.
Does anyone here have any experience using VB6 to send data to a SAP ERP system using SAP's "Exchange" functionality? I may be having to develop an app that does this and would like to get some idea of what I'm up against. Thanks.
Perhaps there is something new but the term "SAP Exchange" generally refers to its connection interface to MS Exchange Server. There is no "VB" involved. The other points of automation are just ActiveX component suites. Thus the issues are the same as if 'connecting' to Office, MSAccess, etc. You need to be more specific. -ralph
On Mon, 23 Apr 2007 15:56:57 -0500, "Ralph" Ralph - Thanks. I can't be much more specific just yet because I simply don't know *anything* about this yet. I've been asked to participate in a conference call to be conducted by our sales people dealing with a potential customer who will want our software to "communicate with their SAP system". I Googled around a bit and found reference to SAP's "Exchange" functionality and thought maybe that might be what my program would be communicating with. Could you possibly point me to something on-line that explains what you referred to as "other points of automation" ? Thanks again for your response. Martin
<snipped> Since this is a VB newsgroup then DCOM would be appropriate. Check out this document for an overview... http://www.**--****.com/ %20Connectors.doc Then just google on terms of interest. A narrower view... http://www.**--****.com/ Notice the abundance of acronyms and how they all mix 'n match. But the real fly in the ointment (there's always a fly doing the backstroke somewhere <g>), is that while ERPs are sold with the banner of a 'single software solution', in practice each installation is often so customized each is quite unique. Occasionally not even recognizable at first glance. Thus a small warning: An initial problem will be the "new-speak". Organizations that adopt SAP will integrate it into their own business model. (Duh! <g>) But will also tend to apply legacy names to SAP models. So don't jump to conclusions - just because they called something a 'pool' doesn't mean it is. <g> hth -ralph
Fly in ointment department: as of SAP GUI version 6.40, the RFC library does not support DCOM, it supports .Net. Depending on the customer's version, you might have to do what I had to do, and start wearing a VB.Net hat part of the time.
On Tue, 24 Apr 2007 08:01:26 -0700, "Steve Gerrard" Steve - Thanks - that's extremely useful to know. The last thing I want to do is get in to the .Net stuff.
does not might time. [Stepping very very carefully here... <g>] Actually because of the distributed nature of SAP's "connections" .Net is a bit easier to use. If your app is COM then you can still use interopt. Just don't plan on designing any icons with lightning bolts on them. <g> -ralph
Dear All Currently we have an issue with forwarding messages received through a SAP connector. A he maximum time for delivering the message expirednon delivery report is returned. According to TechNet article 319023 (You Cannot Forward Messages that You Receive Through an SAP Connector), the SAP connector needs to be configured to use an expiry date that is not later than 12/31/2050 Does anyone knows how to do this? (We are running Exchange 5.5 SP4 Thanks in advance Olivier
Users browsing this forum: No registered users and 96 guest