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

Similar Messages

  • Steps in after migration of fixed assets in SAP R/3 System

    Hi Guru's,
    I migrated all fixed assets from legacy system to SAP R/3 system. Dev,Quality and Mock Production Server.
    Could anybody guide me what is the next process in Fixed Assets?
    That would be greate help from our Guru's
    Regards
    Odaiah Pelley

    Report S_ALR_87011964 will be able to give you a report by Asset Class.
    In terms of the data you have migrated, I am guessing in your current system there is a way to get the same data and therefore you should compare.
    Another check is the total posting you have made to the GL Data Migration account is the same as the total balance in your current system.
    FS10 will give you this.
    Lastly you can also use FS10 for the asset recon accounts if they are grouped in a similar way in your current system.
    The business lead should be able to help you with the data they have and how they could reconcile their data.

  • 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

  • Can we migrate SAP 40B release system from windows NT to windows 2003.

    Hi,
    We want to know can we migrate SAP 40B release system from windows NT to windows 2003 server; if yes, please share with us the OS migration document.
    Regards,
    R Mav

    > Our SAP 4 O B is on windows NT and oracle version is 8.0.5 and wants to do OS migration from NT to win. 2003.
    Neither Oracle 8.0 nor 8i were releases on Windows 2003, they won't work and are not released.
    So I'm afraid the only way you can go is Windows 2000.
    Markus

  • How to extract Inventory data from SAP R/3  system

    Hi friends How to extract Inventory data from SAP R/3  system? What are report we may expect from the Inventory?

    Hi,
    Inventory management
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20handle%20inventory%20management%20scenarios.pdf
    How to Handle Inventory Management Scenarios in BW (NW2004)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Loading of Cube
    •• ref.to page 18 in "Upgrade and Migration Aspects for BI in SAP NetWeaver 2004s" paper
    http://www.sapfinug.fi/downloads/2007/bi02/BI_upgrade_migration.pdf
    Non-Cumulative Values / Stock Handling
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
    Non-Cumulatives
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
    Here you will find all the Inventory Management BI Contents:
    http://help.sap.com/saphelp_nw70/helpdata/en/fb/64073c52619459e10000000a114084/frameset.htm
    2LIS_03_BX- Initial Stock/Material stock
    2LIS_03_BF - Material movements
    2LIS_03_UM - Revaluations/Find the price of the stock
    The first DataSource (2LIS_03_BX) is used to extract an opening stock balance on a
    detailed level (material, plant, storage location and so on). At this moment, the opening
    stock is the operative stock in the source system. "At this moment" is the point in time at
    which the statistical setup ran for DataSource 2LIS_03_BX. (This is because no
    documents are to be posted during this run and so the stock does not change during this
    run, as we will see below). It is not possible to choose a key date freely.
    The second DataSource (2LIS_03_BF) is used to extract the material movements into
    the BW system. This DataSource provides the data as material documents (MCMSEG
    structure).
    The third of the above DataSources (2LIS_03_UM) contains data from valuated
    revaluations in Financial Accounting (document BSEG). This data is required to update
    valuated stock changes for the calculated stock balance in the BW. This information is
    not required in many situations as it is often only the quantities that are of importance.
    This DataSource only describes financial accounting processes, not logistical ones. In
    other words, only the stock value is changed here, no changes are made to the
    quantities. Everything that is subsequently mentioned here about the upload sequence
    and compression regarding DataSource 2LIS_03_BF also applies to this DataSource.
    This means a detailed description is not required for the revaluation DataSource.
    http://help.sap.com/saphelp_bw32/helpdata/en/05/c69480c357354a8846cc61f7b6e085/content.htm
    http://help.sap.com/saphelp_bw33/helpdata/en/ed/16c29a27db6e4d81a015be8673eb80/content.htm
    These are the standard data sources used for Inventory extraction.
    Hope this helps.
    Thanks,
    JituK

  • SAP R/3 System analysis

    Hello!
    Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
    The following functions should be included in this program:
    - detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
    - comparison against a SAP ERP 6.0 reference system
    - extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
    - syntax analysis of program code with respect of adjustement need
    - quality control of own development
    - control of amount of transports within different company areas
    - control of user information, such a user type, logon date, etc.
    - basic control, whether a sufficient authorization concept is available
    - Identification of objects that should be considered for the archiving in oder to decrease the db-size
    My question are:
    <b>- which tasks can be convered with SAP standard transactions what are the names of the transactions?
    - which effort do I investigate for these tasks?</b>
    Thank you very much!
    regards

    Dear Thom,
    To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
    http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
    http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
    Need to consider the following things:
    For Reports…it’s custom developed program …so unless there is any kind of change in requirement from the client regarding the layout…nothing needs to be changed…I think it will work fine in ECC 6.0 to…except few things may needs to be changed..so you need to discuss whether they want the reorts as it is right now…or want to change the layout (adding some new info/fields etc) of any report…so u need to modify the program for those…and estimate accordingly…for a medium complexity’s Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)…so to modify it will be less than that (depending upon the scope of changes)
    Now say for Batch Inputs(interface/Data Migration) using BDC…you need to see how many BDCs are there…again if the field lengths and layouts are not changing…then no need to change anything (except the main thing…..you need to change the obsolete function modules…there are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0…there are some new with enhanced functionality so you need to modify the BDCs…and many cases it happens that the whole transaction screen changes for process…in that case better to develop new BDCs…so you have to consider those parameter…look into and estimate accordingly…modifying a BDC should not take more than 1 PD…
    Now say for Forms…there was no Smart form in 4.6C…form printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart form…in that case…it’s complete new dev…so estimate accordingly…a medium complexity’s form should take 8 PD (FRSTDSCoding+Unit Testing)…you can take it as 10 PD too…even if client wants to keep it is as it was in older version…you have to redevelop the layout in ECC 6.0 again…as form printer is even client dependent…maximum you can copy the program associated with that form in the new version too…and your effort will be saved…again you have to consider if clients wants to change the layout too…
    Now for enhancement…so in that case u need to see individual cases…for a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)…
    One more important thing is that the Unicode Compatibility…this needs to be done….needs to change the code (variable name) accordingly….also Version management tool is used for the standard programs…
    Also pls find the following forums:
    Re: Data Migration from 4.6C to ECC 6.0
    List of transations supported in SAP 4.6c and not in ECC6.0
    Re: Upgradation from 4.6C to ECC  6.0
    Re: what's the advantage to upgrade 4.6c to ECC5.0...
    RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
    Upgrade batch inputs from 4.6C to mySAP ERP 2005
    /thread/317225 [original link is broken]
    Upgrade from SAP R/3 to ECC 6.0
    Hope it will help you.
    Thanks,
    Atin
    <b><b>Reward points if it helps.</b></b>

  • SAP R/3 System analysis before upgrade 4.6C -- SAP ECC 6.0

    Hello!
    Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
    The following functions should be included in this program:
    - detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
    - comparison against a SAP ERP 6.0 reference system
    - extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
    - syntax analysis of program code with respect of adjustement need
    - quality control of own development
    - control of amount of transports within different company areas
    - control of user information, such a user type, logon date, etc.
    - basic control, whether a sufficient authorization concept is available
    - Identification of objects that should be considered for the archiving in oder to decrease the db-size
    My question are:
    - which tasks can be convered with SAP standard transactions what are the names of the transactions?
    - which effort do I investigate for these tasks?
    Thank you very much!
    regards

    Dear Thom,
    To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
    http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
    http://service.sap.com/releasenotes and  http://service.sap.com/upgrade  for functional changes.
    Need to consider the following things:
    For Reports…it’s custom developed program …so unless there is any kind of change in requirement from the client regarding the layout…nothing needs to be changed…I think it will work fine in ECC 6.0 to…except few things may needs to be changed..so you need to discuss whether they want the reorts as it is right now…or want to change the layout (adding some new info/fields etc) of any report…so u need to modify the program for those…and estimate accordingly…for a medium complexity’s Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)…so to modify it will be less than that (depending upon the scope of changes)
    Now say for Batch Inputs(interface/Data Migration) using BDC…you need to see how many BDCs are there…again if the field lengths and layouts are not changing…then no need to change anything (except the main thing…..you need to change the obsolete function modules…there are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0…there are some new with enhanced functionality so you need to modify the BDCs…and many cases it happens that the whole transaction screen changes for process…in that case better to develop new BDCs…so you have to consider those parameter…look into and estimate accordingly…modifying a BDC should not take more than 1 PD…
    Now say for Forms…there was no Smart form in 4.6C…form printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart form…in that case…it’s complete new dev…so estimate accordingly…a medium complexity’s form should take 8 PD (FRSTDSCoding+Unit Testing)…you can take it as 10 PD too…even if client wants to keep it is as it was in older version…you have to redevelop the layout in ECC 6.0 again…as form printer is even client dependent…maximum you can copy the program associated with that form in the new version too…and your effort will be saved…again you have to consider if clients wants to change the layout too…
    Now for enhancement…so in that case u need to see individual cases…for a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)…
    One more important thing is that the Unicode Compatibility…this needs to be done….needs to change the code (variable name) accordingly….also Version management tool is used for the standard programs…
    Also pls find the following forums:
    Re: Data Migration from 4.6C to ECC 6.0
    List of transations supported in SAP 4.6c and not in ECC6.0
    Re: Upgradation from 4.6C to ECC  6.0
    Re: what's the advantage to upgrade 4.6c to ECC5.0...
    RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
    Upgrade batch inputs from 4.6C to mySAP ERP 2005
    /thread/317225 [original link is broken]
    Upgrade from SAP R/3 to ECC 6.0
    Hope it will help you.
    Thanks,
    Atin
    <b><b>Reward points if it helps.</b></b>

  • 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

  • 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 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

  • How to migrate a SAP Oracle 9i to Oracle 10g (on a new machine) ?

    Hello,
    Do you know the proper procedure of such a migration : Migrate a SAP Oracle 9i to a new machine : HP-UNIX, Oracle 10g.
    My understanding :
    (1) Setup the new machine
    (2) Install the latest version of HP-UX
    (3) Install Oracle 10g database program
    (4) Use Oracle Export / Import to copy my existing SAP Oracle 9i to this newly installed Oracle 10g machine.
    (5) copy or tar all the SAP related files, eg.BRTOOLS, ABAP reports, to the new machine
    (6) Modify all the configure files since the machine name is different.
    Is it correct ?
    Is it the most appropriate method ?
    Is Export / Import a proper way to migrate an Oracle to a new version ?
    Should I use Data Gurad instead ?
    Finally, for this migration issue, any SAP Note you will suggest ?

    There are two ways of doing this:
    a) You do a system copy using R3load
    This will give you a "free" reoganization because the tables will be loaded into the database as if you were doing a new installation. The disadvantage is, that it takes more time and good planning.
    b) you do a system copy using backup/restore together with the database upgrade
    This is a fast way to get your system upgraded and if something goes wrong you can still use the old system. Check
    Note 932722 - Upgrade to Oracle 10.2 during a database copy
    this is a note for Windows but you can adapt it to be used on Unix/HP-UX too.
    And just as a remark:
    The "free" support for Oracle 10g is ending next year in June (see Note 1339724 - Oracle 10.2 Extended Support free until July 31, 2011) - after that you have to buy additional support if you want to continue to run 10g. If you run now a migration/upgrade project, why not upgrade directly to 11g?
    Markus

  • Migration of SAP Netweaver

    I'm currently installing SAP Netweaver 7.0 in Windows Server 2008 R2. The database is MS SQL 2008 R2.
    I'm a bit confuse now because I'm not sure need to start a fresh installation or just doing a system copy will do. This is because I already have existing system with server 2003 and MSSQL 2005. I just need to do a system copy to export and import to the new server or I need to do a fresh installation in the new server where I need to install solution manager in order to get the key to proceed with the installation.

    > We would like to migrate a SAP NetWeaver system with ca. 90 interfaces from
    > data center 1 to data center 2.
    > The current OS is SUN and DB is DB2.
    > The destination/future OS is Windows with Oracle.
    > The questions:
    > 1) Which XI specific points (interfaces, messages, etc.) should be considered during the migration?
    You have to be aware that Solaris -> Windows implies an endian change (Solaris SPARC is BE whereas Windows is LE). The receiving systems must "know", that the data coming is of a different endianess - depending on which adapter you use.
    > 2) Which estimate (round about) does it take?
    Nobody can tell you that, it is influenced by hardware, storage power, preparation, parallel tasks etc. etc. etc.
    > 3) Where can I find the appropriate documentation?
    http://service.sap.com/osdbmigration
    Basically you will be doing a heterogenous system copy, roughly spoken "start sapinst, export ABAP and Java, start sapinst on target and import".
    Be aware that you need a SAP certified migration consultant on site to do the migration. If you do it on your own you will loose support in case of problems.
    Markus

  • Asian Language problem (###) after OS/DB Migration of SAP BW 3.5

    Hello,
        We have recently migrated our SAP BW 3.5 system form Windows to Linux OS and now we have some issue in the BEX. when we log in with Language EN in to bex and then run any report related  to Japan/China (Asian) then the reports is showing #### in place of Asian characters.
       It is fine if we log in to Web reporting we have no issues.
    Please provide me the solution asap I will give  you full points
    System: SAP BW 3.5
    OS/DB Migration : from windows 32 bit to Linux 64 bit
    Problem: In Bex asian character are shown as '###' when log in with Language "EN"

    Hello Murali,
           Thanks for your information....I got much idea and i will allot full points for you.
    But the solution which i for is as below
    Option 1 for GUI 710)
    step1 -> as you said changed the language in system Regional setting to Japanese
    step2 -> upgrade GUI to 710
    step3 -> Go to GUI Options and check ON the "With Wizards"
    step4 -> go to the GUI-> select the BW system on it -> click on change button
    step5 -> go to 'code page tab' and then uncheck "Unicode off" and select the language from default to Japanese
    Option 2 for GUI 640 or above)
    step1 -> as you said changed the language in system Regional setting to Japanese
    step2 ->Go to GUI (640) select the BW system on it -> click on change button or properties
    step3 -> click Advance button -> Uncheck 'Default code page' and select the language to 'JA' and then OK

  • Data migration for SAP E-Recruiting

    Hi all,
    We are looking for a standard way to migrate data from a nun sap system into SAP E- Recruiting.
    Is there any way for doing so?
    Thanks,
    Sharon

    There is no standard way available for data migration in SAP for E-recruiting.
    As it believes in the concept of creating new data and a new talent pool.
    Regards,
    Divya

Maybe you are looking for

  • Is there a way to exchange fields automatically?

    Hi, I have a load of reports which currently get their information via a sql query in the command file. The Fields in the report are then adressed under: command.fieldname. Due to some changes in the organisation it is necessary to change the source

  • Can a script be written to ignore/close certain file types?

    If I want to create an action the runs various scripts, can I write a script that tells photoshop to skip/close the file instead of the action stopping becasue it cannot continue? Basically I need to make a script that will ignore .bmp and .eps files

  • Widescreen on SD

    Hey Everyone... first time posting here in the iMovie area. I'm an animator and I got some footage of my work ripped from a DVD in wide screen format. How can I get my other SD (4:3) clips cut in with my wide screen clips for an SD presentation witho

  • Count total rows?

    Hello, In some function of my program, I need to count total number of rows but, I don't need to fetch results. Only the number of rows. Is there any way to count the total number of result rows without fetch? In OCI ver.7, it was very simple. Just C

  • Debugging Anonymous PL/SQL Block

    Does sql developer allow you to debug an anonymous PL/SQL block or is the debugging restricted to compiled procedures/functions? Am a TOAD user but am looking at SQL Developer. Thanks