Data Migration help in SAP

Hi All
Can anyone suggest good datamigration tool,Actually we are migrating our data from Microsoft sql to ORACLE(SAP 4.7) and I have never done this kind of data migration.
I would appreciate small help also.
Thanks in advance.
Regards
Sukrut s

you need to get an OS/DB-Migration service to get support after migration. The migration itself on the production system must be done by a certified migration consultant.
Check
http://service.sap.com/osdbmigration
Markus

Similar Messages

DMS Data Migration-Help required

Hi,
I don't have enough knowledge on DMS Data migration.
In our recent Implementation, we are implementing SAP DMS.
Our client has more legacy data which is in their server. So we have to upload all the data's into SAP DMS.
I gone through few SCN threads and understand that LSMW & BDC will be used for Data migration.
Which is the best method for Data migration?
We are having 50+ document types and it has different processes (status network), Classification & few Object links.
Please advice me and provide me some examples to upload legacy data in DMS.
Thanks in Advance,
Ravi

Hi Ravi,
There are few approach discussed in the thread https://scn.sap.com/thread/2119796
You may check feasibility on these approaches for your scenario.
We are having 50+ document types and it has different processes (status network), Classification & few Object links.
Creating these configurations into SAP is one time and should not be a problem.
I gone through few SCN threads and understand that LSMW & BDC will be used for Data migration.
Which is the best method for Data migration?
How much volume of data do you have in legacy system ?
Have a thought on whether do you really need to migrate all these data into SAP DMS ???
OR
You can configure the DMS system and start fresh leaving the document in legacy system as it is.
Hope this helps.
Regards,
Deepak Kori

Data migration tools in sap

hi,
i am newbie to s.a.p nd i got ma project related to data migration. we are taking data from legacy system to sap database. we are using a tool called cransoft. what about the future of this tool. how to plan my career in this data migration.need help from experienced persons. im a sap abap resource actually. im having practically no work using abap in this project.im very much concerned about ma career.help me out...
thank you

>>will my career depend on the tool im working in or it depends on data migration only
That is something which depends upon how much and what kind of experience you have, if you are an expert in one tool, then your career basically depends on it, but if you understand the concept and have good experience in multiple tools, then you will have broader domain.
In consulting, it is much easier to be an expert in one tool, you are not tied to one client and can find project somewhere else.
But if you are a permanent employee, then it helps to adjust your skillset as per the changing environment.
Having said that, you don't have to go after every tool in the market, try to diversify as per your interests and the market need.
Talking specifically about BODS, i have seen quiet a few clients using or planning to use it so its future looks bright, but then again, future can always change.
Thanks
Aamir

Data migration Tally to SAP B1

Hi Friends
I need a information about data migration from tally to sap business one.
can anybody guide me how to do ?
regards
kamlesh

> Hi Friends
>
> I need a information about data migration from tally
> to sap business one.
> can anybody guide me how to do ?
>
> regards
>
> kamlesh
Hi Kamlesh,
AFAIK, there's no standar tool released by SAP to do the data migration from Tally directly. The possible is export the legacy data to MS Excel, format into DTW format, and import into Business One via DTW.
DTW - Data Transfer Workbench.
I don't know if any partner has developed add-on for this purpose.
Regards,
Chris

Strange legacy data migration problem to SAP CProjects

Dear all,
I am new to CProjects and currently working on migrating legacy data to CProjects through XML. I am facing some strange problems when migrating project data with multiple phases. If the project already exists in Cprojects, the XML import transaction hangs indefinitely and a timeout exception is thrown. While on the other hand, if I upload a new project (with same set of phases), it is readily imported without any problems.
Kindly help!
Thank you all!

Hi Vivek,
If the project already exists, the system creates a simulation from the imported data. You then need to move the simulation to your operational project by performing a reconcilliation. You can't simply overwrite an operational project via an import.
I have included some links below from SAP help which may help (cProjects 3.1).
http://help.sap.com/saphelp_cpro31/helpdata/en/26/cb8740f8aacf62e10000000a155106/content.htm
http://help.sap.com/saphelp_cpro31/helpdata/en/b0/d562404fb6cd01e10000000a155106/content.htm
Regards,
Lashan

HELP ME ON DATA MIGRATION PLEASE

Hi
what is SAP data migration what kind of tools and techniques include in that and also please what are the roles and responsibilities include in that when we are working on project.(RELATED TO ABAP)

Data Migration Current Situation
Data migration or data conversion is a persistent issue facing most organizations who have implemented SAP. Whether it is during the final phases of a new SAP implementation, during SAP upgrades and updates, during corporate restructurings, or during mergers and acquisitions, data migration continues to remain a challenging problem for IT.
Most data migration projects are faced with a time and budget crunch. But, these projects usually require extensive support from programmers and other technical experts and therefore data migration projects tend to get expensive and time-consuming.
The tools for data transfer and data migration provided by SAP are very technical and have a steep learning curve associated with them and they require technical experts to build and implement the data migration scripts.
Data Migration Ideal Scenario
An ideal data migration scenario would let the data migration project be implemented by the end user departments themselves. A few super-users within these end-user departments that supply the data should have the ability to transfer and migrate data themselves without relying on technical experts. Such a scenario would significantly cut the time and effort required in a data migration project.
Reaching such an ideal scenario would require data migration tools that are easy to learn and require no programming. Furthermore, these tools should work across all the different SAP modules and the SAP products, including the different versions of SAP.
Data Migration
Data Migration is the process of moving required (and most often very large) volumes of data from our clients existing systems to new systems. Existing systems can be anything from custom-built IT infrastructures to spreadsheets and standalone databases.
Data Migration encompasses all the necessary steps to cleanse, correct and move the data into the new system *. Technological changes, change in providers, software updates or data warehousing / data mining projects make such delicate and critical operations necessary.
<b>Data Migration can be done using BDC, LSMW, BAPI, Idoc's.</b>
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Differences between bdc session method and call transaction method.
The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel
The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.
Refer this
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html
http://www.****************/InterviewQ/interviewQ.htm
http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
regards,
srinivas
<b>*reward for useful answers*</b>

CRM Masterdata and Data Migration Templates

Could some one please provide me the below templates if you have any...
- CRM Master Data Mapping Template
- CRM Data Migration Design Template
- SAP CRM Data Design Template
Really appriciate your help...
Thanks in advance..
Sr

It is a duplicate one... so just marking it as answered because I could not find the option to delete.

LSMW data migration porcess from the beginning

Hi gurus,
I do understand that there are 14 steps to be completed during migration, but can anyone give me a basic idea as what needs to be done prior to the above steps when starting a data migration project, as i have been only involved in the LSMW(14 steps) process before.
Thanks in advance, points will be awarded for all answers.
Ganga

Hello
As an intro:
Classical data migrations are typically limited to master data and
tend to cause multiple negative impacts on workflow and oper-
ating business units.
To minimize costs, risks, and effort during a data migration and ensure a smooth changeover for operational business processs items, and better reporting
capabilities SAP recently come with a Data Migration Solution called SAP Accelerated Data Migration tool.
This advanced tool, coupled with support from the SAP Services organization and SAP partners, lets you easily migrate and integrate application data from any legacy system into SAP applications and reduce migration costs significantly.
Data migration is done in 4th phase i.e. the final preparation stage of ASAP methodology.
As far as LSMW is concerned, BDC and LSMW both are use for loading data into SAP system. The difference is ,LSMW is loading tool by SAP where you can use various methods to upload, massage data or cleansed your data while loading into SAP from legacy system. The method can be BDC, BAPI, Idocs or SAP ABAP codes. Usually in BDC the user has to write an ABAP program or use other utility to load legacy data.
LSMW has been developed mainly for the Functional people who has no knowledge of the technical aspects of report or BDC in ABAP because its very user friendly and handy to use. So, simply they can upload the master records using LSMW.
Reg
assign points if useful

Data Migration from SAP r/3 to SAP R/3

Hi all,
What is the best method to migrate data from one verison of SAP to another verison of SAP ECC say from SAP 3.1 to SAP ECC 6.0?
This is for all SAP modules including sd, mm, pp, fi, co master and transaction data. I know there are number of technologies to load the data such as LSMW, IDOC, ALE, DI, etc but what is the best way to extract all data feeds to be loaded back into SAP.
Thanks in advace.

Take a look to the following link, may be useful for you
SAP NetWeaver - Data Migration (CA-DMI) [original link is broken]
if helpful reward points are appreciated

Data Migration From Peoplesoft , JDEdwards To SAP.

Hi,
This is kiran here we are doing data Migration work from Peoplesoft And JDEdwards to SAP.in SAP side it involves Master data tables Related to Customer, Vendor, Material. and Meta data tables related to SD, MM, FI. We as SAP Consultant identified Fields from above tables and marked them as Required, Not required, And Mandatory. The Peoplesoft and JDEdwards flocks come up with the same from their side. Then we want map the Fields. as I am new to data Migration any body suggest me what are the steps involves in data Migration How to do Data Mapping in Migration Thanks in advance.
Thanks
Kiran.B

Hi Kiran,
Good... Check out the following documentation and links
Migrating from one ERP solution to another is a very complex undertaking. I don't think I would start with comparing data structures. It would be better to understand the business flows you have currently with any unique customizations and determine how these could be implemented in your target ERP. Once this is in place, you can determine the necessary data unload/reload to seed your target system.
A real configuration of an ERP system will only happen when there is real data in the system. The mapping of legacy system data to a new ERP is a long difficult process, and choices must be made as to what data gets moved and what gets left behind. The only way to verify what you need to actually run in the new ERP environment is to migrate the data over to the ERP development and test environments and test it. The only way to get a smooth transition to a new ERP is to develop processes as automatic as possible to migrate the data from the old system to the new.
Data loading is not a project that can be done after everything else is ready. Just defining the data in the legacy system is a huge horrible task. Actually mapping it to one of the ERP system schemas is a lesson in pain that must be experienced to be believed.
The scope of a data migration project is usually a fairly large development process with a lot of proprietary code written to extract legacy data, transform and load the data into the ERP system. This process is usually called ETL (extract, transform, load.)
How is data put into the ERP?
There is usually a painfully slow data import facility with most ERP systems. Mashing data into the usually undocumented table schema is also an option, but must be carefully researched. Getting the data out of the legacy systems is usually left to the company buying the ERP. These export - import processes can be complex and slow, sometimes specialized ETL tools can help, sometimes it is easier to use what ever your programmers are familiar with, tools such as C, shell or perl.
An interesting thing to note is that many bugs and quirks of the old systems will be found when the data is mapped and examined. I am always amazed at what data I find in a legacy system, usually the data has no relational integrity , note that it does not have much more integrity once it is placed in an ERP system so accurate and clean data going in helps to create a system that can work.
The Business Analysts (BAs) that are good understand the importance of data migration and have an organized plan to migrate the data, allocate resources, give detailed data maps to the migrators (or help create the maps) and give space estimates to the DBAs. Bad BAs can totally fubar the ERP implementation. If the BAs and management cannot fathom that old data must be mapped to the new system, RUN AWAY. The project will fail.
Check these links
http://pdf.me.uk/informatica/AAHN/INFDI11.pdf
http://researchcenter.line56.com/search/keyword/line56/Edwards%20Sap%20Migration%20Solutions/Edwards%20Sap%20Migration%20Solutions
http://resources.crmbuyer.com/search/keyword/crmbuyer/Scm%20Data%20Migration%20On%20Peoplesoft%20Peoplesoft%20Data%20Migration/Scm%20Data%20Migration%20On%20Peoplesoft%20Peoplesoft%20Data%20Migration
Good Luck and Thanks
AK

Data Migration from IDES to Vanilla open source SAP System

Can any one help me as to what are the SD tables that should be migrated between 2 SAP systems in order to operationalize a complete Sales Cycle . This information has to be provided to the Basis team . Where i should i start from and what should be my approach ?

Tables in Sales and Distribution (SD) :
Document Flow
VBFA - Document flow (alg.)
VTFA - Flow shipping documents
Sales order :
VBAK - Header data
VBAP - Item data
VBPA - Partners in sales order
VBKD - Sales district data
VBEP - Data related to line items, delivery lines
Billing document :
VBRK - header data
VBRP - Item data
Shipping :
VTTK - Shipment header
VTTP - Shipment item
VTTS - Stage in transport
VTSP - Stage in transport per shipment item
VTPA - Shipment partners
VEKP - Handling Unit - Header Table
VEPO - Packing: Handling Unit Item (Contents)
Delivery :
LIKP - Delivery header
LIPS - Delivery item
Pricing :
KONH - Conditions header
KONP - Conditions items
KONV - Procedure ( billing doc or sales order)
KOND
Contracts :
VEDA - Contract data
Regards,
Rajesh Banka

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 - SAP EC - Environmental Compliance

Hi,
I’m in a Project here in Brazil and they will start to use the portal SAP EC and I have to do the data migration.
I read in some manuals about the “Export Excel Template”, but I don’t know if this is the correct way to do the data migration for this portal. If I use this way, is this possible I change the fields and create a new template?
Thanks a lot!
Regards,

Hi Victor,
EC30_XML_TransferTool.ZIP
PermitDataTemplateSample.zip
This Zip File containing the EC standard documentation of the XML Transfer Template and an example definition file.
This is correct Template for export and import for mass data .
for User Manual Click here
EC_FP3_overview_part1-generic.pdf open this Pdf and see the page number 16. ( EC provides a separate help document for the new Excel tool.)
All the Best
Edward

RDS for SAP data migration through IDOC's

Dear Experts
Just now we have installed BODS 4.1 and RDS also installed now. I am in the process of exploring the RDS. I found all the migration objects is available in the form of IDOC's. Now my questions are
How to work on custom IDOC's. Do i need to extensively code on R/3 side to upload the custom fields. Like user exit or BADI for custom fileds
If yes then i would say implementation time through RDS will remain more or less same time.
Through BODS or by RDS migration objects is there any way without coding on ABAP R/3 side, Can we achieve migrating custom fields
Please let me how to achieve above requirements by RDS
Thanks
Vijay Mukunthan

Hi Vijay,
You are right, the standard content of the Rapid Data Migration RDS packages brings the content with the standard IDoc interface for SAP standard only. So custom objects are not pre-built with the package. However, we incorporated the foundation to include custom coding as easy as possible:
1) IDoc
We are using the standard interface technology IDoc. IDocs do have an enhancement concept which is described in the online help. There are three main cases and all of them are supported, however two need additional coding:
Z-fields: Additional fields in existing tables lead to IDoc segment extensions
With the IDoc segment versioning concept this is easy to realize without any ABAP coding
Z-tables: Additional IDoc segments will be necessary and lead to a new IDoc version
With the IDoc versioning concept you can easily add Z-segments with leveraging provided user exits
Custom business objects:
You can even create a complete own IDoc message type in Z-namespace for own stuff, leveraging the given ALE layer of the IDoc middleware
2) Enhancement guide
With the RDS package we offer an enhancement guide which helps you to modify the jobs and data flows in the SAP Data Services content according to the changes in the target IDoc structure to reflect additional fields and tables. We built it as a step-by-step guide following for a sample IDoc type but will work similarly for any IDoc.
Best regards,
Frank Densborn.

Regarding Migrating data from Legacy to SAP

Hi All,
We are in Migration Project. We have to upload data from legacy to SAP, either using BDC or Cross-Applications in the following SD scenario's.
1. Customer Master
2. Inquiries
3. Quotations
4. Proposals
5. Sales Order
6. Goods Issue
I would like to know, which concept is better for each of the above scenario. Each option have advantages and disadvantages. So, I need suggestion regarding this.
Regards,
Sathya.

hi
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/backgrou nd processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
also check this link:
Diff. between LSMW & BDC
Re: bdc and lsmw
plz reward points if it helps
rgds.

Data Migration help in SAP

Similar Messages

Maybe you are looking for