cancel
Showing results for 
Search instead for 
Did you mean: 

FMF0, how to find the bad document?

ILIAN_Grigorov
Contributor
0 Kudos

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...

Accepted Solutions (0)

Answers (2)

Answers (2)

iklovski
Active Contributor
0 Kudos

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

iklovski
Active Contributor
0 Kudos

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

ILIAN_Grigorov
Contributor
0 Kudos

Hi Eli.

I think FMF0 produces a log only if it finishes, in my case it does not finish for several hours, and then the system cut it out. As a result, some documents were processed, some were not. But I could not find any log, where should I check?

Actually there is no error, just one or few documents run forever and never end.

Probably if it runs in background there would be something in SM37, but it is difficult to explain to users how to do it....

We do not use new G/L 😞

Regards

Ilian

ILIAN_Grigorov
Contributor
0 Kudos

We have ERP 6.0 EHP 3,

Perhaps these are the related components:

FI-CA 603 0001 SAPK-60301INFICA FI-CA

FI-CAX 600 0012 SAPK-60012INFICAX FI-CA Extended

It seems when the users fixes some documents, FMF0 is OK....

iklovski
Active Contributor
0 Kudos

Well, as I said, check OSS notes. There are several relevant for your release and it does solve many problems. I had the same in several projects.