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

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
26 26-Nov-2021 10:22 14 KB rforbes to previous
25 26-Nov-2021 10:22 14 KB jmyers to previous | to last WORK_RULE_CODE ==> WORK_RULE (Field)
24 26-Nov-2021 10:22 14 KB JEscott to previous | to last
23 26-Nov-2021 10:22 14 KB JMyers to previous | to last
22 26-Nov-2021 10:22 14 KB JMyers to previous | to last
21 26-Nov-2021 10:22 14 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
IFBA
IFBA

Version management

Difference between version and

At line 3 changed one line
%%warning A BASE budget will automatically be created by [UFBDGT]. This budget represents a ‘real world’ picture and should not be altered. You should create working budgets by copying the BASE budget.%%
\\
%%information A BASE budget will automatically be created by UFBDGT. This budget represents a ‘real world’ picture and should not be altered. You should create working budgets by copying the BASE budget.%%
\\
\\
At line 6 changed 4 lines
;[Scenario|SCENARIO_CODE]:This field holds the name of the scenario(s) within the budget area. [UFBDGT] will always automatically create the scenario titled BASE, which should not be altered.
;[Status|SCENARIO_STATUS]:This field shows the current status of the scenario.
;[Stage|SCENARIO_STAGE]:The field displays the current stage of scenario.
;[Description|DESCRIPTION]:The field allows you to provide a short description of the scenario.
;[Scenario|SCENARIO_CODE]:This field holds the name of the scenario(s) within the budget area. UFBDGT will always automatically create the scenario titled BASE, which should not be altered. Scenario_Code is a mandatory 16-character alphanumeric field you must manually enter.
;[Status|SCENARIO_STATUS]:This field shows the current status of the scenario. Scenario_Status is a mandatory field you must fill from the fixed lexicon [X_SCENARIO_STATUS].
;[Stage|SCENARIO_STAGE]:The field displays the current stage of scenario. Scenario_Stage is a mandatory field you must fill from the fixed lexicon [X_SCENARIO_STAGE].
;[Description|DESCRIPTION]:The field allows you to provide a short description of the scenario. Description is a mandatory 50-character alphanumeric field you must manually fill.
At line 11 changed one line
;[Budget Seat|FBS_ID]:Budget Seats are assignments, positions or part of positions that incurs costs. \\i.e. One position (1290) with two FTEs may have two or more budget seats.
;[Budget Seat|FBS_ID]:Budget Seats are assignments, positions or part of positions that incurs costs. \\''i.e. One position (1290) with 2 FTEs may have 2 or more budget seats''
At line 14 changed one line
!!Budget Seats tab
!!Define Budget Areas (IFBA) - Budget Seats
At line 16 changed 4 lines
%%information Any seats EXCEPT for those of the base budget may be edited or deleted.%%
;[Budget Seat|BUDGET_SEAT_CODE]:The code for the budget seat is a combination of the position number and number of iterations of that position.
;[Status|BUDGET_SEAT_STATUS]:This field shows the status of the budget seat.
;[Title|BUDGET_SEAT_TITLE]:A combination of the employee number and the position title.
\\
Any seats EXCEPT for those of the base budget may be edited or deleted.
\\
;[Budget Seat|BUDGET_SEAT_CODE]:The code for the budget seat is a combination of the position number and number of iterations of that position. Budget_Seat_Code is a mandatory 50-character alphanumeric field you must manually enter.
;[Status|BUDGET_SEAT_STATUS]:This field shows the status of the budget seat. Budget_Seat_Status is a mandatory field you must fill from the fixed lexicon [X_BUDGET_SEAT_STATUS].
;[Title|BUDGET_SEAT_TITLE]:A combination of the employee number and the position title Budget_Seat_Title is an optional 100-character alphanumeric field you may manually fill.
At line 23 changed 11 lines
!!Seat Details tab
;[FTE|FTE]:The number of full time equivalent positions for which a commitment has been made by the organization.
;[Wage Rate|WAGE_RATE]:Standard salary or wage amount allocated for this position or employee. If the seat has an employee attached to it, this will be the employee’s wage rate. If the seat is VACANT, this is is the rate that is assigned to the position. This is all defaulted in when the budget is created, however you may change the rate.
;[Rate Basis|RATE_BASIS]:The rate basis is the unit of measure that the associate wage rate is being stored or displayed in.
;[Contract Days|CONTRACT_DAYS]:This field is used for contract assignments only and will indicate the number of days in the contract.
;[Contract Limit|CONTRACT_LIMIT]:This field is for contract assignments only and displays the wage limit for the contract period.
;[Hours Per Day|HOURS_PER_DAY]:This field shows the standard hours per day required for this position.
;[Hours Per Week|HOURS_PER_WEEK]:This field shows the standard hours per week required for this position.
;[Scale/Step|SCALE_STEP]:This field shows the wage scale/step associated with this seat.
;[Scale Override|SCALE_OVERRIDDEN]:If the Scale Override toggle is ON, the wage rate does not correspond with the scale/step indicated and no automatic wage increases ([UFSTEP] for example) will be processed.
;[Use FTE Wage|USE_FTE_WAGE]:If this toggle is ON, the displayed salary or wages is the FTE amount, calculated based on standard full-time hours. If this toggle is OFF, the displayed salary or wages will be a Part Time Equivalent amount, using the FTE factor to prorate the salary or wages.
!!Budget Seats (IFBA) - Seat Details
;[FTE|FTE]:The number of full time equivalent positions for which a commitment has been made by the organization. FTE is an optional 9-character numeric field you may manually enter.
;[Wage Rate|WAGE_RATE]:Standard salary or wage amount allocated for this position or employee. If the seat has an employee attached to it, this will be the employee’s wage rate. If the seat is VACANT, this is is the rate that is assigned to the position. This is all defaulted in when the budget is created, however you may change the rate. Wage_Rate is an 18-character numeric field you may manually enter.
;[Rate Basis|RATE_BASIS]:The rate basis is the unit of measure that the associate wage rate is being stored or displayed in. Rate_Basis is an optional field you may enter using the fixed lexicon X_RATE_BASIS.
;[Contract Days|CONTRACT_DAYS]:This field is used for contract assignments only and will indicate the number of days in the contract. Contract_Days is an optional 9-character numeric field you may manually enter.
;[Contract Limit|CONTRACT_LIMIT]:This field is for contract assignments only and displays the wage limit for the contract period. Contract_Limit is an optional 18-character numeric field you may manually enter.
;[Hours Per Day|HOURS_PER_DAY]:This field shows the standard hours per day required for this position. Hours_Per_Day is an optional 9-character numeric field you may manually enter.
;[Hours Per Week|HOURS_PER_WEEK]:This field shows the standard hours per week required for this position. Hours_Per_Week is an optional 9-character numeric field you may manually enter.
;[Scale/Step|SCALE_STEP]:This field shows the wage scale/step associated with this seat. Scale_Step is an optional field you may fill using the LOV generated from [ISWS] ([P2K_SA_WAGE_SCALES]).
;[Scale Override|SCALE_OVERRIDDEN]:If the Scale Override toggle is ON, the wage rate does not correspond with the scale/step indicated and no automatic wage increases (UFSTEP for example) will be processed. Scale_Override is an optional toggle field.
;[Use FTE Wage|USE_FTE_WAGE]:If this toggle is ON, the displayed salary or wages is the FTE amount, calculated based on standard full-time hours. If this toggle is OFF, the displayed salary or wages will be a Part Time Equivalent amount, using the FTE factor to prorate the salary or wages. Use_FTE_Wage is an optional toggle field.
At line 36 changed one line
!!Seat Info tab
!!Budget Seats (IFBA) - Seat Info
At line 44 changed one line
;[Work Rule|WORK_RULE (Field)]:Work rules are used to determine the standard processing information required to create pay headers and transactions for an employee.
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine the standard processing information required to create pay headers and transactions for an employee.
At line 49 changed 2 lines
!!Distribution tab
The data for the Distributions tab comes from the [IEAS] ([P2K_HR_ASSIGNMENT_DETAILS]) or if the assignment is vacant, from [IDPS] ([P2K_CM_POSITION_DETAILS]) table. You MAY, however, change the information directly on this tab.
!!Budget Seats (IFBA) - Distribution
The data for the Distributions tab comes from the [IEAS] ([P2K_HR_ASSIGNMENT_DETAILS]) or if the assignment is vacant, from [IDPS] ([P2K_CM_POSITION_Details]) table. You MAY, however, change the information directly on this tab.
At line 52 changed 4 lines
;[Seq|SPLIT_SEQUENCE]:The field will indicate the sequential order of the distribution split.
;[Distribution|DISTRIBUTION_CODE]:This field displays the distribution code receiving the portion of costs. This is normally the distribution of the wages associated with the assignment or position.
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates how the distribution is being split.
;[Split %|SPLIT_PERCENT]:If the split rule is ‘By Percent’ then the percent is indicated in this field. This should be defined by a percent amount NOT by a decimal amount. EG, to indicate 5%, you will enter ‘5’ NOT ‘. 05’. If the split rule is ‘By Amount’ then it would be directly entered as the amount EG $500 you would enter 500
;[Seq|SPLIT_SEQUENCE]:The field will indicate the sequential order of the distribution split. Split_Sequence is a 5 digit mandatory field you must manually enter.
;[Distribution|DISTRIBUTION_CODE];This field displays the distribution code receiving the portion of costs. This is normally the distribution of the wages associated with the assignment or position. Distribution_Code is a 50 character alphanumeric mandatory field you must manually enter.
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates how the distribution is being split. Split_Rule is an optional fixed lexicon X_SPLIT_RULE you may use to look up the value.
;[Split %|SPLIT_PERCENT]:If the split rule is ‘By Percent’ then the percent is indicated in this field. This should be defined by a percent amount NOT by a decimal amount. EG, to indicate 5%, you will enter ‘5’ NOT ‘. 05’. If the split rule is ‘By Amount’ then it would be directly entered as the amount EG $500 you would enter 500 Split_Percent is a 5-digit optional percentage field you may manually enter.
At line 58 changed one line
!!Premiums tab
!!Budget Seats (IFBA) - Premiums
At line 61 changed 2 lines
;[Premium|PREMIUM_CODE]:This field displays the user-defined premium code that uniquely identifies this premium within the organization.
;[PC|PC_CODE]:This field will hold the pay component used to store the amount of the premium.
;[Premium|PREMIUM_CODE]:This field displays the user-defined premium code that uniquely identifies this premium within the organization. Premium_Code from [ISPM] ([P2K_SA_PREMIUMS]) is a mandatory field that may be retrieved from the LOV.
;[PC|PC_CODE]:This field will hold the pay component used to store the amount of the premium. PC_Code is an optional field you may using the LOV generated from the [P2K_PR_PAY_COMPONENTS] table.
At line 64 removed 3 lines
;:%%information The information for this field will default in once the PC Code has been selected. You may NOT alter edit this field.%%
;[Premium Level|PREMIUM_LEVEL]:Premium Level indicates where the premium originates.
;[Premium Rate|PREMIUM_RATE]:
At line 68 removed 7 lines
----
!!Statistics tab
The data for the Statistics tab comes from the [IEST] ([P2K_HR_STATISTICS]) table; however, you MAY change the information directly on this tab.
;[Statistics|STAT_CODE]:This field will hold the user-defined statistic code.
;[Abbreviation|ABBREVIATION]:This field will hold the abbreviated description of the pay component. The information for this field will default in once the Stat Code has been selected. You may NOT alter edit this field.
;[Amount $|AMOUNT]:User-defined statistical amount.
At line 76 changed 13 lines
----
!!Assumption Log tab
This tab is the log of assumptions that have been processed for the budget seat that you are on.
The information data for the Assumption Log tab is derived from the ([P2K_FC_ASSUMPTION_LOGS]) table.
%%information You may NOT ALTER the information within this tab.%%
;[Seq|ASSUMPTION_SEQUENCE]:This field displays the sequential order of the assumption within this budget seat.
;[Assumption Action|ASSUMPTION_ACTION]:This field will show what action the assumption will perform.
;[Description|DESCRIPTION]:This field will provide a short description of the assumption processed.
;[Before Value|BEFORE_VALUE]:This field shows the value of the ‘item’ prior to the assumption being processed.
;[After Value|AFTER_VALUE]:This field shows the value of the ‘item’ after the assumption has been processed.
__The information for this field will default in once the PC Code has been selected. You may NOT alter edit this field.__
At line 90 removed 17 lines
----
!!Budget Amounts tab
You may view the calculated budget amounts by selecting the Budget Amounts tab.
;[Start Date|START_DATE]/[End Date|END_DATE]:
These fields display the start and end dates of the period.
;:Budgets are dealt with on a Monthly basis, if you run [UFCALC] for a Bi-weekly Payroll, the Start and End dates will be that of the Pay Period for that Budget.
;:If it is on a Bi-weekly basis and the start of the first Pay Period was 01-Jan-2007, then [UFCALC] would generate as follows:
;:01-Jan-2007 to 13-Jan-2007
;:14-Jan-2007 to 27-Jan-2007
;:28-Jan-2007 to 31-Jan-2007
;:01-Feb-2007 to 10-Feb-2007
;:It does this so that the Pay Period 28-Jan-2007 to 10-Feb-2007 is split over the 2 months as the budget is to be created by month.
;[Pay Component|PC_CODE]:This field displays the pay component generated for this period.
;[Abbreviation|ABBREVIATION]:This field displays the abbreviated description of the pay component.
;[Amount $|AMOUNT]:This field displays the amount calculated in [UFCALC].
;[Distribution|DISTRIBUTION_CODE]:If the pay component has a distribution code attached to it, the distribution heading will be displayed here.
At line 108 changed 66 lines
----
!!Assumptions tab
Planned changes may be entered as assumptions. These changes may be applied to a qualified set of budget seats for a specified time frame and can change FTE, scales/steps, wages, statistics, or premiums
%%warning Copy the BASE scenario before doing any assumptions.%%
Assumption can be one of three types:
|Planned|When you know that there are changes to be made, you should create ‘Planned’ assumption.
|What If|When you are attempting to ‘forecast’ a possible change, you should create a ‘What If’ assumption.
|Wage Step|If [UFSTEP] is run as part of the forecasting process, assumptions will be created and stored as ‘Wage Step’ assumptions by Personality.
The information data for the Assumptions tab can be found in the ([P2K_FC_ASSUMPTION_LOGS]) table.
;[Seq|ASSUMPTION_SEQUENCE]:This field will display the sequential order of the assumption.
;[Type|ASSUMPTION_TYPE]:This field will display the assumption type being defined.
;[Status|ASSUMPTION_STATUS]:This field indicates the status of the assumption.
;[Statement|STATEMENT_CODE]:Users may create global or general statements through the Define Assumption Statement (IFAS) form. This field allows you to link the statement to the assumption.
;[Start|START_DATE]:This field shows the date the assumption is to begin.
;:The information for this field will automatically fill through the IFAS ([P2K_FC_ASSUMPTIONS]) table. You may however, change this data either manually or by using the calendar icon provided.
;[End|END_DATE]:This field shows the date the assumption is to end.
;:The information for this field will automatically fill through the IFAS ([P2K_FC_ASSUMPTIONS]) table. You may however, change this data either manually or by using the calendar icon provided.
;[Description|DESCRIPTION]:This field provides a short description of the assumption.
;[Add Assumption Statement]:You may add an assumption through the Add New Assumption Statement button.
;:%%information Please refer to Assumption Statements for further information on this function.%%
;[Process Assumption]:The Process Assumption icon allows you to see the result of an assumption.
;:In order to perform this function, you must first highlight the appropriate assumption and then click on the Process Assumption button. When completed you will be informed as to how many records were processed.
;[Assumption Action|ASSUMPTION_ACTION]:An assumption is either added to the database (a new premium or statistics) or is updating existing information (a wage increase or FTE change). That action will be indicated in this field.
;[Assumption Formula|ASSUMPTION_FORMULA]:This field holds the formula for the assumption.
;:For example, if you requires a wage increase of 2.5%, the statement for is assumption is ‘Let the wage rate be equal the wage rate times 1.025’.
;:Therefore the formula for his assumption would be:
;:Wage_Rate = Wage_Rate * 1.025
;:%%information Ensure you place spaces before and after the ‘=’ in the formula line.%%
;[Assumption Where|ASSUMPTION_WHERE]:This field allows you to limit the formula to the statement in the ‘where’ clause.
;:For example, if you wishes to increase the wage rate of all in Unit of AMW by 2.5%, the statement would be, ‘Let the wage rate be equal the wage rate times 1.025 where the employee’s Unit is AMW’
;:Therefore, the formula for the assumption would be:
;:Wage_Rate = Wage_Rate * 1.025
;:The ‘Where’ clause would be:
;:Group_Code = ‘FULL-TIME’
%%information FORMULA RULES\\All CHAR or alphanumeric information must be entered with single quotes around them.
\\Standard formula format is A = B + C not B + C = A, as with UserCalcs.
\\Formula: WAGE_RATE = WAGE_RATE * 1.0 (update)
\\Formula: PREMIUM_CODE = 'UNIFORM'(add)
\\Where: UNIT = 'alphanumeric'
\\Where: WAGE_RATE > 12.25
\\Where: VACANT not filled positions
\\Where: NOT VACANT only filled positions%%
\\
----
!!Assumption Logs
The Assumption Log tab is the record of all the assumptions that have been processed for the scenario you is currently viewing. The information for this screen will default in from the [P2K_FC_ASSUMPTION_LOGS] table. You may NOT edit the data in this tab, it is for viewing ONLY.
;[Seq|ASSUMPTION_SEQUENCE]:This field displays the sequential number of the processed assumption.
;[Description|DESCRIPTION]:This field provides a short description of the assumption.
;[Seat|BUDGET_SEAT_CODE]:This field will display the budget seat code.
;[Seat Title|BUDGET_SEAT_TITLE]:This field will display the seat title for this budget seat.
;[Effective|EFFECTIVE]:This field will show the date the assumption is to begin.
;[Expiry|EXPIRY]:This field will show the date the assumption is to end.
;[Before Value|BEFORE_VALUE]:This field displays the value of the ‘item’ prior to the assumption being processed.
;[After Value|AFTER_VALUE]:This field displays the value of the ‘item’ after the assumption has been processed.
----
![Notes|Edit:Internal.IFBA]
[{InsertPage page='Internal.IFBA' default='Click to create a new notes page'}]
;[Premium Level|PREMIUM_LEVEL]:Premium Level indicates where the premium originates. Premium_Level is a mandatory field you may fill with the fixed lexicon [X_PREMIUM_LEVEL].
;[Premium Rate|PREMIUM_RATE]:
This page (revision-26) was last changed on 26-Nov-2021 10:22 by rforbesTop