This page (revision-4) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by KateN

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 2 KB jmyers to previous
3 26-Nov-2021 10:22 2 KB JAiken to previous | to last
2 26-Nov-2021 10:22 2 KB RForbes to previous | to last (UFBDGT) ==> UFBDGT
1 26-Nov-2021 10:22 2 KB KateN to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 3 changed 5 lines
The Create Inital Budget (UFBDGT) screen uses every relevant piece of existing data.
The first scenario created is referred to as the “Base” budget. Each employee’s assignment and/or position being budgeted for, becomes a budget seat. Assignment and position details become ‘Budget Seat Details’; premium and distribution information is attached to the budget seat details.
%%information The filters in UFBDGT behave differently than in other functions. The 'Unit' filter, for example, is respected ONLY when the 'Budget Level' is UNIT. All other filters in this situation would be ignored.%%
The Create Inital Budget (UFBDGT) screen uses every relevant piece of existing Personality data. The first scenario created is referred to as the “Base” budget. Each employee’s assignment and/or position being budgeted for, becomes a budget seat. Assignment and position details become ‘Budget Seat Details’; premium and distribution information is attached to the budget seat details.
At line 10 changed 14 lines
|Budget|Mandatory, Text\\This is the user-defines name of the budget being created.
|Budget Description|Optional, Text\\This is the user-defined description of the budget being created.
|Budget Level|Mandatory, LOV available\\This field indicates the level the budget is to be created at.
|Org Type|Optional, LOV available\\This field limits the budget to the Org Type indicated.
|Budget Interval|Mandatory, LOV available\\This field indicates the period of time is the budget being created for.
|Entity|Mandatory, LOV available\\This field limits the budget to the entity indicated.
|Budget Rule|Mandatory, LOV available\\This field indicates whether positions must be marked as budgeted or not.
|Position Standing|Optional, LOV available\\This field restricts the budget to the positions with the standing indicated
|Position Status|Optional, LOV available\\This field restricts the budget to the positions with the status indicated
|Calendar|Mandatory, LOV available\\This field indicates the business calendar to be used
|Starting|Mandatory, Date\\This is the starting date of the budget within the calendar indicated.
|Ending|Mandatory, Date\\This is the ending date of the budget within the calendar indicated.
|Exception Level|Mandatory, LOV available\\Do you need to see ‘trace’ information?
|Trial|Mandatory, LOV available\\Run in update mode (No) or in trial (Yes)
|__Budget__|__Mandatory, Text__\\This is the user-defines name of the budget being created.
|__Budget Description__|__Optional, Text__\\This is the user-defined description of the budget being created.
|__Budget Level__|__Mandatory, LOV available__\\This field indicates the level the budget is to be created at.
|__Org Type__|__Optional, LOV available__\\This field limits the budget to the Org Type indicated.
|__Budget Interval__|__Mandatory, LOV available__\\This field indicates the period of time is the budget being created for.
|__Entity__|__Mandatory, LOV available__\\This field limits the budget to the entity indicated.
|__Budget Rule__|__Mandatory, LOV available__\\This field indicates whether positions must be marked as budgeted or not.
|__Position Standing__|__Optional, LOV available__\\This field restricts the budget to the positions with the standing indicated
|__Position Status__|__Optional, LOV available__\\This field restricts the budget to the positions with the status indicated
|__Calendar__|__Mandatory, LOV available__\\This field indicates the business calendar to be used
|__Starting__|__Mandatory, Date__\\This is the starting date of the budget within the calendar indicated.
|__Ending__|__Mandatory, Date__\\This is the ending date of the budget within the calendar indicated.
|__Exception Level__|__Mandatory, LOV available__\\Do you need to see ‘trace’ information?
|__Trial__|__Mandatory, LOV available__\\Run in update mode (No) or in trial (Yes)
At line 27 changed 5 lines
|Unit|Mandatory, Multiple selection and LOV available\\This field limits the budget to the unit indicated.
|Group|Mandatory, Multiple selection and LOV available\\This field limits the budget to the group indicated.
|Department|Mandatory, Multiple selection and LOV available\\This field limits the budget to the department indicated.
|Auth Area|Mandatory, Multiple selection and LOV available\\This field limits the budget to the Auth Area indicated.
|Location|Mandatory, Multiple selection and LOV available\\This field limits the budget to the location indicated.
|__Unit__|__Mandatory, Multiple selection and LOV available__\\This field limits the budget to the unit indicated.
|__Group__|__Mandatory, Multiple selection and LOV available__\\This field limits the budget to the group indicated.
|__Department__|__Mandatory, Multiple selection and LOV available__\\This field limits the budget to the department indicated.
|__Auth Area__|__Mandatory, Multiple selection and LOV available__\\This field limits the budget to the Auth Area indicated.
|__Location__|__Mandatory, Multiple selection and LOV available__\\This field limits the budget to the location indicated.
At line 33 changed 3 lines
----
![Notes|Edit:Internal.UFBDGT]
[{InsertPage page='Internal.UFBDGT' default='Click to create a new notes page'}]