Budget Level

The number of these tabs will vary by budget structure as will the names for each level. Not all fields listed in the table below are found on all budget transactions or even all levels within a single budget transaction. In addition to the common accounting line transaction fields found on the budget level tabs, there are several that are unique to the Budget Transaction. (Refer to the “Accounting” topic of the Transactions User Guide for information on common accounting fields.)

Field Name	Field Description
Action	A required value that will drive many edits and updates for a budget line. New, the default value will cause the creation of a budget line on a particular budget level. Modify is used when a budget line already exists and needs to be updated other than changing the active status of line. Deactivate and Reactivate support updates to the active status (an inactive line does not allow any updates by accounting transaction and only allows reactivation by a budget transaction). The appropriate Event Type must be paired with the action and the Line Amount must be $0.00. Delete is used to delete a budget line, only after all the stand alone budget amounts for the budget line are zero. When a budget transaction with this action submits to the Final transaction phase, the budget line will be deleted from the budget level, leaving only the Budget Journal history for the budget line. The appropriate Event Type must be paired with the action and the Line Amount must be $0.00.
Budget FY	A required field for those budget structures that display the Budget FY field. If left blank the field will default much like accounting transactions except where an accounting transaction will only populate that default when going to final, the budget transaction does it upon the first save of the budget line. A special value of 9999 can be used to define a multi-year budget line if that feature is configured for use.
Budget Reference	An optional text field for entering a legislative ID or other descriptive information about a budget line.
COA	Each budget level tab will contain different values and all must be entered on each budget line if a budget line is to be created or updated. In certain exception cases, rollup COA are inferred as part of data entry. In addition to being valid codes on their respective COA reference pages, codes must have the Budgeting indication selected. The inactive COA code edits done on accounting transactions do not apply to budget transactions. COA inference, combination validation, and required element pages do not apply to budget transactions either.
Contact	An optional field for specifying an individual as the contact person for a budget line. Valid values come from the Contact (CNTAC) reference page.
Contact Name	The name associated with the selected contact code is inferred from the Contact reference data.
Debt ID	An optional field found on budget transactions that control spending to allow you to enter the Debt ID of a Bond or Loan that provided funding to the budget line. The Debt ID is informational to explain ‘where’ the increase in budget availability came from. While the field shows choices for Leases, the primary types of debt that will be chosen are Bonds and Loans. There are limits on what ID values can be entered: An Authorization ID cannot be entered. A Loan Application ID cannot be entered. The Debt Instrument Status must be active and not one of the preliminary values. The Debt Instrument Status should not be one that is completed or closed. Please see the Debt Management User Guide for more information on these and other topics.
Description	An optional long text field for entering descriptive text about a budget line.
Dollar Amount	A required amount that will be used to update the budget amount identified by the posting code inferred from the Event Type selected. Whether the Dollar Amount will add to or subtract from the budget amount on the budget line will depend on the next field. Negative dollar amounts are not allowed. Changing the Name, Contact, Description, Reservation Type, Start Date, or End Date do not require an amount other than $0.00 as do the Deactivate, Reactivate, and Delete Action values. A budget line can also be created with a zero amount to later have amounts added or serve just to define a valid budget line that will not have any spending controls. Other situations where $0.00 can be the Dollar Amount: When only an allotment line is being added or modified Modification of a budget control at the line level Creation, modification, or deletion of a link Changing the Name, Contact, Description, Reservation Type, Start Date, or End Date values of a budget line The Deactivate, Reactivate, and Delete Action values are used
Fiscal Year	Although a common transaction field, Fiscal Year on a budget line will default upon the first save of a budget line unlike on accounting transactions when it will only default upon going to final.
Increase/Decrease	A required indication that will determine if the Dollar Amount will be added to or subtracted from the budget amount identified by the posting code of the event type being used. The default for this field is Increase. Keep in mind that increasing a budget amount that is subtracted in the calculation of budget availability is really decreasing budget availability.
Name	An optional text field for assigning a budget line a name for descriptive or identification purposes. If left blank upon the creation of a budget line, the application will establish a name for the budget line. That name will be a concatenation of the Chart of Account elements used to define the budget name or other customized value. If left blank with any other Action value, the existing name will remain with the budget line.
Period	Although a common transaction field, Period on a budget line will default upon the first save of a budget line unlike on accounting transactions when it will only default upon going to Final.
Reservation Type	This field is displayed on those budget transactions where spending is controlled with a Budget FY. The optional field serves as one of the methods for withholding budget authority, and must be defined on the Reservation Type (RSRVT) reference page. Please see the “Budget Reserve” topic for more information on this feature.
Start Date End Date	Optional dates primarily for reporting. Unlike the corresponding header fields that can default, these dates at the individual budget line do not default from the Budget FY field. They can, however, default from the header fields when populated there or from an Appropriation Unit entered on a budget line. Please refer to the “Inference of Start and End Dates on Budget Line” topic for instructions on how to infer dates based on a COA such as Appropriation. The only use of these dates beyond reporting is by the cost accounting feature known as Budget Fiscal Year Front End Split (BFY FES). That feature will compare the Record Date of a transaction to any Start or End Date specified for a budget line read in the process. If equal to either date or between them (note either could be blank), then the process will look to see if the budget line is active. If so, the feature considers the budget line. If not active, the feature skips the record. Refer to the "BFY Staging Configuration" topic in the CGI Advantage - Financial Administration User Guide for information on how to control what can and what cannot happen against a budget line based on what day is being used.

Field Name	Field Description
Funding Year	An optional field found only on reimbursement budget transactions that is the first of a set of fields that will trigger a funding control edits. Funding Year is only allowed if the Event Type is one that updates the Awarded budget amount. Funding Year field is required if the Region and Funding Source ID are populated, or Funding Group is populated, or Funding Allocation ID is populated. When Funding Year and Region are populated, those two values and the Department and inferred Funding Source ID are used to edit that the Award is possible given the Available amount of the matching Funding Source Control (FSC) record. If no match is found the transaction will reject. When Funding Year and Funding Group are populated, those two values and the Department are used to edit that the Award is possible given the Available amount of the matching Funding Group Control (FGC) record. If no match is found the transaction will reject. When Funding Year is populated and Funding Allocation ID infers, those two values and the Department are used to edit that the Award is possible, given the Available amount of the matching Funding Allocation Control (FAC) record. If no match is found the transaction will reject.
Region	An optional field found to invoke Funding Source Control edits. The first is a check to see combination of Department, Funding Year, Region, and inferred Funding Source ID. The second is to edit that the Award is possible given the Available amount of that matching record. Region is only allowed if the Event Type is one that updates the Awarded budget amount. When Region is populated and a Funding Source ID is inferred, a Funding Year is required.
Funding Group	An optional field to invoke Funding Group Control (FGC) edits. The first is a check to see combination of Department, Funding Year, and Funding Group exists. The second is to edit that the Award is possible given the Available amount of that matching record. Funding Group is only allowed if the Event Type is one that updates the Awarded budget amount. When Funding Group is populated a Funding Year is required.
Funding Source ID	Funding Source ID is an inferred field from the Funding Line entered on the budget line when the Event Type is one that updates the Awarded budget amount. The inference comes from the one of three fields populated for the Funding Line: Federal Appropriation Number, Debt ID, or Other Funding Source ID.
Funding Allocation ID	Funding Allocation ID is an inferred field from the Funding Line entered on the budget line when the Event Type is defined to update the Awarded budget amount. When Funding Allocation ID is populated a Funding Year is required.
FHWA Improvement Type	FHWA Improvement Type is a field only found on level 2 of the Program Phase Reimbursable Budget 40 (BGPHR) transaction. This field captures the FHWA Improvement Type entered or inferred for a budget line. A value will infer first from the Program Phase (PHPRG) record, if defined there, that matches the Program and Phase entered on the budget line. If there is no default then a value will infer from the Program (PROG) record, if defined there, that matches the Program on the budget line. If setup in neither location, a valid value from the FWHA Improvement Type (IMPTYP) reference page can be entered. In the event an existing value that did not default from PROG or PHPRG needs to be cleared out for a budget line, a special value of BLNK can be entered on a Modify budget line.
Allotment Distribution Amount	For those budget structures with allotment functionality, this amount is displayed on the tab of the budget level e budget level allotted. The primary use of the amount field is to facilitate the definition of allotment lines with only a percentage value and let the application determine the actual allotment line amounts by multiplying that percentage against the Allotment Distribution Amount. If that amount is $0.00, the application will multiply the percentages against the Dollar Amount instead. The secondary use of the amount field is to provide an amount to edit the sum of allotment line amounts against. In the case that the allotment line amounts were manually entered, the amount serves to check that the total amount allotted was what was intended. If the amount is $0.00, then the sum of the allotment line amounts cannot exceed the Dollar Amount. The amount defaults to $0.00. It can even exceed the Dollar Amount. In the case where the full amount of a previous budget transaction was not allotted, a subsequent transaction will need to have an amount greater than the Dollar Amount to facilitate allotting the remainder.
Allotment Formula ID	For those budget structures that have allotment functionality on the budget level allotted, this field can be used with the Auto Allotment Distribution action (after making both visible) to automatically create allotment lines based on setup on the Allotment Formula (AFOR) page that distributes the Allotment Distribution Amount. If that amount is $0.00 then the Line Amount is distributed.
Transfer Limit Editing	For those budget structures designed to limit transfers out to a percentage of a ‘base budget’ amount, this field is used to define whether an individual budget line is subject to the edit. The choice of Enabled will force the budget transaction to update the Appropriation Transfer Limit. A choice of Disabled will cause the system to skip those updates. The third choice, Unchanged, is used for all budget line adjustments where the current setting is not being changed. (See the “Advanced - Unique Features” topic for more information on this field that is initially hidden).
Text 1 Text 2 Text 3 Text 4	A number of generic, optional text fields are available for select structures to capture additional information beyond Name, Budget Reference, and Description for reporting reasons either as groupings, descriptive details, or interface needs. The values are additionally stored in the Budget Journal (JBUD) and select inquiry pages. The fields are delivered as optional and hidden, so they must first be made visible on Configure Page (DESIGNER) and then any required editing rules applied through Configurable Validations (BORULE). The lengths of each are as follows: 250, 250, 1500, and 250. If desired, a Configurable Rule (BORULE) can be used to define a shorter maximum length, a minimum length, a data type, or even a list of valid values.
Budget Classification	An optional field, supported by the Budget Classification (BUDCLSF) page, is available for select structures to classify budget line updates using pre-defined classifications. The value is additionally stored in the Budget Journal (JBUD). As the field is optional, a Configurable Validation is needed if it is to be required for all budget line updates based on the Line Action and perhaps the Event Type.
Decimal 1	An optional generic decimal field to capture information such as FTE on the budget line. The values are additionally stored in the Budget Journal (JBUD) and select inquiry pages. The fields are delivered as optional and hidden, so they must first be made visible on Configure Page (DESIGNER) and then any required editing rules applied through Configurable Validations (BORULE).

Refer to the "Specialty Actions" topic for information on the actions available on this tab.