Overview
This is a container that allows to have several budget versions, sharing same ceiling structure (data can be different) and also same budget parameters.
A Budget Planning Scenario can be used for budget planning and also for forecasting purposes. A Budget Planning Scenario contains information about Budget Planning Scenario Fiscal Year that has the collection (one to many) of fiscal years allowed to each Scenario which can be used for scenario forecasting and also to accommodate concepts such as MTBF (Medium Term Budget Framework). It also contains a Budget Planning Scenario CoA Group that has the collection (one to many) of CoA groups allowed in each Scenario which will be used to establish the different levels of budget plans within the COA hierarchy.
Navigation
Budget Planning ► Support Entities ► Scenarios ► Budget Planning Scenario
Budget Planning Scenario Screen Fields and Tabs
Field | Description |
Code | This is a unique identifier that is automatically assigned by the system, if the system parameter Generate Scenario ID is set to True, or manually entered by the user if the system parameter Generate Scenario ID is set to false. |
Active | This field is true by default. If user switches this to FALSE then this scenario cannot be used in future transactions. |
CoA | The User must select the CoA which is going to be used for this scenario. |
Administrator | This is the user who acts as an administrator for this scenario who will have the permissions to manage administration functions related to the scenario. |
Consolidated Amounts Distribution Type | This attribute will define type of propagation of changes of consolidated amounts. Possible values are ‘Manual’ or ‘Automatic’. If this parameter is set to “Manual”, each budget plan responsible user will need to update the budget plan amounts, after a consolidated amount is modified. If the parameter is set to “Automatic”, the system will automatically propagate the changes of consolidated amounts to lower levels budget plans. |
Fiscal Period Distribution Needed | The default value is FALSE. If this value is switched to true then the system will allow entering information at the fiscal period level. This distribution can be done in any moment of the budget planning process. |
Rounding Value | Rounding value applied to Budget LIne Domestic Amount, Budget Line Foreign Amount and Budget Line Distribution Amount. |
Method of Rounding | Method of rounding. |
Language | Country specific language that is used to describe the Budget Planning Scenario. |
Name | The name of the Budget Planning Scenario. |
Description | This contains the full description of the scenario. |
Budget Planning Scenario Fiscal Year Tab | This contains the collection (one to many) of fiscal years allowed to each Scenario that can be used for scenario forecasting and also to accommodate concepts, such as MTBF (Medium Term Budget Framework). |
Budget Planning Scenario CoA Group Tab | This contains the collection (one to many) of CoA groups allowed to each Scenario that will be used to establish the different levels of budget plans, with the COA hierarchy. |
Fiscal Period Distribution Tab | This contains the collection of coding block expressions used for distribution if Fiscal Period Distribution Method is “Automatic Uniform” of “Automatic Weighted”, as well as the percentages used by the “Automatic Weighted” method. |
Attachments Tab | This attribute is used to attach one or more files to detail features of the Scenario. |
Overview
This contains the collection (one to many) of fiscal years allowed to each Scenario that can be used for scenario forecasting and also to accommodate concepts, such as MTBF (Medium Term Budget Framework).
Budget Planning Scenario Fiscal Year Tab screen Fields
Field | Description |
Fiscal Year | This attribute will contain the Fiscal Year that is to be allowed in the Scenario. |
Apply for Budget Planning | This is False by default. If it is switched to true then the fiscal year will be used for budget planning and also for forecasting purpose. |
Budget Plans Read Only | If checkbox is not selected, Budget Line Detail Data Entry can be done for this Scenario Fiscal Year, otherwise the Budget Line Detail information is read-only. |
| Apply Ceilings | This is False by default. If set to true, the system will verify that each budget line entered manually or automatically is associated to a Budget Ceiling and Budget Line Coding Block should be validated when inserting a new Budget Line. |
Overview
This contains the collection (one to many) of CoA groups allowed to each Scenario that will be used to establish the different levels of budget plans, with the COA hierarchy.
Budget Planning Scenario CoA Group Tab screen Fields
Field | Description |
CoA Group | This is the reference to the CoA Group that is to be allowed in the Scenario. |
Apply For Ceilings | The default value of this attribute is true. If this checkbox is not ticked, this CoA Group level won't be used for ceilings definition and validation, it will only be used for budget planning data entry. |
| Is Mandatory to Apply to All Budget Lines | It is to determine whether it will apply to all Budget Lines or not. Default value TRUE when "Apply for Ceilings?" is TRUE, otherwise FALSE. User can change to TRUE only when "Apply for Ceilings?" is TRUE. |
| Is Display Ceiling Amount In Validation Message | Default is True meaning that the Ceiling Amount is included in the Ceilings Validation message. If set to False, the Ceiling Amount will not displayed in the Ceilings Validation message. |
Lower Level CoA Group | This attribute is a circular reference to a different Scenario CoA Group which will be in the lower level. |
| Scale For Data Entry And Display Budget Ceilings | Close domain with possible values: "UNIT" - "1" "TEN" - "10" "HUNDRED" - "100" "THOUSANDS" - "1000" "TEN_THOUSANDS" - "10000" "MILLION" - "1000000" "BILLIONS" - "1000000000" "TRILLIONS" - "1000000000000" During data entry of Budget Ceiling, system will show scale to be used for data entry and display of Budget Ceiling amounts. If set to "THOUSAND - 1000", the Budget Ceiling Amounts will be in 1000. This is only for display, system should save in database amounts in units, and only use this parameter for data entry and display. |
Overview
This attribute is used to attach one or more files to detail features of the Scenario.
Attachments Tab screen Fields
Field | Description |
Id | An unique number auto generated by the system. |
| Attachment Classification | Types of attachment. Document Type like- PDF, Word, excel etc |
Language | It represents the language of the document. |
Title | Title of the document attached. |
Description | This is defined by users and contains the description of the Attachment. |
Attachment | The document to be attached is to be selected from the 'Browse' option. |
Date Time | This shows the date and time of the last operation that has been performed on the attachment document. |
| Date | Manually enter by the user for the Attachment date. |
User | This is the last user who have uploaded or updated the document. |
Language | This is the language used in the attachment file. |
Overview
This contains the collection of coding block expressions used for distribution if Fiscal Period Distribution Method is “Automatic Uniform” of “Automatic Weighted”, as well as the percentages used by the “Automatic Weighted” method.
Field | Description |
Fiscal Year | Collection of 1 to many Scenario Fiscal Year(s). |
CoA Group | This will contain a collection (one to many) of CoA groups allowed to each Scenario. |
Coding Block Type Definition | Users need to enter either a coding block or an expression. Level of the mentioned coding block will be the lowest level defined in Scenario COA Group entity. A coding block expression will allow defining a group of coding blocks. |
Overview
Distribution detail per each fiscal period.
Field | Description |
Distribution Concept | Refers to the Distribution Concept. |
Remaining | Indicates if the detail will distribute remaining amount. |
Percentage | Value bewteen 1.00 to 100.00 with 2 decimals. The sum of this field for all concepts in this entity, and same scenario or Version can't exceed 100.00 |