Field help (BUPBUDCTL)

Define the budget control type that must be applied to the budget:

• None (no control).
• Annual (per fiscal year): control of commitments/pre-commitments to check that they do not exceed the annual budget.
• Period: control by commitment/pre-commitment date to check that they do not exceed the budget for the period.
• Sliding (the date crosses over several fiscal years): control on the commitments/pre-commitments to check that they do not exceed the budget envelope fixed by the validity start and end range for the budget. If no date is assigned to the validity start date, the budget creation date is used by default (end date mandatory).
• Accumulated (the date crosses over several fiscal years): control of the commitment/pre-commitment date to check that the amount accumulated from the budget validity start date to the entered commitment period end date is not exceeded. If no date is assigned to the validity start date, the budget creation date is used by default (end date mandatory).

 To enable the budget control, you must associate the budget records to be controlled to the values of theBUP1 to BUP9parameters.
Only the final version of each budget is controlled.

When the budget control is enabled on the company, this control varies if the budget is null (equal to zero) or undefined:

If a budget account and analytical dimension(s) are combined and entered on a purchase order or request, the control on the budget excess is triggered as soon as these combined values are entered in the budget table with a budgeted amount greater than or equal to zero.

If a budget account and analytical dimension(s) are combined and entered on a purchase order or request, the control on the budget excess is not triggered when these combined values are not entered in the budget table.