We implemented consumer portal in our landscape. We have two producer portal and one consumer portal in the landscape. One server contains business packages ESS, MSS and SRM. This server is in NW 7.0. Another server contains customer applications using BPM. This server is NW 7.3. Consumer portal is in NW 7.3. We connected our consumer UWL to ECC, SRM and producer BPM. All the links was coming in the UWL. No issue on that. No changes was required in ESS, MSS and BPM workflow. They were working as usual in consumer portal. Issue we faced is in the workflow of SRM 7.0. Activities were coming to the UWL but when we are clicking on the menu like details and print preview it was not working. These iviews are supposed to open a popup sceen with data from another iview.. Those iviews weer not present in the consumer server. We created remote delta link (RDL) for all SRM 7.0 iview in the consumer server. We also created RDL for business objects. It was still getting error. We did something more than copy. I am discussing all we did to make the menu work from the UWL.
- Create a folder with following information in the location given below (in consumer portal):
Folder Name was SRM RDL. Folder below that does not exists. Screen is captured after all steps done.
- Copy all folder SAP SRM 7.0 and all its content from producer to the newly Created folder. Mind that we are accessing folder of producer portal from consumer portal.
- Paste it under SRM RDL
- Copy SRM folder containing business objects, under the folder in the Business Object from remote portal. We are still accessing producer from consumer.
- Paste it under the folder in the Business Object
- Till now there is nothing unusual. This is required for all iview which is called from UWL of producer portal. In our case it is SRM workflow. Here UWL is calling a business object. Business object is in turn calling the iview through object based navigation. We need to give user access to target RDL iview to user through a role. We identified two iview for detail (of shopping cart) and print preview. We added them in a custom role.
It is worth to notice that Iview is pointing to operation of a business object. This iview is responsible for print preview menu.
following is another iview for viewing detail of shopping cart from UWL menu
Finally two iviews are added to a custom role and users assigned that role. Iviews are not marked visible or entry point here. This will not be shown in the portal but authorization will be checked internally when user clicks on the menu in iview.
Role is given to user from user administration.