Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SM58: RFC Transaction registered

Former Member
0 Kudos

Hi all.

I try to excute a function module in background task, but it doesn't work.

In SM58 all I can see is a line with status "Transaction recorded".

You can process it manually by Edit - Execute LUW, but it should be done automatically.

I think it may be something wrong with the RFC connections.

Can anybody tell me which parameters, tables, transactions, ... I have to check?

Thanks in advance,

Santiago

5 REPLIES 5

Former Member
0 Kudos

I believe you are missing a COMMIT WORK in your calling program.

Help on call in background has statement:

When the COMMIT WORK statement is executed, the function modules registered for the current SAP-LUW are started in the order in which they were registered. ROLLBACK WORK deletes all previous registrations for the current SAP-LUW.

Andrew

Former Member
0 Kudos

hi Santigo

check if u have written COMMIT WORK after calling FM

regards

ravish

<b>plz dont forget to reward points if helpful</b>

Former Member
0 Kudos

Hi all.

I think the problem is not the COMMIT WORK (the function module makes a call transaction, which has a COMMIT WORK associated).

I forgot telling you these points:

- We have several function modules in background task with the same problem

- They work correctly in production enviroment but not in development and test enviroments

- We think Basis people has changed any paramater that might affect all processes in background task. So we think it is a global problem.

Thanks in advance.

Santiago

0 Kudos

Even if the function module has a commit work in its call transaction, that is not being executed because the function call is recorded but not processed.

In later versions of SAP there is now a need for explicit COMMIT WORK in a number of cases where it previously was not needed - eg when sending an Email, a process that worked fine in 46B required an additional commit to work in ECC6.

Andrew

0 Kudos

Hi.

We are in 46C.

We have a big number of processes affected: workflows, IDocs, call functions in background task, ...

As I said before, its a general problem.

Regards.