topic Re: BAPI or RFC for migrating and activating code? in Application Development and Automation Discussions

BAPI or RFC for migrating and activating code?

GQ2 — Thu, 14 Apr 2016 21:13:36 GMT

Hi -- admittedly this sounds like a security concern, but trying to think of ways to automate installation without a lot of manual steps.

Is there any standard RFC's or BAPI's that we could push through a transport or something and then activate it? Maybe even a software component with patches?

Re: BAPI or RFC for migrating and activating code?

Sandra_Rossi — Fri, 15 Apr 2016 06:54:12 GMT

I don't get what you want to automate. If you mean you'd like to execute some ABAP code at import time, then the most simple is to enter a program as a R3TR XPRA entry in the transport request. If you want to execute some code for different dummy or not objects, then you may create a new customizing object in transaction SOBJ, and define an "AFTER_IMP" function module, then enter the entry R3TR Z001 <object> (Z001 being the customizing object). Search forum for more details.

Re: BAPI or RFC for migrating and activating code?

GQ2 — Fri, 15 Apr 2016 12:41:34 GMT

I mean, I want to use RFC to install code, not to execute it.

Re: BAPI or RFC for migrating and activating code?

larshp — Fri, 15 Apr 2016 13:00:00 GMT

do you need it for only code, i.e. PROG/CLAS/FUGR objects? Or do you also need domains/database tables/views/search helps/etc?

depending on your SAP release you could theoretically misuse the ADT(abap development tools/abap in Eclipse) RFC interface. But I dont think its documented, so you have to dig into the code to figure out how to use it.

You can also consider looking into saplink.org or abapgit.org , both will require some extra code to be able to trigger a push remotely. But they already contain the parts for installation of ABAP objects.

Re: BAPI or RFC for migrating and activating code?

GQ2 — Fri, 15 Apr 2016 13:34:00 GMT

Very good idea Lars, I'll try the ADT service.

To be specific, I want to push through an OData service, and turn that on.

There are a ton of specifics here: http://help.sap.com/download/netweaver/adt/SAP_ADT_Configuration_Guide_Backend_en.pdf

I suppose I can do a trace between Eclipse tools + gateway to see what kind of parameters it's passing?

Re: BAPI or RFC for migrating and activating code?

larshp — Fri, 15 Apr 2016 17:28:08 GMT

yea. As far as I know Eclipse wraps the REST call into an RFC call by default, so you can switch on RFC trace and use external breakpoints.

The data passed to the RFC can then be reused to pass to the SICF REST service.

And most surely none of this is supported or encouraged by SAP