SAP Master data migration tools

Hi,
I would like to know if any SAP standard tools which are available for all master data migration,Kindly share the same which is required for us now.
We have to migrate the data from legacy systems to SAP and we have to use only SAP Standard master data migration tools.
Kindly share the same.
Thanks and Regards,
Raveendra

Raveendra,
SAP migrates data from legacy system using standard tools like LSMW, BDC, BAPI. Under LSMW you will have Batch input, Batch recording, BAPI and IDOCs options. Depending upon requirement you can choose any one of them. BAPI is advisable instead of BDC method.
Also for utilities industry SAP has provided ISU Migration tool (EMIGALL).

Similar Messages

  • Looking for Third Party SAP Data Migration Tools

    Hi all,
    I don't know if this is the right place but I was wondering if anyone can provide me a list or a link of the different third party SAP Data Migration Tools. I am specifically looking for productions that migrate data from one SAP system to another.
    Thanks and I hope to hear from you.
    Regards

    Hi,
    Just to weight out my options and compare the diffrent products as a research of sort.
    For SAP tools they use LSMW I believe but I want to check the alternatives.
    Regards

  • 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 object–oriented,
    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

  • SAP Accelerated Data Migration

    Hi
    Can someone tell me if this tool is used only for extraction or can it also be used for reporting??. Whats the transaction code. Do you have to buy an addon to your existing R/3 to have this functional.
    Kindly advise.
    Thanks
    Prahlad

    The SAP Safe Passage Data Migration Services provides the tools and methods you need to make a smooth transition from your Peoplesoft, JDEdwards or Siebel system to mySAP ERP or SAP CRM.
    SAP Accelerated Data Migration focuses primarily on supporting customers in using the SAP ADM migration tool and ensuring that all migration aspects are included in the implementation project of mySAP ERP or SAP CRM. The migration tool transfers master data as well as history and transaction data. The business process started in the non-SAP system can be continued in the new SAP system without process interruption
    refer the below page to download an article ( about 4 page)
    http://www.sap.com/community/pub/SimpleSearchResultPage.epx?SearchID=5430195
    mail me at [email protected] if you are not able to download
    Regards
    Vivek
    Reward points for all useful answers

  • Downloding the SAP master data and transaction data to a flat file

    Hello All,
    Is there any SAP standard method or transaction to download the SAP master data and transaction data to flat file.
    With out using ABAP development, SAP had provided any tool or method to download the SAP system master and transaction data to flat file.
    Thanks,
    Feroz.

    hi
    as of now up to my knowledge no.

  • Hr master data migration

    Hi
    I am working in a sap hr master data migration project.The client is having sap hr system  in one location ,they want to migrate the datas of other 3 locations into sap hr system.(2 diffrent countries ).I have prepared a business blue print for 3 locations,now client want a Functional Design Document for 3 locations .
    Can any one help me to prepare a design document.Is there any standard format ?
    Payroll ,time managementand benefits are in third party system.In this project only hr master data migration

    hai sony joseph,
    as per the thread you need to prepare data migration strategy document for each module,if yes  i will give some guidance overthat.
    Regards,
    Chiran Reddy.

  • Backoffice methodlogy and data migration tool

    Anybody know about backoffice methodology?This methodology was developed by backoffice associates.I would like to know more about it.
    see the link below
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ad903bcc-0901-0010-25bd-a0e5aebcf2b0
    If anyone know please help.
    Message was edited by:
            abi baski

    So, I loaded my CUCM with 6.1.4 which is absolutely compatible with UCCX 7.0.1 and I still get the same error which is as follows:  Data Migration is only supported on CUCM Deployments.  I am using the Data Migration Tool for 4.0.5 to 7.0.1 UCCX deployments.  All necessary services are started on the CUCM and the UCCX license and CUCM pass validation.  I am at a loss as to why I am getting this error.  Does anyone have any ideas?

  • Error when using Channel Migration Tool in SAP Directory Content Migration Tool

    Hi Experts,
    I'm trying to migrate a file receiver channel using the Channel Migration Tool in SAP Directory Content Migration Tool.
    I enter the channel name and then select it or click in "Edit"; I get the bellow error:
    Thanks in advance.
    Su May
    500   Internal Server Error
      SAP NetWeaver Application Server/Java AS
    The initial exception that caused the request to fail, was:
    java.lang.NullPointerException: while trying to invoke the method
    com.sap.pi.tools.dirmig.channel.metadata.SoftwareComponentVersion.getVersion()
    of a null object returned from
    com.sap.pi.tools.dirmig.channel.metadata.AdapterMetadataFactory.getLatestSWCV(java.lang.String)
    at
    com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.ChannelSelectionView.onActionChannelTableSelect(ChannelSelectionView.java:548)
    at
    com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.wdp.InternalChannelSelectionView.wdInvokeEventHandler(InternalChannelSelectionView.java:486)
    at
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
    ... 56 more
      See full
    exception chain for details.
    Failed to process request. Please contact your system
    administrator.
    While processing the current request, an exception occured which could not be handled
    by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the
    cause of the problem, please contact your system administrator. To facilitate
    analysis of the problem, keep a copy of this error page. Hint: Most browsers
    allow to select all content, copy it and then paste it into an empty document
    (e.g. email or simple text file).
    For further information about the Web Dynpro error page, error
    analysis and a description of well-known error situations, see SAP note
    1113811.
      Correction Hints
    Exception
    could be caused by the development component: sap.com/tc~pi~tools~dirmig~wd
    Note: The above hints are only a guess. They
    are automatically derived from the exception that occurred and therefore can't
    be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type
    AJAX Client
    User agent
    Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
      Trident/5.0)
    Client Type
    msie 
    Client Type Profile
    ie6
    ActiveX
    enabled
    Java Applets
    enabled
    Accessibility mode
    disabled
    Inline CSS
    false
    Validate by rendering
    true
    Server
    Web Dynpro Runtime
    vendor: 'sap.com', name: 'tc/wd/webdynpro', scV: 'sap.com',
      scN: 'WD-RUNTIME', location: 'SAP AG', counter: '7.4008.20140808120905.0000',
      R: '7.40', SP: '8', PL: '0', change number: '613920', codeline:
      NW731CORE_13_REL
    J2EE Engine
    7.40.3301.367419.20140806095041
    System ID (SID)
    Server Node ID
    |6080050|60800|Server 00
      00_60800|douaklsappod.douglas.local/10.2.0.87|SERVER|RUNNING
    Java VM
    SAP Java Server VM, version:6.1.071 24.55-b08, vendor: SAP AG
    Operating system
    Windows Server 2008 R2, version: 6.1, architecture: amd64
    Application
    Java EE Application (deployable object)
    sap.com/tc~pi~tools~dirmig~wd
    Web Dynpro Application
    DirectoryCockpit
    Request URI
    /webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd/DirectoryCockpit
    Version
    vendor: 'sap.com', name: 'tc/pi/tools/dirmig/wd', scV:
      'sap.com', scN: 'SOAMON', location: 'SAP AG', counter:
      '7.4008.20140828111619.0000', R: '7.40', SP: '8', PL: '0', change number: '9' 
    Web Dynpro Code Generation Infos
    sap.com/tc~pi~tools~dirmig~wd
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd:
      SapDictionaryGenerationCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:01:39+0000, changelist=402811, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd:
      SapDictionaryGenerationTemplates
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:02:11+0000, changelist=402811, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapGenerationFrameworkCore
      7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T19:41:09+0000, changelist=402838, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapIdeWebDynproCheckLayer
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:25:15+0000, changelist=612716, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelCommon
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T19:44:59+0000, changelist=402897, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL, buildtime=2014-08-22T19:42:52+0000,
      changelist=402897, host=vmw5876, is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelDictionary
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T19:51:47+0000, changelist=402813, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapMetamodelWebDynpro
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:03:52+0000, changelist=612717, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapWebDynproGenerationCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:25:48+0000, changelist=612716, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd:
      SapWebDynproGenerationTemplates
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:25:36+0000, changelist=612716, host=vmw5876,
      is-central=true)
    WD web module
      webdynpro/resources/sap.com/tc~pi~tools~dirmig~wd: SapWebDynproRuntimeGen
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:22:51+0000, changelist=612719, host=vmw5876,
      is-central=true)
       sap.com/tc~wd~api
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapDictionaryGenerationCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:01:39+0000, changelist=402811, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapDictionaryGenerationTemplates
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:02:11+0000, changelist=402811, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapGenerationFrameworkCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL, buildtime=2014-08-22T19:41:09+0000,
      changelist=402838, host=vmw5876, is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapIdeWebDynproCheckLayer
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:25:15+0000, changelist=612716, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapMetamodelCommon
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T19:44:59+0000, changelist=402897, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapMetamodelCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T19:42:52+0000, changelist=402897, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapMetamodelDictionary
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T19:51:47+0000, changelist=402813, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapMetamodelWebDynpro 
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:03:52+0000, changelist=612717, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapWebDynproGenerationCore
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:25:48+0000, changelist=612716, host=vmw5876,
      is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapWebDynproGenerationTemplates
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL, buildtime=2014-08-22T20:25:36+0000,
      changelist=612716, host=vmw5876, is-central=true)
    WD web module webdynpro/resources/sap.com/tc~wd~api:
      SapWebDynproRuntimeGen
    7.4008.20140806095041.0000 (release=NW731CORE_13_REL,
      buildtime=2014-08-22T20:22:51+0000, changelist=612719, host=vmw5876,
      is-central=true)
    Detailed Error Information
    Detailed Exception Chain 
      java.lang.NullPointerException:
    while trying to invoke the method
    com.sap.pi.tools.dirmig.channel.metadata.SoftwareComponentVersion.getVersion()
    of a null object returned from
    com.sap.pi.tools.dirmig.channel.metadata.AdapterMetadataFactory.getLatestSWCV(java.lang.String)
    at
    com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.ChannelSelectionView.onActionChannelTableSelect(ChannelSelectionView.java:548)
    at
    com.sap.tc.pi.tools.dirmig.wd.wd.comp.channelmigration.wdp.InternalChannelSelectionView.wdInvokeEventHandler(InternalChannelSelectionView.java:486)
    at
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
    at
    com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
    at
    com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
    at
    com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
    at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
    at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
    at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
    at
    com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at
    com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:101)
    at
    com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at
    com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at
    com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at
    com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at
    com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at
    com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at
    com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at
    com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

    Hi,
    Go to NWA>Configuration>Infrastructure>Java System Properties, Click on the Applications tab and search tc~pi~tools~dirmig~wd & Start Application as shown in below screenshot.
    I am not sure but you can try this if it helps.
    Regards,
    Dipen.

  • SAP Accelerated Data Migration (ADM) Tool

    Hi-
    Has anyone used ADM for SAP HR/HCM data migration?
    If yes, can you please share your experience?
    <REMOVED BY MODERATOR>
    Thanks,
    Edited by: Hunk2007 on Feb 19, 2008 6:11 PM
    Edited by: Alvaro Tejada Galindo on Feb 19, 2008 12:14 PM

    Hey
    Did anyone use ADM for SAP HCM Implementation ??? Are you planning to use this tool or use the standard ways to load data ?
    Please let me know
    Deepthi

  • 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 Services as a data migration tool

    Hello All,
    Has anybody used Data Services as a data migrition tool from a SAP ECC system?  If so what is it like to use and are there any documents on this?
    Cheers,
    Nick.

    Hi Nick.
    About documents, here are some of them, but one that I think it could be useful for your understanding is the "BI109 SAP Data Migration" session: http://www.sdn.sap.com/irj/scn/shop?rid=/media/uuid/c08b931e-2a83-2c10-2aba-cb3968c5bc4e.
    It shows the data migration framework based on SAP BusinessObjects technologies for legacy to SAP and SAP to SAP migrations.
    More technical documents, showing how to set up iDocs, LSMW, etc:
    http://help.sap.com/bp_dmg603v1/DMS_US/Documentation/DM_installation_guide_EN_US.doc
    http://help.sap.com/bp_dmg603/DMS_US/Documentation/DM_Quick_Guide_EN_US.doc
    Regards,
    July

  • Que on Material Master Data Migration

    Hi All
    We are trying to allocate parallel currency to an existing co code, and since SAP recommends not to add parallel currency to an existing co code, we have decided to go ahead with a new co code - thereby transferring all master and transaction data as part of data migration..
    However, my Qs is.. do we have to migrate the material master data aswell since when I make the material to plant assignment in customizing, it should then officially belong to the new co code too right?
    Please advise
    RS

    Hello Jürgen
    Thanks for your reply.
    I dont think you fully understand my scenario..
    we have an entity that wants to introduce a parallel currency to all their reporting.. therefore, addiding a parallel currency to an active company code is not possible and they are not keen to go with material ledger...
    therefore, we suggested a brand new co code as of 01.01.2012. So the current co code is not going to be active after 31.12.2011. We are creating a brand new co code and doing data migration for all the master data and transaction data.
    meaning, Vendor, Customer, GL, AP & AR item Data, GL item data and asset master and transaction data.
    In customizing, after creating the new company, we will make the assignments to plant purchasing/sales org etc.
    My Qs - do we also need to migrate the material master since it belongs to a Plant. Therefore, when we assign the co code to the Plant, it will automatically be available in the co code when creating a PO etc..
    this is my Qs
    thank you
    RS

  • LSMW: Material Master Data migration

    I will be migrating material master data using LSMW IDOC.
    I also want to migrated associated material class data.
    The question is:
    How do I extract the material class data so that I can load them with LSMW IDOC CLFMAS after the materials are loaded?

    Hi,
    You have 2 possibilities.
    1. If it is 1:1 transfer for source SAP system to target SAP sytem ( without data modification ) you to establish the ALE interface and distriute by using the prg: RBDSECLF
    2. If it is a transfer of CLF data between 2 SAP systems where you need to modify the data based on some rules after you extract the data from the source system, you could extrace the data from Legacy by BAPI: BAPI_OBJCL_GETDETAIL. Once you extract the data, you could process as per the reqmt, & load the data by LSMW either by DI or by IDoc method.
    Hope this helps.
    Best Regards, Murugesh

  • Shared Master Data - SMD Tool Configuration

    Hello Experts,
    I have a requirement to generate ALE-IDOC for Customer and Vendor master change. So we are planning to use Shared Master data Tool of SAP.
    Have done the settings in BD52, BD50, BD61.  But do i need to configure BD64 ?
    My requirement is generate the IDOC in the same client, in the sense when master data is changed IDOC are to be triggered and they will be stored in a shared folder for other system to pick it up.
    So we need to have the source and destination as same client....
    Not sure whether SHared master data will work for same client ? Please let me know your expert thoughts.

    hi,
    Shared Master Data is a component which drives the distribution of any changes in the centralally maintained master data. The SMD component writes a change status in tables BDCP and BDCPS. For EG. whenever you change any data with respect to a material, the changes are logged in two tables namely CDHDR and CDPOS. Now there is a program RBDMIDOC which reads these changes and distributes the same. Change document Object are nothing but the component with which the fields are configured,so that any changes on those fields are recorded. You can find them in Tx. SCDO.
    For Material Master the change doc. object is. MATERIAL.
    Reward points if you find this useful.
    Rgds

  • HR Data Migration Tool

    Please suggest what is the best migration tool to upload HR data into SAP.

    Hi Dirk,
    Thanks for the information, please do let me know whether SAP Data Service 4.2 is licensed or can be used with my existing SAP ECC license.
    Regards
    Amit

Maybe you are looking for