Skip to Content

Self Services – One EP Multiple ECC systems

Business Scenario

A customer having one Enterprise portal and Multiple ERP system
and there is a need to implement Self services that uses one
portal and communicates to multiple client.



We shall take one example of Employee Self services where there is one Enterprise
portal server having a Business Package for employee self service
that has to communicate to Multiple ECC systems.

1. Copy the ESS role provided by SAP. Create one copy per ERP client.

Role path in Enterprise Portal


2. Create systems with appropriate naming conventions in Enterprise Portal with respective Aliases. Each system will contain respective ECC server parameters. Make sure you use fully qualified domain names while configuring WAS and ITS in the system.You need to remember that WAS can only contains either of the below Technolgy Componenets.


  •      BSP
  •      ABAP 
  •      JAVA


  1. Create JCOs for each of the below with different names
  2. Start targeting each role one by one and make change in the iview property “application parameter”


You need to use parameter sap-wd-arfc-useSys for java iviews. For
the rest of iviews you can use the respective system created in
step 2. Other than java iviews all iviews have system parameter
property. For java iview you can refer to link below.


Once you are done with the iview configuration you will need a lot
of concentration in home page frame work. Make sure each system has
different naming convention for resources and services atleast.


The Dependecies of some application can cause an error if there
are any hardcoded urls. i.e. reporting launch pad under Manager
Self services has urls hardcoded and it may not function as

Role path in Enterprise Portal
You must be Logged on to comment or reply to a post.
  • Barin,

    You have made some good points in this blog.  However the most important part in this blog is the comments around the JCo connections and you have just made a few comments and referred to a help link.  If you go into more detail around this it will be a much better blog.


    • Hi Paul

      thank you for the kind words.

      1. the jco part is the most important when an iview executes so you are right.
      2. i didn’t want to paste something from so have pasted the link.

      I am open to questions if you have the idea is to create multiple jco connections per client and then make the java iview access the jco.


  • You make the steps look simple, but they are quite complicated and error prone. When you also consider the home page frame work in ERP, which is effectively a hardcoded list of PCD objects, I would suggest it is more efficient to install multiple portal servers.
    • hi michael

      thank you for taking time to read this.

      certainly the best option is to install multiple portal server. but what about hosting companies. There are some hosting companies which run the services on one portal.

      I am right now supporting a project that has 14 ERP clients using one portal. There are total 227 customers running the same setup.

      homepage frame work is managable. the issue will arise in workflows and reporting launch pad. we are currently running 14 differnt homepage frameworks in one portal.

      Reporting has a product issue that needs modifications or change.


      • In my opinion, issues such as isolating performance or stability issues when everyone is using the one portal plus the need to keep everyone on exactly the same releases mean that the hosting companies are making their life easier (or cheaper) rather than providing a quality service.
        Virtualization techniques nowadays should allow multiple portal systems to have their own runtime space without impacting others.
  • Hi Barin,

    very interesting blog.
    I’ve decided to implement this scenario usign 1 EP and 2 HCM system.
    Actually we have already activate one ESS&MSS linked to the first HCM.
    I’m starting to cofigure the 2nd HCM.
    I’m new on this tread, so I’m asking you some more info.

    1. I have to copy the old roles to the new ones.
    2. Then I’ve to duplicate the System/Aliases and JCO.
    3. Targeting the iView: this mean that I’ve to duplicate all the iView? The “application parameter” is at iView level (or the system parameters for non java iView).

    The role is associted to the user so the user will work on his specific HCM sys.

    Thanks in advance,

      • Hi Barin,

        I’m to asking to you one more help.

        Your point 4.: All the ESS MSS iviews are of type

        It’s seems that the iView are of type webdynpro and even if the properties “Customer Exits for ‘ParameterProvider’” and Application Parameter are there … is not working.

        I’ve created a custom provider service that extend ICustomerParameterProvider; then a custom WebDynpro DCs that call a BAPI and an application integrator iView.
        The configuration of the provider is done (DebugMode = true and Use_CustomerExit_ParameterProvider=true)
        Activating the debug for it all is OK (the getParameter(..) method receive my parameter tag)
        Then I try to setup the same scenario for one of the standard ESS iView, but seems that my service is not called, the debug is not activated when the iView start in the Portal.
        Looking at the SAP ESS iView seems that is not an Appliation Integrator iView but an WebDynpro iView so I done the same think for my custom webDynpro and the provider is not activated.

        I’m doing or forgetting somethink or I’ve to change all the ESS iView?

        We are on EP 7.0 SP18.

        One more time thanks,

    • I’ve one more question: what about the users? in our actual scenario the EP is configured to demand the user management to the ABAP system. What can we do if, actually, the users are defined on HCM. In the future we will have 2 HCM systems.

      Thanks a lot,

      • hi

        The ERP user is cross client so even if you are mapping multiple client the user will exist in all.

        this will solve the problem.