cancel
Showing results for 
Search instead for 
Did you mean: 

Not allowing to post in the previous year after 01st April in EAPS 806

0 Kudos
263

We have migrated to S4HANA EAPS 806 recently. When we are trying to post the MIRO entries in the year 21-22, system is giving error

Document item & has not yet been carried forward to the current year

But we are not intending to c/f this MIGO entry (value type 54) and are intending to post the MIRO in the year 21-22. But after we do c/f using FMJ2 to the year 2022, SAP is allowing to post MIRO in both the years 21-22 and 22-23. This is creating issues in budget consumption, etc.

Accepted Solutions (0)

Answers (2)

Answers (2)

iklovski
Active Contributor
0 Kudos

Hi,

You have to see where your documents stand from FM year perspective. If you carried-forward PO, but not the GR, you would have difficulties to post IR in 2021. Only if all the document chain remains in 2021, you would be able to make postings in 2021. Also, if your update profile is PBET-type, you have to perform carry-forward and cannot leave the documents in FM year different from fiscal year.

Regards,
Eli

mlabrude
Participant
0 Kudos

Hi ,

please, specify which year your posting the MIRO: 2021? or 2022?

Which profile are you using?

On the other hand, what do you mean by "This is creating issues in budget consumption, etc."?

Best regards

Marc.

0 Kudos

Thank you Marc.

We are posting the invoice entry (MIRO) in the year 2021. But system not allowing to post. We are following PBET and value type 50, 51 defined for Period Based.

With FMJ2, system is carrying the budget to the year 2022 but after FMJ2, when we are able to post the entry with posting date 31.03.2022, budget for the year 2021 is consumed and budget which was c/f # FMJ2 to the year 2022, is showing as available in FMAVCR01.

Thanks & regards,

mlabrude
Participant
0 Kudos

Hi,

are you carrying forward commitment budget as your carrying forward the purchase order? I mean, if you're trying to post MIRO in 2021, I guess it's because you want to consume 2021 budget instead of 2022 budget. Through customizing, you are able to carryforward budget corresponding to PO are you're carrying forward the PO (Under: SPRO => Public Sector Management => Funds Management Government => Closing Operations => Closing Operations for Budget Control System (BCS) => Activate Budget Carryforward for Commitment) Creating a new entry for you FM Area for the value 51, you are activating Automatic Budget Posting that carries automatically the budget of a PO when PO is carried forward.

for example:

- Budget in 2021=100$ / PO in 2021 = 100$ / Available in 2021 = 0 $

- PO carry forward to 2022 (so MIRO can be posted in 2022)

- Budget in 2021=0$ / PO in 2021 = 0$ / Available in 2021 = 0 $

Budget in 2022=100$ / PO in 2022 = 100$ / Available in 2022 = 0 $

When MIRO is posted against 2022, budget PO consumption is reduced in 2022:

Budget in 2022=0$ / PO in 2022=0$ / Invoice in 2022 = 100$ / Available in 2020 = 0 $

Let me know if this is what you need or if I misunderstood your problem.

regards

Marc.

0 Kudos

Thank you Marc.

Sorry for the delayed reply.

Our case is :

PR, PO and MIGO are done in the year 2021.Now when we are trying to post MIRO also in 2021, but on the system date in the year 2022, we are getting error message " Document item &/& has not yet been carried forward to the current year" though our posting date is 31.03.2022 i.e. in the year 2021.

We have PBET active, value type 54 is not enabled for PBET. We do CCF for value type 54 as well. We use Commitment budget and not payment budget.

Thanks & regards,

SVKM Core Team

mlabrude
Participant
0 Kudos

Hi,

I would try FMJ0 with the PO so it would be carried forward form 2021 to 2022 with zero value.

Please, check it and if it doesn't work we should try something else.

Regards

Marc.

0 Kudos

Hi,

We can use FMJ2 to c/f the GR/IR creation and then post GR reduction in the year 2022. But we are wanting to post GR reduction in the year 2021, after the system date change to the year 2022 (any time after 1.4.22).

Thanks & regards

SVKM Core Team