
I would define the interface components in data dictionary and then (as a placeholder for the 3rd party software in SAP) an empty function module incorporating the interface references. Up to 4.6C SAP function builder can create the visual basic coding which must be reviewed and corrected, but it saves a lot of time. Lastly you must define a logical destination like “3rdparty” in SAP (sm59) to itentify the 3rd party software.
In the SAP user exit you may call the placeholder function module, extenting the call with “destination 3rdpart”.

Two ideas:
1. Use WS_DOWNLOAD() (or whatever?) to export the data to the workstation from the user-exit. Write a VB executable that reads and validates the data - also call it from the exit with WS_EXECUTE() just after the download. Reverse the process to import the results. Sounds yucky but it works smoother than it sounds.
2. VB works great with RFC’s directly but you need to know how to generate a FRC interface via the SAP DCOM compiler and incorporate it into a VB prg. Then you have a little smoother integration.










