Commitment budget problem when adding a line to an old PO (from previous year)

[noy_ash]

Dear experts,

We use BCS and configured budget for PO based on Delivery Date (update profile).

There is PO with one line, created on 1.5.2021, delivery date is 1.7.2021 and its 9B fiscal year is 2021. Its FM commitment budget balance is 0. Hence we didn't carryforward it (FMJ0).

Now (2022) I want to add a new line, with delivery date 1.6.2022, and FMIR for 9B 2022 is opened (for PO) and 9B 2021 is closed, as long as I don't do FMJ0 to this order, the system shows error: "Period ... fiscal year 2021 for commitment budget not open for FM posting in VT 51".

My question is:

Why the system check 2021? I'm adding a line with 2022!

The rest (line number one) is irrelevant!

I have to add that if I do FMJ0 to the first line, there is no error. (As the system doesn't determine the fiscal year as 2021 for the 1st linr, but 2022. As expected.)

Thanks in advance,

Noy.

[noy_ash]

2. Regarding PBET:

We work with Encumbrance Tracking: FY Based (not Periodic Based).

Does it change your answer?

[iklovski]

Definitely. Without PBET, the situation is even more mysterious than before. I would of course debug the system and check at what point and based on which parameters the error is shown. But, you can leave it to SAP to check it out, under assumption that you didn't modify the standard code. Please, post an update as soon as you hear from them; it's interesting to see what they have to say on this.

[iklovski]

Hi,

It looks like that with adding a new line, there is some sort of update on the previous line, which makes the system to check for line 2021. Try and close the commitment with FMMC and check if the problem persists.

Regards,

Eli

[noy_ash]

Thanks for your prompt answer Eli. However it doesn't solve the problem.

Before I marked the 1st line as Final Invoice, it tries to write it on 2021 and even after it, it tries the same.

The sum of FMIOI was ans still zero for this PO.

It is not a spesific issue for one PO. It happens with any PO that has lines with "old" (previous years) Delivery Date and I try to add a new line.

[iklovski]

If it tries to do it before you mark final invoice, this is fully OK. But after, this is definitely wrong. What is your SAP release package?

[iklovski]

Also, check what happens in FMIOI if you execute FMJ0 and add a new line. Does it change anything for the line which was carried-forward.

[noy_ash]

SAP release package is 750.

When I execute FMJ0 and add a new line: the 1st line, that was carried-forward has nothing special, I don't see any change, except for CPUDT and CPUTM.

[iklovski]

This is strange... Why CPUDT would change if no changes are applied to the line?

[noy_ash]

I'll open OSS for the CPUDT changing.

However I still have 2 questions:

1. If I have only one PO line, from last year and its Final Invoice is marked. And when I try to add a new line this year it says the period is closed. Then I open the period (2021) and run FMJ0, and then closing the period. After that I try to add a new line. This time is works, and it deems the new line as 2022 and nothing is changed at the 1st line (nor CPUDT).

Does it mean that it seems as a Bug and I need to open OSS for it?

2. Why do you deem the system behavior as making sense when you said "If it tries to do it before you mark final invoice, this is fully OK"?

It means for me, that every time I close a year, in addition to my main action of FMJ2 to all of the PO in the system, I have to do FMJ0 as well. Unless the customers can't add new line to a current PO. (Take into account that we don't oblige the customers to mark the Final Invoice.)

I think the system should have checked that if the PO balance (from the FM point of view. Meaning FMIOI ) is zero, the customer can add lines even if there is no FMJO nor Final invoice for the previous PO lines.

Thanks,

Noy.

[iklovski]

1. Yes, it seems like a bug to me. Unless, you have something in MM (development) which triggers this change. Anyway, would be interesting to see what SAP has to say on this

2. Marking final invoice flag might change commitment record in FMIOI with the FM date of the change. Hence, system would expect carry-forward, if you work with PBET logic