Attachment L Requirements Traceability Matrix Software Requirements.xlsx
XLSX spreadsheet 48 KB Posted
- Solicitation number
- S000000321
- Issued by
- Arkansas
About this file
This document outlines a state and local contract opportunity for SAP S/4HANA Implementation and Upgrade Services for the state of Arkansas, specifically for the jurisdictions of Pulaski County and the City of Little Rock. The scope of work includes upgrading the state's existing ERP system, AASIS ECC, to the SAP S/4HANA platform. The key objectives are to improve efficiency through business process reengineering and automation, modernize technology, support data-driven decision making, and comply with legal and reporting requirements. The contract will cover project management, discovery, configuration, integration, testing, training, and post go-live support services. The contract term is for an initial 3-year period, with the potential for up to 4 one-year renewals, not to exceed a total of 7 years. Proposals are due by April 24, 2024.
The total budget or award value for this contract is not specified. The existing technology environment includes on-premise HANA database versions, SAP ERP Central Component (ECC), Business Warehouse (BW), and various other SAP and third-party components that will need to be integrated with the new S/4HANA system. The contract does not appear to have any set-aside designations or restrictions on the types of organizations that can respond, and the state has not identified any incumbent vendors or current contractors for this work.
View the file
Other files
Show all 26
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
HRPay integration
| End-to-End Process | Sub-Process | Activity | Module | Requirement Desc | Sub-Requirement | Requirement (The System shall...) | Priority | Notes/Context | Sort1 | Sort2 | Requirement Source |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 000 | The system shall provide outbound integration of the following financial structures from S/4HANA to the HR Solution | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 001 | Commitment Item | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 002 | Cost Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 003 | Functional Area | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 004 | Fund | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 005 | Funded program | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 006 | Funds Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 007 | Grant | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 008 | Internal Order | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 009 | Profit Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 010 | WBS Element | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 011 | Segment | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 012 | General Ledger Account | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 013 | Sponsored Class | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | FI-CO |
FI-GL
FI-GRANTEE
FI-PS
| HR INTEGRATION | Outbound Financial Master Data | 014 | Sponsored Program | ||||
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 000 | The system shall provide outbound integration of the following financial structures from S/4HANA to the Time Capture Solution | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 001 | Commitment Item | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 002 | Cost Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 003 | Functional Area | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 004 | Fund | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 005 | Funded program | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 006 | Funds Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 007 | Grant | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 008 | Internal Order | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 009 | Profit Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 010 | WBS Element | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 011 | Segment | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 012 | General Ledger Account | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 013 | Sponsored Class | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 014 | Sponsored Program | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 000 | The system shall provide outbound integration of the following financial structures from S/4HANA to the Payroll Solution | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 001 | Commitment Item | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 002 | Cost Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 003 | Functional Area | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 004 | Fund | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 005 | Funded program | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 006 | Funds Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 007 | Grant | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 008 | Internal Order | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 009 | Profit Center | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 010 | WBS Element | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 011 | Segment | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 012 | General Ledger Account | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 013 | Sponsored Class | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Financial Master Data | 014 | Sponsored Program | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Employee Self Service Information | 000 | The system shall provide outbound integration of the following financial structures from the timekeeping solution to the Employee Self Service Solution | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Employee Self Service Information | 001 | Time Taken | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Outbound Employee Self Service Information | 002 | Leave Balance | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | 000 | The system shall provide for inbound information from the HR Solution to S/4HANA: | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0000-Actions | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0001-Organizational Assignment | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0002-Personal Data | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0006-Addresses | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0077-Additional Personal Data (if needed for EEO reporting) | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0105-Communication | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | xxx | 0027 - Cost Distributions | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Employee Mini-Master | 000 | The system shall provide for the inbound integration of the following Organizational Management objects from the HR solution to S/4HANA | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Organizational Management Objects | 001 | Organizational Units | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Organizational Management Objects | 002 | Positions | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Organizational Management Objects | 003 | Jobs | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Inbound Organizational Management Objects | 004 | Cost Center for Position | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | HR Vendor Integration | 001 | The system shall provide for outbound integration from S/4HANA to the Payroll Solution for HR Vendors | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Drill-down from Summary Payroll Posting to Employee level information | 001 | The system shall provide for bidirectional integration to allow for drill down to the underlying data by employee and financial accounting object from the HR/Payroll FI Posting. | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | ACH remittance advice for Garnishments. | 001 | The system shall provide for inbound integration of Garnishment information from the Payroll solution to the S/4HANA solution (for inclusion on ACH remittance advice). | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Payment Documents in S/4 for Bank Reconciliations | 001 | The system shall provide for inbound integration from the Payroll Solution to S/4HANA for payment information (updates to tables PAYR and REGUH for externally printed warrants). | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Payroll Posting to Finance | 000 | The system shall provide for inbound integration from the Payroll Solution to S/4HANA for: | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Payroll Posting to Finance | 001 | Gross to Net Payroll Expense Posting | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Payroll Posting to Finance | 002 | Third Party Remittance Invoices | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Payroll Posting to Finance | 003 | Net Payroll Cash Postings | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Budget Check for HR Payroll Expense | 000 | The system shall provide for bi-directional integration between the Payroll Solution and S/4HANA to check available budget for pending payroll expenses: | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Budget Check for HR Payroll Expense | 001 | When simulating payroll expense postings | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Budget Check for HR Payroll Expense | 002 | Prior to posting payroll expense | |
| 00 System-Wide | HR Payroll Integration | Outbound Financial Master Data | HR INTEGRATION | Budget Check for HR Payroll Expense | 003 | At earlier points prior to simulating payroll expense postings (please provide a detailed explanation of when this is possible) |
Requirements Traceability Matri
| End-to-End Process | Sub-Process | Activity | Module | Requirement Desc | Sub-Requirement | Requirement (The System shall...) | Sort |
| 00 System-Wide | 00 System-Wide | 01 Attach Documents | ALL | Classify Attachments | 001 | The system shall allow users to assign a classification to an attachment (e.g., Vendor W-9) | 1 |
| 00 System-Wide | 00 System-Wide | 01 Attach Documents | ALL | Classify Attachments | 002 | The system shall prevent users from viewing attachments if they do not have authorization to view, change or delete the Attachment Classification. | 2 |
| 00 System-Wide | 00 System-Wide | 02 Custom Reporting | ALL | Include Public Sector Objects in SAP Cloud Analytics CDS Views | The system shall provide that all Funds Management and Grants Management objects are included in Core Data Services views that are determined to be in scope. | 3 | |
| 00 System-Wide | 00 System-Wide | 03 Maintain Business Partners | ALL | Integration with Standard Address Service | The system shall support integration with a Standard Address Service to improve the consistency of addresses throughout the system and to reduce the risk of duplicates. | 4 | |
| 00 System-Wide | 00 System-Wide | 04 System Integrations | ALL | Technical System Integrations | The system shall provide the ability to integrate with Vertex Inc. for Sales and Use Tax Generation. | 5 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Encryption | The technical environment shall provide the ability to encrypt outbound files. | 6 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Encryption | The technical environment shall provide the ability to decrypt inbound files. | 7 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Encryption | The technical environment shall provide the ability to generate and store encryption keys. | 8 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Extracts | The system shall provide the ability to extract various types of Vendor data into a format consumable by agencies. | 9 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Extracts | The system shall provide the ability to extract various types of Financial data into a format consumable by agencies. | 10 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Extracts | The system shall provide the ability to extract various types of Asset data into a format consumable by agencies. | 11 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Data Extracts | The system shall provide the ability to customize file layouts for extracts to be consumed by agencies and vendors. | 12 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | File Storage | The technical environment shall provide the ability to securely store encrypted inbound and outbound files for a retention period. | 13 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | File Storage | The technical environment shall provide the ability to securely view stored encrypted inbound and outbound files during the retention period. | 14 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Notifications | The technical environment shall provide the ability to send notifications for missing files. | 15 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Notifications | The technical environment shall provide the ability to send email notifications for successful file processing. | 16 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Notifications | The technical environment shall provide the ability to send email notifications for failed file processing. | 17 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 000 | The technical environment shall provide the ability to process encrypted files, such as: | 18 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 001 | • BSEG files | 19 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 002 | • DHS CHRIS/TANF vendors files | 20 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 003 | • Bank routing number files | 21 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 004 | • Fleet files | 22 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 005 | • Vendor files from Tyler Technologies portal | 23 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 006 | • Fund activity files from AIRS | 24 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 008 | • Agency CO Plan Data | 25 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 009 | • Employee Benefit Billing files from Vendor | 26 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | 010 | • BAI Files for bank clearing data | 27 |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | The technical environment shall provide the ability to monitor scheduled jobs. | 28 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | The technical environment shall provide the ability to research / troubleshoot errors including, but not limited to logs, spools, etc... | 29 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | The technical environment shall provide the ability to load system tables using encrypted files. | 30 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | The technical environment shall provide the ability to append a date / time stamp to incoming and outgoing file names. | 31 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | The technical environment shall provide the ability to automatically route files to a specified location based on the naming convention of the file. | 32 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | Interface File Processing | The technical environment shall provide the ability to export and encrypt generated 1099 files. | 33 | |
| 00 System-Wide | 00 System-Wide | 05 Technical Interfaces | ALL | NACHA Regulations | The technical environment shall be compliant with NACHA Regulations. | 34 | |
| 00 System-Wide | 00 System-Wide | 06 User Support | ALL | Context Sensitive Help | 000 | The system shall provide context sensitive help, such as: | 35 |
| 00 System-Wide | 00 System-Wide | 06 User Support | ALL | Context Sensitive Help | 001 | • documenting next steps in a process | 36 |
| 00 System-Wide | 00 System-Wide | 06 User Support | ALL | Context Sensitive Help | 002 | • field level guidance | 37 |
| 00 System-Wide | 00 System-Wide | 06 User Support | ALL | Context Sensitive Help | 003 | • Linkage to state-specific policies and procedures related to an end-user activity | 38 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Control Budget at Level below Legal | 000 | The system shall support multiple availability control budgets: | 39 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Control Budget at Level below Legal | 001 | Appropriation Control budgets | 40 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Control Budget at Level below Legal | 002 | Project budgets | 41 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Control Budget at Level below Legal | 003 | Organizational Budgets | 42 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Control Budget at Level below Legal | 004 | Program Budgets | 43 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Provide Flexible Budget Warning Levels | 000 | The system shall allow for multiple levels of severity for Availability Control Budgets, for example: | 44 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Provide Flexible Budget Warning Levels | 001 | Budget warning when a threshold is met (e.g., 80 percent) | 45 |
| 01 Plan To Report | 01 Budget Management | 01 AVC Ledgers | FI-FM | Provide Flexible Budget Warning Levels | 002 | Budget error when the total budget is consumed | 46 |
| 01 Plan To Report | 01 Budget Management | 02 Budget Transfers | FI-FM | No Unauthorized Budget Transfers across Legal Budget | 001 | Prevent unauthorized users from posting a budget transfer that crosses the FM objects used for legal budgeting | 47 |
| 01 Plan To Report | 01 Budget Management | 02 Budget Transfers | FI-FM | No Unauthorized Budget Transfers from/to "Special Characters" | 002 | Prevent unauthorized users from posting a budget transfer to or from a "Special Character" (Control Object for the Commitment Item) | 48 |
| 01 Plan To Report | 01 Budget Management | 02 Budget Transfers | FI-FM | Prevent use of Statistical Commitment Items in Budget Transfers | 000 | Prevent the transfer of budget to a statistical commitment item | 49 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 000 | The system shall determine the following Commitment Item Attributes from General Ledger Accounts when automatically creating Commitment Items from GL Accounts. | 50 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 001 | Financial Transaction 30 for Commitment Items to be posted to Funds Management | 51 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 002 | Financial Transaction 50 for Commitment Items not posted to Funds Management where the General Ledger Account is a manual clearing account | 52 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 003 | Financial Transaction 60 for Commitment Items not posted to Funds Management where the General Ledger Account is a reconciliation account | 53 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 004 | Financial Transaction 90 for Commitment Items not posted to Funds Management where the General Ledger Account is a cash-related account | 54 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 005 | Commitment Item Category 1 for asset and liability General Ledger Accounts | 55 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 006 | Commitment Item Category 2 for fund balance/net position, revenue, and other financing source General Ledger Accounts | 56 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 007 | Commitment Item Category 3 for expense and other financing use General Ledger Accounts | 57 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 008 | Statistical Flag set for Fund Balance GL Accounts that are not closing to the Modified Accrual Fund Balance Account | 58 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 009 | Statistical Flag set for Revenue, Expense, Other Financing Sources and Uses that are used to reconcile between Modified and Full Accrual | 59 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 010 | Statistical Flag set for Revenue, Expense, Other Financing Sources and Uses that are used to reconcile between Budgetary Fund Balance and Modified Accrual Fund Balance | 60 |
| 01 Plan To Report | 01 Budget Management | 03 FM Master Data Maintenance | FI-FM | Automatically Create Commitment Items | 011 | Statistical Flag not set for Revenue, Expense, Other Financing Sources and Uses that close to Modified Fund Balance Account | 61 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Currently Certified Revenue in AASIS | 000 | The system shall capture adjustments to Original Certified Revenue in Funds Management by: | 62 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Currently Certified Revenue in AASIS | 001 | Fund | 63 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Currently Certified Revenue in AASIS | 002 | Funded Program | 64 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Currently Certified Revenue in AASIS | 003 | Commitment Item | 65 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Currently Certified Revenue in AASIS | 004 | Across All Funds Centers | 66 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Currently Certified Revenue in AASIS | 005 | Across All Functional Areas | 67 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Original Certified Revenue in AASIS | 000 | The system shall capture Original Certified Revenue in Funds Management by: | 68 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Original Certified Revenue in AASIS | 001 | Fund | 69 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Original Certified Revenue in AASIS | 002 | Funded Program | 70 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Original Certified Revenue in AASIS | 003 | Commitment Item | 71 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Original Certified Revenue in AASIS | 004 | Across All Funds Centers | 72 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Maintain Original Certified Revenue in AASIS | 005 | Across All Functional Areas | 73 |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Restrict Available Appropriation to Currently Certified Revenue | The system shall maintain Currently Available Appropriation Budget only to the limits of the Currently Certified Revenue | 74 | |
| 01 Plan To Report | 01 Budget Management | 04 Revenue Certification | FI-FM | Restrict Available Appropriation to Originally Certified Revenue | The system shall maintain Original Available Appropriation Budget only to the limits of the Original Certified Revenue | 75 | |
| 01 Plan To Report | 01 Budget Management | 05 Other Revenue Budgets | FI-FM | The system shall allow for additional versions of Revenue Budgets, such as the Annual Revenue Estimat and Agency Revenue Budgets (at lower levels of detail than the revenue certification). | 76 | ||
| 01 Plan To Report | 02 General Ledger Management | 01 Enter Journals | FI-GL | Controls over supporting documentation | The system shall prevent any user from modifying or deleting files that were attached to a financial transaction after the documents has been posted. | 77 | |
| 01 Plan To Report | 02 General Ledger Management | 01 Enter Journals | FI-GL | Submit Uploaded Journals for Verification | They system shall route uploaded journal entries to a reviewer for posting. | 78 | |
| 01 Plan To Report | 02 General Ledger Management | 01 Enter Journals | FI-GL | User cannot post own Journal | 001 | The system shall prevent end users that initiate a journal from posting the journal. | 79 |
| 01 Plan To Report | 02 General Ledger Management | 01 Enter Journals | FI-GL | User cannot post own Journal | 002 | The system shall prevent end users that are the last one to modify it from posting the journal. | 80 |
| 01 Plan To Report | 02 General Ledger Management | 02 Enter Journal - Interagency | FI-GL | Matching Interagency Transfers | 000 | The system shall provide a mechanism to match interagency transactions: | 81 |
| 01 Plan To Report | 02 General Ledger Management | 02 Enter Journal - Interagency | FI-GL | Matching Interagency Transfers | 001 | That are captured on multiple documents (sender invoice/GL Journal and receiver Invoice/GL Journal) | 82 |
| 01 Plan To Report | 02 General Ledger Management | 02 Enter Journal - Interagency | FI-GL | Matching Interagency Transfers | 002 | That are captured on a single document that is approved by both the sender and receiver | 83 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Fund must be entered | 000 | The system shall require end users to enter a value for the Fund on financial postings: | 84 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Fund must be entered | 001 | On all Profit and Loss Accounts, since the State is redesigning coding block requirements from having a one-to-one relationship for Cost Center and Fund to allowing multiple funds to be used with a cost center, | 85 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Fund must be entered | 002 | On select Balance Sheet entries that are not subject to document splitting requirements, such as Cash in State Treasury | 86 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Prevent "Unassigned" Master Data values | 000 | The system shall prevent the "Unassigned" Value (for example, "9999999999") from being used on any FI, Grant, or FM Line Item except those that serve to carry remaining balance to be posted on long document chains from one document to the next (e.g., The Payroll Posting Clearing Account) for the following Master Data Objects: | 87 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Prevent "Unassigned" Master Data values | 001 | Segment | 88 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Prevent "Unassigned" Master Data values | 002 | Profit Center | 89 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Prevent "Unassigned" Master Data values | 003 | Fund | 90 |
| 01 Plan To Report | 02 General Ledger Management | 03 General FI Posting | FI-GL | Prevent "Unassigned" Master Data values | 004 | Grant | 91 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-GL | Allocation of Fund Balance | 000 | The system shall support the following activities to allocate fund balance as appropriate for for the fund: | 92 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-GL | Allocation of Fund Balance | 001 | Close P&L balances to a default Fund Equity account | 93 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-GL | Allocation of Fund Balance | 002 | Allocate the unallocated balance of the default Fund Equity account to the correct Fund Equity account as specified for each fund via an FI Posting | 94 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-AP |
FI-AR
| FI-GL | Mutliple Bases of Accounting | 000 | The system shall account for billed revenue on the following bases: | 95 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-AP |
FI-AR
| FI-GL | Mutliple Bases of Accounting | 001 | Cash Basis - as it is deposited | 96 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-AP |
FI-AR
| FI-GL | Mutliple Bases of Accounting | 002 | Modified Accrual - as invoiced when available and measurable | 97 |
| 01 Plan To Report | 02 General Ledger Management | 04 Financial Reporting | FI-AP |
FI-AR
| FI-GL | Mutliple Bases of Accounting | 003 | Full Accrual - as earned | 98 | ||||
| 01 Plan To Report | 02 General Ledger Management | 05 Interest Allocation | FI-GL | Allocate Interest based on an average daily cash balance per fund | The system should allocate interest earnings based on the average daily cash balance by fund and agency | 99 | ||
| 01 Plan To Report | 02 General Ledger Management | 06 Manage Petty Cash | FI-GL | Attachments to Cash Journal | 001 | The System shall allow users to either a) attach supportng documents to a Cash Journal (preferred) | 100 | |
| 01 Plan To Report | 02 General Ledger Management | 06 Manage Petty Cash | FI-GL | Attachments to Cash Journal | 002 | The System shall allow users to attach supporting documentation to the FI Document created from the Cash Journal | 101 | |
| 01 Plan To Report | 02 General Ledger Management | 07 Trust Fund Reporting | FI-AP | |||||
| FI-GL | Automatic Reclassification of cash receipt and payment activity | The system shall support automatic reclassification of custodial (trust/fiduciary) fund amounts from revenue/expense to liability General Ledger Accounts for financial reporting | 102 | |||||
| 01 Plan To Report | 02 General Ledger Management | 07 Trust Fund Reporting | FI-AP | |||||
| FI-GL | Automatic Reclassification of cash receipt and payment activity | The system should be able to record cash receipts and payments to Trust Funds offset as income and expense for budgetary basis accounting and AVC | 103 | |||||
| 01 Plan To Report | 03 Project Management | 01 Project Planning | FI-PS | Integrated Project Planning | 000 | The system shall provide project planners to: | 104 | |
| 01 Plan To Report | 03 Project Management | 01 Project Planning | FI-PS | Integrated Project Planning | 001 | Copy plan or actuals to a version of the Project Plan in S/4HANA | 105 | |
| 01 Plan To Report | 03 Project Management | 01 Project Planning | FI-PS | Integrated Project Planning | 002 | Use standard project planning functionality to finalize the new version of the Plan | 106 | |
| 01 Plan To Report | 03 Project Management | 01 Project Planning | FI-PS | Integrated Project Planning | 003 | Copy the Project Plan Version to a Version of the FM Budget, using functionality similar to FMCYCOPI_CO (Plan Data Transfer from CO) | 107 | |
| 01 Plan To Report | 03 Project Management | 01 Project Planning | FI-PS | Integrated Project Planning | 004 | Call FMDERIVE to determine the FM Objects | 108 | |
| 01 Plan To Report | 03 Project Management | 01 Project Planning | FI-PS | Integrated Project Planning | 005 | Return an error if any FM Object cannot be determined via the Derivation Strategy | 109 | |
| 01 Plan To Report | 03 Project Management | 02 AUC Settlements | FI-PS | Placeholder for AUC Pain Points (Kathy and Josh) | 110 | |||
| 01 Plan To Report | 03 Project Management | 02 AUC Settlements | FI-PS | Restrict Project Revenues to WBS elements that don't have a settlement | 111 | |||
| 02 Procure to Pay | 01 Procurement | 01 Maintain Products | MM-PUR | Link Service Master to UNSPSC | The system shall maintain a relationship between Services procured and the UNSPSC Code for that service. | 112 | ||
| 02 Procure to Pay | 01 Procurement | 02 Process PCards | FI-AP | |||||
| MM-PUR | PCard as Method of Payment | The system shall provide for the use of credit cards as a method of payment | 113 | |||||
| 02 Procure to Pay | 01 Procurement | 03 Process Purchasing Documents | MM-PUR | Total Project Cost | Procurement Documents must capture Total Project Cost at the header level. This is passed to the Bureau of Legislative Research via the BLR Portal. | 114 | ||
| 02 Procure to Pay | 02 Accounts Payable | 01 Discounts | FI-AP | |||||
| MM-PUR | Invoice Dates for Discounts | The system shall capture the Invoice Receipt Date, separate from the Entry Date, Posting Date or Document Date as the basis for calculating discounts | 115 | |||||
| 02 Procure to Pay | 02 Accounts Payable | 02 Invoice processing | FI-AP | Configurable Field Positions | The system shall allow for reconfiguring Invoice Receipt entry screens to locate commonly used fields closer to the beginning of the input line. | 116 | ||
| 02 Procure to Pay | 02 Accounts Payable | 02 Invoice processing | FI-AP | |||||
| MM-PUR | Opentext integration for Accounts Payable Processing | The system shall provide an Opentext solution for accounts payable processing as Optional Scope | 117 | |||||
| 02 Procure to Pay | 02 Accounts Payable | 02 Invoice processing | FI-AP | |||||
| MM-PUR | Range of Service Dates | The system shall capture Start Date and End Date for billed services. | 118 | |||||
| 02 Procure to Pay | 02 Accounts Payable | 03 Expense Processing | FI-AP | Payments from Appropriated Funds | The system shall prevent generation of a payment from an appropriated fund unless the associated expense has been posted. | 119 | ||
| 02 Procure to Pay | 02 Accounts Payable | 05 Process Financial Documents | FI-AP |
FI-GL
| MM-PUR | Consistency of Coding Block | Ensure consistency of coding block across the spectrum of documents processed that have a subsequent Expense Error Correction: the original invoice, expense error correction(s), credit memo, deposit for the refund of expenditure, sales and use tax remittance, and/or sales and use tax rebate | 120 | |||||
| 02 Procure to Pay | 02 Accounts Payable | 06 Vendor Registration | FI-AP | Vendor Registration Self Service | 000 | The system shall support the following requirements for Vendor Registration: | 121 | |
| 02 Procure to Pay | 02 Accounts Payable | 06 Vendor Registration | FI-AP | Vendor Registration Self Service | 001 | Single on-boarding process for Vendor Self Service | 122 | |
| 02 Procure to Pay | 02 Accounts Payable | 06 Vendor Registration | FI-AP | Vendor Registration Self Service | 002 | Integrated Address Validation | 123 | |
| 02 Procure to Pay | 02 Accounts Payable | 06 Vendor Registration | FI-AP | Vendor Registration Self Service | 003 | Integrated tax ID validation | 124 | |
| 02 Procure to Pay | 02 Accounts Payable | 07 Display Business Partner | 000 | The system should allow for suppression of the following details for unauthorized users: | 125 | |||
| 02 Procure to Pay | 02 Accounts Payable | 07 Display Business Partner | 001 | Tax ID | 126 | |||
| 02 Procure to Pay | 02 Accounts Payable | 07 Display Business Partner | 002 | Bank Details | 127 | |||
| 02 Procure to Pay | 02 Accounts Payable | 08 1099 Processing | FI-AP | 1099 Reporting | The system shall have Extended Withholding Tax activated to enable 1099 processing | 128 | ||
| 02 Procure to Pay | 02 Accounts Payable | 08 1099 Processing | 1099 Reporting | The system shall allow payments from external systems be consolidated into the amounts for 1099 reporting . | 129 | |||
| 02 Procure to Pay | 02 Accounts Payable | 08 1099 Processing | FI-AP | Refunds of Expenditure and 1099 | The system shall include refunds to expenditure in regular and correction 1099's. | 130 | ||
| 02 Procure to Pay | 02 Accounts Payable | 09 Integration with HR | FI-AP | |||||
| HR INTEGRATION | Block Separated Employee Vendors' | 001 | The system shall inactivate employee Vendors within an Account group (Vendors with a Pernr) that are not actively employed | 131 | ||||
| 02 Procure to Pay | 02 Accounts Payable | 09 Integration with HR | FI-AP | |||||
| HR INTEGRATION | Block Separated Employee Vendors' | 002 | The system shall block separated employee vendors for posting after a period of time (e.g., 4 weeks) so that final reimbursement payments can be made. | 132 | ||||
| 02 Procure to Pay | 03 Bank Accounting | 01 Reconcile Bank Accounts | FI-TREAS | |||||
| SD | Automate Commercial Bank Account Reconciliation | The system shall support automation of commercial bank account reconciliations, using BAI file formats and processes, or an equivalent. The Selected Contractor shall deploy this process to all Commercial House Bank Accounts in AASIS. | 133 | |||||
| 02 Procure to Pay | 03 Bank Accounting | 01 Reconcile Bank Accounts | FI-AP | |||||
| FI-TREAS | High Volume Open Item Management | The system shall support extraordinary volume processing of open item managed outgoing cash accounts | 134 | |||||
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Maintain Grantee Business Partner | 000 | The system shall maintain business partners for the following Roles: | 135 | |
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Maintain Grantee Business Partner | 001 | Grantee | 136 | |
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Define Grantee User Business Partner | 002 | Grantee User | 137 | |
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Define Grantee Auditor Business Partner | 003 | Auditors | 138 | |
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Define Grantee Employee Business Partner | 004 | Employees | 139 | |
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Define Business Partner | The system shall maintain Business Partners in the Grantor Management System | 140 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 01 Maintain Business Partners | Grantor Management | Define Grantee User Business Partner | The system shall synchronize Business Partner information with S/4HANA. | 141 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Integration with S/4HANA | The system shall maintain Grantor Programs as Funded Programs | 142 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Program Master Data in FM | The system shall capture start and end dates for each phase of the Grantor Program Lifecycle | 143 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Program Master Data in FM | The system shall enforce start and end dates for each phase of the Grantor Program Lifecycle | 144 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Application Templates | The system shall have the ability to configure forms and the application process based on individual program requirements. | 145 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 000 | The system should provide an overview of Grantor Management Programs in process classified as either: | 146 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 001 | Being advertised | 147 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 002 | Accepting applications | 148 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 003 | Evaluating Bids | 149 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 004 | Finalizing Awards | 150 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 005 | In Process | 151 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 006 | In Closing | 152 | |
| 02 Procure to Pay | 04 Manage Grants Given | 02 Maintain Grantor Program | Grantor Management | Maintain Grantor Program Status | 007 | Closed | 153 | |
| 02 Procure to Pay | 04 Manage Grants Given | 03 Maintain Internal Orders | Grantor Management | Integration with S/4HANA | The system shall use Internal Orders to account for Grantor Awards | 154 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 04 Enter Grantor budget | Grantor Management | Integration with S/4HANA | The system shall maintain budget transfers from the appropriation level to the Grantor program Level. | 155 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 05 Advertise Program | Grantor Management | Preparing for Advertisement | The system shall support a Program Advertisement Phase | 156 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 05 Advertise Program | Grantor Management | Preparing for Advertisement | The system shall maintain program descriptive information on a public facing website | 157 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 05 Advertise Program | Grantor Management | Preparing for Advertisement | The system shall provide access to apply for advertised programs on a public facing website. | 158 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 05 Advertise Program | Grantor Management | Preparing for Advertisement | The system shall have the ability to download a list of Business Partners in order to generate and send solicitation letters | 159 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 000 | The system shall allow applicants to: | 160 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 001 | Enter applications online. | 161 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 002 | Save in process applications online. | 162 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 003 | Edit saved applications online. | 163 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 004 | View applications online. | 164 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 005 | Retrieve applications online. | 165 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 006 | Submit applications online. | 166 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 007 | Attach documents to applications | 167 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Applying for Grants | 008 | Amend their application if the Program requests additional information | 168 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 000 | The system shall track the following statuses for each application: | 169 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 001 | New | 170 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 002 | In Process | 171 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 003 | Submitted | 172 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 004 | Reviewed | 173 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 005 | Incomplete | 174 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 006 | Accepted | 175 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 007 | Rejected | 176 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 008 | Revision requested | 177 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Tracking Application Status | 009 | Revised | 178 | |
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Validate Submission | System shall check for application completeness for online components of an application according to criteria specified by the Program Administrator. | 179 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Integration with S/4HANA | The system shall allow for pre-committing funds for applications when submitted | 180 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Application Review Workflow | The system shall provide workflow for applications | 181 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Capturing Attachments to an Application | The system shall capture email and other contact information for applicants | 182 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Notifying Applicants | The system shall support email notification to applicants | 183 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Notifying Applicants | The system shall confirm receipt of applications when submitted electronically or in hard copy. | 184 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Notifying Applicants | The system shall be able to create a PDF document of an in-process application (identified as a "DRAFT") and attach it to an email. | 185 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Notifying Applicants | The system shall be able to create a PDF document of a submitted application (identified as a "Final") and attach it to an email. | 186 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Application Submission Closure | The system shall close application submittal periods at specific dates and times. | 187 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Application Submission Closure | The system shall allow closed applications to be reopened unitl a specific date and time. | 188 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 06 Accept Applications | Grantor Management | Application Submission Closure | The system shall enforce a hard close on an application, after which the applicant cannot modify their submission. | 189 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 07 Evaluate Applications | Grantor Management | Define Survey | The system shall allow for definition of a form that will capture scoring criteria for the Grantor Program | 190 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 07 Evaluate Applications | Grantor Management | Manage Output and attachment | The system shall support users to view, print, and transfer electronically all online application information and attached documents once an application has been submitted. | 191 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 07 Evaluate Applications | Grantor Management | Score Applications (BRF - Business Rules Framework) | The system shall provide a workflow to users identified as evaluators | 192 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 07 Evaluate Applications | Grantor Management | Score Applications (BRF - Business Rules Framework) | The system shall capture user input of scores | 193 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 07 Evaluate Applications | Grantor Management | Score Applications (BRF - Business Rules Framework) | The system shall tabulate all scores in support of awarding grants to Grantees | 194 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Score Applications (BRF - Business Rules Framework) | The system shall allow authorized users to select applicants to award. | 195 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Notifying Applicants | The system shall notify applicants of the results of their evaluation (accepted or rejected). | 196 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Award Grant | The system shall capture an Agreement for each Grantee award | 197 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Award Grant | The system shall capture a cost category to reflect the nature of the expense paid for. | 198 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Award Grant | The system shall allow for different cost objects per Cost Category. | 199 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Award Grant | The system shall convert the application pre-commitment to a commitment, if used | 200 | ||
| 02 Procure to Pay | 04 Manage Grants Given | 08 Award Grant | Grantor Management | Award Grant | The system shall create an Award commitment if not pre-encumbered. | 201 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .