I have a general question concerning SAP API resp. reading SAP data (from transaction queries) and processing in third-party module.
Is there a best-practice?
Just to make it clear what we need to do I´ll step a little more into detail and our first approaches..
A "mighty" BAPI which you pass a transaction qualifier and some input parameters to SAP (via JCo e.g.) The resultset will be false or filled with data (e.g. xml) you would expect when filling and submit the SAP GUI transaction form.
A SAP scheduler that saves an export list as SAP-Internal-XML corresponding to some presets (e.g. filters) to disk. A highly dynamic scheduler in preference to one scheduler per requested transaction result.
A web service (via XI e.g.) which passes transaction queries defined by some parameters when requested by third-party. A dynamic technique (like "select * from transaction-x) would be the silver bullet.
We want to avoid re-engineering SAP (transaction) logic by combining several BAPI / IDOC calls in third-party e.g.
I´m open to suggestions :)
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!