Migration R/3 - mySAP

Hi,
I need information about migration (tools, possibilities...) SAP R/3 to mySAP. I can't found any usefully documentation about it. Did anyone know resources about documentation of migration?
thanks
mike

Sure...
What do you need in particular ?
Basically, there is no specific issue (but you have to consider all the "normal" elements you have to manage when you go for a source system upgrade !)
Let me know if you need more help...
Bye,
Roberto

Similar Messages

  • SAP EH&S 4.6C Migration to SAP ECC6

    Hi All,
    We are having separate SAP R/3 instance for EH&S module (4.6C system). The transactions system is SAP R/3 4.7 system and is due for ECC6 upgrade. Just want to know
    1.     Has anything changed in EHS module from 4.7 to ECC6. If yes, what?
    2.     if we migrate the EH&S functionality from the separate instance for EHS to transactional system in ECC6 / 4.7 R/3  system - will it get affected.
    3.     What will be the best time to do the migration of EHS data to transactional system (before or after upgrade). We are using specifications, active phrase libraries, reports, report templates and report generation variants and WWI server for MSDS.
    Request your help. Thanks
    PS: Even partial answers will also help a lot.
    Best Regards,
    Vithal

    Hi,
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
    /people/thomas.mann2/blog/2006/08/22/sap-upgrade-conflicts-1
    http://service.sap.com/instguides > mySAP Business Suite Applications > mySAP ERP > mySAP ERP 2005 > Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences, refer to the below site u2013
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6. Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality, which can be downloaded to a word document if required. Also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps some extent.
    regards,
    mahesh.

  • Migration Key - How to Open a CSS Message

    Hi Team,
    We got the discovery system and asked SAP to get us a separate licence for mySAP ERP 2005. We got the CD-DVD's and SAP says that we can generate the licence key from the service marketplace. Now in the installation guide, it is mentioned that we should get the migration key by using CSS and opening a message in CSS Component: CA-SOA-DS. When I go the tab "Report Product Error" in CSS, the table control which displays the systems is still blank. I cannot go to the next step and open a message to request migration key. We really don't want to install the CD-DVD's on a separate server. We just want to get the discovery system up and running and it looks like without the migration key we can't proceed further.
    Questions:
    1) How do I start a CSS message without the system number getting displayed in the service marketplace. I have the installation number etc with me.
    2) Do we have to install and run something else prior to asking for migration key?
    Please respond as this is causing problems. Your help will be much appreciated.
    Thanks

    Hi Sachin,
    I'll try to shine some light on the topic you brought up.
    The Discovery System is shipped already pre-installed on the hardware. Thus there are no CD-DVD's that would allow installation on a seperate system. It follows the concept of an appliance.
    To license it you need to have a valid license for SAP ERP on MS SQL. This is the installation number you will need to request the license key from Service Marketplace. If you don't have that in place (no license or on different DB) please contact your SAP counterpart.
    Following the steps in the Quick Guide (https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b22d4e44-0e01-0010-ffa4-fe9c59939e5e) in sequence should guide you through all the necessary activities.
    Hope that helps,
       rAimund

  • Pre and post-upgrade tasks in BW for Upgrading R/3 4.6c to mySAP ECC 5.0

    We are currently in the process of migrating our R/3 4.6c System to mySAP ECC 5.0.
    We would appreciate if anyone could provide the major and minor
    Changes / impacts / measures, to be taken in BW side.
    <u><b>Questions:</b></u>
    1. What are the major impacts on the extractors, mainly delta?
    2. Do we need to activate all the datasource immaterial of its status?
    3. Steps to be taken for Unicode conversion
    4. Routines and structure change if any?
    5. Is there any change in DDIC objects?
    6. Any old methods that can be replaced by new methods? (for better performance e.g, LIS was replaced by LO)
    7. Changes in the database.
    8. Anyother issues
    Any relevant document will be helpful.
    Thanks & Regards
    Chandran Ganesan

    It depends on what you are taking about: functional or Technical.
    Tehcnially, after the upgrade you should make sure all the PI are working fine. The other things (i.e. extract)should be able keep the same. Unless you want to take advantage of the new WAS640 functionaity.
    If you plan to migrate your BW system into ECC 5.0, you might have long way to go. 
    Also, depends on your BW release. If it's BW 3.1 or below, you might need to upgrade by end of this year anyway.

  • Data conversion/migration

    Hi,
    what kind of data conversion/migration are we looking in plant maintenance and inventory management?
    Regards,
    Vijay

    Dear Vijay Srikanth,
    I think you are asking for all such activities in Plant Maintenance which can be automated using some data conversion / data migration programs. Where by the user will just upload his data and the activity is achieved by the program. Please refer to the following documentation and search for the term 'Activites in Plant Maintenance'.
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/MYSAP/SR_PM.pdf
    You will find all the required information there. Thank you.
    Regards,
    kartik

  • Data Structure for New General Ledger for mySAP 2004

    Guys,
    We are preparing to upgrade to mySAP 2004.
    mySAP 2004 doesn't have data migration tool for upgrade "classic" ledger to new ledger with advanced functionality. To utilize all new functionality, data should be migrated to the new ledger. Data migration tool in this case should be developed (ABAP). What is the difference in data structure of new ledger?
    if anybody who already went thru upgrade and could share some examples of programs for mySAP 2004 upgrade, my e-mail : [email protected]
    Thanks in advance,
    Mike

    Now I have the same problem. Anyone has a solution for this matter?

  • 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

  • Migration of FI-CA system

    I wander how to perform migration of FI-CA (ECC6.0) system from an HP-UX to Linux Redhat on VMware. It is an system with   Oracle database
    The amount of data is 1,5 TB. What would be the (aprox) time for export.
    Where could I find guide for heterogeneous system copy to perform that?

    Eric,
    That is not an issue for us.  Oracle is now supported in production on VMware (excluding RAC).  A new OSS note was generate ~ a couple of weeks ago.:
    SAP Note 1173954 - Support of Oracle for VMWare
    Note Language: English Version: 6 Validity: Valid Since 13.01.2010
    Summary
    Symptom
    You plan to use VMware with SAP Products with the Oracle Database.
    This note decribes Oracle's official support policy for VMware in SAP
    environments.
    More Terms
    VMware, Linux, Windows, RAC
    Cause and Prerequisites
    You encounter a problem with the Oracle single instance database (no RAC)
    with SAP running in a VMware virtualized environment on the Windows or
    Linux OS platform.
    For SAP with Oracle in VMware virtualized environments please consider the
    following additional prerequisites:
    o Oracle 10.2.0.4 and higher (no Oracle 10.2.0.2, no Oracle 10.2.0.3,
    no Oracle 9.2.x)
    o Only Oracle single instance, no support for Oracle RAC
    o minimum recommended Windows OS: Microsoft Windows Server 2008
    o VMware ESX 3.5 and higher will be supported (includes VMware vSpere
    v4)
    o Every customer opening SAP support calls needs to clearly signal in
    the first line of the message text that they are using a
    virtualized environment using VMware.
    Solution
    Oracle has not certified any of its products on VMware virtualized
    environments. Oracle Support will assist customers running Oracle databases
    on VMware in the following manner:
    Oracle will only provide support for issues that either are known to occur
    on the native OS, or can be demonstrated not to be as a result of running
    on VMware.
    If a problem is a known Oracle issue, Oracle Support will recommend the
    appropriate solution on the native OS. When the customer can demonstrate
    that the Oracle solution does not work when running on the native OS,
    Oracle will resume support, including logging a bug with Oracle Development
    for investigation if required.
    If the problem is determined not to be a known Oracle issue, the problem
    will be forwarded to VMware for support. When the customer can demonstrate
    that the issue occurs when running on the native OS, Oracle will resume
    support.
    The above solution description is in line with the context of Oracle
    Metalink Note 249212.1.
    Andre Kemp
    Sr. Product Marketing Manager u2013 APAC
    Certified mySAP 2000 Basis Consultant, and SAP Migration Specialist
    VMware
    Sydney, Australia
    Edited by: Andre Kemp on Jan 27, 2010 11:20 AM

  • R/3 Enterprise migration required to migrate EP 6.0 SP2?

    We currently have R/3 Entprise Core 4.7 installed, w/Ext Set 1.10, and are running Enterprise Portal 6.0 SP2 with the J2EE 6.20 Engine.
    Can we install Netweaver 2004s and migrate EP 6.0 SP2 to the current release (in order to take advantage of the Web Dynpro for ABAP and Visual Compose tools) without migrating R/3 Enterprise to mySAP ERP?
    Thanks,
    Paul

    Hi Paul,
      You can upgrade the portal with out upgrading the R/3 enterprise.  Note, that you can't go directly from EP6 sp2  to NW 2004s.   You have to migrate to NW04 and then perform the upgrade to NW 2004s.  Check the portal migration home page at http://service.sap.com/nw-epmig
    Good Luck,
    John

  • Syntax errors while migrating from non- unicode to Uni code

    What are the syntax errors while migrating from non unicode to Uni code

    Hi Sudheer,
    u can get the information related to errors while migrating from non- unicode to Uni code from the below...pls go through...
    Note 765475 - Unicode Conversion: Troubleshooting
    these are the notes related to the issues of migration form non unicode to ounicode.
    Related Notes
    986907 - SQL Server settings for R3load based system copy
    954001 - Error fix: ILLEGAL_SUBSTRING_MODIFICATION in SUMG
    936441 - Oracle settings for R3load based system copy
    928909 - Repair table data in SUMG in Unicode systems
    895804 - Problematic rows in table DMEE_TREE_NODE
    895560 - Support for languages only available in Unicode system
    885441 - Common Migration Errors
    842788 - DB Multiconnect: Unicode Migration
    837173 - RADCUCNT in Unicode Conversion: Collective Note
    756534 - Automatic Assignment of Languages with Character Statistics
    753334 - Unicode Conversion: Problem in Japanese device types
    726954 - Private Use Areas in Unicode Systems
    722193 - RFC legacy non-Unicode clients and Unicode servers
    718329 - R3load terminates the export during a Unicode conversion
    695196 - Error in the export for Unicode migration
    672835 - Textflags could cause problems during Unicode conversion
    627764 - Unicode migration: table pools inconsistent after conversion
    614550 - Troubleshooting BC-I18
    587896 - Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1
    573044 - Unicode conversion for HR application
    480671 - The Text Language Flag of LANG Fields
    379940 - Unicode based mySAP availability
    79991 - Multi-Language and Unicode support of SAP applications
    73606 - Supported Languages and Code Pages
    42305 - RSCPINST (I18N configuration tool)
    regards,
    rudra..
    Assign points if helpful

  • Migration to ECC and BW in one instance

    Hello,
    a customer has the ERP part on 4.6c and a BW on 3.1.
    Is there a standard migration path to ECC 5.0 with an internal BW on netweaver 04?
    Is it possible to first upgrade the BW system on a separate instance and later migrate it into the upgraded ERP ECC 5.0 system, so that there is only one instance at the end?
    Thanks for help!
    Matthias

    Hi Magesh,
    mySAP ERP 2004 is a new ERP solution from SAP.
    It divided into variuos software components. Basically you can divide mySAP ERP 2004 into 3 types of components
    1) ABAP Components
    2) JAVA Components
    3) Additional Components
    SAP ECC 5.0 is one of the ABAP Components. The ECC consists of the ECC application and the ABAP SAP Web Application Server 640. The plug-ins are an integral part, which are used to connect for example to SAP BW. It consists of the following S/W Components
    EA-IPPE 300PI
    EA-RETAIL 500
    EA-PS 500
    EA-HR 500
    EA-GLTRADE 500
    EA-FINSERV 500
    EA-DFPS 500
    EA-APPL 500
    SAP_APPL 500
    SAP_HR 500
    Hope this helps.
    Regards,
    Shubham

  • Document Splitting-Migration steps

    Dear Consultant,
    Any body is having documentation regarding Document splitting Migration Steps.It is very very urgent.
    Please help us.
    Regards,
    Kalpana

    Hi
    You need to migrate from Classic GL to New GL. With New GL Document Splitting comes with.
    The following notes would be helpful to you.
    1070629 - FAQs: New General Ledger Migration
    1039752 - New G/L migration: Restrictions and important information
    1030497 - SAP ERP 6.0: Public sector scenarios in new general ledger
    1014369 - NewGL migration: Availability of Development Support
    1014364 - NewGL migration: Information, prerequisites, performance
    1006320 - Expenditure Certification: Certifying Payment Amounts
    966000 - mySAP new general ledger and Joint Venture Accounting
    890237 - New GL with document splitting: Legacy data transfer
    Also you can have more indepth at http://service.sap.com/GLMIG.
    Regards,
    Suraj

  • Differences in Depreciation key table structure between SAP 4.5b and mySAP

    Depreciation keys in SAP 4.5b were stored in a different table structure to depreciation keys stored in mySAP ERP 2005. Deprecation Keys that existed before the SAP upgrade still exist in the old set of tables; these have a status of “Migrated” in SAP.  Any new or modified depreciation keys will only be reflected in the new set of tables; these have a status of “Active”.  Of course, there is a third Depreciation Key status, “Inactive”, which means that it is not in use.
    There doesn’t seem to be any documentation on the mapping between these tables.  I need this in order to update our custom reports.
    Can anyone help?
    (T090 T090NA T090C T090NAT T090T T090NAZ T090P T090ND T090NP T090NR T090NSG T090NS T090NDT T090NPT T090NRT T090NSK T090NST)

    Dear Yogesh,
    Please go through Upgrade info @ service.sap.com.
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Major difference is ECC6 is netwear product having WASJAVA+ABAP
    secondly support unicode apart from this we have other diff. you can get fom master guide from service.sap.com/instguides
    For installing ECC 6.0 you required a solution manager key.With out solutionmanager key you cannot install ECC6.0.
    For ECC 6.0 is called netweaver component here you have ABAP+JAVA stack.
    ECC6.0 supports UNCODE.
    For installing 4.6 you don't required solution manager key.It only having ABAP stack.
    4.6C supports NONUNICODE.
    Hope this would add some more info.
    Regards,
    Naveen.

  • How to migrate the Objects from 3.1c to BI7

    Hi,
    We are in Functional Upgradation.
    How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
    Please help me to doing this....
    regards,
    anil

    BW Upgrade tasks (BW 3.1C to BI 7.0)
    Prepare Phase:
    Task     How-To     Who
    Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
    Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
         Basis/BW
    Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
         BI 7.0 Upgrade notes
         SAP Web Application Server 6.40 upgrade notes
         OS and DB specific upgrade notes
         SAP BW Add-on upgrade notes
    (e.g. SAP SEM, ST-PI, etc)
         Plug-In upgrade SAP notes
         Other notes identified in above notes and/or upgrade guides.
         Basis/BW
    Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
         First check the most current information from the SAP BW homepage http://Service.sap.com/BW  -> <SAP BW release> -> Availability
         Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
         Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
         Basis
    Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
         SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
         WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
         Basis
    Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
         SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
         Source system Plug-In requirements     Basis
    Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
         ETL Tools (example:  Ascential, DataStage, etc)
         Scheduling tools (example. Control-M, Maestro, etc)
         Monitoring tools (example: HP OpenView, Patrol, etc)
         Other OS or DB related tools     Basis
    Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
    The IGS chart migration will also be required after the SAP BW web report conversion.
         If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
         If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0.  (ArcView 8.2?).
         If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
    Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides  -> SAP NetWeaver).
         Basis
    Test and distribute new SAP BW Frontend
              Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
         A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
         After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
         Basis
    Alpha Conversion:
    Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
    Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
    Transaction RSMDCNVEXIT
    Check the system status:
         u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
         u201CNo Check yet/Inconsistent Internal Vales existu201D:
    The Alpha converter check has not been executed.
         u201CCharacteristics have Inconsistent Internal Valuesu201D:
    The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
         BW
    Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
    Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
         Basis/BW
    Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
         Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
         Basis
    Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
    SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
         This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
    Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
         Basis/BW
    Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
         In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
    For SAP BW developments not already collected in the transport collector, a decision must be made:
    Deploy the developments or wait until the upgrade has completed to deploy.
    o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
    o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
         In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
         BW
    Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
         Basis/BW
    Pre-upgrade Process:
    Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
         There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
         It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
         BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
    For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
         You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
         Basis
    Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
    Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
         Transaction DB02:
    o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
    o     Check missing database objects (indices, tables, etc)
    o     Missing indices may identify erred data loads or process problems
    Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
    Note: check for running data loads before executing a repair!
    o     Check DDIC/DB consistency
         Verify database objects and consistency
    (e.g. SAPDBA check for offline data files)
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         BW
    Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
    Note: this test should be repeatable so you can re-validate after the upgrade!
         Ensure that any inconsistencies are identified and corrected
         RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
         Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
         BW
    Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
    Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
         Check DB statistics for missing Indexes for InfoCubes and Aggregates
    o     User transaction RSRV to check      BW
    Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
         Ensure the Support Package queue is empty
         Confirm all applied Support Packages     Basis
    Check all u2018Repairsu2019     Check for unreleased repair transports
         Release all unreleased transports
    In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
         Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
         BW
    Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
    All InfoObjects should be active or saved (not activate):
    o     Check all inactive InfoObjects:
    Transaction RSD1 (Edit InfoObjects),
    click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
    Modified InfoObjects are denoted by yellow triangles!
    o     Determine if revision should be activated or removed.
         'Reorgu2019 or u2018Repairu2019 all InfoObjects
    This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
         Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
         BW
    All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
    All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
    o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
         BW
    All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
    o     All update rules and transfer rules should be active or deleted.
    o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
    All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
    o     All InfoCubes should be activated or deleted.
    o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
         BW
    All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
    o     For Original release SAP BW 3.x:
    A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
    Please see SAP note 484519 for details.
         BW
    Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
         Database admin
    Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
    o     Repeat PREPARE until all checks are successful.     Basis
    Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
    o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
    o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
    o     Incorrect data classes could create activation errors during the upgrade.
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         Basis/BW
    Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
    Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
         Database Admin
    Before Execution:
    All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
    The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
         Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
    - timing depends on the type of upgrade selected
         Basis/Admin
    Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
    - timing depends on the type of upgrade selected
         BW
    Check system parameters     Check OS, DB, and Instance profile parameters.
         Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
         Check for any DB specific parameters for BI 7.0
         Check for any new OS parameters     Basis
    Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
         Database Admin
    After Execution:
    Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
         BW
    Check the system logs     Perform a technical systems check.
         Example: Check system and all dispatcher logs (inc. ICM logs)
         Basis
    Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
         Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
         Basis
    Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
    o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Apply latest patches          Apply the latest SPAM patch
         Apply any required support packages that were not bound into the upgrade.
         Basis
    Apply additional BI 7.0 Support Packages
    (if required)          SAP recommends that customer remain current on SAP Support Packages.
         Review SAP Notes for all SAP BW Support packages applied in previous task.
    o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
         Review and implement SAP note 569128 as required     Basis
    Configuring Information Broadcasting EP/KMC Connections
         If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
         Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
         Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
         For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
         Basis
    Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
         Repeat tests that we executed prior to the upgrade.
         Validate results      BW
    Check InfoCube views for consistency     Check consistency of InfoCube fact table views
         It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
         BW
    Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
         The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
         It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
    o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
         Check that all other Source Systems are active.
    o     Activate as required.     Basis/BW
    Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
    Validate that personalization has been activated in your SAP BW system.
    Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
         Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
    Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
         To activate highlighted Personalization, click Execute.     BW
    For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
         Re-create all indexes in the ODS Object definition screen in transaction RSA1.
         ODS indexes must conform to the new naming convention
         BW
    Converting IGS chart settings
         Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
         Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
    o      Test via transaction RSRT
         Execute the conversion process as directed the BI 7.0 upgrade guide.
         Note: This step is required for all BI 7.0 upgrades     Basis
    Backup your SAP BW system     Perform a full database backup (including the File system)
    Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
         Database Admin

  • 4.6B Migration+Upgrade - ECC6 Discussion

    We will be upgrading from 4.6b on a Windows/SQLServer platform to ECC6.0 on a Unix/DB2 platform.  The first step in this process is a migration to the new OS and RDBMS.
    I would like to discuss the potential pitfalls of the migration to Unix and DB2 here.  Perhaps you've been through this process and can give me some input on what to watch out for?  I already know of a number of things that will break due to EXEC SQL use.
    Thanks for any input.

    Dear Crew,
    It is not the direct answer of your question but while upgrading you might need them.
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences pls refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
    and also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps you.
    Do award points if you found them useful.
    Regards,
    Rakesh

Maybe you are looking for