Budget Codes

• Budget (field BUD)

Enter a Budget code (1 to 3 alphanumeric characters) that will be used as the sole identifier for this budget.

• field DESTRA

Budget title.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Short description (field SHOTRA)

The short description replaces the standard description when display or print constraints require it.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Definition level (field LEV)

This field is used to indicate whether the budget must be defined at company or site level.

• Currency (field CUR)

Indicate the currency in which the budget must be created.
By default, this field is initialized to the CURSHRFLD currency (Common zone currency) of the parameters values (Common data).

• Divisor (field DIVAMT)

Specify a unit for the divisor.

For example, to build a budget in Euro, enter 1. All amounts will be divided by 1 (Amount = €10,000 Amount obtained = 10,000). 

To build a budget in Kilo Euro, enter 1,000. All amounts will be divided by 1,000 (Amount = €10,000 Amount obtained in Kilo Euro = 10).

• Operating budget (field GDDFLG)

This flag is used to specify that the budget setup is used in the operating budget management. Then, it can no longer be used in the "standard" budget entry/modification functions, or in analytical balance inquiry.

 Upon accounting validation of a document, the system checks the validity of the budget line but it does not check the values of the third dimension type.

• Quantity entry (field QTY)

If this field is set to 'Yes', it will be possible to build a budget in quantities, for the natures being managed in quantities (via a non-financial unit).

• Control type (field BUDCTL)

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.

• Budget misc. operations (field BUPODS)

The user can update the budgets via the budgetary MOs.
This way, each event on a budget can be tracked by creating MOs (comprehensive method).

Indicate if the budget code can be managed via the budgetary MOs function:

• None: No budget management by budget MO.
• Manual: The budget management can be carried out by the "Budget MO" function in addition to the standard "Budget entry" function.
• Complete: The budget management can be carried out by the "Budget MOs" function in addition to the standard Budget entryfunction. In addition the latter will generate a Budget MO describing the operations carried out in the budget.

• Access code (field ACS)

This access code makes it possible to prohibit access to the budget for certain users.

 If this field is assigned, only users with this access code in their profiles can act on the budget setup.

According to the rights granted, the following operations will be possible:

• Inquiry: Used to view the budget setup (the display of the database record is always possible).
• Modification: This allows the modification of the database record.
• Execution: Grants execution rights on the database record.

• Validity start date (field VLYSTR)

Optional field, makes it possible to enter a start date relating to the entity validity.

• Validity end date (field VLYEND)

Optional field, makes it possible to enter an end date relating to the entity validity.

• Chart of accounts (field COA)

The selected chart of accounts must necessarily be the subject of an analytical tracking.

• Pyramid (field PYMACC)

The budget can be entered at an aggregated level. In this case, specify an account pyramid.

• Level (field PYMACCLEV)

If an account pyramid has been entered, specify the budget entry level.

• Dimension type (field DIE)

This field is used to enter or select any dimension view set up in the database.

• Pyramid (field PYMCCE)

The budget can be entered at an aggregated level. In this case, specify a dimension pyramid.

• Level (field PYMCCELEV)

If a dimension pyramid has been entered, specify the budget entry level.

• Version (field VER)

THis field mentions the code of the budget version under which the budget data can be saved.

• Description (field VERDES)

Title of the budget version.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Status (field STA)

When the version status is:

• Open: it is possible to enter elements contained in the budgets through the functions Budget Entry, Budget MO entry, Budget Copy and Budget Calculation.
• Closed: the entry of new elements is not possible for this version of the budget.

• Final (field CTL)

This field is used to define a version of the budget to be controlled. For a budget to control setup code defined in the BUP1 to BUP9 parameters, the budgeted amounts taken into account are those of the final version.

A budget with the "final" status can be opened or closed (modifiable or not but always controlled).

 Only one version of the budget can be "final".

• By default (field DEF)

The version having this status is suggested by default upon budget entry, entry of budget MOs or inquiry of the analytical balance.

 One and only version, at a given time, can have the status "by default".