During software implementations data transfer and the set-up of periodic/permanent interfaces is one of the most costly and time-intensive work packages. Several market studies have shown that, on average, data transfer accounts for 20% of implementation costs. In individual cases it can exceed that amount. In order to perform the initial data transfer from non-SAP systems, you need to efficiently carry out the following steps: 
1. Identify data to be transferred in the legacy system and, if possible, eliminate (Clean up/filter) obsolete data and inconsistent data records at the same time. 
2. Extract relevant data and write it to an ASCII file. 
3. Convert the data from ASCII format to the object-specific data format required by SAP. 
4. Process the converted data file based on BAPI, batch input or direct input technologies using SAP Load Programs (load). 
5. Run your own check programs (if available) to further examine the results of the data transfer. You can compare information such as the number of open items or the number of materials in both systems. Basic consistency checks are run during loading, as R/3 does not allow the creation of inconsistent data sets. 

You will be given two files (both in the single spreadsheet file), the first a file containing 199 records (File 1) of customer data. This is the file that will be converted. The second file contains about 10 records (File2) and becomes the template file. Using a package cleanse the 199 customer records. Use another package to convert the customer data into the same format as your template file. 
What to hand-in 
? Student declaration form with % participation included and team number. 
? File of cleansing 
? File of conversion 
? Word file with assumptions and screen captures describing the process of cleansing and conversion in full. 
? Final output file (in xls or txt or csv format) after cleansing and conversion 

Introduction 
KKAE is an industrial company that is undergoing an SAP implementation The rollout has reached the phase of data conversion and migration. This deliverable aims to show the procedures of how KKAE Pte. Ltd handled the data cleansing and data mapping based on a list of employees who were using SAP system in KKAE. The conversion is based upon a set of business assumptions. 
Details 
Two files are used in this activity. The first file is a list of employees who are using SAP system. The list contains their contact and SAP access information. Some of the information is duplicated, and some information contains human-unreadable characters or invalid data. The other file is a template that shows the required layout format of the final output list. 
The main objectives of this activity were as follows: 
• Mark all the duplicated data with proper error flags. 
• Mark all the missing data with proper error flags. 
• Verify the human-unreadable characters, then take proper action on it; either remove the human-unreadable character or correct the unreadable character. 
• Verify and mark all the invalid data with proper error flags, then correct it. 
• Once the data is cleansed, map the data based on the template's pre-defined layout and create the final list. 

Business Assumptions 
The following is the list of business assumptions made in this activity. 
• Data backup has been performed on the employees' relevant data before the data cleansing and mapping activity. The data backup is to prepare for any incidence in wrong data manipulation. 


• The head office of KKAE is located in Australia/Sing/India. Documents and reports must be displayed/printed in English. Grammar and spelling in all the documents and output reports follow the English version. For example, some of the foreign salutations will be kept. 

• The final output list will serve as a global internal contact list that includes all the key employees who are involved in the SAP Business-By-Design Project. As it is a contact list, some data such as the contact numbers, must be stated in complete format with country code, area code, followed by the phone number. 

• KKAE has started to use SAP system since 1996. 

• The data source was extracted on 31 March 2012. 

• Before the data extraction activity, a junior staff had executed a wrong program. That wrong program duplicated some data in the database. It has also shifted some data to the wrong fields. In addition, some data has been overwritten by wrong data or un-readable/ASCII codes. 

• Each row of record represents a single employee and the record stores the employee's contact and SAP related information. All the rows are unique and there should be no duplication. 


SPECIFIC INSTRUCTIONS: 
Data cleansing file has to be the BCO5651 MELBOURNE 1.. THERE ARE 3 DIFFERENT FILES.. THE ONE TO BE CONVERTED IN WITH NUMBER 1. 
Data conversion needs to be done with a software called MAPFORCE. 
Each and every process throughout the cleansing and conversion process needs to be documented, with screenshots and proper reasons and assumptions. Sample assignment is attached . 
Excel file is attached as well. 
There is a folder called all targets, my converted file should look like target 1 given in all targets. 

============================================= 
There are specific instructions... data cleansing can be done anyhow.. just need to document each and every step with screenshots and reasons. 
And data conversion needs to be done preferable with the use of a software called mapforce.