EMF Value adjustment workflow commitment

[#1]

Hi all,

We are using workflow for Value Adjustment (VA) document used for increase/reduce of Earmarked Fund (EMF) amount.

When creating the VA document, a standard WF is initiate. The amount is saved at field 'amount changed'. If the WF approved, the amount changed is added to the overall amount of the EMF. If the WF rejected, the amount changed is deleted.

When creating the VA document the changed amount commitment is posted to FMIOI and FMAVCR as regular commitment that consumed the available budget.
I am looking for a way to delay the commitment posting to the time that the VA document is approved.

I try to use function 'EXIT_SAPLFMFA_001' and raising the statistic flag, but all EMF and VA history commitment gets the statistic flag.

Thanks,

Amit Blumshtein

[iklovski]

Hi Amit,

To my understanding, without modification of standard code, you won't achieve this. I wonder, though, if what you want to do is consistent with the 'concept of prudence' in EMF availability control. What happens if valuation is negative, and you put statistically, meanwhile consuming EMF? Or you want to restrict it only to positive valuations?

Regards,

Eli

[former_member584205]

Hi Eli,

The EMF is created as obligation of the user to be consume by accounting document.

The main business cause for this process is to prevent from the user to reduce EMF without the accounting department approval. Once the approval is given, the commitment should be reduce, but not before.

Thanks.

Amit Blumshtein

[iklovski]

I see... but, what is the functional concern? That the budget will be consumed, and reduction will not be approved eventually? This shouldn't happen as ledger 9D (workflow) updates in FMAVCT should prevent this scenario.

[former_member584205]

The concern is that the user committed o amount X. When the accounting department try to post the accounting document related to the EMF (etc. the expense amount X) the amount X will be reduced by VA and there will no avilable budget.

The current WF update FMAVCT as soon as the VA is created and before the approval process ends.
Do you have reference for preventing the update to FMAVCT ? How is the line at FMIOI is updated in this case? When does FMAVCT is updated in this case?

Thanks.

Amit