SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error in FP50 - Manual Outgoing Checks Lot

Former Member
0 Kudos

Hi Experts,

I am experiencing some error while running transaction FP50 (Error - Balance in Document currency is not zero, posting not possible). Please help me to find the solution.

Thanks & Regards,

Mansoob

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Mansoob,

Error >0003 'Balance in &1 is not zero, posting not possible' will need analysis really but I would suggest you implement SAP Note 1350607 & 1140943 and test if it resolves it.

Let me know how it goes.

regards,

David

View solution in original post

6 REPLIES 6

Former Member
0 Kudos

Hi Mansoob,

Error >0003 'Balance in &1 is not zero, posting not possible' will need analysis really but I would suggest you implement SAP Note 1350607 & 1140943 and test if it resolves it.

Let me know how it goes.

regards,

David

0 Kudos

Hi David,

Thanks for your reply.

I have tried both the notes but the problem could not be solve. I am getting the same error. Any further suggestion will be highly appriciated.

Thanks,

Mansoob

0 Kudos

Hi Mansoobkhan,

Thanks for the reply. Unfortunately errors like this need to be debugged and I would advise you to do same. At the point of posting, could you enter debugger and set watchpoint on sy-msgno = 003 and see what is going on. If you cannot do this, please send an OSS message to SAP and we will analyse it for you.

Thanks a lot.

regards,

David

0 Kudos

Hi David,

I have raised an OSS note and waiting for the same. Thanks for you guidence and help.

Regards,

Mansoob

0 Kudos

Dear Mansoob,

How did you solve the above error. I am also experiencing the same error.

Can you please tell the solution you applied.

Thanks and Regards,

Rajesh

Edited by: Rajesh CV on Nov 24, 2010 6:04 PM

0 Kudos

Hi Rajesh,

I could not resolve this problem. This error was occuring in IDES but when I move to my development client, this error is not there.

Thanks,

Mansoob