Outbound Budget Detail Extract (KKI009)
- 29 May 2024
- 5 Minutes to read
-
Print
-
DarkLight
-
PDF
Outbound Budget Detail Extract (KKI009)
- Updated on 29 May 2024
- 5 Minutes to read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Interface Description
This Interface provides Agency Business Systems with all Budget Detail Activity details from Florida PALM in a Flat File format output. This interface will create separate data files for each Agency Business Unit based on run control parameters. The interface will be available for a variety of selection criteria including but not limited to:
- Commitment Control (KK) Budget Ledger groups (Appropriations, Releases, Reserves, Projects, Allotments and Revenue).
- Budget Journal Status: budget journals that are not yet edited, not yet submitted for approval, approved but not yet posted, posted, or in error.
Click below to view the conversion file layout and sample data file.
Business Process Model
This interface can be found in the following business processes:
- 20.1.1 Enterprise Post Appropriations
- 20.1.2 Manage Agency Allotments
- 20.1.4 Agency Estimated Revenue
- 20.2.1 Manage Budget Checking
- 20.2.2 Manage Cash Checking
- 20.2.3 Invested Balance Checking
- 20.3.1 Carry Forward
- 20.3.2 Certified Forward
- 20.3.3 Continuing Appropriations
Interface Selection Criteria
The interface data selection criteria includes the following:
| Data Field | Data Field Details |
|---|---|
| Business Unit | Required |
| Ledger Group | Required |
| Budget Header Status | Optional |
| Journal Date From | Required |
| Journal Date To | Required |
File Layout
The layout of the interface is listed below.
| Data Field | Record Type | Data Field Description |
|---|---|---|
| Field Name | Record Type | Description |
| Record Code | Journal Header | Record Code identifying the information on the record. |
| Business Unit | Journal Header | Used to define an organization or organizational subset that is independent with regards to one or more accounting or operational functions. Legacy Mapping: Operating Level Organization (OLO) |
| Journal ID | Journal Header | Identifies a journal entry, consisting of a header and one or more lines. The Journal ID itself does not have to be unique, but together with the journal business unit and journal date, it forms a unique journal identifier. |
| Journal Date | Journal Header | Specifies the date the journal was created. |
| System Source | Journal Header | Shows how the budget journal was entered into Florida PALM. System sources for KKI009, which are informational only for agencies to note how the budget journal was entered into Florida PALM. • PNL - Online Journal Entry Page • SCP - Journal Copy |
| Budget Header Status | Journal Header | Shows the budget status of the journal. |
| Ledger Group | Journal Header | A ledger consists of posted balances that represents a set of books for a business unit. |
| Journal Header Amount | Journal Header | Shows the total amount for the budget journal, debits plus credits. |
| Journal Header Description | Journal Header | Used to give a short description of the purpose of the journal |
| Filler1 | Journal Header | This field is reserved for future use in Florida PALM. |
| Filler2 | Journal Header | This field is reserved for future use in Florida PALM. |
| Filler3 | Journal Header | This field is reserved for future use in Florida PALM. |
| Filler4 | Journal Header | This field is reserved for future use in Florida PALM. |
| Filler5 | Journal Header | This field is reserved for future use in Florida PALM. |
| Record Code | Journal Line | Record Code identifying the information on the record. |
| Business Unit | Journal Line | Used to define an organization or organizational subset that is independent with regards to one or more accounting or operational functions. Legacy Mapping: Operating Level Organization (OLO) |
| Journal ID | Journal Line | Identifies a journal entry, consisting of a header and one or more lines. The Journal ID itself does not have to be unique, but together with the journal business unit and journal date, it forms a unique journal identifier. |
| Journal Date | Journal Line | Specifies the date the journal was created. |
| Journal Line | Journal Line | Identifies the individual lines on the budget journal |
| Budget Period | Journal Line | Budget Period (Appropriation year). |
| Organization | Journal Line | Tracks information according to a breakdown of the organization. |
| Account | Journal Line | Provides functionality to capture detailed transactional data. |
| Fund | Journal Line | Used to segregate and capture specific activities or classify certain objectives in accordance with special regulations, restrictions, or limitations (e.g., restricted fund). |
| Budget Entity | Journal Line | Represents organizations and/or functions to which appropriations are made and typically represents a program. |
| Category | Journal Line | Category ChartField represents both appropriation categories and revenue source codes. |
| State Program | Journal Line | Stores Chart of Accounts information and provides the basic structure to segregate and categorize transactional and budget data. |
| Grant | Journal Line | Grant ID value used to track financial assistance that provides support or stimulation to accomplish a public purpose. |
| Contract | Journal Line | Contract ChartField captures expenditure and revenue transactions for two party agreements. |
| OA1 | Journal Line | Service Location. It used to identify specific appropriations. |
| OA2 | Journal Line | Stores Chart of Accounts information and provides the basic structure to segregate and categorize transactional and budget data. |
| PC Business Unit | Journal Line | Project Costing Business Unit |
| Project | Journal Line | 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 | Journal Line | 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 | Journal Line | PC Source Type identifies the purpose or origin of a transaction. |
| Line Amount | Journal Line | Shows the amount for the individual lines on the budget journal |
| Journal Classs | Journal Line | Identified the type of reserve amount. |
| Budget Line Status | Journal Line | Identifies the budget status of the line |
| Filler1 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler2 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler3 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler4 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler5 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler6 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler7 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler8 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler9 | Journal Line | This field is reserved for future use in Florida PALM. |
| Filler10 | Journal Line | This field is reserved for future use in Florida PALM. |
Version History
| Date | Revision Description |
|---|---|
| 12/01/2023 | Original Version |
| 05/24/2024 | Update System Source Field Description |
Was this article helpful?
