Inbound Combination Edit Spreadsheet Upload (GLI084)
-
Print
-
DarkLight
-
PDF
Inbound Combination Edit Spreadsheet Upload (GLI084)
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Interface Description
The Inbound Combination Edit Spreadsheet upload gives Agencies the ability to upload in mass, combination edit rule configurations instead of having to manually maintain the rules using the online Combination Edit pages.
Click below to view the interface file layout and sample data file.
Business Process Model
This interface can be found in the following business processes:
- 10.1.1 Agency Add or Modify ChartField Values
- 10.1.5 Enterprise Set Up and Maintain Trees and/or Combination Edits
Interface Selection Criteria
The interface data selection criteria includes the following:
Data Field | Data Field Details |
|---|---|
SetID | Required |
Combination | Required |
File Layout
The layout of the interface is listed below.
| Data Field | Record Type | Data Field Description |
|---|---|---|
| Agency Business Unit | Detail | Designate the Agency Business unit to which the new combo rule will be established. |
| Process Group | Detail | Designates the process group the combination edit rule is assigned to in Florida PALM configuration |
| Combination Rule | Detail | Designates the Combination Edit Rule that is configured in Florida PALM. |
| Seq Nbr | Detail | Sequence Number establish how many combinations is/are to be loaded. |
| Organization | Detail | Organization ChartField tracks information according to a breakdown of your organization. |
| Account | Detail | Provides functionality to capture detailed transactional data. Can be specified as a balance sheet account or operating account. |
| Fund Code | Detail | Segregates and captures specific activities or classifies certain objectives in accordance with special regulations, restrictions, or limitations. |
| Budget Entity | Detail | Budget Entity ChartField represents organizations and/or functions to which appropriations are made and typically represents a program. |
| Category | Detail | Category ChartField represents both appropriation categories and revenue source codes. |
| State Program | Detail | Stores Chart of Accounts information and provides the basic structure to segregate and categorize transactional and budget data. |
| Grant | Detail | Grant ChartField is used for tracking grants funding. |
| Contract | Detail | Contract ChartField captures expenditure and revenue transactions for two party agreements. |
| OA1 | Detail | OA1 tracks optional organization reporting, cost pools, expenditures, revenues, or other specific use. |
| OA2 | Detail | OA2 tracks optional organization reporting, cost pools, expenditures, revenues, or other specific use. |
| PC Business Unit | Detail | Project Costing Business Unit. |
| Project | Detail | Project ChartField is used to capture a planned undertaking of something to be accomplished or produced, having a beginning and ending date, for which expenditures/costs and revenues are to be tracked. |
| Activity | Detail | Tracks specific tasks that make up a Project and records transactional details; a Project must have at least one associated Activity ID. |
| PC Source Type | Detail | Source types identify the purpose or origin of a transaction. |
| PC Category | Detail | Project Category provides more flexibility and granularity in tracking and analyzing costs; not required. |
| PC Subcategory | Detail | Subcategories provides more flexibility and granularity in tracking and analyzing costs; not required. |
Version History
Date | Revision Description |
|---|---|
12/01/2023 | Original Version |
| 07/08/2024 | Sample Data File Updated |
Was this article helpful?
