18 Mar 2013
5 mins read
The white paper lists and describes steps needed to perform data conversion for SAP from the staging point of view.
The goal is to enable the staging developers during Data conversion process and help them verify the data converted before it goes into SAP.
Developers working on the Staging part should have the following pre requisites.
Data conversion process involves converting/processing the data received from the legacy applications/systems and transforming it into desired output structure of SAP as per the specifications provided.
Functional specification documents provide details about the business rules that are to be applied on the data before it goes into SAP. Staging team does the work of applying those business rules by writing stored procedures in ORACLE.
Data conversion process
Once a mapping document is in place and has been verified by business users, the actual development of code and import process of data is initiated for a particular conversion.
SQL Loader utility is used to import data into ORACLE tables. Data received from a legacy system could be in various forms. For e.g. it could either be in a tab delimited, CSV or can even be in an excel spreadsheet format. It is important to review the data received is in correct format and ensure that no field / information is missing. Process to import data may differ depending upon the format in which data has been received.
In case the data received is in tab delimited format, MS Excel can be used to prepare the file before it is used with the SQL Loader tool. Although data can be imported to ORACLE as is, but sometimes the data received is not directly importable into ORACLE tables and has to be converted into a format which is acceptable to the ORACLE.
Select Import Data option available under Data->Import External Data menu option.
Processing the data imported is one of the major steps in data conversion process. It’s quite possible that in a real life scenario, changes to the code might be required during the course of data conversion for a particular module in the procedures created for processing the data.
One way to protect and maintain the code written for a particular type of conversion is to write a new stored procedure. That’s the way it’s been mostly done while there have been changes that we were to make in our code during the process of conversion in Wave I. Maintaining separate versions of code like this is a tedious process especially without an integration of a version management tool with the development environment.
Here is an example of a data conversion process for a module (Sales Order), where there was a requirement to create a separate set of data for all the orders belonging to plant in Canada. In this kind of a scenario, we had created a separate procedure to process the records for Canadian plant. During this conversion process, there have been number of changes, which were done quite frequently to each of these two separate procedures and the nature of changes that were to be made were also different for each of the plants. In a real life scenario, it becomes very difficult to maintain separate versions and also keep track of the changes being made on continuous basis to these different sets of code.
Once the processing is complete, the data has to be delivered to the SAP.
Versions of the data are maintained as the data goes into different environments in SAP. It’s required because of the following reasons:
An exception report helps the staging team in reporting the users/developers of the legacy system to identify the problems at their end and resolve them and re-send the data to the staging team to process it, so that the same could be uploaded in SAP too. A typical format of an exception report is a collection of raw data fields along with a reason as why those could not get processed. This is sent usually in an MS excel format.
Also, count of records processed and the records that came as part of the raw data is maintained and communicated to the business users/legacy system team to find out how much data got loaded and how much of it failed to load.
Enterprise Solutions
20 Sep 2018
18 Sep 2018
26 Oct 2015
28 Sep 2015
26 Aug 2015
11 Jun 2014
13 Feb 2014
12 Feb 2014
Enterprise Solutions, Manufacturing and Consumer
31 Jan 2014
27 Jan 2014
03 Jan 2014
03 Dec 2013
28 Nov 2013
19 Nov 2013
03 Oct 2013
01 Oct 2013
30 Sep 2013
24 Sep 2013
19 Sep 2013
10 Sep 2013
27 Aug 2013
19 Aug 2013
25 Jun 2013
17 Jun 2013
11 Jun 2013
Digital Assurance, Enterprise Solutions, Others
26 Apr 2013
12 Apr 2013
05 Mar 2013
Digital Assurance, Enterprise Solutions
27 Feb 2013
18 Feb 2013
14 Feb 2013
BI & Analytics
19 Mar 2009
26 Nov 2010
Digital Assurance
02 Jan 2012
17 Feb 2012
Infrastructure Mgmt. Services
02 Mar 2012
03 Jan 2013
04 Feb 2013
06 Feb 2013
21 Feb 2013
Others
01 Mar 2013
04 Mar 2013
22 Mar 2013
29 Apr 2013
13 May 2013
26 Aug 2013
03 Sep 2013
26 Sep 2013
01 Nov 2013
20 Dec 2013
22 Jan 2014
20 Mar 2014
24 Mar 2014
17 Apr 2014
Manufacturing and Consumer
26 Jun 2014
30 Jun 2014
10 Jul 2014
15 Jul 2014
16 Jul 2014
18 Jul 2014
28 Oct 2014
13 Jul 2015
06 Aug 2015
07 Oct 2015
07 Mar 2016
22 Mar 2016
13 May 2016
23 May 2016
Application Transformation Mgmt.
11 Jul 2016
25 Aug 2016
03 Sep 2016
14 Sep 2016
15 Nov 2016
22 Nov 2016
25 Nov 2016
Business Process Services
25 Apr 2017
Banking and Financial Services
18 May 2017
30 May 2017
23 Jun 2017
27 Jun 2017
18 Jul 2017
26 Oct 2017
Healthcare, Insurance
28 Nov 2017
11 Dec 2017
25 Jan 2018
21 Feb 2018
14 Mar 2018
( Mandatory field * )
The information you provide will be used in accordance with our terms ofPrivacy Policy
Please Check on "I Agree" to register for the blog.