Skip to Content

FMF0, how to find the bad document?

Hello experts,

I could use an advise about FMF0. There is a lot of talk on the forums about that transaction. We noticed, that usually it goes smooth, unless there is a single bad document (i.e. with a lot of operations inside).

In other words - the transaction LOOPS on that very document and if you try to execute it for all the others it is OK, and if you try to execute it for this one bad document it goes forever.

My question is how to discover this bad document, on which FMF0 loops, without debugging?

Last time we discovered it by accident!

Best regards,

Ilian

P.S. I am a basis guy, and I'm sorry if my FI explanations sound a bit odd...

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • May 02 at 01:59 PM

    Hi,

    First of all, FMF0 produces error log, where a 'bad' document is shown along with the problem which stops SAP from processing payment transfer. Secondly, an error doesn't prevent successful execution of other documents in the same process. And, finally, it could be that the document shown in error log is not directly linked to the population processed by FMF0; it all depends if the data is consistent in FM tables along with FI split tables, if you use New G/L, but don't use on-line payment transfer.

    Hope this clarifies your issue. Otherwise, provide more information with concrete examples.

    Regards,

    Eli

    Add comment
    10|10000 characters needed characters exceeded

  • May 03 at 12:21 PM

    Hi,

    It is more related to problems reported for performance of FMF0. What release do you have? There are plenty of notes for this issue. For example:

    1042238 - RFFMS200:Performanceimprovement

    1718446 - RFFMS200:Performanceoptimization 2

    1681821 - RFFMS200:Performanceproblems

    Regards,

    Eli

    Add comment
    10|10000 characters needed characters exceeded