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

SUS - In a same system different client

Hi,

We are planning to implement SUS ( EBP-SUS), in the same system as the EBP is setup with a different client. We are using extend classic in the EBP.

Can some can share any config documentation or any useful information to implement this process.

Thank you

Sreedhar Vetcha

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 06:46 PM

    you can deploy sus and srm on same machine in different clients

    the inforamtion should be available in SRM installation or master guide,

    see sap note 508806 .

    but currently extended classic PO's are not supported in SUS, only standalone and classic are supported .

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 07:19 PM

    hi,

    Please refer to the OSS note with number 543544 for details

    Related threads:

    note-543544---sus-extended-classic-scenario-for-eb

    is-xi-required-for-ebp-sus-scenario

    BR,

    Disha.

    <b>Pls reward points for useful answers.</b>

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2007 at 09:37 PM

    Hi

    <b>Please go through this -></b>

    <u>Yes, we require XI for EBP - SUS scenario.

    This is to route the incoming XML in to correct system. Here 3 systems will be required.</u>

    1) Integration Server (XI) also called PI (Process Integration).

    2) EBP ( Integration engine)

    3) SUS (integration Engine).

    <b>It will be almost same as the scenario with different clients and same server.

    Your RFC destination settings will be different and SLD business system settings will be different to some extent (as server changes).</b>

    Otherwise, I do not think there is much difference.

    <b>It's not different. It's going to be same as mentioned earlier.

    You can't have a HTTP connection to SUS from EBP..it will be ABAP system only.

    You will have HTTP connection to ABAP server for XI system in SRM.</b>

    <b>Nothing changes. Pl do the config as you would have done when they are in the same server - diff clients.</b>

    <u><b>SUS is the BSP application.</b></u>

    <b>SUS and Supplier Portal (aka Supplier Workplace) are the same.</b>

    For supplier integration it depends on the business process. SUS supports some

    essential processes, focus for small suppliers with no backend. Supplier

    integration needs to be clusered on the supply base and solution defined for each.

    <b>SUS is a BSP application with a SAP touch.</b>

    SUS is comparable to Supplier Registration Screens, somehow litttle bit different to SRM screens, the SAP look is there. When the SAP Portal us used for integrating several different applications for suppliers, then it also looks like SAP, like SAP Portal, where different applications can be called.

    <u><b>Yes , IF EBP AND SUS are in different clients , then the data inside this must also be known in the SUS system.</b></u>

    <u>Related links -></u>

    note-543544---sus-extended-classic-scenario-for-eb

    ebp-and-sus-on-differnet-server

    <u>Hope this will help. Do let me know.</u>

    Regards

    - Atul

    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.