Transport between versions

Will a SSM transport from 7.0 load to 7.5?
Thanks
Cliff

Cliff,
Yes, you can transport 7.0 files to 7.5. There is an upgrade guide on the Service Marketplace you can follow for moving from SSM 7.0 to SSM 7.5
http://service.sap.com/instguidesCPM-STM > Strategy Management 7.5
Regards,
Bob

Similar Messages

  • Transports between 2 different versions of SAP

    We are developing a product on ECC 6.0 (IDES) system and I'm trying to figure out how we can delivery the product to our customers.  We have our own development namespace in SAP.  Some of our customers are on ECC 6.0 and some are still on 4.7.  Can we send a transport that was created in ECC 6.0 to a 4.7 system?
    Thank you,

    Hi,
    It is possible to transport between 2 different versions but it is dangerous : you have to know exactly what you are transporting and the dependencies with standard SAP code.
    So, it is much safer to recreate your source code in a developement system of the new version and create new transport orders from there...
    Regards,
    Olivier

  • What is the difference between version 4.7 EE and ECC 6.0 in SD module.

    Hi SAP Gurus,
    what are the features in 4.7 EE version in general.
    what are the features in ECC 6.0  version in general.
    then give me the exact difference between version 4.7 EE and ECC 6.0 in SD module.
    if u give the information, then u will get the rewards.
    Regards,
    somu.

    Hi Somu,
             These are additional enhancements avialble in ECC6.0 other than that remaining same as 4.7E
    1.E-Commerce:- SAP ERP provides powerful e-commerce capabilities that can be expanded in an easy, cost-effective manner in line with business growth. Organizations can run a complete sales process on the Internet, and provide business-to-business (B2B) and business-to-consumer (B2C) customers with personalized and interactive online self-services.
    2.Mobile Sales for Handhelds:-SAP ERP enables sales professionals to access front- and back-office business processes and to manage critical sales activities in the field using standard PDAs or other handheld devices (including those with bar code scanners). In this area, SAP ERP provides the following functions:- Customer managementWith SAP ERP, sales professionals may enter, view, and modify detailed customer information, and view sales order history for each customer.- Sales order managementSAP ERP enables sales staff to take sales orders via bar code scanners; search, create, and modify sales orders; and list or sort sales order partners.- Material managementSupport for material management for mobile sales enables staff to view material lists or details for a specific material, search material, and display customer-specific prices.
    3.Resource-Related Down Payments and Billing:-- Supports creation of down-payment requests analogous to the functions offered by resource-related billing- Enables organizations to bill the requesting company code for services provided via a resource-related billing document.
    4.SAP Beverage Functions Available for the Consumer Products Industry:- As of SAP ERP Central Component (SAP ECC) 5.00, the following functions from the SAP beverage industry solution are available for the consumer products industry:* SAP ECC 5.00, consumer products (EA-CP 500)- Material sorting- Extra charge- Empties management- Part load lift orders- Pendulum list indirect sales- Sales returns- Excise duty* SAP ECC 5.00, supply chain management extension (EA-SCM 500)- Direct store delivery back-end- Master data- Visit control- Transportation planning (including loading units, aggregation categories)- Vehicle space optimization- Output control (including valuated delivery note)- Route accounting (including tour data entry, cash payer, route settlement)* SAP ECC 5.00, industry-specific sales enhancements (EA-ISSE 500)- Extended rebate processing.
    5.Credit Management:-Integrating sales and distribution (SD) credit management with SAP Credit Management application:With SAP ERP 6.0 application, you can also use SAP Credit Management in SAP Financial Supply Chain Management set of applications (FIN-FSCM-CR) to perform all credit checks and commitment updates for all areas of sales (SD-BF-CM). In SAP Credit Management, you can update the data from multiple systems. This enables you to execute credit checks with consistent data in distributed systems, too. Furthermore, you can connect to external credit information providers by extensible markup language (XML) interfaces. Alternatively, you can continue to use SD Credit Management (SD-BF-CM).
    6.E-Commerce: Catalog Management :-As of SAP ERP 6.0 application, you must carry out product catalog replication from your ERP solution to the Text Retrieval and Information Extraction (TREX) server for use in the Web shop, using the report ISA_CATALOG_REPLICATION.
    7.E-Commerce: Quotation and Order Management:- Order creation with reference to a contract that has been displayed* Lock of sales documents to avoid concurrent access during the order change process* Display of bills of material in the shopping basket* Free goods processing* Processing of grid products for the SAP Apparel and Footwear application* One-step business order processing* Selection of multiple transaction types in the shopping basket* Credit card support in business-to-business (B2B) Web shop* Material number format conversion* Maintenance of delivery priority in the shopping basket (B2B)* Document search for all documents across all sales areas* Interprocess communication-characteristic value display in basket and order confirmation
    8.E-Commerce: Selling Over eBay:-Creation and management of product listings on eBay leverages the e-commerce order management and fulfillment capabilities of the SAP ERP application by easily tying existing tax, pricing, shipping, and payment configurations to post-auction processing. Enhancements in 2005: * You can use the business-to-consumer (B2C) checkout instead of the eBay checkout. With the B2C checkout, you can maximize cross-selling and up-selling opportunities by leveraging B2C functionality, determine tax and shipping using the elaborate methodologies available through condition techniques in SAP ERP 6.0. * E-mail notification scenario: winner notification to keep the auction winner updated with the status of the auction and of his or her order * Monitoring through features such as single-activity trace (SAT), heartbeat, and logging * Creation and publishing of multiple-item auctions and manual retraction of winners
    9.E-Commerce: User Management:-- Web-based user management for business-to-business internet users - Assignment of authorization roles to users in web-based user management - Automatic migration of SU05 to SU01 internet users
    10.Enterprise Services in Sales Order Management:-Please check in the Enterprise Services Workplace site which enterprise services are available for sales order management on the SAP Developer Network site (www.sdn.sap.com).
    11.Internet Pricing and Configurator (IPC):-The IPC is enhanced and integrated to allow configuration within the sales documents of the SAP ERP application reusing existing model data while leveraging its improved functionality and advanced user interface within SAP ERP.
    12.Price Catalog (PRICAT): – Inbound Processing (Retail):-Inbound message processing of PRICAT essages:As of SAP ERP Central Component enterprise extension retail 6.0 (EA-RET 600) component, you can create and change article data automatically, or in an interface for mass data handling. The system takes both single and generic articles and bills of material and prices into account.
    13.Rebate Condition Records Using Scales:-As of SAP ERP 6.0 application, you can set up rebate agreements so that the scale base value and the rebate scale level is derived from the total sales volume of multiple condition records. You do this by grouping condition records in the rebate agreement.
    14.SAP Role: – Internal Sales Representative:-SAP role – internal sales representativeThis role delivers all the functions to fulfill the requirements of an internal sales representative. This includes tasks such as answering phone calls from customers and prospective customers, processing incoming inquiries and sales orders, and preparing quotations and sales contracts.Target groupThe responsibilities of an internal sales representative (or customer service representative) include the following:- Answering phone calls from customers and prospective customers- Answering product, price, and order status related questions- Processing incoming inquiries and sales orders- Preparing quotations and sales contracts- Taking sales orders and ensuring successful order processing – for example, taking care of the completeness of sales documents, releasing delivery-blocked orders, and so on - Support for the outside sales force – for example, checking on quotations, updating customer master data, and so on- Preparing reports and sales analyses for the sales manager and the sales teamWork overview This work center gives you an overview of your daily work and gives you easy access to your most important tasks. Sales documents This work center allows you to work on all your sales documents. You can create and maintain inquiries, quotations, sales orders, sales contracts, scheduling agreements, and billing documents. Order fulfillment This work center allows you to monitor order fulfillment. You can display deliveries, backorders, and shipments, and can check product availability.Master data This work center enables you to work on all your master data. You can create and maintain business partners, customer agreements, prices and conditions, and products.
    I hope it will help you
    Regards,
    Murali.

  • Transport between different releases

    Hi,
    Is it possible to have transports between two server with different releases,
    one is on 701 and other is on 700,
    pls advise.
    Thanks

    Hello Irfan,
    Transport of customizing between diffeent releases is NOT supported. Also generated objects, which were generated by customizing, should NOT be transported between different releases.
    SAP objects may NOT be transported between different releases (e.g. a table in an old release could have less fields than in the newer release and thus such a transport might delete data or if an abap calls a function module and in new release have one parameter more,then you get syntax errors if you transport only one of them from a system with the old release, ...).
    So data loss and severe inconsistencies can happen if you transport SAP objects between different releases, or between systems with same release but different support package level or between systems with different addons or different add-on versions etc.
    For pure customer objects (e.g. Z-tables, Z-programs, Y-tables, y-programs or objects in customer name space) it might be ok to transport them. But if e.g. your Z-table uses an SAP data element which has maybe been changed in the new release or does maybe no more exist, you can also get problems during transport of your z-table.
    Data loss and severe inconsistencies can happen if you transport SAP objects between  different releases, or between systems with same release but different support package level or between systems with different addons or different add-on versions etc.
    Please check the following:
    1090842   Composite note: Transport across several releases
    1089083   Transports between Basis Releases 7.0* and 7.1*
    556734    FAQ Transport: Setup and further information
    Pay attention to point 5 and 6.
    5. Are transports possible between systems with different Support Package versions?
    6. Are transports possible between different R/3 releases?
    Best Regards
    Niraj

  • Difference between version

    Hello
    I would like know difference between version 4.6 & 4.7 and when do the version was released,

    Hi,
    SAP 4.7 has all the features such as development workbench, transport management system, monitoring, versioning and business object repository of already existing SAP 4.6C.
    Web Application Server6.20 of 4.7 includes all the features of SAP Basis of SAP 4.6C.
    Differences:
    SAP 4.7 has a more structured approach as compared to SAP 4.6C from a technical perspective. It is based on mySAP.com technology, which is actually the Web Application Server 6.2C. This not only includes SAP Basis Technologies with their latest advancements but also the new features of SAP Web AS 6.20.
    SAP 4.7 is more structured even from a functional perspective as this version has been developed after functional and infrastructure developments of earlier SAP R/3 4.6C.
    In SAP 4.7 the functional and infrastructure developments are made on separate levels. The functional developments are made in the Enterprise Extensions and infrastructure developments are made in the Enterprise Core unlike SAP 4.6C in which both the developments take place within the systems.
    SAP in its Web AS has additional enhancements in the form of package concept, global parameterization with business configuration sets, Unicode compliance and accessibility that are not present in 4.6C.
    SAP 4.7 Core supports the above-mentioned enhancements that SAP 4.6C does not.
    SAP 4.7 unlike 4.6C has Enterprise Extensions that can be separately deployed and have their own releases.
    Chek these out
    Here is the link for the same
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
    http://service.sap.com/releasenotes
    Regards,
    Vinod

  • Transports, M version of query element missing in Dev

    Hello
    We're trying to import transports to a system copy of our Development system but when trying to do so we get an error in RS_AFTER_IMPORT saying "Element XYZ is missing in version M". (The transports comes form Dev). The element is a Text-variable
    When checking in table RSZELTDIR in Dev-Copy I do only see A and D versions of the element XYZ. The same is true in Dev. But in QUA and PROD the element exists in A, D and M versions.
    Is this normal? And how do we do if the transport strategy is to Transport between Dev and Dev-Copy?
    Thanks in advance
    / Daniel

    Thank you for your answer.
    However the same transport has entered QA and PROD correctly, it's only when transporting into Dev-Copy that it fails.
    Scenario :
    Day 1 : a system copy was taken
    Day 2-10 : transports leaving Dev going to QA and PROD
    Day 11 : Dev-Copy created from the system copy from Day 1
    Day 12: The transports from Day 2-10 is being imported into Dev-Copy (and Query transports failing)
    So the developers have collected needed objects in the first place, but something is happening when importing into Dev-Copy..... the M versions is missing in Dev-Copy (and Dev) compared to QA and PROD
    / Daniel

  • From ABAP view, what is the difference between version 4.7 and ECC 6.0 ?

    Hi,
    I am a ABAP developer. I want to know the difference between version 4.7 and ECC 6.0 from a programmer
    perspective.
    I also want to know  what is obsoleted and what is enhanced.
    Thanks.
    Best Regards,
    Chris Gu

    I'm not sure if any of this is in your 4.7 version, but I know it wasn't available in our 4.6C before we upgraded and we have found the following extremely helpful in ECC 6.0:
    1.  The new ABAP Debugger - Search SDN and you'll probably find a bunch of info on these enhancements
    2.  The Enhancement Framework - this is a great new framework allowing enhancements to standard SAP programs without having to use "core Mods".  Had we known about it prior to our upgrade, we could have probably eliminated 75% or so of our custom Z Programs which are copies of standard SAP code  and 100% of our core mods (of which we only have a handful)
    3. Code Inspector and more importantly the ability to turn it on to automatically run when releasing a transport.
    4. The ABAP workbench has changed a bit with a new editor including some minimal code completion.
    5.  Automatic generation of services from any remote enabled function module.
    These are just a few of the things that I've found helpful in an upgraded environment.

  • Transport protocol version error in Integration Directory API

    Hi All,
    I am trying to create SOAP receiver communication channel using Java-only PI 7.31 directory APIs. I have passed all the required parameters to the CommunicationChannelIn service, but it's throwing error - "Enter at least one object key for operation 'create'".
    When I tried to test the service through WS Navigator, it's giving exception - "Enter a value for attribute 'Transport Protocol Version'" which doesn't exists in case of SOAP adapter creation.
    Has anybody come across this issue? If the adapter metadata does not specify any transport protocol version, then shouldn’t the validation checks in  CommunicationChannelIn service provider proceed without errors on a blank value for this attribute?
    Note: I have gone through all the SCN blogs, discussion threads we have on topics related to Integration Directory API.
    Thanks in advance for all the help and suggestions.
    Regards,
    Yashu Vyas

    Hi All,
    I am trying to create SOAP receiver communication channel using Java-only PI 7.31 directory APIs. I have passed all the required parameters to the CommunicationChannelIn service, but it's throwing error - "Enter at least one object key for operation 'create'".
    When I tried to test the service through WS Navigator, it's giving exception - "Enter a value for attribute 'Transport Protocol Version'" which doesn't exists in case of SOAP adapter creation.
    Has anybody come across this issue? If the adapter metadata does not specify any transport protocol version, then shouldn’t the validation checks in  CommunicationChannelIn service provider proceed without errors on a blank value for this attribute?
    Note: I have gone through all the SCN blogs, discussion threads we have on topics related to Integration Directory API.
    Thanks in advance for all the help and suggestions.
    Regards,
    Yashu Vyas

  • What are the differences between version 9 and X of the Reader?

    I have been running various releases of Version 9 of the Adobe Reader for a long time. I have noticed that when there is an update available for Version 9 and I click on the "more information" button on the update, it takes me to a web page where there is information on the latest levels of both Version 9 and Version X, but I cannot find any information on what the differences are between version 9 and X. I read the FAQ and found nothing on this, and I even searched this forum and was surprised that there were no topics on this question already.
    Can someone tell me the differences between the 2 versions. I am running Windows 7; is that important as to which version of Reader I should use?

    http://www.adobe.com/products/reader.html
    http://blogs.adobe.com/asset/2010/07/introducing-adobe-reader-protected-mode.html
    Both Adobe Reader 9 and Adobe Reader X work on Windows 7 .
    Hope this helps.

  • I have an old version of itunes installed in my iPod.I had a syncronize mistake and I tried to change iTunes to 10.4.1. Now iTunes doesn't recognizes my ipod because of the difference between versions. What can I do?

    I have an old version of itunes installed in my iPod.I had a syncronize mistake and I tried to change iTunes to 10.4.1. Now iTunes doesn't recognizes my ipod because of the difference between versions. What can I do?

    I reinstalled the current version of iTunes, 8.2.1.
    Current version?? Did this post appear out of a time warp?  The current version is 10.7!
    http://www.apple.com/itunes/download/

  • Documentation on differences between Version ECC 6 and Old version

    We are looking for information/documentation on differences between Version ECC 6 and Old version for HCM. Appreciate for your great help.
    Best Regards,
    Eric

    Hai..
    Re: differnce b/n 4.7 and  ecc 6.0
    Re: Difference Between SAP Version ECC 4.6, 4.7, SAP 5.0, 6.0 with SA
    https://websmp210.sap-ag.de/releasenotesRelease Notes
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://service.sap.com/instguides
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://solutionbrowser.erp.sap.fmpmedia.com/

  • DataGUard between versions

    Hi,
    What are the limitations on oracle dataguard between versions?
    I assume you can't do oracle dg from 10g to 11g but where is it written officially?
    Thanks

    I assume you can't do oracle dg from 10g to 11g but where is it written officially?its not working .
    Check
    10g Primary database work with a 11g Standby database

  • Difference between versions

    hi ,
    I want to know the difference between versions of 5.0 and ECC 6.0 .any information is rewarded.

    Hi,
    Please check these information from other thread.
    ECC 5.0 is based on WAS 6.40 and ECC 6.0 is based on WAS 7.00.
    From functional point of view there are some minor differences, as the core functionalities are not changed a lot. However there is Industrial Solutions intergarated to ECC 6.0 by default.
    From ABAP point of view you have the following new elements/components:
    - New ABAP editor /meanwhile it's available via downport for lower releases as well/
    - ABAP WebDynpro
    - Enhancement framework
    - Regular experssion support
    Also check this link for functionality differences.
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Regards,
    Ferry Lianto

  • Firefox 4. Could not find compatible GRE between version 2.0 and 2.0.

    When run firefox it output to stdout "Could not find compatible GRE between version 2.0 and 2.0." and exit. What is this? I use xulrunner-system-cairo 1.9.2.15-1.
    Last edited by veg (2011-03-24 17:56:41)

    @veg just get rid of xulrunner-system-cairo and install xulrunner. Now our xulrunner is compiled with system cairo support

  • Transports between systems after support package application

    Hi gurus, we need to apply a lot of support packages into the development system and I wanna know if in the meantime we need to "freeze" all transports between systems.
    This because the systems (DEV - QA - PRD) are in differente support package level. This until we apply the support packages into the others systems
    Thanks in advance.
    Ronald.

    Yes, any transport which is taking SAP standard code from DEV to QA to PRD should not move if the systems in landscape are on different support pack level. Because it can happen that SAP has done some modification to that standard code in new support pack.
    However, anything which is isolated Z-development (like some z-output report or smartforms) can proceed.
    But, I suggest , stop moving transports until all systems have same support pack level.
    G@urav.

Maybe you are looking for