cancel
Showing results for 
Search instead for 
Did you mean: 

Fund Management fmrp_rw_budcon

0 Kudos
180

In fmrp_rw_budcon , is the budget consumed at the time of PR (or) at PO (or) during GRN /Service Entry ?

FOr Example, When PR is created for ( Work "A") for RS 1 lakh , a negative entry of Rs 1 lakh is created at the same time, thereby unblocking the Budget. This budget can be used for any other purpose even though PR is created for A.

PO for "A" can get created a few days later. This causes budget deficit for "A".

Former Member
0 Kudos
Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with: https://community.sap.com/resources/questions-and-answers, as it provides tips for preparing questions that draw responses from our members. For example, you can:- outline what steps you took to find answers (and why they weren't helpful)- share screenshots of what you've seen/done- make sure you've applied the appropriate tags- use a more descriptive subject lineThe more details you provide, the more likely it is that members will be able to respond. Feel free to also take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.htmlShould you wish, you can revise your question by selecting Actions, then Edit.

By adding a picture to your profile you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html

Accepted Solutions (0)

Answers (1)

Answers (1)

mlabrude
Participant
0 Kudos

Hi,

I'm not sure I'm understanding your issue. Purchase documents works as a chain, so when PR is posted, it's supposed to consume the available budget and prevent it from being consumed by any other document. On the following step, when PO is posted based on a PR, the amount of PR is reduced by the amount of the PO. For example:

PR 100$, PO 80$:

Data in FMIOI table:

2022 PR 0100 +100$

2022 PR 0200 -80$

2022 PO 0100 +80$

If this is not the way your system is working, maybe you should check if the issue occurs for all you FM areas, or if you have any exit implemented that could change the standard behaviour.

Regards.

Marc