This function makes it possible to create new budgets based on already existing budgets (or the copy of such budgets). These budgets are defined on a company (or a site) and a fiscal year.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The screen is composed of three separate parts:

  • Source budget: copy basis,
  • Target budget: new budget to create,
  • Calculation: used to associate specific rules to the copy.

Entry screen

Source block:

Specify the budget to use as template: budget code, company and/or site (depending on the setup of the budget record) and fiscal year.

Target block:

Specify the budget to create: budget code, company and/or site and fiscal year. If the budget record does not exist, it is possible to create it by duplicating the 'Original' budget record (some fields such as the budget description, for instance, must be completed manually in the budget record).

SEEINFO Copy of dimension types:

In the BUD - Budget table, dimension types are copied according to the order used in the company's analytical ledger and not the order set up at the budget level.

Source

Budget (field BUDORG)

Budget on which the copy is based.

Version (field VERORG)

Number of the budget version.

Company (field CPYORG)

Company for which the original budget has been defined.

Site (field FCYORG)

Site for which the original budget has been defined.

Fiscal year (field FIYORG)

Enter or select the fiscal year number.

Start date (field DATDORG)

Date until which the records are selected. This date can only correspond to the end of a period.
End date (field DATFORG)
Ledger type (field LEDTYPORG)

Specify the ledger type for which the budget should be managed.

SEEINFO Those ledgers for which it is possible to run a budget have active "Analytical" and "Budget" flags in the Ledgers function.

Target

Budget (field BUDDES)

If the destination budget exists, it must have the same structure "Accounts / Dimensions" as the original budget:

  • same chart,
  • same dimension types,
  • same pyramids and levels.

If the destination budget does not exist, its creation is submitted. This new budget is by default strictly identical to the original budget.

The destination budget can show an amount (or a quantity) that is similar to the original budget but it can also show an increase or a decrease with respect to the original budget, via the coef field.

Examples :
Coef entered = 0. 95 means a 5% decrease.
Coef entered = 1. 20 means a 20% increase.
field DESBUDDES

No help linked to this field.

Version (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.

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

No help linked to this field.

Company (field CPYDES)

Company for which the destination budget has been defined.

Site (field FCYDES)

Site for which the destination budget has been defined.

Fiscal year (field FIYDES)

Enter or select the fiscal year number.

Start date (field DATDDES)

Date from which the records are selected.
End date (field DATFDES)
Ledger type (field LEDTYPDES)

Specify the ledger type on which the budget should be managed.

SEEINFO Those ledgers on which it is possible to run a budget have active "Analytical" and "Budget" flags in the Ledgers function.

Calculation

Coefficient (field COEF)

It is possible to apply a multiplying coefficient to the budget to be created.
Basis of transfer (field FLGDSP)

Two transfer bases are available:

In totals by period

The original budget is copied by period and updates the amounts for the budget to be created period by period. The original budget distribution is thus conserved. The time distribution of the account of the budget to be calculated is not modified. The number of periods of the original budget and the budget to be calculated must be the same.

For instance:

Original budget N-1: from 01/01/N-1 to 31/12/N-1

- Period 01: 607000/SERV01/DIV01: 1000

- Period 02: 607000/SERV01/DIV01: 2000

- Period 03 to 12: 607000/SERV01/DIV01: 0

Calculated budget N: from 01/01/N to 31/12/N

- Period 01: 607000/SERV01/DIV01: 1000

- Period 02: 607000/SERV01/DIV01: 2000

- Period 03 to 12: 607000/SERV01/DIV01: 0

In yearly amounts:

The original budget is copied with respect to the whole period considered, that is by total. The allocation key of the account record is then applied, to find a budgeted amount period by period. The time distribution of the nature for the budget to be calculated, is applied to the global amount. Example:

Original budget N-1: from 01/01/N-1 to 31/12/N-1

- Period 01: 607000/SERV01/DIV01: 1000

- Period 02: 607000/SERV01/DIV01: 2000

- Period 03 to 12: 607000/SERV01/DIV01: 0

- Time distribution key for 607000: 50 for January, 50 for February and 0 for the rest

Calculated budget N: from 01/01/N to 31/12/N

- Period 01: 607000/SERV01/DIV01: 1500

- Period 02: 607000/SERV01/DIV01: 1500

- Period 03 to 12: 607000/SERV01/DIV01: 0

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation