Enterprise Set Up and Maintain Trees and or Combination Edits (10.1.5)

Business Process Overview

DFS maintains Tree and ChartField Combination Edit for statewide use in recording and reporting within Florida PALM. A Budgetary Value Combination edit of Business Unit, Fund, Budget Entity, and Category will be maintained by DFS for each agency. Agencies may request configuration or modifications to the Budgetary Value Combination Edit by notifying DFS. The Budgetary Value edit will limit the COA values used on transactions to the specified values in the designated edit for an agency.

Business Process Diagram

Business Roles

The Business Process Flow Diagrams use horizontal swim lanes to depict where activities are performed by different parties or systems. Each swim lane is titled with a role, either agency-based or within DFS and in some cases, is representative of an external entity or system. The swim lanes may change from page to page within a single business subprocess as more or fewer roles are required to execute sections of the business subprocess. 

• DFS GL COA Maintainer: DFS role responsible for completing approved updates and modifications to ChartFields

Business Process Flows Details

The tables below describe steps in each business subprocess as reflected on the Business Process Flow Diagrams. The tables also reflect information associated with each step describing the intent of the specific process. Florida PALM screenshots are included within the sections to allow connections to be made from specific business subprocess steps to screens within Florida PALM. This information should be read in conjunction with the Business Process Flow Diagrams.

Tree Manager Page

ChartField Combination Editing Definition

ChartField Combination Editing Rule

ChartField Combination Editing Group

Accounting Events

Accounting events originate during transaction processing in the applicable source module. The accounting events impact the source module, Commitment Control ledgers, and the General ledger (Actuals).

• Source Module accounting entries require user input (I) of the primary line (i.e., expenditure, revenues) with an automated (A) system offsetting line (i.e., payable, receivable) during transaction entry. The source model transaction must pass Edit Check, Budget Check, and Cash Check (on applicable entries) prior to posting the transaction.
• The Run Budget Check (Commitment Control) process automatically affects balances in the appropriate budget ledger (i.e., appropriation, spendable cash) if the transaction passes the budget check process.
• After the transaction is posted in the source module, an automated system process summarizes and posts the entries in the General Ledger module to the Actuals Ledger.

The table below provides the most common accounting events applicable to this business process.

Reports

Key Reports are displayed as icons with the Report Number on the Business Process Flow Diagrams. The table below provides the reports identified to be produced at a particular process step or used to support the completion of a process step.

Conversions

The table below identifies the Conversions related to this Business Process. These items are not included within the Business Flow Diagrams; however, these items are important elements of each Business Process.

Interfaces

The table below provides the Interface IDs for each interface identified on the Business Process Flow Diagrams.

Forms

The table below provides the Form Numbers for any forms identified on the Business Process Flow Diagrams.

Workflows

The table below provides the Workflow Numbers for any workflows identified on the Business Process Flow Diagrams.

Version History