Wiki: IFBA

BUDGET AREA#

Budget Areas contain scenarios, budget seats (assignment and/or positions) and assumptions within each scenario. You may create and maintain budget areas through the Define Budget Areas (IFBA) form.
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.

Define Budget Areas data definitions are found in the P2K_HR_ASSIGNMENT_DETAILS, P2K_CM_POSITION_DETAILS,P2K_HR_ASSIGNMENT_DETAILS, P2K_CM_POSITION_DETAILS, P2K_FC_BUDGET_SEATS and P2K_FC_BUDGET_SEAT_DETAILS tables.

Scenario: 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: 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: 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: The field allows you to provide a short description of the scenario. Description is a mandatory 50-character alphanumeric field you must manually fill.

Rank: Rank is a mandatory 5-character numeric field you must manually enter.

Budget Seat: 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

Define Budget Areas (IFBA) - Budget Seats#

The definition data for the Budget Seat tab may be found in the P2K_BUDGET_SEATS.
Any seats EXCEPT for those of the base budget may be edited or deleted.

Budget Seat: 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: 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: A combination of the employee number and the position title Budget_Seat_Title is an optional 100-character alphanumeric field you may manually fill.

Context: This screen will be automatically filled by the system. The name of the employee in that position will appear. If the position is vacant, that will also be indicated.

Budget Seats (IFBA) - Seat Details#

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: 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: 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: 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: 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: 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: 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: 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_WAGESCALE_STEPS).

Scale Override: 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: 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.

Budget Seats (IFBA) - Seat Info#

The data for the Seat Info 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.

Position: This field displays the position assigned to the employee and/or for which the budget is being created.

Job: This field shows the job that the employee is hired to perform and which is associated to the position.

Unit: This field shows the unit affiliated with the employee and/or position.

Group: This field identifies the group that determines the policy rules under which the employee and/or position must be processed.

Department: This is the department to which the employee and/or position is assigned.

Work Rule: Work rules are used to determine the standard processing information required to create pay headers and transactions for an employee.

Range: Salary range provides minimum and maximum guidelines for the salary payable for the job. This range will can be used for a comparison with an employee's salary.

Status: This field indicates the employment status of the budget seat. This status will be derived either from the assignment details of an employee or from the default employment status of the group for vacant budget seats.

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.

Seq: The field will indicate the sequential order of the distribution split. Split_Sequence is a 5 digit mandatory field you must manually enter.

Distribution;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: 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 %: 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.

Budget Seats (IFBA) - Premiums#

The data for the Premiums 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.

Premium: 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: 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.

Abbreviation: This field will hold the abbreviated description of the pay component.

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 indicates where the premium originates. Premium_Level is a mandatory field you may fill with the fixed lexicon X_PREMIUM_LEVEL.

Premium Rate