Budget adjustments

• Budget misc. operation (field NUM)

The budget MOs are defined by means of:

• a number,
• a description,
• a budget,
• a budget version.

The document number of the budget MO cannot be accessed because it is assigned automatically.
The description is optional.
When a budget MO is automatically generated from the budget entry function, the description matches the following elements:"Budget MO + User name + Creation date".

• Description (field DES)

• Budget (field BUD)

This field specifies the budget code onto which the budget MO must be posted.
Enter in this field the budget to be updated.
On entering the second line, the system uses by default the value of the previous line.

• Transaction (field BUDTYP)

This field specifies the transaction for information purposes only and it cannot be accessed.
It only appears for those budget MOs having a Complete option assigned at budget level.
Any creation or modification of the budget leads in this case to the generation of an MO: the Transaction field then uses the entry transaction code used to create the budget.

• Version (field VER)

This field specifies the budget version onto which the budget MO must be posted.

• Reversal (field ENAEXT)

This function is used to automatically reverse a budget MO.
This function is accessed by the Functions/Reversal menu.
The dialog box makes it possible to specify a reversal date and a description (the system proposes a default description, for instance: Reversal: Journal no. of the budget MO + user code).
When these data have been entered, the box Reversal is then checked and the field Reversal date is filled.

• Reversal date (field DATEXT)

This field specifies the date entered on reversal creation.

• Company (field CPY)

This field uses the company code.
The company code of the operation is initialized via the site associated with the user code.
It can be modified provided it has been chosen from the list of authorized companies.
On entry of the second line, the sytem uses by default the value of the previous line.

If the budget is defined at company level, the company must necessarily be specified.
In that case, the Site field is no longer accessible and it is only assigned for information purposes.

• Site (field FCY)

This field uses the site code.
It can only be accessed if the budget is defined by site.
The code of the operation site is initialized by the site associated with the user code.
It can be modified provided it has been chosen from the list of authorized sites.
On entry of the second line, the system uses the value of the previous line.

If the budget is defined at site level, the site must necessarily be specified.
In that case, the Company field is automatically filled with the site company.

• Ledger (field LEDTYP)

This field specifies the ledger type. This information is dependent on the choice of the budget and the company.
The link is performed on the chart of accounts.

• Period start (field STRDAT)

The start date is always set against the start of a period.
Depending on the control type set up for the budget, the start date submitted by default on the first entry line can take the following values:

• Yearly: start date for the current fiscal year.
• Period: start date of the current period,
• Global: budget validity start date,
• None: no date proposed.

For the next lines, the start date is initialized to the value entered on the previous line.

• Period end (field ENDDAT)

The end date is always set against the end of a period.
Depending on the control type set up for the budget, the end date submitted by default on the first entry line can take the following values:

• Yearly: financial year end date linked to the entry start date,
• Period: period end date linked to the entry start date,
• Global: budget validity end date,
• None: no date proposed.

• field ACC

This field specifies the accounts linked to the chart of accounts set up for the selected budget.

• field CCE1

This field is used to indicate the dimension or the analytical dimension group for which the budget must be created.
One to nine dimension types are thus defined with respect to the order and number of dimension types defined at budget level.

• Currency (field CUR)

The currency proposed by default is that of the budget. It is possible to enter data in a different currency from that submitted. The exchange rate type applied is that of the common data parameter BUDTYPCUR.

 It is recommended to use the ISO coding during the creation of a new currency.

• Amount (field AMT)

The amount is entered for the start/end period defined beforehand.
Upon creation of the MO, this amount is distributed by period in the budget currency. This distribution depends on the budget weighting code linked to the acount or group of accounts.
The divisor is also taken into consideration during this distribution.

• Unit (field UOM)

On analytical inquiry, this field determines the non-financial unit linked to the displayed account.
The non-financial unit is determined when setting up an account associated with a given value.
This unit is called upon entry.

• Quantity (field QTY)

This field can only be accessed if:

• the budget is calculated in quantity,
• the account is followed by a non-financial unit.

The quantity is automatically calculated by dividing the budgeted amount by the non-financial unit value.
The quantity can be modified.