Hi All,
As per the below link
I tried to do the ABAP upload to SAP ECC, but getting the below error.
Here I’m attaching my R/3 data store config settings and the error log.
I have strode generated .aba code in local drive in the below path
C:\Program Files\Business Objects\BusinessObjects Data Services\Admin\abap
Can someone guide me to correct this issue?
Thanks in advance.
Regards,
Sabitha.
SDS_ABAP_settings.doc (218.0 KB)
Sabitha Mandla (BOB member since 2012-07-20)
The idea of execute_preloaded is not to have the ABAP program generated on a local drive but to install it in the SAP system so we call it only.
http://wiki.sdn.sap.com/wiki/display/EIM/Moving+ABAP+to+Production+(DI+12.1)
http://wiki.sdn.sap.com/wiki/display/EIM/Moving+to+Production
Werner Daehn 
(BOB member since 2004-12-17)
Hi Werner,
We have the process in place to create ABAP programs and transport them to production.
But when I came across a link
http://wiki.sdn.sap.com/wiki/display/EIM/Moving+ABAP+to+Production+(DI+12.1)
'In DI 12.1 a new feature was introduced to upload the ABAPs with the click of a button.
What does it mean
are we going to create ABAP programs in SAP from DS with upload properties option?
If yes, please let me know where I’m doing wrong from my config settings.
Please clarify the purpose of this option.
I have another request, as we have couple open issues and a critical issue to execute a job in production environment. The job uses R/3 and APO data stores based on our Business requirement. Same job runs fine in development environment…
Can you help on consulting with us for our issues?
Please let us know how to get your consulting time.
Regards,
Sabitha.
Sabitha Mandla (BOB member since 2012-07-20)
Many questions but actually it is all very simple.
The standard way (as described in the second link of above’s post) is somebody writes ABAP source code, this is copied into a se38 transaction, saved, then released to be transported to prod and finally ends up there.
How ABAPs are transported in your company depends, you should ask one of your SAP Basis people for help. There will be documents to be filled out, naming conventions to be followed etc.
What we have done for you in 12.1 is that you no longer have to copy the source code into the se37 SAP transaction. You rightclick an ABAP dataflow, say generated abap and in the next dialog you check the “upload” box. Then this first manual step is done for you by the tool, doing the exact same things you had done for you. After that the abap is available in dev and can be released, transported etc just like before.
If you really need help with that, please send me an email and I will setup a call with you for an hour or two to get your started.
Werner Daehn (BOB member since 2004-12-17)
Hi Werner,
Thanks for the details.
Yes we would like to explore and utilize this option.
Right now we copy the generated code from DS to a word document and send it across to ABAP development team they create programs in SE38 and copy this code into it and create a transport to migrate to production.
Please setup some time to go through these details.
FYI : I’m in US central time. I can take your call outside of work hours. Please setup some time at your convinience.
Appreciate your help.
Regards,
Sabitha.
Sabitha Mandla (BOB member since 2012-07-20)
Please send me an email to discuss the details. Most of my contacts are in Palo Alto, so I am used to work late.
Werner Daehn (BOB member since 2004-12-17)