Skip to Content
author's profile photo Former Member
Former Member

SRM 7 ehp1 with ECC 6 ehp5?

Gurus,

Is it mandatory to use SRM 7 ehp1 with ECC 6 ehp5? Our client has ECC 6 ehp 4 and is now upgrading from SRM 4 to SRM 7 ehp1. Can you share some links where I can confirm if SRM 7 ehp1 with ECC 6 ehp5 is mandatory?

Also pl let me know what is the difference between shopping cart creation in SRM 4.0 and SRM 7.0 ehp1. SAP says they have changed something and made it more user friendly. Is it different from normal SRM 7 (without the ehp component?)

Regards,

John

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Oct 27, 2011 at 03:09 PM

    Hi John,

    From follwing solution browser URL, you can find the new feateres etween the SAP SRM older version and current release verions. Even you can export the details and dig in deep.

    http://erp.fmpmedia.com/Search.aspx

    Regards,

    Krish

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 27, 2011 at 07:30 PM

    Hello,

    No, it is not mandatory. You can have SRM 7.01 with ECC EHP4.

    ESOA functionality is already available in EHP4.

    I hope it clarifies.

    Regards,

    Ricardo

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi ,

      I am sorry I have missed typed the information. If xml is used PI is mandatory. I am really sorry for this.

      Also if you lower the ERP type in define system landscape system will still create xml for PO creation. Hence if you use SRm 70 or higher PO creation will use xml and PI us mandatory. I have worked on SRM 70 and SRM 70 EHP1 landscape.

      I am sure about this behaviour.

      Regards

      Sam

  • author's profile photo Former Member
    Former Member
    Posted on Jun 12, 2012 at 04:16 PM

    Hi,

    There are 3 ways of sending PO from SRM to ECC

    1.Via - RFC ( by setting the system landscape to a lesser version ) it will not have any side effects just that it used RFC connections instead of ESOA

    2.Via PI - by setting the landscape to the current version and configure the relevant XML services in the SOAMANGER

    3. via Non PI Web Services- by setting the landscape to current version . This time the webservices are configured in SRM system itself.

    I have configured transfer of Contracts from SRM 7.01 to ECC 6.5 EHP5 as Contract/ Scheduling Agreement to the backend with Non PI Web Services(via XML). This way we didnt have to install PI at the client place which saved them a lot.

    I have written a blog on how to transfer central contracts from srm to ecc using web services but without PI , please find the link below and hope it is helpful.

    http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from-srm-to-ecc-using-web-services-without-pi

    Regards,

    Naveen

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.