cancel
Showing results for 
Search instead for 
Did you mean: 

Prevent negative budget after a transfer (pre-post status)

Former Member
0 Kudos

I have a situation where the system allows budget transfers (with insufficient budget) to pre-post using FMBB. The scenario is as follows...

Cur Exp Avail

FundCenterA 100 50 50

FundCenterB 200 25 175

Although only 50 is available in fund center A, the system allows the user to pre-post a transfer for more than 50 (75 for instance) from fund center A to B.

After the initiator creates the pre-post transfer document, approval of the transfer is attempted by a budget analyst, but the document remains in pre-post status and the analyst can't take any further action.

Can preventing this be accomplished through consistency checks causing the initiator to get a hard error? If so, how or why not? If it cannot be done using consistency checks then what are my choices.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Update - - -

The system will issue a hard error when the transfer is created ONLY if the "check document" button is pushed. The problem is that the user creating the transfer cannot be forced to check the document before hitting prepost. Any ideas/suggetions?

Former Member
0 Kudos

I looked back at note 983853. The last bullet under the solution suggested...

"Create and assign a tolerance profile that contains absolute variances, which triggers an error message for the absolute variance equal to the value 0."

Instead of creating a new tolerance profile which I have attempted in the past, I changed the existing profile to include absolute variances as well as usage rates...and added two separate tolerance limits for activity of posted budget 90 and budget posted provisionally 95 and set them for absolute variance only of the value 0.

Both 90 and 95 had to be changed because...

When only activity 95 is changed for absolute variance, the check document feature (F7) does not detect a negative budget but attempting to pre-post will result in an error.

When only activity 90 is changed for absolute variance, the check document feature detects the negative budget but pre-post will not detect an error and allow the user to proceed.

Therefore both 90 and 95 are needed together.