Data migration/ conversion

Hi,
Am new in contract management, we need to implementing contract management in SRM 4.0. Below are few question that i need to be clarified on:-
1. Are there any standard template for uploading contracts from legacy system
2.Upload contracts from legacy system into SRM then interface with the existing ones in R/3
3.Upload contracts from R/3 into SRM and be able to trace back to the original legacy system GOA
4. Can you upload more than 5000 contract line items
5.Load contracts from legacy system into SRM then distribute to R/3
6.Contracts loaded from either legacy system or R/3 can they be uploaded with their attachments and save those attachments to C-folders.
7. Once contracts are upload to SRm and there is chnages in R/3 will there be automatic update (e.g. Material flagged for deletion)
8. Once contract has been distributed to R/3 from SRM, can updates happen automatically
Rgs,
Maggie

Hi Dina,
Thanks for your reply.
Well based on your suggestion i am gonna follow the following points. Kindly let me know if anything wrong in these.
1) To bring the the transactions which were closed and entered as the opening balances in Oracle GL then we can bring them as one consolidated distributed & accounted expenditure or summerized by resouces categories (Labor,Material,Subcontractor,Usage,Misc.). and post them in one PA/GL period.
2) All the open purchase orders/rececipt accural , supplier invoices,Inventory cost will be imported from the respective sub ledgers(Purchasing,AP,INV).
2) For AR invoices and revenue we create one mannul event and generate the one consolidated Invoice and recognized the revenue. Post both Invoice and revenue in same period where the historical cost is posted.
Regards,

Similar Messages

How to test Data migration/conversion?

I'm writing Java scripts to migrate a 8i database to 10g db with totally different schema. My question is after the migration is done, any process/tool that I can use to verify all the data has been migration successfully and completed?
Thanks,
Andy

Does "totally different schema" mean "totally different data model"? If so, there is no automatic way for any tool to ensure that the data in two different data models matches-- you would have to write custom scripts for that sort of thing since only you know how the data is supposed to be translated from one data model to another.
Justin

Data migration/conversions!!

Hi friends,
1. what type of data CANNOT be uploaded from legacy system into SAP system using BDC/LSMW/BAPI.
2. Which Non-SAP systems wont support the data upload to SAP system. If so, what is the alternative??

Hi,
1. All kind of data can be uploaded in SAP. You may require to do some conversion to load into SAP.
2. Mostly all the systems support data uploead, as they are not directly connected with SAP. We mostly download data from those system in flat files and upload in SAP.
Regards,
Atish

Legacy Data Migration - question on conversion

Hello All,
We are trying to build a generic tool which could help the conversion process in data migration.
For eg, If the material name in legacy starts with AB (AB6790), the same has to be referred in SAP as SQ6790.
So its replacing initial few characters during the conversion process.
Like this, I am expected to collect possible scenarios and
develop a generic tool, which can cover some possible conversion conditions.
Can you please help me with such scenarios, which you may have come across in project needs.
Thank you.
Meenakshi

Rahul,
I strongly suggest you do a search in the CRM General & Framework Forum on this topic. If you are looking for specific objects to migrate there are several posts on the major data elements in crm (transactions, business partners, products).
In general the technique is to use the LSMW combined with the XIF-IDOC adapter to convert data into the CRM system.
My blog here will explain the general process:
/people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter
Thank you,
Stephen

ASAP Data Migration / Data Conversion / Data Transfer Templates

Hi,
I'm looking for the ASAP Data Migration / Data Conversion / Data Transfer Templates that used to be available in ASAP.
Some time I ago, and I believe it was on this site and can no longer find it, I found a zip file which contained the above .xls template to manage all the data conversions on a project. Also included was the data mapping template .xls
Many thanks.

Hi,
I'm looking for the ASAP Data Migration / Data Conversion / Data Transfer Templates that used to be available in ASAP.
Some time I ago, and I believe it was on this site and can no longer find it, I found a zip file which contained the above .xls template to manage all the data conversions on a project. Also included was the data mapping template .xls
Many thanks.

Data Migration for Open Purchase Order

Hi, All,
Is there anyone know how to Count the volume for Open Purchase Order. What's the normal strategy for the Data Migration and Cut-over stage?
My client want to know how many Open Purchase Order in the legacy system and then determine manual or automatic data migration. If manual, how to do? If automatic, how to do? Because all materials and vendors, plants are different number. How to track? How to find out to match between new and old?
Thank you very much

JC,
Sounds a bit early to be making decisions about the realization phase. It doesn't sound like you have finished the Blueprinting phase yet, much less the testing phase.
Anyhow, in my experience I typically use LSMW (Legacy system migration workbench) to load MM master data (material masters), Inventory (WIP, RM, FG, etc) Purchasing Master data (Vendors, Purchase Info Records, Source Lists, Quota Arrangements), and Purchasing transactional documents (POs, PurReqs, Scheduling Agreements, etc). Depending on the complexity and volume of data, it may be necessary to write custom programs to load the data. You will find this out during your requirements gathering.
It is uncommon but possible to load all of these data manually. I have never run across a client that wants to pay a consultant's hourly rate to sit at a terminal to peck away loading master data, so if the client intends to have his own users enter the data manually, the project manager should make provision that there will be qualified TRAINED client employees available for this data entry. I did help with a portion of a conversion once manually; of Sales Credits, but there were only about 30 SD docs to load. I did this the evening before go-live day, while I was waiting for some of my LSMW projects to complete in the background.
A good opportunity to 'practice' your data loads is right after you have completed your development and customization, and you have gotten the approval from the client to proceed from the pilot build to the full test environment. Once you have moved your workbench and customization into the client's test environment, but before integration testing, you can mass load all, or a substantial portion of your conversion data into the qual system. You can treat it like a dry run for go-live, and fine tune your processes, as well as your LSMW projects.
Yes, it is good practice to generate comparisons between legacy and SAP even if the client doesn't ask for it. For Purchase orders on the SAP side, you could use any of the standard SAP Purchasing reports, such as ME2W, ME2M, ME2C, ME2L, ME2N. If these reports do not meet the requirements of the client, you could write a query to display the loaded data, or have an ABAPer write a custom report.
You didn't ask, but you should also do comparisons of ALL loaded data - including master data.
It sounds like you are implying that the client wants YOU to extract the legacy data. For an SAP consultant, this is not very realistic (unless the legacy system is another SAP system). Most of us do not understand the workings of the myriad legacy systems. The client is usually expected to produce one or more legacy system technical experts for you to liase with. You normally negotiate with the technical expert about every facet of of the data migration. In addition, you will liase with business users, who will help you and the implementation team to logically validate that the final solution (turnkey SAP production system, fully loaded with data) will meet the client's business needs.
Finally, you mentioned how do you track the mapping of master data between legacy and SAP. There are many ways to do this. I normally try to get the legacy person do the conversion on his end, eg, when he gives you the load file, you would like to have already translated the master data and inserted the SAP relevant values into the file. If this is not possible, I usually use MS Access databases to maintain a master map, and I perform the mapping on a PC. If your data package is small, you can probably get by using MS Excel or similar.
Good Luck,
DB49

Confuse on PR & PO data migration approach new to MM module

Hi All,
I'm pretty confuse with the PO data migration approach when it comes to PO is GR or partial GR or GR&IR. I'm hoping that someone can enlighten me. i understand that we typically don't migrate PO when it is GR & IR, FI team usually will bring over to the new system as an vendor open item in AP. How about the PR or PO which have gone through or half release strategy? What is the follow up process? I have created a criteria table below. How Could someone point me in the right direction? Thanks in advance.
PR
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
Flag for Deletion
N
Flag for Block
Y
PO
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
GR but no IR
GR & IR
N
AP will bring over as open item
Flag for Deletion
N
Flag for Block
Y
Partial
Y
For partial GR to recreate PO only with missing GR quantity
Regards,
John

Hi John,
The approach that i have followed recently is that we have considered PO as the base document and converted other documents based on the PO condition. This means you first need to see if the PO is to be converted or not. Then you can proceed to convert the related documents like PR, Agreement, Info record, Source list, etc.
Also open qty for PO should be considered for Material and Service line items both.
Once a GR/SES is created, it gets updated in the PO history table EKBE with its related transaction/event type.i.e. EKBE-VGABE = 1 for GR and 9 for SES. Quantity and value also gets updated in case of material and services. You can compare this consumed quantities with PO quantity.
Please see below from SCN and let me know if you need more info on PR or PO conversion.
Purchase Requisition Conversion Strategy
Thanks,
Akash

Data Migration from Legacy System in CRM

Hi All,
We are going to Implement a new CRM project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of CRM and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Active Campaigns/Campaign Content/Dispositions
4. Contacts
5. Contracts
6. Opportunities
7. Payment Arrangement History
8. Payments
9. Premises
10. Rate Changes
11. Security Deposits
12. Business Partner Relationships
13. Web self-service information
14. Usage that has been used for quotes
15. Tax history information, including AXCIS
17. Service Requests
18. Service Order History
19. Security Deposits
20. Reference Values
21. Rate Changes
Can anybody please tell any transaction code in CRM where can I find the Data migration for the above objects is possible or not.
Thanks in Advance,
Sai.

Hello,
for migration into CRM I would suggest the 'XIF-Interfaces'; these are interfaces provided in CRM for connection to external systems. I'm not sure if this will cover all objects mentioned above, but at least some of them should exist.
Some information about existing interfaces can be found in the integration repository under http://ifr.sap.com/index.html; from the start screen first select 'Enter the repository' and then have a look under 'generic components' and 'SAP CRM'.
Regards, Katja Ohliger

Data Migration from Legacy System in IS-U

Hi All,
We are going to Implement a new IS-U project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of IS-U and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Business Partner Relationships
4. Active Campaigns/Campaign Content/Dispositions
5. Connection Object
6. Contacts
7. Contracts
8. Opportunities
9. Payment Arrangement History
10. Payments
11. Premises
12. Rate Changes
13. Security Deposits
these are few and there are some more..,
Thanks in Advance,
Sai.

Hi Ram,
Use Transaction Code EMIGALL. It will ask for company code. By default Company Code is SAP. If you entered with the SAP you will get all the objects.Then goto menu IS-U Migration-->User Handbook. It will give you details Idea.
Also Check the following Procedure
You can find detailed documentation of EMIGALL in SAP itself. Use Transaction EQ81 to display it. It provides all the concepts and procedures to work with EMIGALL.
Here are some points about EMIGALL :
1. It Migrates data Business Object wise
2. It uses Direct Input Technique
3. It has more than 100 objects of IS-U
and the steps for implementation goes like this:
1)You have to create a user specially for migration which will have all the authorizations related to migration workbench, BASIS and IS-U
2)You have to create your own company in EMIGALL. There is a default company called SAP.
3)Company SAP contains all the Business Objects
4)You have to figure out what business objects u need and then u have to copy those business objects to ur company from Standard Company SAP
5)Each objects contains more than one structure and each structure can contain more than one fields. The relation goes like this
Object ---> Structure ---> Field
6)You have to define field rules for each required field of the object. You have to mark "Not required" for fields u don't need
7)After field rules for a given object is set u have to generate load report i.e. actual Direct Input Program which will migrate data. This program is generated on basis of field rules set by u.
8)After the load report is generated u have to prepare an input file (import File) for migration. The import file should be according to structure provided by SAP and must be in binary format. SAP Provides the structure of file according to your configurations. You have to write ur own Data conversion program(in any language) for this task.
9)You take import file as input and migrate the data using generated load program
10)Finally u can check the Migration Statistics and Error Log
Thanks and Regards,
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta

AR & AP Data migration from legacy

Hi,
1.What are the precaution to be taken for Data migration from legacy system?
2.We intend to use a conversion ac ( Dr conv ac cr Vendor ) Is it Correct way of doing it ?
3.How do i ensure that all my invoices uploaded correctlt ?
4.What is the best Standard program to get it doen ?.
5.Is LSMW is best to do it or shall I have to go for custom development?
Any piece of yr advice is appreciated.
Thanks, Chitra

Hi Chitra,
Following link are helpful in understanding LSMW:
Note 105244 - LSMW 1.0: known problems, tips and tricks
Re: LSMW and error handling
/community [original link is broken]
For Data Migration:
Note 400257 - Data Migration and Upload Report
Note 739860 - Data migration from a legacy system to SAP
Hope this helps.
Please assign points as way to say thanks

Data extraction / Conversion / Mapping / Miration

Hi All,
Can any one please explain the meaning of the below terms and how data is moved from Non SAP system to SAP system?.
"Data extraction / Conversion / Mapping / Miration"
Kindly give me detailed step by step instructions on how to accomplish this. Also if there is any documentation please forward.
I appreciate the help in advance.
Raj

Hi Raj,
We can use LSMW, BDC, eCATT to upload the data from Legacy to SAP system.
Data Extraction - Data has to extract from legacy in to some flat file like Xls.
Conversion - Convert as per the need of SAP.
Mapping - Mapping the extracted field with SAP field for upload.
Migration - Data migration from legacy to SAP using any tool like LSMW, BDC, CATT.
Good Luck
Om

SAP Accelarated Data migration

Hi All,
Could someone kindly provide more info about SAP ADM. I am uanble to get any info about the same. I would like to understand as to how exactly the tool works. I have the 4 page PDF that is posted on the site but its not clear on the actual tool. Can someone kindly provide me with some document or screen shots or any more info about it. My mail id is [email protected] Could someone kindly reply at the earliest.
Thanks
Prahlad

Hi Prahlad,
Go through this hope u can understand.
With SAP Accelerated Data Migration, you can reduce migration
costs by as much as 50% and avoid interruption of business
processes. Moreover, shutting down the source system after
migration reduces system administration costs and total cost
of operations. In short, you realize the following benefits:
Significantly reduced cost and time to complete migration
projects
Accurate, cost-effective data transfer applicable for any kind
of source system
Better data quality because of preconfigured business objects
that ensure data consistency
Improved end-user productivity and acceptance thanks to
migration of historical data
Effective migration that avoids interruption of business
processes
Full support services to avoid risks and ensure the optimum
performance of your new business applications
Faster return on investment
In short, a smoother, more cost-effective migration to a new
technology solution ultimately positions your organization
to lower your total cost of ownership, maintain competitive
advantage, and pursue new business opportunities.
Expertise in Action
SAP Accelerated Data Migration applies a business objectoriented,
two-step approach that uses a neutral interface as a staging area
and predefined migration content for the conversion and upload
of data. The neutral interface enables the SAP tool to generate
predefined migration content and prevents all potential legal
issues regarding the intellectual property of any source-system
vendor. The whole data migration process from the source to
the target system consists of just two steps, as follows:
1. Data is extracted from the source system into the standard
interface as XML files.
2. Data migrates from the interface into the mySAP Business
Suite database. The migration is based on a new migration
workbench engine developed by SAP based on the SAP
NetWeaver® platform. All requirements for mapping structures
and fields and developing complex conversion rules are solved
within this engine (see Figure 1).
Once the migration is complete, business-unit end users have
access to all the legacy data in the new applications as if it had
originated there. They can continue to work on the existing
business process items in the new applications and benefit from
improved functionality.
Lifting the Limitations
Much of the cost and effort involved in classical data migrations
are generated by migration content development, as follows:
Identifying business objects for migration to properly support
the business
Defining the structure and field mapping for the relevant
business objects
Developing conversion rules for all necessary value mapping
Readily available migration content can simplify this effort.
SAP Accelerated Data Migration provides preconfigured business
content, helping you migrate it to your new system more efficiently
and rapidly. The tool allows the migration of all types of
data, independent of its current state within a business process.
This includes master and dynamic data, as well as partially
processed and historical data, to minimize data loss. Business
processes are uninterrupted and normal operation procedures
can be retained.
By providing a standard, neutral interface and reading data as an
XML file, SAP Accelerated Data Migration is applicable for any
kind of source system. Preconfigured data migration objects built
specifically for SAP applications significantly simplify the conversion
from non-SAP software data into SAP software data objects,
yielding far-reaching benefits. Besides reducing related IT costs,
you can be certain of consistency across business-object boundaries.
Through a direct insert into the database, you avoid the
performance limitations of classical data migration.
Reward points if helpful.
Thanks

Data Migration (FI/CO)

Hi,
Kindly let me know the process for data migration from legacy to SAP system.
The client wants us to migrate not only the open items but also all the line items (since there are not much transactions as the company was newly incorporated).
We are following the BDC approach, I need to know if there is a debit item then which account is to be credited.
If any document please send to my email [email protected]
Points would be awarded.
Thanks
SS

Hi SS,
I would recommend you to check the LSMW. You can achieve a lot with this tool to convert master data and transaction. Check also the modules you have. For example the asset module has special functions for conversion purpose.
Greetings,
S

Transaction Data Migration

Is there a "best practice" for transaction data conversions from a legacy system into R/3? I am in a project where I have to create a strategy for SCM transaction data (PO's, Inventory, Vendor Invoices, and so on). I would like to know the pros and cons of migrating a PO in their various stages (Open, G/R but not yet invoiced, Partial G/R). Basically a strategy to propose to my client regarding their SCM transaction data.
Thanks for your help!!!!

hi,
For uploading the GLs :-->
Use FB50 entry Dr GL a/c Credit Data migration a/c or controlling a/c
For uploading the Vendor balances : -->
Use FB60 entry Dr Data migration a/c or controlling a/c and credit Vendor a/c (individually)
For uploading the Customers balances :-->
Use FB70 entry Dr Customers a/c (individually) Cr Data migration a/c or controlling a/c
For uploading the Assets-->
AS91 -> for uploading assets in AA
OSAV --> for uploading assets in GL entry Dr Asset (invidiually) Cr Data Migration account or controlling account
You can use LSMW for uploading all these things
After uploading all, your data migration account will become zero.
For posting the transactional data use LSMW for relevant TCODES
Radha

DATA Migration Strategy of Inventory from one SAP system to another

Hi,
We are migrating data from one sap system to another due to business split . I would like to know what are the considerations, dos and donts for inventory/stock balance migration.
Appreciate your responses on the same.
Kind regards,
Tanuja

Hi
Here are some of the links for Data migration in SAP which may be really helpful for you..Please have a look at them.
http://www.packtpub.com/article/data-migration-sap-business-one-part1
http://www.sap-press.de/download/dateien/1468/sappress_migrating_your_sap_data.pdf
http://sceisqaweb.sc.gov/documents/Agencies-Approach-and-Plan-for-Data-Conversion.pdf
Thanks.

Data migration/ conversion

Similar Messages

Maybe you are looking for