Data transfer tools
Your stakes / issues
- Transfer your data from an old application to your new SAP system
- Provide complete continuity for all flows in process at the date of the changeover
- In the new system, convert the flows in process to the newly defined processes so the ongoing old flows don’t follow a degraded process
- Eliminate existing duplicates in the old applications and don’t create any in the target system
- Initiate high quality data to avoid destroying the investments made for the new system
Our approach
-
For data transfer projects in SAP, we have 2 major objectives:
- Reduce as much as possible the development load in the upstream systems
-
Use a kit of generic tools that can be adapted based on the customer solution
-
Our data transfer process is based on the differential method:
- Store transferred elements by unique identifiers
- Check that the transferred element is in SAP
- Ability to redo the transfer as many times as possible without fear of altering the data already transferred
- Can automatically check the transfer programs and the transferred data
-
Makes it easy for the customer to match and check the transfer: often the unique identifier corresponds to the coding of the transferred element based on old information systems
-
Throughout your data transfer process we will:
- Help you define a pertinent transfer strategy that respects your stakes
- Provide our know-how in terms of processing data quality
- Automate the transfer to a maximum so your personnel can concentrate solely on the high value added tasks
- Develop transfer tools that resist actual uncertainties through to the last day before the changeover
METHODOLOGY
One of the data transfer principles according to CODiLOG can be summarized in a single phrase: “To carry out a transfer is to do what we would have done if we already used SAP”
This means that in order to guarantee a successful data transfer, one has to know the target solution.
Consequently, the data transfer has to adapt to each customer solution.
-
A methodology that can be used to perform several successive transfers as part of a roll-out, while taking into account the data from the old application that has to be migrated, but also the data already present following the previous roll-outs and current work performed by the companies already in production.
-
A differential treatment that can be used to self-check the transfer results.
- Knowledge of the structure of addresses for the main countries in Europe and North America
TOOLS
CODiLOG uses the following tools:
-
LSMW, standard tool supplied by SAP
- Generic LSMW processing routines (standardize addresses; determine appropriate VAT codes, etc.)
- Read data from former information systems
- Transform these data (develop transformation tools in SAP format)
-
Inject the data in SAP
-
CODiLOG’s Generic Programs Kit (transcoding tools, standardization, merge and purge) includes tools that can be adapted based on the customer’s solution and that reduce the development load to a maximum in the upstream systems:
- Recognize character chains (detect duplicates / improve third party database, etc.)
- Manage exception files
- Powerful transcoding tool: configuration tables and priority rules management
-
Manage the differential transfer mode
-
Repositories to standardize the data (countries, cities, postal codes, road type, etc.)
- Tools to recognize duplicates in databases (Customer, Supplier, Item, etc.)
The whole developed exclusively in SAP using ABAP programming
The advantages of our approach
- Flexibility of the transfer modes based on target processes
- Adaptability of transfer tools
- Transfer in differential mode