Application Development and Automation 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: 
Read only

In ECC 6.0,Error while executing a code in Background or direct execution, but works fine while debugging

Former Member
0 Likes
971

I am trying to execute a program in ECC 6.0 system which creates invoices.

When I execute this program in background, It shows below error in job log:

The key to reconciliation is blocked by <Fikey> <Username>.


FYI : On every execution reconciliation key is different so it cannot be blocked by any user.

If I executed this directly by pressing F8 then also the same error getting populated in status bar.

But while debugging mode, It is working fine & it creates invoices.

Can anybody help on this problem?

1 ACCEPTED SOLUTION
Read only

kumud
Active Contributor
0 Likes
932

What is the program name?

Regards,

Kumud

7 REPLIES 7
Read only

former_member282968
Contributor
0 Likes
932

Hi Pratik,

Could be because of authorization.Just check the authorization objects for the users.

With regards,

Read only

0 Likes
932

Thanks for the reply.

Authorization Object is not used any where in the code.

Read only

Venkat_Sesha
Product and Topic Expert
Product and Topic Expert
0 Likes
932

In the Online Process. Do one thing.

In the Selection Screen do /h and Execute It will immediately stops at the Event At Line Selection or so.

Here from the Menu Debugging. Select the "Break At Statement"

In the Command Enter "Message".

Now Press F8. See if stops at the error Message what you are getting.

Do a Reverse Engineering. Hope this helps.

Read only

0 Likes
932

- thanks for the reply.

But the program is automatically scheduled in background.
We want the program to be run in background only, we don't want to execute the program in foreground.

Read only

Venkat_Sesha
Product and Topic Expert
Product and Topic Expert
0 Likes
932

Hi Pratik,

I agree there are some process that we do follow. To Identify the Issue first lets see the execution in Foreground and later you can move to analyze in Background.

Please put up some screen shots of the errors you get so that it will be helpful for us to analyze.

hope this helps.

Read only

kumud
Active Contributor
0 Likes
933

What is the program name?

Regards,

Kumud

Read only

Former Member
0 Likes
932

Thanks all,

But the issue is solved now.

We have upgraded our system to ECC 6.0 but SAP Logon GUI version that we were using was old.
After upgrade of SAP LOGON the issue is solved