topic Re: Some doubts using abap in Application Development and Automation Discussions

Some doubts using abap

Former Member — Sat, 02 Aug 2008 09:19:06 GMT

Dear experts,

I have used functionmodule as RFCs to fetch data from SAP

using java/jco.Here i realised that all work has to be done in sap itself.Java is just a platform to fetch that object and show me the data.

However i wish to know can i use native java platform itself

ie only jdk installalation with jco to write reports and fetch output just as i work in se38.

Is there any separate java library for this where i can use joins ,pass querys just as i do in normal abap.

Am i close to netweaver ,these questions are alway budding in my mind

Regards,

Aditya Sharma

Re: Some doubts using abap

Former Member — Sat, 02 Aug 2008 11:49:35 GMT

As far as i know it is not possible. If it is netweaver u can that.

else u can manipulate the fetched data.

Re: Some doubts using abap

ian_maxwell2 — Sat, 02 Aug 2008 19:59:20 GMT

This is an area that I've gone changed my view on over the years.

When Netweaver was first introduced with it's dual stack (ABAP and Java) I was frustraited that you couldn't access the ABAP DB Schema from the Java side of the stack. The architecture (which you can get aroudn if you really want to, but I wouldn't reccommend it) forces you to use either RFCs or WebService calls to access data on the ABAP stack from the Java stack.

As time has gone on though I have realized that this is actually a good setup from an architecture perspective because it forces you into a seperation of concerns where your ABAP modules are implimenting a buisenss object layer around the data in the ERP system. Additionally if you are building a composite application that combines SAP functionality with that of services provided by other applications then this actaully keeps some architectural purity to it becuase the SAP ABAP system is treated the same as any other system that it is utilizing.

So my recomendation would be to stick with service calls accross the stacks and not direct DB access. In the end you'll have applications that are architected better.

~Ian