report SAP BCS FMRP_FW_BUDCON + No matching funds center found

[wanjiru]

Hello Guys,

In FMRP_FW_BUDCON report there commitment items which are orphaned(they have No matching funds center found).this happens when we move to budget version 0 from version 5.

kindly advice on why this is happening.

see below for explanation, all the oprhaned commitment items should be under fund center 111002

[iklovski]

Hi,

There could be no figures posted in FM without a fund centre. If it happens it is a major bug. What SAP version do you use? If you are in ECC release (not in S/4), run FMAVCREINIT report and check the report again.

Regards,

Eli

[wanjiru]

Hi Eli,

we are on this version of ERP.

running report FMAVCREINIT

after running report FMAVCREINIT, the anomally still exists

[wanjiru]

@ Eli ,

actually this orphaned commitment items are duplicates from the below funds center(111002).

see the funds center below

[iklovski]

Hi,

Please, check two tables: FMBDT and FMAVCT for the commitment items in question. Check whether the figures are stored with an empty fund centre (which is unlikely) or on a fund centre which they should have been.

Regards,

Eli

[wanjiru]

Hi Eli,

lets take example commitment item 60001020, version 0 , year 2022 , table FMBDT

There are two number of hits

example commitment item 60001020, version 0 , year 2022 table FMAVCT

there is one hit and no funds center

regards,

[iklovski]

Well, this is obviously wrong. Please, try and run FMAVCREINIT, but don't limit the selection (except for the ledger) as you did in your screenshot.

[wanjiru]

Hello Eli,

It doesn't change even after running FMAVCREINIT still the anomaly is there.

Regards

[iklovski]

Did you run it without restriction this time? You can also try FMAVCDIFF if it is applicable

[wanjiru]

@Eli,

It doesn't change even after running FMAVCREINIT without restrictions , still the anomaly is there.

this report FMAVCDIFF shows AVC data is consistent

[iklovski]

Though it is possible to fix it by intervening in the tables, I would definitely show this case to SAP and ask for resolution. So, I'd suggest to raise OSS ticket. Please, keep this forum updated on the result, if you get any feedback

[wanjiru]

@Eli ,

will definitely raise a ticket with SAP.

[wanjiru · Accepted solution]

Hi ELi,

we did raise incident with SAP and suggested we look at the derivation strategy which helped fix the jumbled Budcon report structure plus remove the orphaned commitment items.

we edited the derivation strategy with help of finance consultant.this is how it looks like with the derivation strategy

TCODE SPRO

We no longer have orphaned commitment items.

regards

@Eli thanks for the assistance.