How to define different open interval rule for GR and IR?

[Former Member]

Hello all

In the beginning of a Fiscal Year (until January 15 u2013 20) I have the following problem:

Users are, mistakenly, posting service entry sheets (SES) or material document, with posting date of a new fiscal year, from purchase order from previous FY. As a result, budget is consumed from the new fiscal year. I do not want to carry forward this PO, I want to post this material document in the previous FY.

I tried to close posting for VT 54 for the new FY (only for the first 2 weeks of the new FY. I used FMMI), but then I can not post invoices, and I do want to post invoices.

I am looking for a way to close FY in FM for SES or material document only, and not for invoices. Is any one know how?

More details:

I use ECC6 with ENHP 4.

I use Former budget.

PBET is not active.

Value types 51 and 54 are relevant for budget.

Thank you for your answer

Uri Noyman

[mar_novalbos]

Hello Uri,

"Users are, mistakenly, posting service entry sheets (SES) or material document, with posting date of a new fiscal year, from purchase order from previous FY. As a result, budget is consumed from the new fiscal year."

I wanted to ask you for some clarification here: I would expect the SES consuming the reference PO, rather than consuming budget.

Also, please have a look at this part of the online help:

[Closing operations|http://help.sap.com/erp2005_ehp_04/helpdata/en/f0/ca4266260211d28a430000e829fbbd/content.htm]

In the 'Implementation considerations' part, it's stated:

It is not necessary to carry out closing operations with the fiscal year change in the system if you do not use period-based encumbrance tracking or, whilst using the Budget Control System, have activated multi-year budget execution. If you therefore decide not to carry out closing operations, budget already used remains in the old fiscal year and cannot be used in the new fiscal year. Open commitments are correctly reduced in the old fiscal year if you process them further in the new. (For example, a purchase order from 2005 can be reduced by an invoice arriving in 2006.)

Are you finding those SES actually are consuming budget instead of reducing the reference PO?

On the other hand, you might also think about using Multi-year budget execution, it may also be helpful in your scenario.

You can find the information here:

[http://help.sap.com/erp2005_ehp_04/helpdata/en/f0/ca5716260211d28a430000e829fbbd/frameset.htm]

'Recording Actual and Commitment Data ->Multi-Year Budget Execution '

Hope you will find this information helpful

Kind regards

Mar

[Former Member]

Hello Mar and thank you for you answer.

I will tray to clarify the problem:

I am using closing operation and this is the reason that the budget is consumed in the new fiscal year and not in the original year of the commitment.

In our organization, we carry forward open PO at the and of January of the new FY. Until then we post SES with reference to open PO from previous year, with posting date of previous year. At the end of January we carry forward the remains commitments and budget for commitments to the following year. This is the way our business process is design.

The problem is that when you enter SES, the system sets default posting date of current FY and often, user forgets to change the posting date to the previous year.

In this case the posting in FM is as follow:

VT AT FY

51 100 2009 (previous)

51 200 2009

54 100 2010

The mining of this is that the budget is consumed from 2010 and no budget will be carry forward to cover it, which means double budget consumption. If an invoice is posted, and payment run is executed (as it usually is), it is not possible to cancel the documents.

I am trying to prevent these mistakes by closing FY for FM postings of SES using transaction FMMI. But SES and invoice have the same VT and I have to allow posting invoices in the new FY.

Is there a way to forbid posting of SES and allow posting invoices at the same FY?

Do you now another way to solve the problem?

Thank you

Uri Noyman

[CesarCarreno]

Hi Uri, may be the BAdI FM_OPEN_PERIODS can be useful for your issue.

Best regards

César

[Former Member]

Thank you Cesar.

It looks like the right solution for my problem.

I am working on it now

Best regards

Uri Noyman