The best option below? SAP (Oracle) to MS SQL data exchange
Hello Folks,
I've been going around in circles for the past few days trying to come up with the best option for this issue. Here is the issue and what I've determined. Could you please comment or offer advice on whether my decision is correct.
Issue: We have SAP 4.6C on an AIX box using Oracle. Many times a day we need to populate an MS SQL server database on an external system using data from the SAP system. We are currently using forms on the MS SQL side to manually look at SAP screens and to copy the data over. I've had looked at every discussion on this site and through SAP documentation.
One option would be to create a batch abap program that periodically connects to MS SQL and populates it:
1. HOWEVER, I can't use the Native SQL code in an abap to connect to the MS SQL server since according to OSS note 178949, due to the fact that the SAP system is on a Unix OS, I will be missing a critical DLL file.
The next option is to call and SAP RFC or BAPI externally via ASP:
2. Using a direct connection to the Oracle database is an option (ODBC) but that circumvents SAP security. We are ONLY doing a READ from the Oracle database however (no writes!).
3. DCOM connector is an option but it will no longer be supported by SAP at the end of 2004.
4. .Net connector is the replacement for DCOM connector and seems the best bet.
5. Business connector is overkill for this requirement.
So.... I am leaning towards a .Net connector solution.....
Does anyone have any thoughts????
Thanks!
Isn't ALE/IDocs also a possibility?
Although to be honest it sounds like you've thought this one through carefully and methodically.....
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
You don't say how much data is to be transferred.
Oracle has an tool/script to export (and I think it's called export) all data from a selected table. The script basically basically performs a SELECT * FROM TABLE, sets the delimter to a comma and redirects the output a specified file. The relavent import script is basically an INSERT command which could easily be mimicked by MS SQL I would have thought.
Perhaps it's worth looking into this.
We used to move data from Oracle to a third party system using this method as a conection was not possible. fortunately for me at the time the thord-party product used personal Oracle so it was easy. But, I'm pretty sure this should work with MS SQL.
Dr Sidewalk
_________________
"In the middle of difficulty lies opportunity" - Albert Einstein
"Money isn't everything in life, unless you don't have it". David King
"Fail to plan, plan to fail"
"Success is a journey, not a destination."
You don't say how much data is to be transferred.
Oracle has an tool/script to export (and I think it's called export) all data from a selected table. The script basically basically performs a SELECT * FROM TABLE, sets the delimter to a comma and redirects the output a specified file. The relavent import script is basically an INSERT command which could easily be mimicked by MS SQL I would have thought.
Perhaps it's worth looking into this.
We used to move data from Oracle to a third party system using this method as a conection was not possible. fortunately for me at the time the thord-party product used personal Oracle so it was easy. But, I'm pretty sure this should work with MS SQL.
Dr Sidewalk
_________________
"In the middle of difficulty lies opportunity" - Albert Einstein
"Money isn't everything in life, unless you don't have it". David King
"Fail to plan, plan to fail"
"Success is a journey, not a destination."
Hi,
look at a Tool called Data-Junction. AFAIK they are bought by Pervasive Software. But for this need maybe the right Utility.
cheers
Henning