At our company commitment carryforward is only possible for one year, meaning that documents created in the current year and fund. e.g year 2009 fund A9, can be carriedforward the commitments and the budget to the next year and equal fund e.g year 2010 fund A9.
The problem arises when in 2010 the flow of documents is not completed, meaning that my purchase order is not completed receptioned or invoiced. From that moment, the commitments can´t consume carryforward budget.
Now what it is done is:
Creating a new funds reservation in 2011, adding a new line item to the purchase order with account assignment the new funds reservation and the quantities pending to delivered. For the ones delivered but not invoiced direct invoices are made against the new funds reservation.
I don´t know which is SAP Bestpractices for this cases in order to avoid modifying the purchase order or lost the purchase order history due to direct invoices, any suggestions?
The issue is that now refuses to go shopping in this way and wants the budgetary effects do not impact on purchasing documents. This means creating new
lose lines or purchase history to make direct invoices against the reserve.
What we were trying was made a commitments carriedforward this documents without budget, meaning documents that are in year 2010 fund a9 will be carryforward to fund a11 year 2011, and consume the budget of 2011, but for the commitments of a10 2010 the commitment carryforward must be with budget and result in fund a10 year 2011.
We performed t-code fmj2 to transfer a9 2010 documents to a11 2011. But those documents dont appear at a11 2011 but neither remain at fmj2. I understand that are pending that i make the budget transfer in order they appear but as i said I dont want to transfer budget for this cases I want them to consume from a11 2011. Is this possible and compatible with budget carryfoward for commitments to the following year. Am I missing running any t-code or customizing.
Sorry for the long and not very clear explanation.
Best regards and thanks for the help
Mar Novalbos replied
We've looked into this and found this customizing needs to be carried out in tx OLME:
Update the field status settings for the account assignment categories so that they are an optional entry (instead of being hidden or display only).
Normally, if the user cannot make the FMAA change manually via ME22N,
then the fields will also not be able to be changed automatically
with the reassignment tools.
If a combination of both changes (i.e. setting 'Account assignment changeable' flag combined with Field status settings) does not work or is not suitable for customers, then it should be reported to SAP via Support message for further checks.