Compatibility of RMCA 4.6 version in ECC 6.0

Hi All,
We are going for Technicle upgradition of our SAP systems from 4.6c to Ecc 6.0. Currently we are using RMCA with version 4.6c. Could you please let me know whether RMCA 4.6c will work in ECC 6.0? If not any notes to be applied?
Thanks in advance!
Regards,
Raj

Hi All,
Found solution.
Raj

Similar Messages

  • Compatible versions with ECC 6.0

    Hi,
    We are planning the upgrade of our SAP installations:
    - R3 4.6C, 4.7 --> ECC 6.0
    - BW 3.1, 3.5 --> BI 7.0 (NW2004s)
    - SRM 2.0 --> SRM 5.0
    - CRM 4.0 --> CRM 5.0
    Of course we can't do all the upgrades at the same time, so, in order to decide in which order we make the upgrades, we must be sure that the new versions will be compatible with the old ones.
    In the quicklink "service.sap.com/r3-plug-in", menu option "SAP R/3 plugin --> Integration of SAP R/3 / Enterprise, ERP and SAP Components" there are some tables where we can analyze the compatibility between all the BW, SRM and CRM versions and R3 versions prior to ECC 6.0 (4.6C, 4.7, ECC 5.0), according to the plug-in version. From 2005 there seems to be a strategy change in the integration interfaces:
    "SAP ECC 6.0 and subsequent releases will automatically contain all integration interfaces that so far have been contained in the SAP R/3 Plug-In and that ensured the technical integration with other SAP Components."
    As I understand, ECC 6.0 will automatically contain all the integration interfaces and there will be no more R/3 Plug-In versions. How can I check the compatibility between ECC 6.0 and the other BW, SRM and CRM versions? In the quicklink there are integration matrix available for R3 Enterprise and ECC 5.0 but there is no information for ECC 6.0. Are the versions compatible with ECC 5.0 too compatible with ECC 6.0? As ECC 6.0 seems to "automatically contain all integration interfaces that so far have been contained in the SAP R/3 Plug-In", does it mean that the integration matrix available for ECC 5.0 is too valid for ECC 6.0?
    We have found a specific note (931020 "SRM connection to an ERP 2005 (ECC 600) backend") for the integration between ECC 6.0 and SRM but we didn't find any note regarding BW or CRM.
    How can we check wich versions (BW, SRM, CRM) are compatible with ECC 6.0? Can we use the integration matrix available for ECC 5.0 in the quicklink "service.sap.com/r3-plug-in", are there specific notes like the one available form SRM (931020)?
    We need to be sure as soon as possible that after the upgrade of our R3 4.6C and 4.7 versions to ECC 6.0 they will be compatible with our actual BW (3.1, 3.5), SRM (2.0) and CRM (4.0) versions.
    Thanks in advance!!

    to followed unicode rules.
    ABAP Development under Unicode
    Prior to Unicode the length of a character was exactly one byte, allowing implicit typecasts or memory-layout oriented programming. With Unicode this situation has changed: One character is no longer one byte, so that additional specifications have to be added to define the unit of measure for implicit or explicit references to (the length of) characters.
    Character-like data in ABAP are always represented with the UTF-16 - standard (also used in Java or other development tools like Microsoft's Visual Basic); but this format is not related to the encoding of the underlying database. 
    A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
    In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or a NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
    If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
    As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
    Other Changes 
    1.     Bit Statements
    2.     Adding Field Sequences
    3.     Loops with VARY and VARYING
    4.     Creating Subroutines
    5.     Saving Programs
    6.     Assigning Types for GET/SET PARAMETER
    7.     Unreachable Statements
    8.     Function Modules with Incorrect Parameter Names
    1. Bit Statements
    Previously, the system checked for the bit statements SET BIT i OF f [TO g] and GET BIT i OF f [INTO g]whether the field f is character-type; X fields, X strings, and flat structures are usually regarded as character-type. For Unicode programs this is no longer useful, because the types X and XSTRING no longer count as character-type and the bit by bit access to character-type fields or structures is no longer platform-independent. Therefore, with these operations in Unicode programs, the field f must be type X or XSTRING.
    For the bit mask operations f O x, f Z x, and f M x you could previously use all number-type and hence all character-type types for the left operand f. In Unicode programs, the f operand must now be type X or XSTRING.
    2. Adding Field Sequences
    When adding field sequences, restrictions apply to the following statements in Unicode:
    ADD n1 THEN n2 UNTIL nz [ ACCORDING TO sel ] GIVING m ...
    ADD n1 THEN n2 UNTIL nz TO m [ RANGE str ].
    1.     The operands n1, n2, and nz must be type-compatible with one another.
    2.     The distance between nz and n1 must be an integral multiple of the distance between n2 and n1.
    3.     A syntax or runtime error occurs if the fields n1, n2, and nz are not in a structure. This structure must be recognizable statically or its valid area must be marked explicitly using the RANGE addition.
    4.     At runtime, the system ensures that the RANGE area is not left.
    ADD n1 FROM i1 GIVING m [ RANGE str ].
    1.     Field n1 must be within the structure. The structure must be explicitly defined using the RANGE addition if it is not recognizable statically.
    2.     For this variant, the system also checks at runtime whether n1 and the addressed values are within the structure.
    3. Loops
    Loops with the VARY or VARYING addition are also problematic in Unicode, since a type-a access to memory contents cannot be ensured and memory can be overwritten inadvertently.
    DO ... VARYING f FROM f1 NEXT f2.
    For this statement, the fields f, f1, and f2 must be type-compatible with each other. To prevent memory contents being overwritten, a RANGE for valid accesses is introduced implicitly or explicitly for the following statements:
    DO ... TIMES VARYING f FROM f1 NEXT f2 [ RANGE f3 ].
    WHILE ... VARY f FROM f1 NEXT f2       [ RANGE f3 ].
    A syntax or runtime error is caused if f1 or f2 are not included in f3. If the RANGE addition is missing, it is defined implicitly from FROM f1 NEXT f2 as follows:
    1.     If both f1 and f2 are statically recognizable components of the same structure, the valid RANGE area is defined from the smallest structure that comprises f1 and f2.
    2.     A syntax error is triggered if it is recognizable statically that f1 and f2 are not part of the same structure.
    3.     A valid area must be defined explicitly using the RANGE addition if the connection between f1 and f2 is not recognizable statically.
    If you specify a deep structure as the RANGE addition, the system checks for every loop pass that there are no field references, object references, tables, or strings in the area read.
    4. Creating Subroutines
    When automatically generating subroutines using the statement GENERATE SUBROUTINE POOL itab NAME name, the generated program inherits the content of the Unicode flag of the generating program.
    5. Saving Programs
    When automatically generating programs using the statement INSERT REPORT prog FROM itab, default values are set for the TRDIR entry as before. Amongst other things, this statement has the new addition UNICODE ENABLING uc, with which the Unicode flag of the inserted report receives the value of uc. If this addition is missing, the following applies:
    1.     A Unicode program creates a Unicode program.
    2.     A non-Unicode program in turn creates a non-Unicode program.
    3.     A non-Unicode program becomes a Unicode program if it is overwritten by a Unicode program.
    4.     A Unicode program remains a Unicode program if it is overwritten by a non-Unicode program.
    6. Assigning Types for GET/SET PARAMETER
    For the statements GET PARAMETER ID pid FIELD f and GET PARAMETER ID pid FIELD f, f must be character-type. You can use the EXPORT and IMPORT statements for storing non-character-type fields and structures.
    7. Unreachable Statements
    In Unicode programs, unreachable statements cause a syntax error. In non-Unicode programs, there was previously only a syntax warning.
    8. Function Modules with Incorrect Parameter Names
    In Unicode programs, calling a function module, whose parameter names are specified statically as a literal or constant, causes an exception that can be handled if an incorrect parameter name was specified. This only applies to function modules that are not called via Remote Function Call. In non-Unicode programs, an incorrect name was previously ignored.

  • Every time I start iTunes I get the message: "iTunes exec has been set to run in compatability mode for an older version of Windows. Turn off compatability mode for iTunes before you open it." How do I turn off the compatability mode?

    Every time I start iTunes I get the message: "iTunes exec has been set to run in compatability mode for an older version of Windows. Turn off compatability mode for iTunes before you open it." How do I turn off the compatability mode? Particularly when I have to do it before I turn on iTunes.

    Try the following document, only be sure that none of the boxes in the compatibility mode tab are checked (not just the compatibility mode box itself):
    iTunes for Windows: How to turn off Compatibility Mode

  • Is there any difference between R/3 4.7 version and ECC 5.0????

    Hi All,
      Is there any difference between R/3 4.7 version and ECC 5.0 for the transaction RSA5.
    Regards,
    Andy

    Andy
    Functionality wise I didn't see any difference other than new datasources in ECC5.0
    Thnaks
    Sat

  • Equivalent table for A920 & A928 in 3.1 i version to ECC 6.0

    Hi Friends,
    I am working in an upgrade project from 3.1 i to ECC 6.0
    I have a report to be migrated from old version to ECC 6.0
    I have 2 tables - A920 & A928 which are no longer available in ECC 6.0
    A920 is a condition table - Customer / Price list / Currency / Material
    A928 is price list currency table
    Please let me know the equivalent tables to be used in ECC 6.0
    Thanks.
    Warm Regards,
    Narayana Rao.

    Hi,
    Whenever you generate condition table with the same table number with prefix A you can see that in SE16,but as you are asking this tables in ECC 6.0,so check 920&928 tables or exist in the system as condition table(V/06)....
    Regards,
    Chandra

  • Versions for ECC 5.0

    Hi ,
    We are going to implement ESS MSS in ECC 5.0 and EP is 7.0
    Please guide me versions for SPs,Business packages,EA-HR,Java stacks etc any other things if i need to do.
    I am not sure about this.Can anyone guide me.
    Thanks ,
    Usha

    Hi ,
    You can find following details.
    SAP EAHR 26 ( ESS / MSS
    My ERP 2005 Package - Version SP14
    ECC 5.0 + EP 7.0
    Pakages
    1 PCUI - GP ( SP 11 )
    2 ESS          ( SP 11)
    3 MSS         ( SP 11 )

  • Change the Product version from ECC to ERP 6.0

    Hello Experts
    I am planning to apply EHP4 on my Development ECC system. In line with the the suggestion from guide "How to install SAP Enhancement Package 4 for SAP ERP 6.0" system I am supposed to define my ECC system with leading product version ERP 6.0.
    My Ecc system is currently defined with Product version SAP ECC 6.0.
    As per the above guide and also suggestion from "Note 1344564 - Maintenance Optimizer: Check system landscape" which says-
    "In particular for a system of the product SAP ERP, assign the product version of SAP ERP, not SAP ECC."
    I am supposed to change the leading product version to ERP 6.0.
    Now with the current definition of system with product version SAP ECC 6.0, it is being used in a logical component. In order to change this I need to delete the associated logical component. The problem is -this logical component is being used in more than one Project definition that has huge documentation associated with them.
    My question -
    will the deletion of current logical component affect my documentation in any way?
    How can I change the product version from SAP ECC 6.0 to SAP ERP 6.0 without affecting the current setup?
    Regards
    Dhiraj

    Hello Warren,
    Thanks for the suggestion.
    I have already taken care of all the suggested notes in the master note that you suggested. I am able to generate the XML file for other solution defined in my system. In those I have my ECC system defined purely as ERP 6.0 system. I am not able to make out why its not generating the XML for this solution.
    Regards
    Dhiraj

  • LR5 versions, catalog compatibility and latest non-cloud version

    I've been using LR3, then 4 now 5 - I was running 5.3.
    However, my HDD crashed so I rebuilt my Win7 OS, reinstalled LR5, but it's now the cloud version (which I don't have a licence for). Even more frustrating (or maybe it's a blessing in disguise), my LR5 catalog is NOT compatible with LR5.7.1 ?!? It says it's too old.
    I've searched, but cannot find any documentation saying there's a compatibility issue between different versions of LR and when I upgraded from 4 to 5, it managed a catalog upgrade. Now I'm doing a "minor" upgrade, it cannot read it ?
    Where is there a compatibility matrix showing which catalog version can be read / upgraded by which LR versions?
    Bearing all that in mind, I think I'll stick to my previous non-cloud version of LR, but my question is which version should I use and will it be compatible with my catalog backup.
    Thanks in advance (and sorry for my rant )

    Hi Jim,
    Thanks for your reply.
    I've calmed down a bit now And managed to download 5.7.1 standalone in non-cloud version. But the problem remains.
    Or:
    Does that mean my catalog is corrupt?

  • Interface from 4.7 version to ECC 6.0

    Hi all,
       We are having HR system in 4.7 version. We are implementing FI and Travel management in ECC 6.0 version. we need to have an interface from HR system to ECC 6.0 travel system. Which method is suitable for this?? Can we go for BAPIs??
    Thanks in advance,
    regards,
    Chandra.

    Hi,
    If you want the data to be exchanged in a synchronus manner then BAPI's are the way to go.
    However, as I see no need of the same there, ALE / IDOC's should be a preferred way of doing as you can configure the IDOC's to be triggered as soon as there is a change in the data.
    And like you mentioned, both are SAP systems, so you wouldn't need a middleware, you can communicate using IDOCS'.
    Regards,
    Ravi
    Note : Please mark all the helpful answers

  • Dart version and ECC 6.0 upgrade

    We are currently on ECC 5.0 running dart version 2.4.  We are discussing upgrading to ECC 6.0.  If we upgrade, is there a newer version of dart that by default is automatically installed with the upgrade?

    Hi,
    When doing an upgrade the Dart level depends on the SAP HP/APPL level you apply to your system. If your below that given in the note above you have to do some manual installation for DART 2.6.
    If your going to a EHP system you have to have EHP 4 in your system, otherwise you will have to do some manual installation as well.
    For an EHP system have a look at SAP Note  1419580 for more information.
    Kind regards,
    Mark

  • LSMW VERSION FOR ECC 6.0

    Hi All,
    Can any one please let me know what version of  LSMW should be used for ECC6.0.
    Thanks in advance
    Gopi

    Hi ,
    You could use version 4.0 for LSMW for ECC version 6.0.
    Thanks,
    Archana

  • Compatibility between CS3 and earlier versions?

    As the web developer I have Contribute version 3, but some of
    my new clients
    will be buying the latest Contribute CS3 to update their site
    pages. Can I
    still set up their roles and editing rights for a site and
    create a
    connection key to send to them that will work for them in
    Contribute CS3
    without difficulty? And can either of us still edit the site
    pages,
    regardless of the fact that we are each using different
    versions of
    Contribute?
    In conclusion, are there any backward compatibility issues I
    should be aware
    of between the newer version and older versions of CS3 when
    administering,
    and connecting to, the same website?
    Thanks in advance.
    (Please reply to forum. E-mail address is bogus to prevent
    spam)

    Thanks for the advice.
    "ThinkInk" <[email protected]> wrote in
    message
    news:f0sa43$dvh$[email protected]..
    >I had the same problem when C4 arrived and I could'nt
    purchase C3 for my
    > clients.
    >
    > The key is to use Transitional Mode (adminstrator
    settings,
    > compatibility),
    > here's wat the HELP says:
    >
    > --------------------------
    > Enabling compatibility with older versions of Contribute
    > Contribute 4 offers administrators two compatibility
    options--one that
    > allows
    > users with earlier versions to work on the website, and
    one that does not:
    >
    > Transition Mode
    > In this mode, users of earlier versions of Contribute
    can continue working
    > on
    > the website, along with Contribute 4 users. This lets
    you evaluate the new
    > version and set up new roles and permissions without
    disrupting users with
    > earlier versions of Contribute.
    >
    > Compatibility Mode
    > In this mode, all users must use Contribute 4. Users
    with earlier versions
    > cannot work on the website.
    >
    > Contribute 4 starts in Transition mode by default when
    you migrate from
    > Contribute 3. Use this mode temporarily; when you?re
    ready, transition all
    > users to Contribute 4 and enable Compatibility Mode.
    >
    > To enable Compatibility Mode:
    > In Contribute 4, select Edit > Administer Websites,
    and then select a
    > website.
    > The Administer Website dialog box appears.
    >
    > Select Compatibility from the category list on the left.
    > The Compatibility options appear in the Administer
    Website dialog box.
    >
    > Select Compatibility, and then click Close.
    > After you enable Compatibility Mode, all users connected
    to the website
    > must
    > use Contribute 4.
    >
    > ------------------------
    >
    > It's really better to upgrade yourself to the newest
    version, so you know
    > what
    > extra options your clients have and you can support
    them. I managed to get
    > both
    > C3 en C4(I purchased the upgrade) running on my PC, so
    maybe that's also
    > an
    > option.
    >
    > grtz. Hayo
    >

  • Delete a Plan version in ECCS

    My main objective is to clear a ECCS Dimension 03 plan version of all total records and line items records.  I want everything cleared to zero before I start rolling up new plan data from PCA to ECCS.  What is my assurance that I have done that?

    Hi,
    With transaction 0KE1 by leaving 'blank' the field 'profit center' all
    profit centers are considered for the deletetion. You can reset all
    your planning data without selecting one by one.
    Please check before in your test system.
    I hope this helps,
    Regards,
    MLM

  • Backwards Compatibility: 4.1 to newest version

    I am the admin and am running 4.1, my client (because of compatibility issues on her new laptop) is considering upgrading to the latest version. Will everything still run and work alright? I would prefer that I don't have to upgrade as well .

    Hi Cheese444,
    Greetings from Adobe.
    If your client is also the admin of the same website then you may also need to upgrade as it is recommended that all the administrators should use the same version of Contribute. If your client has any other role apart from admin(like publisher or writter) then there should be no issues if you both have different versions.
    Regards,
    Mayank

  • New version of ECC in 2010?

    Any idea if SAP is releasing a new ECC version in the year 2010?

    the new SAP version is called -  SAP Business Suite 7 which is Fully SOA-enabled. Demo is already in market. will be used by enterpises by the end of this year.
    please follow this link for other use full informations.
    http://www.sap.info/en/solutions/sap_business_suite/sap_erp/06_02_2009_SAP%20Business%20Suite_SAP%20Business%20Suite%207_en.html
    BR
    Rajeev

Maybe you are looking for