Data Service 4.2 SP01 - Abap Program Error

Hi Everyone,

We are testing an update for SBOP DATA SERVICES 4.2 SP01 PL 2, but when we tried to execute Jobs that contains “Abap DataFlow R3” component, but we receive the next error:
RFC CallReceive error <Function /BODS/RFC_ABAP_INSTALL_AND_RUN: RFC_ABAP_MESSAGE, Changes to Repository objects are not permitted in this client)- Changes to Repository objects are not permitted in this client[SAP NWRFC 720][SAP Partner 731][PRD][][<ds_username>][4103]>.

So, we search for BODS/BODS group function, but it doesn’t exist in our SAP ECC, then we tried to upload the transport files located in X:…\Data Services\admin\R3_Functions\transport (K900187 and R900187), but it failed too, the error says that the files are too old for the SAP ECC version, in fact the readme.txt file there mentions that we don’t need to load the files since we have SAP NetWeaver 7.31.

Could someone please help me to get, locate or generate these BODS/BODS group functions in our SAP ECC?


Megahanx :costa_rica: (BOB member since 2008-10-21)

ECC Version?

I think you are trying to run jobs in “Generate and Execute” mode in PROD.

Try “Execute Preloaded” with your Programs migrated to PROD


ganeshxp :us: (BOB member since 2008-07-17)

Thanks ganeshxp,

I have heard about it many times, but the thing is that we don’t understand why in Data Integrator worked with the option “Execute and Generate” in DEV, CAL and PRD, but now in Data Services 4.2 it seems that I cannot longer execute and generate in PRD or CAL…

Now even if I run the jobs in “Execute Proloaded” mode give the next error:

<<< Error creating RFC function </BODS/ABAP_RUN>: <RFC_ABAP_EXCEPTION-(Exception_Key: FU_NOT_FOUND, SY-MSGTY: E, SY-MSGID: FL,
SY-MSGNO: 046, SY-MSGV1: /BODS/ABAP_RUN)>. Notify Customer Support. >>>

Thats the reason why I looking for BODS/BODS functions… :crazy_face:


Megahanx :costa_rica: (BOB member since 2008-10-21)

From which version are you coming? Since 4.1 the application actively checks the client.

There is no way to work around that. So start using the transport mechanims of SAP for the background jobs…


Johannes Vink :netherlands: (BOB member since 2012-03-20)

Thanks Johannes,

Could you be more specific with “Since 4.1 the application actively checks the client”?

We came from Data Integrator 11.7, after that we were with Data Services 4.0. But now we are forced to update to Data Services 4.2 because it’s only the version compatible with Business Objects 4.1.

Also we have around 150 Jobs using DFR3 Abap program, and our basis team told us that there is no sense in work with transports from DEV and CAL in order to execute an abap Job from DS in SAP-PRD. In a nutshell they said that it means a lot of work for them, and DS must be able to generate and execute programs in DEV, CAL and PRD as Data Integrator or Data Services 4.0 used to do.

What can I do to make they understand or believe me?


Megahanx :costa_rica: (BOB member since 2008-10-21)

Since 4.1 there is no option to generate & execute abap in production. Or you need to open the client (NOT an option).

Talk and complain to SAP. They changed the behaviour of the product, without clearly communicating (oeh! lawsuits!) and even the documentation of 4.1 suggests that you still have the option to generate and execute abap in production.

I’d suggest that you also take this topic up with your contract management (if there is such a thing in your company). This is can be used in the contract negotiations for pricing. Or even a claim…

Regarding your basis team: most of the jobs are not going to change. So it is once effort to move them all to production. And the first time I guess you can bundle them in 1 transport etc. I think the jobs also all have a certain development class? Maybe there are options to transport the jobs in one go.

Some information:
http://wiki.scn.sap.com/wiki/display/EIM/DataServices+and+SAP+Security

But nothing about checking if the client is open or not.


Johannes Vink :netherlands: (BOB member since 2012-03-20)

Hello Megan,

you have to contact SAP support for this one I think.
Have you checked my post?

Problem viewing data between BODS 3.2 and BODS 4.2


aragornII :belgium: (BOB member since 2006-12-21)