Migration of SAP 4.7 to ECC 6.0

Hello Experts.
Can anyone of you give me the steps involved in migration of SAP 4.7 to ECC 6.0. I would appreciate if I can get a document with the screenshots on this. Many thanks for your help in advance.

Hi.. you dont have to create shadow instance by ur self.. the prepare & SAPup will handle that.. you just have to prepare an unused system number.
since ur 4.7 is already on unicode.. i think you can start with prepare script, and follow the whole prepare process.
few checklist that i know is like checking missing tables, clearing update lock, releasing transport requests, SPDD & SPAU.
I didnt remember the exact steps.. but u can get it from the upgrade guide from SAP Marketplace.
http://service.sap.com/instguides
Message was edited by:
        Muda Ikhsan

Similar Messages

  • Migration from SAP 4.7 to ECC 6.0

    Hi Friends,
      We are currently using 4.7 version and we are moving to ECC 6.0(it's not an upgrade project, we are building a new system). We have some workflow templates in 4.7 and we want to migrate it to ECC 6.0. What is the best practice for this. If we save the existing workflow templates and BOR objects in 4.7 in a transport request and move this transport request to ECC 6.0 system will it work? or do we need to create the entire workflow template again in 6.0? Keep in mind that we are not doing the upgrade here. Please advice.

    Hi,
    It better download a XML file (from 4.7) and upload it in the ECC 6.0
    In Menu, Workflow > Import/Export> Export to Xml file (in 4.7)
                  Workflow > Import/Export> Import from Xml file (in ECC)
    If you did any customizing in the BO, copy it manually, Because in the ECC the Most of BO are enhanced some attributes & method are included in the std.
    Regards,
    Surjith

  • Migrating BADI from 4.7 to ECC 6.0

    Dear Gurus,
    We r migrating from SAP 4.7 to ECC 6.0
    We have one BADI - ME_PROCESS_PO_CUST where we have made changes according to the requirement
    After upgrading to ECC 6.0. This BADI is not working even though it is in active mode.
    Any specific procedure for BADIs during upgrade
    Please let me know how to make it work ?
    Rgds,
    Saurabh

    hi Saurabh,
    did you got solution
    pls let me know that, we have same problem...
    thanks in advance.

  • Migrating an SAP 4.7x110 system on W2003 32-bit to a 64-bit host (x86_64)

    We want to migrate an SAP 4.7x110 system on Windows Server 2003 32-bit to a 64-bit host (x86_64). Afterwards we want to upgrade the system to ECC 6.0.
    According to PAM, 4.7x110 is not supported on Windows 64-bit.
    According to note 960769,
    "After the migration to the 64-bit hardware, your SAP system may have a status that is not supported by SAP for productive use (see Note 814834). You may need to upgrade to a new SAP release. In this exceptional circumstance, SAP offers support for the duration of the upgrade.  Note that SAP does not support a longer, more productive use of such a system for the period after the migration and before the upgrade....
    ...We generally recommend to use SQL Server 2005 (64-bit) for the productive use on x86_64. However, the 32-bit operation of SQL Server 2000 on Windows x86_64 64-Bit (supported by Microsoft) is also supported by SAP...
    ...The following table illustrates which OS/DB combination supports each SAP release in the target system.
    Source System   Target System (Kernel, DB Software)     Support Comment
    3.1I   3.1I 32-bit, MSSQL 2000 32-bit    only for upgrade (a,c)
    4.0B   4.0B 32-bit, MSSQL 2000 32-bit    only for upgrade (c)
    4.5B    4.5B 32-bit, MSSQL 2000 32-bit    only for upgrade (c)
    4.6C   4.6D 32-bit, MSSQL 2005 64-bit     productive (b)
    620   640 64-bit,  MSSQL 2005 64-bit    productive (b)
    640   640 64-bit,  MSSQL 2005 64-bit    productive (b)
    700   700 64-bit,  MSSQL 2005 64-bit    productive (b) "
    According to note 814834,
    "SAP supports the x86_64 platform on Windows 2003 Server SP1 x64 for kernel 4.6D and kernel 6.40 and higher. ... For product versions based on kernel 6.40 and higher, only 64-bit operation is supported."
    According to note 905634, about SQL Server 2005 support (where a mention to R3E 4.7 x110 is missing)
    "Supported SAP products based on SAP_BASIS 6.20 and SAP_BASIS 6.40
    Product Windows platforms
    BW 3.10 x86, IA-64
    SCM 4.0 x86, IA-64
    EBP/CRM 4.0 x86, IA-64
    ECC 5.0 SR1 x86, IA-64, x64
    NetWeaver'04 SR1 x86, IA-64, x64
    SCM 4.1 x86, IA-64, x64
    SRM 4.0 SR1 x86, IA-64, x64
    CRM 4.0 SR1 x86, IA-64, x64
    R3E 4.7 x200 SR1 x86, IA-64, x64
    SolMan 3.2 SR1 x86, IA-64, x64 "
    +//////////////////////+//
    According to all this information, may I move our 4.7x110 system onto a Windows Server 2003 SP1 64-bit, SQL Server 2005 64-bit, and after that we would upgrade to ECC 6.0?
    Thanks !!!
    Eva
    Edited by: Eva Verdaguer on Jul 25, 2008 12:41 PM

    Sorry, I forgot posting the SAP answer, which is also "Yes":
    30.07.2008 - 16:19:00 CET - Respuesta by SAP     
    Dear Eva,
    Yes, you can move to the 64 bit platform with SQL Server 2005 according
    to note 960769.
    Information in note 905634 means there is no installation DVD for
    release 47x110 for SQL Server 2005. So it is not possible to do a fresh
    installation of 47x110 except if you follow the workaround of note
    899111 (for x64).
    Best Regards,
    Manuel García Guardiola
    SAP Active Global Support - Netweaver Web Application Server
    ****************************************************************+
    Thanks very much for your message, anyway.
    Regards !!
    Eva

  • Migration of SAP From Windows to AIX

    Gurus
    I need information regrading migration of SAP ECC 6.0 on Oracle from Windows to AIX.
    Thanks

    Hi ,
    You will find information in the System Copy Guide .
    https://websmp104.sap-ag.de/instguidesNW70
    SAP NetWeaver 7.0 (2004s) --> Installation ---> <download the suitable system copy guide>
    You would also find lot of SAP Notes , go through them and let us know if you have any specific questions/concern.
    Regards,
    Neel

  • Migrating to SAP General Ledger (NewGL)  on a different box

    We are looking at migrating to SAP General Ledger on a production system with over 150 company codes and 10 years of unarchived data. Since this results in pretty large database tables we are looking at several options to minimize business impact.
    Among the available options, I have been told that it is possible to perform a migration from one box to another rather than in-place. I'm having trouble visualizing how transactional data from other modules (CO, SD, MM, PP etc) would be preserved in this case.
    Can anyone tell me if migrating from classic GL on one box to new GL on another is possible? Does it really reduce downtime? If so, how does it achieve this time savings? What are the pitfalls of taking this approach? Can a box-to-box approach be taken without loss of non-GL transactional data?
    Thanks in advance,
    Paul

    Hi,
    we migrated on 31st of march 2008 3 different 46c systems (AT, IN, CN) with 3 huge and a few small company codes into one ECC 60 system (using HR, SD, MM, PM, PP, QM, FI, CO). In ECC 60 we are using NewGL, document split, functional area reporting, PRCTR-wise balance sheets, segment reporting, FI/CO online integration, leding ledger IFRS, 2 non leading ledgers for every comp. code,...
    The migration project was started a year before go-live the system downtime was only the 31st of march (one day) for each company code.
    The main thing was, that we decided not to migrate any old transactional data to the new system but only the data (master data, open items, open PO's,...) thats needed.
    So the old stuff remains still in the old system (FY-end closing was done there) and all comp.codes started the new fiscal year in the new system.
    Due to the fact that many reporting issues where covered by business warehouse this ensured a continously reporting across the old and new system landscape and there was never a need to have "old" data visible in the new system.
    BR Christian

  • Migration and SAP Support for BW 3.1

    Hi,
    I have couple of queries regarding Migration and SAP Support.
    What is the required patch level that need to be mantained in BW 3.1 for a direct upgrade to BI 7.
    I would like to know whether SAP still supports BW 3.1. I searched in SAP Service marketplace, but didn't get much information regarding this.
    Your inputs are highly appreciated.
    Regards,
    Hari

    Hello,
    BW Upgrade from 3.x to 7.0
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e62b9990-0201-0010-42a7-ddcf5c93cafd
    Hope it will help you.
    Regards,

  • Hi Experts confusion on migration  from "SAP Business One" to "SAP R/3"

    Hi All
    I am a certified SAP Business One Certified Solution consultant and working on SAP Business One for the past 2.5 yrs and done 4 implementations.
    I want to migrate to SAP R/3 and have confusion on weather to join Project Systems/Material Management for training and pursue my career in the same. I want to do the Online Certification for the same.
    I feel like Jack of ALL and Master on None after working on SAP Business One.
    Pls guide me on the possible R/3 career options after SAP Business One and weather my experience in SAP will be counted for my future SAP career.
    I am confused Pls help.

    Better get trained in area of domain experience and get SAP certified.
    Check also this links
    Career Advice: SAP Business One to R3 transition in Ottawa Canada
    SAP B1 or R/3...which one to select
    http://it.toolbox.com/blogs/sap-library/sap-business-one-vs-sap-r3-system-architecture-13952
    http://it.toolbox.com/blogs/sap-business-one/sap-business-one-training-isnt-that-the-same-as-r3-9066
    Contact nearest SAP education partner for getting trained.
    http://www.siemens.co.in/en/about_us/index/our_business_segments/information_and_communication/sisl_business_profile/education_training/general_faq.htm
    http://www.sap.com/asia/services/education/schedule/schedule_IN.htm

  • Migrating the SAP-Scripts to smartforma which are related to Finance(FI)

    Hi,
    Do we can migrate the SAP-Scripts to Smartform which are related to Finance(FI) & those SAP-Scripts are called by a standard print program (RFFOUS_C)
    Urgent answer need please!!!
    Thanks,

    Hello,
    Yes you can migrate script to smartform  there are different ways to migrate.
    Use program SF_MIGRATE..
    to migrate from scripts to smartforms.
    Reward if helpful.
    Viswam.

  • Migration of SAP Workflow to non-SAP system

    Hi All,
    If there is a SAP Standard or custom Business Workflow in SAP system and if we want to implement the same business flow in some non-SAP system(EX: Oracle Apps,Workflow tools etc.,) where Workflows can be used...
    Can we migrate the SAP workflow into that system (non-SAP) by converting to the SAP Workflow template in xml or other format that supports the non-SAP system?
    Can the above said scenario be done?
    Or what is the process of Migrations of Workflows from SAP to non-SAP or Vice versa.?
    Thanks in advance
    Hraish Kollipara

    Hi,
    From your posting what I can understand is you want to model the same Process in other System e.g. Oracle Apps  which is already modeled and working properly in SAP system. I wonder if its possible to download the template from a system and use it in other. As per my knowledge every system has its own development Engine which is configured to work in a specified way. So if its possible then its really time saving.
    Regards,
    Vaishali.
    Edited by: Vaishali Rautray on Nov 20, 2009 5:20 PM

  • Migration from SAP BC To SAP P.I

    HI Experts ,
    I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
    1) What kind of challenges can be faced during migration from BC to XI?
    2) What is the best practise for doing the same?
    3) Can you share some scenario from where i can have some idea how to do migration?
    4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
    Would appreciate your valuable inputs on the same!
    I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
    Regards
    Saras Jain

    Hi Saras,
    I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
    Scenario
    SAP Business Connector enables data exchange between an SAP system and
    external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
    replaces SAP Business Connector (SAP BC).
    We distinguish between standard scenarios (that do not contain customer-specific
    development) and individual scenarios (that do contain services or mappings created
    by the customer). The following sections describe how to migrate both types of
    scenarios to SAP XI.
    Scenario 1 (IDoc – HTTP, HTTP – IDoc)
    An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
    XML. It is sent to an external business partner by using HTTP.
    An external business partner sends an XML document by using HTTP to SAP BC or
    to SAP XI. The document is converted to an IDoc and sent to a connected SAP
    system in the internal system landscape.
    Scenario 2 (IDoc – Mail, Mail – IDoc)
    An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
    XML. It is sent to an external business partner as an e-mail.
    An external business partner sends an e-mail to SAP BC or to SAP XI. The
    document is converted to an IDoc and sent to a connected SAP system in the
    internal system landscape.
    Flow Services
    Flow services are services that are written in the proprietary graphical-based flow
    language of SAP BC.
    Java Services
    Java services are services that are written in the Java language.
    There are several platforms that support Java, including SAP XI. However, the data
    model used in the Java services in SAP BC is proprietary.
    Stylesheet Transformations
    Stylesheet transformations are often used for mapping purposes. They take an XML
    document as input, convert it according to rules defined in the stylesheet, which is
    also an XML document, and produce an XML document as output.
    The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
    Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
    SAP NetWeaver is the open integration and application platform from SAP. With
    NetWeaver ’04, there is a significant overlap between the functions of SAP
    NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
    as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
    mapping, routing, and adapters to connect to a large number of third-party back-end
    systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
    based on SAP NetWeaver. Customers looking for a strategic integration solution for
    the complete application landscape should therefore now favor SAP NetWeaver.
    The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
    BC has not been developed further since this release. SAP BC is not released for
    any further platforms (such as Windows 2003) and does not support any further JDK
    versions, including the current version (Version 1.4).
    For information about the supported SAP BC versions, JDKs, and operating systems,
    see SAP Note 309834. For information about the support and maintenance strategy
    for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
    aware of the following:
    • A solution based on SAP BC cannot be a strategic, long-term solution.
    • A solution based on SAP BC is based on technology that was implemented in
    2003 and that is no longer further developed.
    • SAP BC is supported on limited platforms and for limited JDKs only. Vendor
    support for some of these platforms and JDK versions will soon be
    discontinued.
    SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
    on webMethods’ proprietary Integration Server, whereas SAP NetWeaver is based
    on open standards, such as BPEL4WS (business process execution language for
    web services). Therefore, only parts of an SAP BC implementation, such as XSLT
    mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
    programming based on SAP BC, such as SAP BC flow language, is unlikely to be
    reusable in the SAP NetWeaver context.
    Purpose of this Migration Guide
    The purpose of this migration guide is to provide scenario-based descriptions of the
    migration from a company’s system landscape that uses SAP BC to exchange
    documents with business partners, to a system landscape that uses SAP XI instead.
    This migration guide outlines, for certain scenarios, the individual steps a company
    has to take to replace an existing SAP BC implementation with SAP XI.
    The basic steps in the back-end systems are:
    • Defining the logical systems
    • Maintaining the ALE distribution model
    • Maintaining partner profiles and EDI ports
    • Maintaining RFC destinations
    The basic steps in the SAP XI system are:
    • Maintaining the System Landscape Directory
    • Configuring the IDoc adapter
    • Maintaining the receiver determinations, interface determinations, and
    interface agreements
    • Maintaining the communication channels
    The type of scenario to migrate typically has an impact on the communication channels only.
    Scenario 1 IDoc/HTTP
    IDoc – HTTP Using SAP BC
    Within the system landscape of a company, an SAP system sends an IDoc
    asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
    document. The fields of the IDoc are not modified, that is, the conversion does not
    involve any mapping of source fields to target fields. After conversion, SAP BC uses
    HTTP to send the XML document synchronously to an external URL of a business
    partner.
    System Landscape
    • An SAP system and SAP BC are installed within the same system landscape
    of a company.
    • The following information is defined in the SAP system to allow data
    exchange between the SAP system and SAP BC:
    o An RFC destination and a logical system for SAP BC
    o The distribution model is maintained, if necessary
    • The following information is defined in SAP BC:
    o An SAP server with an alias is defined. For this SAP server, the
    information that the SAP BC requires to connect to the SAP system is
    specified.
    o A listener is configured to listen to requests from the SAP system.
    o A routing rule with the transport type “XML” is configured for the
    specific sender, receiver, and message type. The routing rule
    determines how a message is to be routed and where it is to be routed
    to. The scenario described does not use an ACL, (Access Control List
    to restrict execution permissions for this routing rule) or pre-processing
    or post-processing SAP BC services.
    4.2 IDoc – HTTP Using SAP XI
    Check the prerequisites described above under Prerequisites for Standard
    Scenarios.
    The IDoc adapter is used to receive an IDoc from an SAP back-end system and
    convert it to XML.
    The adapter used to post this XML to an external destination is the plain HTTP
    adapter.
    To set up the communication channel, perform the following steps:
    1. Locate the routing rule in SAP
    Business Connector.
    In the Administration View, choose
    Adapters – Routing to navigate to
    Routing Rules.
    2. Select the details of the relevant routing rule.
    To display the details, choose the green triangle (Edit).
    Transport is typically set to XML and a URL is specified. You can use this
    URL in your SAP XI settings.In some cases, Transport is set to
    B2B Service and the parameters Server Alias, Folder and Service
    exist. This is the same as when Transport is set to XML and has the
    URL http://<serverhost>:<port>/invoke/<folder>/<service>.
    You can find <serverhost> and<port> in the definition of the
    remote server under Settings –>Remote Server in the Administration
    View.
    3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
    Use the following settings:
    • Adapter Type: HTTP Receiver
    • Transport Protocol: HTTP 1.0
    • Message Protocol: XI Payload in HTTP Body
    • Adapter Engine: Integration Server
    • Addressing Type: URL Address
    • Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
    Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
    regards
    Aashish Sinha
    P : Reward points if helpful

  • SAP Best Practices on ECC 6.0 IDES

    Hi,
    We are trying to implement SAP Best Practices on ECC 6.0 IDES Server.
    1) IDES Server has patch level greater then the one mentioned in the implementation guide. Is it ok to continue with SAP Best Practices installation.
    2) Uploading Notes through t-code SNOTE gives an error stating" Data file of SAP Note is incomplete". Please suggest how to proceed with applying notes.
    We are using tcode SNOTE --> Goto --> Upload SAP Note.
    Thanks & Regards,
    Satish

    Hi
    check if the SAP note has some pre-requisites?
    Ensure that you follow the procedure regarding the note upload:
    Do not copy & paste, ALWAYS quote the source.
    http://help.sap.com/saphelp_nw04/helpdata/en/7c/04f33925f12d20e10000000a114084/content.htm
    Read the "Rules of Engagement"
    SAP download manager is required for it.
    SAP Best Practices package specifies prerequisites to install the SAP application.
    Ravi
    Edited by: Juan Reyes on May 21, 2009 4:59 PM

  • OM and PA data transfer from SAP 4.7 to ECC 6.0

    Dear Experts,
    hi
    i am working on one project where i will need to design the data transfer from SAP 4.7 to ECC 6.0. this is not a upgrade project.
    the data of PA and OM are in 4.7 which is existing system. i need to transfer entire data into ECC 6.0 so i can use that data for my E-Recruitment module ( we are doing E-rec fresh implementation.)
    we will keep both the systems (4.7 and ECC 6.0). ECC 6.0 will be used for E-Rec and OM only. for PA and Payroll we will use 4.7.
    can some one tell me,
    1. what are the key points to keep in consideration from OM point of view ?
    2. which is the best method to transfer the OM structure and data from 4.7 to ECC?
    3. what are the risks?
    4. which system we should make master system and which will be the slave system? why ?
    your input will be much appreciated.
    thanks and regards
    chandra

    Hi Chandra,
    I was under the impression that you are planning to use PA & OM from 4.7, now I read it again.
    Now its advisable to keep ECC 6 as a master system, becoz OM is the stating point of the HR processes where all Orgnization unit, job, position exists. Later the same data can flow to the slave system for PA use. As OM is the starting point, this system should be the master system.
    Abou the IDoc interface.
    Check the basic type HRMS_A05, whether it has all the data you need to transmit. T-Code WE30
    If you need to add something you can create a Z version in WE31. I selected HRMS_A05 as it is present in both the SAP version.
    Next there are series of transaction you need to process. Check with technical person who hands IDoc interafcing.
    Steps are:
    Assigning Message type to IDOC Type with extension. T-Code WE82
    Create Logical System:
    T-Code SALE-> Basic Settings-> Logical Systems-> Define Logical System
    It is required to configure in the sending system as well as in the receiving system
    Assign Logical System to Client:
    T-Code SALE-> Basic Settings-> Logical Systems-> Assign Logical System to Client
    Create RFC Destinations:
    T-Code SM59, select ABAP connection of type 3.
    Create Distribution Model: T-Code BD64
    Generate Partner Profile: T-Code BD82
    Maintain sending system partner profile: T-Code WE20
    Link Message Type to Function Module T-Code WE57 in receiving system only
    Hope this will help.
    Let me know if you need anything else.
    BR/Manas

  • Upgradation Minimum sp level & kernel level for SAP 4.7 to ECC 6.0

    Hi,
    We recently created a test box , copy of devolopment.
    We are running on SAP 4.7 with sap_basis and sap_abap with sp level 46.
    SAP 4.7 with kernel release 640 and kernel patch version 155.
    Oracle 9i.
    What is minimum support pack level  and kernel patch level required to upgrade from sap 4.7 to ecc 6.0.
    As per threads it looks like kernel patch version should be 175.
    Can any one guide me with sap note which provides the info of minimum sp level and kerenl patch level.

    The source system requires a certain support package level (that is described in the upgrade guides) because the tools that to the import require them.
    So the easiest way is to check the upgrade guides and the mentioned notes which is the minimum support package level for the source system to start the upgrade.
    The target level must be at least equivalent or higher.
    Markus

  • Migration of SAP Script to SmartFrom

    Hi Experts,
    I migrated an SAP Script to a Smartform. The SAP Script have a lot of PERFORM <...> IN PROGRAM <....> and these are written in a report porgram. I want to know, how to convert those calls and subroutines so that I can use them in Smartforms. your help is appreciated.
    Thank you,
    Surya.

    You can copy the code into CODE BLOCKs in Smartform.
    In SAPscripts, these performs are used to calculate some value or processing some data.
    You can do the same in the CODE blocks in Smartform. Identify what exactly that perform is doing and identify where exactly you can write that in Smartform so that it fits with overall flow of the Smartform.

Maybe you are looking for