Fmf0 Error: different fiscal years

[noy_ash]

Dear experts,

When I run FMF0, I get an error:

Status: E

Message text: Invoice and payment in different years.

In short:

The invoice baseline date in the middle of December 2020, payment terms are 60 days, what brings it to a supposed payment at 2021.

However, the financial department has decided to pay it on 2020. (They have done F110 Tcode.)

On 31.12.2020 I tried to run FMF0 with: Entry Date & Fm Posting Date of 31.12.2020 and Fiscal year 2020.

Then I got that error message. (Invoice and payment in different years.)

Is this a bug?

Any idea how to solve it?

I don't want to change the bline date .(15.12.2020)

However only when I change it to enough early date (e.g. 1.10.2020) I can use the FMF0 in otder to create 0250 (Btart).

Thanks,

Noy.

[TammyPowlas]

What is the error message number?

[noy_ash]

I tried to use TX OF29 in order to deactivate the difference check. It has prevented the error, 0250 has been created, however the 0100 of the invoice at Fmifiit table (value type) still in 2021.

I need the whole process at 2020.

[noy_ash]

There is no error message number. I've written the TX output. It gives a table with a column called Message Text: Invoice and payment in different years.

[emmanuel_fuentes_12]

On transaction code OF37 what is the update profile you are using?

[noy_ash]

We've copied 000200 and created Z profile. The only change is: VT 50, PB changed from empty to X. (FMUP01)

[iklovski]

Hi,

You might want to check this OSS note:

1577919 - RFFMRPFI: Message FMUP138 displayed in error

But this error message could be justified if you use an update profile with PBET and the invoice is not in the same year as the payment. So, it may not be a bug.

Regards,

Eli

[noy_ash]

Thanks for your answer Eli. However it has been imolemented already and I don't try to reconstruct the invoice.

Our PBET is defined by FY-Based.

The invoice is not in the same year as the payment. But they have created the invoice at December 2020 and want to pay it on 2021.

If it is not a bug, what should we do? To add a Z check that prevent such cases?

Thanks in advance,

Noy.