ALE between ECC6 EhP5 et ECC6 EhP4

I was wondering if there are any risks working with two different EhP versions between HCM (EhP5) and FICO (EhP) through an ALE connection. It should depend on the content exchange between these domaines, and at this stage of the project only basic content (such Cost Center, Company Code, etc.) should be bound between HCM and FICO through ALE.
Is someone out there already experienced this ALE connection between EhP5 and EhP4 and if so, how did it work?

Hello Lionel,
If your only worry is about the risk involved in transferring data from one EHP to other EHP, Then there is no risk involved in this, ALE transfer will work perfectly, there would be no issue. Moreover EHP are based on ECC 6.0 base, So the base is same in both the cases. ALE transfer will work in the same manner you need to create IDOC structure on both the sides and then do the further activities.
Hope the above should be helpful.
Best Regards,
Deepak

Similar Messages

  • CProjects access in ECC6 EHP5

    Hi,
    Recently we installed IDES ECC6 EHP5, and I tried to access cProjects URL, by calling webdynpro DPR_MAINFRAME but i dont see the cProjects under it, I used to get the cPRojects URL in earlier EHP's like EHP4 and EHP3 from DPR_MAINFRAME. but i dont find it in EHP5. then I surfed to SICF and called cproject URL by testing a service... the URL is <hostname>.<domain>:port/sap/bc/webdynpro/sap/cprojects . I can log in to the cProject, but once i log in i dont see the menu to create project or open existing project. I can see button for creating simulation/versions, tabs like structure, resource, accounting, DMS etc.,...but dont find a menu for creating/opening the project. It seems there is been a change in EHP5 regarding cprojects. So, Can you please let me know how to access/work with  cProjects in EHP5 System.

    HI,
    Withh ECC Enhp5, SAP PPM version must be SAP PPM 5.0 Check the version in your landsacpe. And in PPM 5.0, the url link has got changed for cProjects. The link is as below
    <Protocol>://<Host>.<Domain>.<Extension>:<Port>/sap/bc/nwbc/SAP_BPR_PPM
    Proper additional roles need to be assigned to access SAP PPM. Refer to the configuration guide for SAP PPM 5.0
    Regards
    Amit

  • SAP 4.7 to ECC6 EHP5 Upgrade inc.OGSD - "/ICO/MOC_NEW_GUI" nametab error

    Hello all,
    I'm currently running a SAP upgrade from 4.72 to ECC6 EhP5 SPS6.
    This upgrade include OGSD upgrade from4.72 SP12 to OGSD 6.10 SP5.
    Duing phase upgrade phase RUN_RSPTBFIL_DEST, I have the following error message : Could not read nametab "/ICO/MOC_NEW_GUI".
    According to OSS note 1377262, I download fix A61000INOGSD.SAR and extract file A-61000INOGSD.SAP in <upgdir>/cofiles (and also in <transdir>/cofiles).
    Phase RUN_RSPTBFIL_DEST is still in error when I repeat it.
    I note that content of A-61000INOGSD.SAP file is a little bit different regarding my error message:
    Inside file:
    I 2EETW109 table "/ICO/MOC_NEW_GUI" does not exist in nametab.
    My error message:
    2EETG011 "[DESTINFO] Could not read nametab""/ICO/MOC_NEW_GUI"
    Many thanks for your help & feedback,
    Chris

    Hello Chris,
    we experienced the same issue as you.
    After discussion with the SAP Support team, it appears that this migration path is not the good one.
    The right procedure is now to upgrade to ECC6 EhP5 with OGSD 6.10 SP0 and then to apply manually the SPs you want on OGSD add-on.
    I think they are currently updating the corresponding OSS Notes.
    I hope it will help.
    Vincent

  • Diff between ECC5.O and ECC6.0

    Hi guys,
    Can any one give me the differenece between ECC5.0 and ECC6.0 in SAP-PM and what are the upgradations in ECC6.0 Plant maintencne.
    Bhanu

    Hi,
    The advantage is there are new functionnality available, more standard reports & tables, etc.
    Advantage of 64 bits is in the amount of memory that your system will be able to use.
    32 bits systems are limited to 4 GB of memory. With 64 bits systems you can virtually use 18 millions TB of memory (almost limitless... from our point of view).
    So it's better for systems with high number of users, high need of memory for buffers, etc. , to be in 64 bits kernel.
    For ECC6 goal is to be in 64 bits unicode.
    regards,
    Venkatesan Anandan

  • Diff between ECC5.0 and ECC6.0

    Hi,
    This is Ramakrishna,can any one give proper explanation diff between ECC5.0 and ECC6.0
    Regards
    Ramakrishna

    Hi,
    Refer following link;
    [SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
    Following are the basic differences as far as MM Module is concerned;
    Pickup list - Batch where-used list display in transaction MB56
    u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
    u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
    u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
    Usability enhancements for transaction MIGO for the posting of goods movements
    u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
    u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
    u2022 User changes the default values in the menu path "Settings -> Default Values."
    u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
    - Goods receipt
    - Goods issue
    - Transfer posting
    - Remove from storage
    u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
    New report : display list of invoice documents (MIR5)
    u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
    u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
    u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
    u2022 In the output list, the report shows both posted and held invoices.
    u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
    Requirement prioritizations in materials management
    u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
    u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
    Mass maintenance of outline agreements
    The following two transactions available:
    u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
    u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
    Commitment plan for purchase contracts
    u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
    u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
    u2022 This commitment plan itself can have any number of items.
    u2022 User can define a value and a validity date for each commitment plan item.
    u2022 This enables user to pre plan different values for different periods of time.
    u2022 The software generates an earmarked fund document for a defined commitment plan item.
    u2022 This earmarked funds document can in turn contain several different items with different account assignments.
    u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
    u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
    u2022 Account assignment to a different account assignment object is then no longer allowed.
    Availability check in "Enjoy purchase order and requisition"
    u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
    u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
    - To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
    - Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
    u2022 Two settings are possible with availability check:
    - Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
    - Delivery proposal - Full confirmation
    External services: putting service items in the purchase order on hold (changed)
    User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
    Customizing transactions OX18 replaced by view
    The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
    Goods receipt: new movement types in inventory management
    The following new movement types are available in inventory management:
    - 107: Goods receipt to valuated goods receipt blocked stock
    - 109: Goods receipt from valuated goods receipt blocked stock
    Prepayment of invoices
    This functionality is characterized as follows:
    u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
    u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
    u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
    u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
    u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
    u2022 When the software posts invoices, it continues to execute the standard checks.
    u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
    u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
    u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
    Purchasing accounting information to the former SAP Business Information Warehouse
    u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
    u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
    Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
    u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
    u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
    u2022 Functionality for report RMMR1MRS is enhanced.
    u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
    u2022 To do so, set the relevant indicator on the initial screen of the report.
    Parking service items
    It is now possible to put service orders without errors or with commitment errors on hold.
    Report MB5B : Stock on Posting Date
    u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
    u2022 This functionality is not available in Release 4.7.
    Stock Transfer Between Storage Locations
    u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
    u2022 As a result of which user can input issuing storage location with supplying plant.
    u2022 Facility of using different delivery types for different issuing storage locations is available.
    u2022 Shipping Point data can also be determined based on the issuing storage location

  • SAP SD--Difference of upgrade between SAP4.7 and ECC6.0

    Hi friends,
    Somebody can pls tell --Difference of upgrade between SAP4.7 and ECC6.0 in terms of sap SD module or any links for this.
    Rahul

    Hi Rahul,
    Your question is a little general...Maybe you could go to sap help portal to search for the documentation for upgrading to 600.
    As I know, we have some new functionality in release 600. For example, shipping point determination with storage location, automaticly outbound delivery creation after saving stock transfer order...
    Also the screen is different for most list transactions like VA05.
    Regards,
    Smile

  • Difference between 4.7 and ECC6

    Hi
    Could any one explain me the difference between 4.7 and ECC6
    Regards
    Uday

    Hi,
    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.
    Regards,
    Rakesh

  • Technical difference between ECC5.0 and ECC6.0

    Hi everyone,
    Can anybody tell me whats is the Technical difference between ECC5.0 and ECC6.0.
    I am doing upgrade from ECC5.0 to ECC6.0 in Retail.
    Regards,
    Divya

    Dear Divya,
    When it is a technical upgrade from a lower version to ECC6.0, many objects like includes, Function modules, reports, OSS notes, DDIC objects, BDC/Print programs, SAP scripts, screens will get affected due to the upgradation. So we need to check with all these objects.
    u2022 We will encounter short dumps while executing certain programs. This may be due to the usage of obsolete function modules or Unicode errors.
    u2022 The BDCs in the upgraded version will become defective as many of its screen field names will be changed during version change.
    u2022 Program texts of many programs will be lost. They have to be restored.
    u2022 In case of tables, enhancement category has to be provided.
    u2022 There is a possibility of losing the variants during upgradation. So care should be taken to retain them before upgradation.
    u2022 ECC6.0 is case sensitive, so many of the interface programs will fail to transfer (FTP) files between systems. These objects have to be changed so that the commands passed to the external system be UPPERCASE.
    So a developer should be aware of the following:
    u2022Unicode programming is followed in ECC6.0. So we need to be aware of it to rectify certain Unicode errors which are likely to occur.
    u2022You have to run the transactions SPAU & SPDD to check for list of standard & custom objects that needs modification in the upgraded version.
    Check the below link to find more details on usage of SPAU & SPDD transactions
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    u2022Should be aware of the objects that have become obsolete in ECC6.0. They have to be replaced by appropriate ones.For eg.:
    --> The WS_* function modules have been replaced by GUI_* FMs in ECC6.0 as WS_* FMs have become obsolete from 4.7
    -->Tables like TVARV & TTREX have been replaced by TVARVC & TTREXN respectively in ECC6.0.
    u2022In case of tables, we need to specify the Enhancement category.
    u2022Due to upgradation, we will lose out some variants. So we should take a back-up before proceeding with the upgradation.
    u2022In case of BDC programs, some field names will be changed. So they have to be named appropriately.
    Please check with the below links for more details:
    SAP Upgrade guide:
    http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
    From ABAP's perspective, the following link helps you:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
    For technical upgrade inputs:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
    https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
    Hope this helps you.
    Regards,
    Rakesh

  • Differences Between ECC5.0 and ECC6.0 in Controlling

    Sir.
    can you Explain?
    Differences Between ECC5.0 and ECC6.0 in Controlling
    Regards

    Hi There,
    Check the below link:-
    [http://solutionbrowser.erp.sap.fmpmedia.com/Search.aspx]
    here enter your source system and target system and the differences will be listed.
    Regards,
    Gaurav

  • How to set up ALE between 4.7 and ECC 6.0 version

    Hi,
    We are running on 4.7 EE version of SAP with all main modules. Now we are building another system for HR module in ECC 6.0 version of SAP.
    Now the requriement is all the HR transactions posted in ECC 6.0 version shoule be moved to 4.7EE SAP system. For that i need to set up a ALE between ECC 6.0 and 4.7EE.
    So please hlep me the process flow to set up this. Is there any pre-requisites?
    Please suggest me..
    Thanks
    Yadayya

    Hi Yadayya,
    Please follow the link below for details:
    <link to blocked site removed by moderator>
    You can easily transfer IDoc's from 4.7 to ECC 6.0
    Regards,
    Pranav.
    Edited by: Thomas Zloch on Oct 18, 2011 2:09 PM

  • Excel layout changed after EHP5 upgrade from EHP4.

    Hi All,
    We have just finished the EHP5 upgrade from EHP4 for ECC 6.0 for our production system. BUT we noticed that The standard layout, (also known as Dynamic List Display) has been chagned in EHP5 compare to EHP4.
    This is affected us as we have lot of macros enable for the excel files.
    Request you all to help. Is there any sapnote, anyway we can resolved this issue.
    Thanks

    Hi Markus,
    Thanks for reply.
    I not sure how i can attached file over here? Is there anyway to attached files in the forum?. I have the before and after image of excel file.
    But the position of the data which is downloaed in the excel sheet has been changed after upgrade. For example ,Before upgrade the column named "Description" in the production plan report was in the second column i.e. B where as after upgrade the "Description" column in the production plan report is in the first column i.e. A.
    I mean the postion of the data changed in after upgrade. Therefore macro which are enable are not working anymore.
    New Format Example
    Production plan          
    Description                        Material                               Sales doc.
    IRB 2600 M2004                 3HAC020536-018              104861
    IRB 2600 M2004                 3HAC020536-018              2BT0615486
    OLD Format
    Production plan                    
                                          Description                    Material                               Sales doc.
                                          IRB 2600 M2004            3HAC020536-018               104861
                                          IRB 2600 M2004            3HAC020536-018               2BT0615486
    Hope this above will help to make it clear.
    After checking this message ... the output example given above seems to be not showing the way i itend to... But in above example in the old format the Description column was at column B instead of column A after upgrade.
    Thanks
    Edited by: deepak.shinde on Oct 11, 2011 8:34 AM
    Edited by: deepak.shinde on Oct 11, 2011 8:36 AM

  • ECC6.0 - upgrade from EHP4 to EHP6 - cross release transports.

    Hi Experts
    We are planning to upgrade our system from ECC6.0 -EHP4 to EHP6.
    Source - ECC6.0-EHP4
    Target - ECC6.0-EHP6(Enhancement pack6)
    Current ECC version -
    SAP_BASIS 701 0014 SAPKB70114 SAP Basis Component
    SAP_APPL 604 0013 SAPKH60413 Logistics and Accounting
    We would like to know during the project if we can do a transport
    between upgraded development ECC6.0 -EHP6 to non upgrade production ECC6.0-EHP4.
    We have data from note 1090842 and 1273566.
    But last 10 lines of note 1090842 are contradictory wherein on one side it says you can do transports between Releases 7.0*, 7.3* and 7.4* and
    on other it says it can be problem if support pack levels are different on same release.(if problem can happen on same release with different pack
    level then there are greater chances of issues between different releases).Note 1273566 is clear and suggest no issues exist yet for
    technical and logical transports between suggested version 700/701 to >=702
    Also below is the extract from SUM guide - (SUM-1.0-SP07)
    RECOMMENDATION
    We strongly recommend that you perform transports only between systems of the same release or enhancement package level, and where the same business functions are activated. If you do not follow this recommendation, you do so at your own risk regarding potential problems.
    Please suggest if we need to create Dual maintainance parallel landscape during the tenure of project where two development system co-exist.One
    with current and one with upgraded version and changes need to be done on both in parallel.Support fixes and LTO’s go from non upgraded dev to non upgraded prod.
    Thanks

    Hello
    I won't perform cross version transport even if it can be possible.
    As of 7.02 cross version transport are prevented by default with option SP_TRANS_SYNC (see here under note).
    The best way is, if possible, to have a manual dual maintenance. All corrections created in the Ehp4 dev should be manually recreated in the Ehp6 dev.
    What is usually done is to upgrade at first a copy of production for test/discovery purpose, the aim is to identify most of the regressions/evolutions. This will reduce the time you will have to spend in the migrated dev to adjust your system. You then migrate dev and enter in a freeze period where you reduce activity on legacy Ehp4 system to the minimum (bug correction for prod).
    One good thing with the manual reprocessing of changes on the Ehp6 system is that this kind of constraint will help consultants to reduce their activity.
    Regards
    1742547 - Information about component version check in TMS

  • ECC6 EHP5 issue with authorisations now need access to S_DEVELOP

    Hi
    We have ECC6 and have just upgraded to EHP5 and have found that many HR reports/transactions now need access to S_DEVELOP authorisation object.  This  has caused issues with our user roles.  Has anyone else experienced this issue?
    Many thanks
    Julie

    Hi Julie,
    Please implement SAP note :  1487329  "Additional Authorization Check in ABAP Workbench" that should solve your issue. There is also note 1617448 "WD ABAP Team Calendar needs S_DEVELOP authorization to load". Hope it helps,
    Kind Regards
    Christine

  • Interface Consideration between ECC5.0 and ECC6.0

    Hi Experts,
    We are in upgrade project where our Finance system is going to upgrade to ECC6.0 where as Process system is going to remain on ECC5.0 , just wanted to know what and all consideration need to take place before proceeding on this,
    Any documentation or comments will much appreciated
    Riyaj

    Hi Riyaj,
    There are a number of [upgrade tools|http://service.sap.com/upgradetools] and [upgrade services|http://service.sap.com/upgradeservices] available on the SMP which can help you decide on the best roadmap to follow.
    The query you have posted is a little vague, however from a general point of view, business processes are backward compatible between ECC 6.0 and ECC 5.0 so I would not foresee and issues here.
    The ideal scenario, and one that SAP recommends would be to have all systems on a parallel release, but this is not always practical from customers point of view, and many have such multi release landscapes in place.
    Of course goes without saying, that however you decide to proceed, make sure that you thoroughly test your target configuration in a sandbox landscape first.
    Best Regards,
    Paul

  • Screen difference between 4.5B and ECC6

    Hi,
    Could you kindly provide me with some documnet or link , where i can actually see the screen changes for the standard SAP transactions between the 4.5B and the ECC6 version?
    Regards,
    Ruchika

    main diffeences between SAP 4.7 and ECC 6.0 versions ?
    diff between 4.6c to 4.7 abap
    difference between SAP 4.6C and SAP ECC6.0
    For functional differences please check out the following link:
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Regards

Maybe you are looking for