Data conversion requirements and strategy

Data conversions are required to transfer University financial data from the central legacy systems to the Kuali Financial System KFS to support core business processes.

Successful data conversions are critical to allow the legacy accounting systems to be decommissioned and University transaction processing to be accomplished from the KFS system. Data conversions must be accurate and comprehensive to enable the university's business to be conducted with the Kuali Financial System.

CV Data Conversion Requirements and Strategy | Oracle Database | Invoice

The term "data conversion" is loosely used to describe activities associated with seeding KFS with preconceived data. Some data will be loaded from legacy sources, e. Other data will be loaded from data files provided by subject matter experts, e.

Sample Data Conversion Requirements

And other data may be extracted from other existing KFS environments. In some cases, the data will not just be loaded but will be transformed, or translated, based upon business rules that describe the mapping from legacy to KFS.

The primary goal of data conversion is to transfer legacy data to the Kuali Financial System, applying business rules in order to ensure that KFS will work for Cornell's business process and we can utilize the full potential of KFS.

Over the life of the KFS Implementation Project, data conversion processes and practices will fundamentally support the meeting of many of the project's most significant objectives, including:.

Each of these activities have distinct lifecycles that will require similarly distinct data conversion approaches.

Over time, these approaches will converge into a singular validated path seeding the database of the eventual Pre-Production KFS environment. This data conversion work offers an opportunity to cleanse or correct erroneous legacy data so that the data seeded into KFS is of optimal quality.

Collaborations with the stakeholders of each of the above activities must be driven by functional requirements. A data mapping from legacy to KFS must be maintained over the life of the entire KFS Implementation Project.

At first it will be a working document that supports the myriad activities across the project. Over time it will become a refined data dictionary. For the early project work, this has proven to be the most cost effective and efficient approach.

Data Conversion Strategy - KFS Implementation - Dashboard

While the need for a data conversion process is temporal, i. Driven and motivated by elicited functional requirements, the team will sensibly seek. Space Details Your profile picture is used as the logo for your personal space.

Change your profile picture. A t tachments 0 Page History Restrictions Page Information Resolved comments Link to this Page… View in Hierarchy View Source Export to PDF Export to Word. Pages … Home KFS Implementation Technical Integration Data Conversion Team.

Created by Bryan Hutchinson , last modified on Feb 23, NOTE - This is a living document and subject to change. Powered by Atlassian Confluence 5. Report a bug Atlassian News Atlassian.