Project Related ChartFields

Design

When using a Project value, there are four additional Project-related ChartFields for agency use. The transactions that are recorded with these ChartFields allow agencies to access module features and functions to manage their operational and reporting needs.

The Activity ChartField tracks specific tasks that make up a Project and records transactional details. Each Project must have at least one associated Activity and may have multiple. Activity may be assigned to multiple projects. Activity values are up to fifteen (15) characters in length and established and maintained by DFS.

Source Type, Project Category, and Subcategory values are optional and not specific to a Project and can be used across multiple Projects at the agency’s discretion. The Source Type ChartField identifies the purpose or origin of a Project-related transaction. The Project Category and Subcategory ChartFields provide more flexibility and granularity in tracking and analyzing costs. To use a Subcategory value, you must use a Project Category value. Source type, Project Category, and Subcategory are not related and can be used independently but require a Project and Activity to be recorded. Source Type, Project Category, and Subcategory values are five (5) characters in length and are established as appropriate by each agency.

The following design considerations are applied when defining an Activity, Source Type, Project Category, and Subcategory in Florida PALM:

• Values are GL and PC Business Unit specific and only available for use by the associated GL Business Unit; these values are not shared across agencies
• Activity is required on a transaction when a Project value is used
• Activity values must be unique within a Project, but may be repeated across the agency
• Activity values are established and maintained at a statewide level by DFS and available for use by all agencies
• Source Type, Project Category, and Subcategory values are uniquely numbered
• Source Type, Project Category, and Subcategory are optional on all transactions that use a Project
• Source Type, Project Category, and Subcategory are established through the PC Module

Assumptions

The following assumption is considered when defining a Project-related ChartField value:

• Agencies follow internal agency-specific procedures to establish Project-related ChartField values
• Agencies define the most critical use of the Project-related ChartFields to capture financial data for reporting purposes. The identified critical use must be the primary use of the ChartFields across the agency
• The ChartField Structure Request is not available for Project-Related ChartFields

Maintenance

Project-related ChartField values, excluding Activity are maintained by each agency. Agencies can add or modify applicable Project-related ChartField values.

Version History