EHP3 for SAP SRM
7.0
EHP7 for SAP ERP
6.0
October 2014
English
UI Integration (S06)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
UI Integration (S06): Configuration Guide
Copyright
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting
an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any
time for any reason without notice. The information in this document is not a commitment, promise, or
legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 2 of 39
SAP Best Practices
UI Integration (S06): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP SE
Page 3 of 39
SAP Best Practices
UI Integration (S06): Configuration Guide
Content
S06: UI Integration – Configuration Guide ................................................................................ 7
1
Overview............................................................................................................................. 7
1.1
Purpose .................................................................................................................... 7
1.2
Target Group ............................................................................................................ 8
1.3
Required Know-How ................................................................................................ 8
2 Roles and Authorizations for SAP NetWeaver Business Client and SAP NetWeaver
Portal ......................................................................................................................................... 9
3
2.1
Roles and Authorizations for SAP Supplier Relationship Management .................. 9
2.2
Roles and Authorizations for SAP Supplier Life Cycle Management .................... 11
SAP NetWeaver Business Client Configuration ............................................................... 13
3.1
Activate SAP NWBC Interface ............................................................................... 13
3.1.1
System Requirements........................................................................................ 13
3.1.2
Activate Portal-Independent Navigation Frame ................................................. 13
3.1.3
Deployment ........................................................................................................ 14
3.2
4
Activation of Services for SAP NWBC ................................................................... 16
3.2.1
Activation of Services for SAP SRM .................................................................. 18
3.2.2
Activation of Special Services for SAP SRM ..................................................... 18
3.2.3
Activation of Services for SAP Supplier Lifecycle Management ....................... 18
SAP NetWeaver Portal Configuration .............................................................................. 20
4.1
Installation of the Business Package ..................................................................... 20
4.1.1
System Requirements........................................................................................ 20
4.1.2
Important SAP Notes ......................................................................................... 20
4.1.3
Download Business Packages .......................................................................... 21
4.1.3.1
Business Packages for SAP SRM 7.0 Enhancement Package 2 ................. 21
4.1.3.2
Business Packages for SAP Supplier Lifecycle Management ...................... 21
4.1.4
Content of the Business Packages .................................................................... 21
4.1.5
Deployment of the Business Packages ............................................................. 22
4.1.6
Check Business Package Deployment .............................................................. 22
4.1.7
Check Portal Content Permissions .................................................................... 22
4.2
Basic Configuration ................................................................................................ 23
4.2.1
Portal System Objects ....................................................................................... 23
4.2.1.1
Assign a System Alias ................................................................................... 25
4.2.2
Permission to the Portal Content ....................................................................... 25
4.2.3
Single Sign-On Configuration ............................................................................ 25
4.2.3.1
Export the Certificate ..................................................................................... 25
4.2.3.2
ABAP Stack ................................................................................................... 26
4.2.3.3
Import Certificate ........................................................................................... 26
© SAP SE
Page 4 of 39
SAP Best Practices
5
6
User Management Setup ................................................................................................. 27
5.1
Authentication ........................................................................................................ 27
5.2
User Management Scenarios................................................................................. 27
5.2.1
User Store: Database ........................................................................................ 27
5.2.2
User Store: ABAP .............................................................................................. 27
5.2.3
User Store: LDAP .............................................................................................. 28
Universal Worklist Configuration ...................................................................................... 29
6.1
UWL Configuration ................................................................................................. 29
6.1.1
System Connection ............................................................................................ 29
6.1.2
Set UWL Refresh Handling ................................................................................ 30
6.1.2.1
Refresh Time from Cache ............................................................................. 30
6.1.2.2
Cache Validity ................................................................................................ 30
6.2
Customizing the UWL iView ................................................................................... 30
6.2.1
Hide Navigation Panel ....................................................................................... 30
6.2.2
Hide Connection Errors...................................................................................... 30
6.3
7
UI Integration (S06): Configuration Guide
Customizing the UWL Configuration File ............................................................... 31
6.3.1
Download UWL Configuration File ..................................................................... 31
6.3.2
Upload Configuration File .................................................................................. 31
6.3.3
Change Tab Order / Remove Tabs from UWL .................................................. 31
6.3.4
Change Translations .......................................................................................... 32
6.3.5
Columns in the UWL .......................................................................................... 33
6.3.6
Display Refresh Button ...................................................................................... 33
6.3.7
Remove Sections from Preview Pane ............................................................... 33
6.3.8
Remove Actions from Preview Pane ................................................................. 33
6.3.9
Remove Actions from Specific Workitems ......................................................... 33
Customize the Portal ........................................................................................................ 35
7.1
Standard Look and Feel ......................................................................................... 35
7.1.1
Create a Folder for Customer Objects ............................................................... 35
7.1.2
Customizing the Framework Page ..................................................................... 35
7.1.3
Hide Search Field .............................................................................................. 35
7.1.4
Change Portal Help Link .................................................................................... 36
7.1.5
Portal Content Translation ................................................................................. 36
7.1.5.1
Create a Translation Worklist ........................................................................ 36
7.1.5.2
Assigning Texts and Releasing Worklists ..................................................... 36
7.1.5.3
Generate the Translation Data ...................................................................... 37
7.1.5.4
Release the Worklist for Translation ............................................................. 37
7.1.5.5
Searching for the Worklists and Uploading translations ................................ 37
7.1.5.6
Define the Source and Target Languages .................................................... 37
7.1.5.7
Choose Load for Translation ......................................................................... 37
© SAP SE
Page 5 of 39
SAP Best Practices
UI Integration (S06): Configuration Guide
7.1.5.8
Translating Texts ........................................................................................... 37
7.1.5.9
Publishing Translations ................................................................................. 37
8
Where to Find More Information ...................................................................................... 39
9
Tips ................................................................................................................................... 39
9.1
Http or Https ........................................................................................................... 39
9.2
Switch between SAP NetWeaver Portal and SAP NetWeaver Business Client .... 39
© SAP SE
Page 6 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
S06: UI Integration – Configuration Guide
1 Overview
1.1 Purpose
This document is intended to provide a compact but comprehensive configuration guide for
consultants integrating SAP SRM 7.1 and higher and SAP Supplier Life Cycle Management
1.0 via two options:

With SAP NetWeaver Business Client (SAP NWBC) (see chapter 4 of this document).

With SAP NetWeaver Portal (see chapter 5 of this document).
The following options for navigating in the Portal and for Portal-independent
navigation are supported for SAP SRM scenarios and for SAP Supplier Lifecycle
Management:
Scenario
Deployment
SAP NetWeaver
Portal
SAP NetWeaver
Business Client
SAP SRM Self-Service
Procurement
One client
x
x
SAP SRM Self-Service
Procurement
Multiple Backend
x
x
SAP SRM Operational
Sourcing
One client
x
x
Multiple Backend
x
x
Multiple Backend
x
x
(Suppliers log on to the
purchasing system)
SAP SRM Operational
Sourcing
(Suppliers log on to the
purchasing system)
SAP SRM Operational
Sourcing – decoupled
bidding
(Suppliers log on to a
separate SRM system
outside the firewall)
Decoupled Bidding
via SRM-SUS
system outside the
firewall
SAP Supplier Life Cycle
Management
Buyside
x
x
SAP Supplier Life Cycle
Management
Sellside
x
x
(Suppliers log on to a
separate Supplier Life Cycle
© SAP SE
Page 7 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
Scenario
Deployment
SAP NetWeaver
Portal
SAP NetWeaver
Business Client
system outside the firewall)
1.2 Target Group
The target group for this documentation is consultants on customer projects who are
concerned with the product implementation. For the integration of SAP SRM 7.1 into an
SAP NetWeaver Portal, we strongly recommend contacting an experienced portal consultant,
as it requires detailed knowledge of SAP NetWeaver Portal from a technical point of view.
1.3 Required Know-How
Knowledge of Portal content creation (roles, worksets, pages, iViews, and so on), as well as
Portal system administration is required for working with chapters referring to the Portal
integration. We recommended the following training courses:

SAPEP

EP200

EP600

ADM200
© SAP SE
Page 8 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
2 Roles and Authorizations for SAP NetWeaver
Business Client and SAP NetWeaver Portal
2.1 Roles and Authorizations for SAP Supplier
Relationship Management
Roles describe the activities that internal employees or external business partners can
perform in a business scenario. After logging on to the system, users see all functions that
they need to process their tasks.
Roles are defined in the transaction Role Maintenance (PFCG). For more information, see the
customizing for SAP Supplier Relationship Management (SAP SRM) under SRM Server
(Cross-Application Basic Settings (Roles (Define Roles.
You can find a complete list of all roles available for SAP SRM in SAP Note 1261825.
Implementation Considerations
You can access SAP SRM applications using either SAP NetWeaver Portal or the Portalindependent navigation frame.
If you choose to use SAP NetWeaver Portal, the roles, which are delivered as part of the
business package for SAP SRM define the content that is visible for each role. In this case,
the PFCG roles described here are used as authorization roles only. For each Portal role,
there is a corresponding PFCG role. For more information about the Portal roles, see the
documentation for the same Business Package for SAP Supplier Relationship Management.
If you choose to use the Portal-independent navigation frame, the PFCG roles are used to
define the content of the navigation frame, for example, the menu structure, service links, and
Web Dynpro applications. For more information, see Portal-Independent Navigation Frame.
The following sections describe the PFCG roles that are new in Enhancement Package 2 for
SAP Supplier Relationship Management 7.0 (SAP SRM 7.0). These roles are intended to be
used when all business functions are activated. If you do not use all business functions,
change the content of the roles. For more information, see section Important Information
About Roles in Enhancement Packages.
Roles that are not listed here have not been changed for the enhancement package. You can
find the documentation for the unchanged roles under Roles for SAP SRM 7.0.
If you do not activate any business functions, you can use the SAP SRM 7.0 roles.
We recommend that you do not assign two versions of the same role to one user.
For example, do not assign /SAPSRM/OP_PURCHASER_EHP1 and
/SAPSRM/OP_PURCHASER_EHP2 to the same user.
For roles containing transaction codes for an SAP ERP system, the
authorizations are not assigned automatically. Only when you edit a role using
transaction PFCG in the SAP ERP system, the system assigns default
authorizations for these transaction codes. You can then change the
authorizations according to your needs.
© SAP SE
Page 9 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
PFCG roles are also required when you use SAP NetWeaver Portal for business
user navigation, as authorizations are read from the PFCG roles.
Roles for SAP SRM
SRM Roles
PFCG
Portal
SAP SRM: Invoice
Verification Clerk
/SAPSRM/ACCOUNTANT
com.sap.pct.srm.core.ro_invoicer
SAP SRM: Administrator
/SAPSRM/ADMINISTRATO
R
com.sap.pct.srm.core.ro_srmadministr
ator
SAP SRM: Administrator
/SAPSRM/ADMINISTRATO
R_EHP1
com.sap.pct.srm.core.ro_srmadministr
ator
SAP SRM: User
Administrator
/SAPSRM/USER_ADMINIS
TRATOR
SAP SRM: Bidder
/SAPSRM/BIDDER
com.sap.pct.srm.core.ro_bidder
SAP SRM: Bidder
/SAPSRM/BIDDER_EHP1
com.sap.pct.srm.core.ro_bidder
SAP SRM: Employee
/SAPSRM/EMPLOYEE
com.sap.pct.srm.core.ro_employeeself
service
SAP SRM: Employee
/SAPSRM/EMPLOYEE_EH
P1
com.sap.pct.srm.core.ro_employeeself
service
SAP SRM Employee for
ESS
/SAPSRM/EMPLOYEE_ES
S
com.sap.pct.srm.core.ro_employeeself
service
SAP SRM: Manager
/SAPSRM/MANAGER
com.sap.pct.srm.core.ro_manager
SAP SRM: Operational
Purchaser
/SAPSRM/OP_PURCHASE
R
com.sap.pct.srm.core.ro_operationalpu
rchaser
SAP SRM: Operational
Purchaser Admin
/SAPSRM/OP_PURCHASE
R_ADMIN
SAP SRM: Operational
Purchaser
/SAPSRM/OP_PURCHASE
R_EHP2
com.sap.pct.srm.core.ro_operationalpu
rchaser
SAP SRM: Operational
Purchaser
/SAPSRM/OP_PURCHASE
R_EHP1
com.sap.pct.srm.core.ro_operationalpu
rchaser
SAP SRM: Component
Planner
/SAPSRM/PLANNER
com.sap.pct.srm.core.ro_componentpl
anner
SAP SRM: Internal
Dispatcher
/SAPSRM/RECIPIENT
com.sap.pct.srm.core.ro_goodsrecipie
nt
SAP SRM: Purchasing
Assistant
/SAPSRM/SECRETARY
com.sap.pct.srm.core.ro_purchasingas
sistant
SAP SRM: Strategic
Purchaser
/SAPSRM/ST_PURCHASE
R
com.sap.pct.srm.core.ro_strategicpurc
haser
SAP SRM: Strategic
Purchaser
/SAPSRM/ST_PURCHASE
R_EHP1
com.sap.pct.srm.core.ro_strategicpurc
haser
SAP SRM: Strategic
Purchaser
/SAPSRM/ST_PURCHASE
R_EHP2
com.sap.pct.srm.core.ro_strategicpurc
haser
© SAP SE
Page 10 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
SRM Roles
PFCG
Portal
SAP SRM: Supplier
/SAPSRM/SUPPLIER
com.sap.pct.srm.core.ro_supplier
SAP SRM: Survey Owner
/SAPSRM/SURVEY_OWN
ER
com.sap.pct.srm.core.ro_survey_owne
r
SAP SRM: Survey
Reviewer
/SAPSRM/SURVEY_REVI
EWER
com.sap.pct.srm.core.ro_survey_revie
wer
SAP SRM P2P:
Operational Purchaser
(ERP)
/SAPSRM/OP_PURCHASE
R_ERP
com.sap.pct.srm.suite.ro_operationalp
urchaser_erp
SAP SRM P2P:
Operational Purchaser
(ERP) - EHP1
/SAPSRM/OP_PURCHASE
R_ERP_EHP1
com.sap.pct.srm.suite.ro_operationalp
urchaser_erp
SAP SRM P2P:
Operational Purchaser
(ERP/SRM)
/SAPSRM/OP_PURCHASE
R_ERPSRM
com.sap.pct.srm.suite.ro_operationalp
urchaser
SAP SRM P2P:
Operational Purchaser
(ERP/SRM) - EHP1
/SAPSRM/OP_PURCHSR_
ERPSRM_EHP1
com.sap.pct.srm.suite.ro_operationalp
urchaser
SAP SRM: Strategic
Purchaser (ERP)
/SAPSRM/ST_PURCHASE
R_ERP
com.sap.pct.srm.suite.ro_strategicpurc
haser_erp
SAP SRM: Strategic
Purchaser (ERP) - EHP1
/SAPSRM/ST_PURCHASE
R_ERP_EHP1
com.sap.pct.srm.suite.ro_strategicpurc
haser_erp
SAP SRM: Strategic
Purchaser (ERP/SRM)
/SAPSRM/ST_PURCHASE
R_ERPSRM
com.sap.pct.srm.suite.ro_strategicpurc
haser
SAP SRM: Strategic
Purchaser (ERP/SRM) EHP1
/SAPSRM/ST_PURCHSR_
ERPSRM_EHP1
com.sap.pct.srm.suite.ro_strategicpurc
haser
SAP SRM One Client:
Invoice Verification Clerk
/SAPSRM/1C_INVOICER
com.sap.pct.srm.oneclnt.ro_invoicer
SAP SRM One Client:
Supplier
/SAPSRM/1C_SUPPLIER
com.sap.pct.srm.oneclnt.ro_supplier
2.2 Roles and Authorizations for SAP Supplier Life
Cycle Management
The relevant roles and authorizations for SAP SRM and SAP Supplier Life Cycle
Management can be found in SAP Note 1261825 SAP SRM 7.xx: Information on PFCG roles
and Portal roles. Attached to this note, an excel file shows the evolution and the
relationship/mapping of PFCG roles and Portal roles in SAP SRM 70x.
SAP Supplier Lifecycle Management is delivered with a set of roles that allow internal
employees or external business partners who are assigned to these roles, perform their tasks.
These roles are also referred to as PFCG roles and use the Portal-independent navigation
frame, which is based on SAP NetWeaver Business Client (HTML). You can access the roles
in the transaction Role Maintenance (PFCG). After logging on to the system, users see all the
functions that they need to process their tasks displayed on the user interface in the form of
service links. For more information, see the individual role descriptions.
© SAP SE
Page 11 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
Some roles are meant to be used only outside the firewall (Sell side roles), whereas most
roles are exclusively used behind the firewall (Buy side roles).
Roles are delivered regardless of whether you have activated a business function
or not. Enhanced roles overwrite the standard roles in your system when you
install a new support package or a new release. Standard roles are copied to the
customer namespace and are used as backups for customer-specific roles. If you
want to benefit from the new features of a role you have to adapt your customerspecific roles accordingly.
PFCG roles are also required when you use SAP NetWeaver Portal for business
user navigation, as authorizations are read from the PFCG roles.
Supplier
Lifecycle
Manageme
nt Roles
PFCG Role
Related Portal Role
Sell
Side
Buy
Side
Category
Manager
/SRMSMC/CATEGORY_MANA
GER
/SRMSMC/CATEGORY_MAN
AGER
X
Questionna
ire
Manager
/SRMSMC/QUESTIONNAIRE
_MANAGER
X
/SRMSMC/QUESTIONNAIRE_
MANAGER
Appraiser
/SRMSMC/EVALUATION_APP
RAISER
SRMSMC_APPRAISER
X
Approver
/SRMSMC/APPROVER
/SRMSMC/APPROVER
X
Translator
/SRMSMC/TRANSLATOR
/SRMSMC/TRANSLATOR
X
Initial
Supplier
/SRMSMC/SUPPLIER_INITIAL
n/a
X
Qualificatio
n Expert
/SRMSMC/QUALIFICATION_E
XPERT
/SRMSMC/QUALIFICATION_
EXPERT
X
Employee
Administrat
or
/SRMSMC/EMPLOYEE_ADMIN
ISTRATOR
/SRMSMC/EMPLOYEE_ADMI
NISTRATOR
X
Supplier
Master
Data
Manager
/SRMSMC/SUPPLIER_MASTE
R_DATA
/SRMSMC/SUPPLIER_MAST
ER_DATA
X
Administrat
or
/SRMSMC/ADMINISTRATOR
/SRMSMC/ADMINISTRATOR
X
© SAP SE
X
Page 12 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
3 SAP NetWeaver Business Client
Configuration
If you are not using SAP NetWeaver Portal and thus cannot use its navigation frame, you can
use this function to work with the applications of SAP Supplier Relationship Management
(SAP SRM) and SAP Supplier Lifecycle Management. The look and feel of the Portalindependent navigation frame is similar to the Portal-based navigation frame. The functions
available to the individual users depend on the PFCG roles, defined in transaction Role
Maintenance (PFCG) that you assign to the users.
3.1 Activate SAP NWBC Interface
3.1.1 System Requirements
Ensure that you have installed the latest and appropriate SAP frontend components.
The download path below leads you to an overview on how to install SAP frontend
components and how to apply patches. On the navigation level SAP Frontend Components,
you can select the SAP frontend components depending on your requirements.
To download the SAP frontend components, go to the Software Download Center (SWDC) on
SAP Service Marketplace:
https://service.sap.com/swdc → Support Packages and Patches → Browse our Download
Catalog → SAP Frontend Components
Download the version SAP NetWeaver Business Client 3.0 (SAP NWBC 3.0).
SAP NWBC 3.0 is released for all customers with SAP NetWeaver 7.01 SP06
against a single ABAP stack.
SAP NetWeaver Business Client 3.0 is an optional user interface connected to
SAP BP for SRM. The minimum technical prerequisite is Enhancement Package
1 Support Package Stack 6 for SAP NetWeaver 7.0 Application Server ABAP
(SAP NW 7.01 SPS06 AS ABAP). We strongly recommend using the related
application support package stack – Enhancement Package 6 Support Package
Stack 4 for SAP ERP 6.0 Application Server ABAP (SAP ERP 6.06 SPS04 AS
ABAP) as a minimum.
In addition, import the corrections referred to in SAP Note 1353538 SAP NetWeaver Business
Client 3.0 - Patch Collection. This note is also listed in the section SAP Notes and Messages
of this document.
3.1.2 Activate Portal-Independent Navigation Frame
Use
To activate the SAP NWBC interface for SAP Supplier Relationship Management and SAP
Supplier Lifecycle Management, execute the following steps:
Procedure
© SAP SE
Page 13 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
1. Access the activity using one of the following navigation options in the respective system
(SAP SRM system)
Transaction Code
SPRO
SAP IMG
SAP Supplier Relationship Management → SRM Server →
Technical Basic Settings → Portal-Independent Navigation
Frame → Activate/Deactivate Portal-Independent
Navigation Frame.
2. For the Planned Status of Customizing Switch field, change the status to Active by
choosing from the drop-down list.
3. Choose Save.
3.1.3 Deployment
Use
To deploy SAP NWBC, you must carry out the following steps.
Procedure
1. Activate the Portal-independent navigation frame in your SAP SRM system in the
Customizing of Supplier Relationship Management → SRM Server → Technical Basic
Settings → Portal-Independent Navigation Frame → Activate/Deactivate PortalIndependent Navigation Frame.
2. Check if following settings were processed:
3. In your SAP SRM system, create an HTTP connection (to your back-end system) in the
Customizing of Supplier Relationship Management → SRM Server → Technical Basic
Settings → Define RFC destination or use transaction code SM59.
Use connection type H to define the settings for HTTP connection.
4.
Enter an alias for the HTTP connection in your SAP SRM system in the Customizing of
Supplier Relationship Management → SRM Server → Technical Basic Settings → Define
System Landscape.
Under System Alias for POWL Navigation, enter the alias of the required SAP back-end
system.
5. Activate the services relevant for SAP NWBC for HTML in transaction SICFMaintain
Services.
Note: If you use the automated implementation content delivered with your rapid
deployment solution, the services for your solution are activated automatically. If you want
to check the activation use transaction SICF.
6. Enter the HTTP connection defined (without the suffix) in the customizing activity Define
System Landscape as System Alias for POWL Navigation.
For detailed information regarding the deployment of SAP NWBC, check the
following SAP Notes:
© SAP SE
SAP Note
#
Description
Component
Area
Remark
1437987
Release of
Portalindependent
SRM-EBPCA-UI
Info
This note provides an
overview of the
prerequisites for using
Page 14 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
SAP Note
#
Description
Component
Area
navigation
frame for
SRM 7.0
Remark
SAP NWBC 3.0 in SRM
7.0.
However, the required
steps for SAP NetWeaver
described in note
1437317 are already
described in note
1353538 (see section
above). No action
required at this point.
Note 1435692 is already
mentioned in the section
above and mandatory to
be applied.
Note 1430999 contains a
list of notes Only apply
these notes in case of
issues during usage. No
action is required at this
point.
1368177
SAP NWBC
v3.0 Release
on NW7.00
and NW701
BC-WD-CLTBUS
Usage
Not required – this note
contains only text and is
the starting point for the
installation of SAP NWBC
3.0. Skip the steps
mentioned in this note
and implement the
referenced SAP Notes:
1353538 (see below)
1400383 (see below)
© SAP SE
1353538
SAP
NetWeaver
Business
Client 3.0 Patch
Collection
BC-WD-CLTBUS
Usage
SAP Note 1353538 refers
to other notes. Check
which notes are required
for your system landscape
or SAP NWBC.
1400383
SAP BP:
SAP NWBC
3.0 as of
EhP4 for
SAP ERP
6.0, ABAP
Config
BC-WD-CLTBUS
Usage
This note describes in
detail how to set up SAP
NWBC. Check with your
system administrator in
case of questions. This
note requires deep basis
knowledge.
1433603
NWBC
causes locks
in Web
Dynpro apps
especially
POWLs
BC-WD-CLTBUS
Usage
Page 15 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
SAP Note
#
Description
Component
Area
1651708
Navigation to
NWBC SUS
URL for Bid
Decoupling
Scenario
SRM-SUSADM
Usage
Remark
SRM-EBPBID
SAP NetWeaver Business Client – Activate Context Menu Additional
Details
If you choose to use the Portal-independent navigation frame, the roles that are delivered as
part of the Business Package for SAP SRM cannot be used. Instead, existing authorization
roles in SAP SRM or SAP SLC (check chapter 2 for relevant roles) are used to define the
content of the navigation frame, such as the following screen elements:

Menu structure, including work centers, worksets, and service link folders

Service links necessary to start applications
Example: Shopping Cart

Applications that are started directly from a business object and not from the menu
structure
Object-based navigation (OBN) is used for indirect navigation in the Portalindependent navigation frame. The object model of the OBN provides a definition of
all business objects and their operations. The semantic business objects are mapped
in the roles to the available Web Dynpro applications.
Example: Edit Shopping Cart started from a shopping cart listed in the POWL

Applications displayed in the content area to which users navigate from the
navigation frame
Examples: Shopping Area and POWL
3.2 Activation of Services for SAP NWBC
Activate the services needed for SAP NWBC using the transaction SICF.
1. Access the activity using the following navigation options:
SICF
Transaction Code
2. On the Maintain Services screen, choose Execute (F8).
3. On the Maintain service screen, expand the virtual hosts / services node as follows and
activate all the services listed below:
default_host
sap
public
bc
icons
default_host
sap
public
bc
icons_rtl
default_host
sap
public
bc
pictograms
default_host
sap
public
bc
ur
default_host
sap
public
bc
Web
Dynpro*
default_host
sap
public
bc
webicons
© SAP SE
Page 16 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
default_host
sap
public
bsp
default_host
sap
public
icf_info*
sap
htmlb
default_host
sap
public
icman
default_host
sap
bc
bsp
sap
public
default_host
sap
bc
bsp
sap
rsr_bex_launch/
default_host
sap
bc
bsp
sap
system
default_host
sap
bc
igs_data
default_host
sap
bc
NWBC*
default_host
sap
bc
print*
default_host
sap
bc
smart_forms
default_host
sap
bc
wd_trace_tool
default_host
sap
bc
wdvd
default_host
sap
bc
Web Dynpro
kyk*
default_host
sap
bc
Web Dynpro
sap
cfs_application
default_host
sap
bc
Web Dynpro
sap
configure_*
default_host
sap
bc
Web Dynpro
sap
create_complaints_comp
default_host
sap
bc
Web Dynpro
sap
cust_cockpit_comp
default_host
sap
bc
Web Dynpro
sap
FITE_EXPENSES
default_host
sap
bc
Web Dynpro
sap
FITV_POWL_TRIPS
default_host
sap
bc
Dynpro
sap
FITV_TRIP_FORM
default_host
sap
bc
Dynpro
sap
hress_a_cats/
default_host
sap
bc
Dynpro
sap
lcm_application
default_host
sap
bc
Dynpro
sap
lo_oif_cdocs_appl
default_host
sap
bc
Dynpro
sap
lo_oif_main_app
default_host
sap
bc
Dynpro
sap
LO_OIF_OC
default_host
sap
bc
Dynpro
sap
lo_oif_reuse_cond_appl
default_host
sap
bc
Dynpro
sap
lo_oif_vcfg_appl
default_host
sap
bc
Dynpro
sap
lord*
default_host
sap
bc
Dynpro
sap
mmpur_ui_pr_app
default_host
sap
bc
Dynpro
sap
mmpur_vndctcdta_app
default_host
sap
bc
Dynpro
sap
mmsrv_sp_details_app
default_host
sap
bc
Dynpro
sap
mt_order_app
default_host
sap
bc
Dynpro
sap
o2c_*
default_host
sap
bc
Dynpro
sap
POWL*
default_host
sap
bc
Dynpro
sap
psu_md_wui_wda_pss_oif_cfg
default_host
sap
bc
Dynpro
sap
qimt_notification_app
default_host
sap
bc
Dynpro
sap
sawe_sa
default_host
sap
bc
Dynpro
sap
sawe_time_ps call
default_host
sap
bc
Dynpro
sap
wd_*
default_host
sap
bc
Dynpro
sap
wdhc_application
default_host
sap
bc
Dynpro
sap
WDK*
bc
*activate all services.
© SAP SE
Page 17 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
4. Choose Back.
3.2.1 Activation of Services for SAP SRM
Activate the services needed for the SAP SRM using transaction SICF.
1. Access the activity using the following navigation options:
SICF
Transaction Code
2. On the Maintain Services screen, choose Execute (F8).
3. On the Maintain service screen, expand the virtual hosts / services node as follows and
activate all the services listed below:
default_host
sap
bc
Dynpro
sapsrm*
default_host
sap
bc
Dynpro
sap
ibo_wda_inbox
default_host
sap
bc
Dynpro
sap
ibo_wda_wfl_substit
default_host
sap
bc
Dynpro
sap
ibo_wdc_wfl_substit
default_host
sap
bc
bsp
sap
bbp_ve_service
default_host
sap
bc
bsp
sap
smart_forms
default_host
sap
bc
bsp
sapsrm*
default_host
sap
sapsrm*
default_host
sap
bw
Bex
*activate all services.
4. Choose Back.
3.2.2 Activation of Special Services for SAP SRM
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SICF_INST
2. On the ICF: Report for Activating Special Service During Installation screen, enter the
Technical Name '*' and choose Execute to activate all services.
3.2.3 Activation of Services for SAP Supplier Lifecycle
Management
Activate the services needed for the SAP Supplier Lifecycle Management Buyside using
transaction SICF.
1. Access the activity using the following navigation options:
Transaction Code
SICF
2. On the Maintain Services screen, choose Execute (F8).
3. On the Maintain service screen, expand the virtual hosts / services node as follows and
activate all the services listed below:
© SAP SE
Page 18 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
default_host
sap
Public
Bc
Ur
default_host
sap
Public
Bc
Icons
default_host
sap
Public
Bc
Icons_rtl
default_host
sap
Public
Bc
Webicons
default_host
sap
Public
Bc
Pictograms
default_host
sap
Public
Bc
Web
Dynpro
adobeChallenge
default_host
sap
Public
Bc
Web
Dynpro
Mimes
default_host
sap
Public
Bc
Web
Dynpro
Ssr
default_host
sap
Public
Bc
Web
Dynpro
viewDesigner
default_host
sap
Public
Bc
myssocntl
default_host
sap
Bc
Bsp
Srmsmc
Qua_cmn
default_host
sap
Bc
Bsp
Srmsmc
Evaluation
default_host
sap
Bc
Bsp
Srmsmc
Sup_delta
default_host
sap
Bc
Nwbc
Smc
default_host
sap
Bc
Web Dynpro
Sap
Powl
default_host
sap
Bc
Web Dynpro
Sap
Ibo_wda_inbox
default_host
sap
Bc
Web Dynpro
Srmsmc
Wda_emp_det_bcard
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_I_BP_SUPPLIER
default_host
sap
Public
Web Dynpro
Srmsmc
WDA_I_BP_TRANSFER
default_host
sap
Public
Web Dynpro
Srmsmc
WDA_I_QNR_OVP
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_I_SEP_OVP
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_I_SES
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_I_SEV_OVP
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_I_SQP_OVP
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_I_SQQ_OVP
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_PUC
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_QLB_OVP_MAN
default_host
sap
Bc
Web Dynpro
Srmsmc
WDA_QLB_OVP_TRNS
Activate the services needed for the SAP Supplier Lifecycle Management Sellside using
transaction SICF.
1. Access the activity using the following navigation options:
SICF
Transaction Code
2. On the Maintain Services screen, choose Execute (F8).
3. On the Maintain service screen, expand the virtual hosts / services node as follows and
activate all the services listed below:
default_host
Sap
Bc
Bsp
Srmsmc
ros
default_host
Sap
Bc
Bsp
Srmsmc
System
© SAP SE
Page 19 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
default_host
Sap
Bc
Bsp
Srmsmc
Qua_cmn
default_host
Sap
Bc
Bsp
Srmsmc
Ros_ext
default_host
Sap
Bc
Bsp
Srmsmc
Ros_ext2
default_host
Sap
Bc
Bsp
Srmsmc
S3q_ext
default_host
Sap
Bc
Bsp
Srmsmc
Sup_delta
default_host
Sap
Bc
Bsp
Sap
Thtmlb_scipts
default_host
Sap
Bc
Bsp
Sap
Thtmlb_styles
default_host
Sap
Webcuif
Uif_callback
default_host
Sap
Bc
Bsp
Sap
System
default_host
Sap
Bc
Bsp
Sap
Public
Bc
default_host
Sap
Public
Bsp
Sap
Public
Bc
default_host
Sap
Public
Bsp
Sap
System
default_host
Sap
Public
Bsp
Sap
Htmlb
default_host
Sap
Public
Bc
default_host
Sap
Public
Bc
ur
4 SAP NetWeaver Portal Configuration
SAP NetWeaver Portal serves as a single point of entry to the applications,
services, and information of the organization.
Running SAP NetWeaver Portal is an IT scenario providing role-based and
secure access to all types of applications, services, and information in an
enterprise workset environment.
4.1 Installation of the Business Package
4.1.1 System Requirements
Requirements for integrating SAP SRM and SAP Supplier Lifecycle Management to
SAP NetWeaver Portal can be found in the Product Availability Matrix (PAM) at
http://service.sap.com/pam.
Check which Portal Roles have to be maintained according to the scenario you have selected
(see details in chapter 2).
4.1.2 Important SAP Notes
Check the following SAP Notes before you start the implementation:
SAP Note #
Title
1457932
BP for SRM 7.0 EhP1: Installing the Business Packages
1178469
BP for SRM 7.0: Additional installation information
1178470
BP for SRM 7.XX: Additional upgrade / migration information
1232945
BP for SRM 7.XX: Installing the Business Packages
© SAP SE
Page 20 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
1732280
Enable portal for bid decoupling in SUS
1649846
BP for SRM 7.0 EhP2: Installation Information
1772459
Bid Security Enhancement: Error while creating RFx
4.1.3 Download Business Packages
4.1.3.1 Business Packages for SAP SRM 7.0 Enhancement
Package 2
The Business Package is shipped with SAP SRM 7.0 Enhancement Package 2 or the
SAP Business Suite DVD set. It can be found on the Java Component DVD.
After installing the version delivered on the DVD, upgrade to the version, which fits to the
version of SAP SRM 7.2 installed in your landscape.
To download a support package of the Business Package, use the Maintenance Optimizer in
SAP Solution Manager. By downloading a SP stack for the SAP SRM 7.0 installation you will
automatically get the corresponding version of the Business Package.
Alternatively, you can download the Business Package manually at
http://service.sap.com/patches → A - Z Index → S → SAP SRM → SAP SRM Enhancement
Package → EHP2 for SAP SRM 7 → Entry by Component → Portal Content.
Download all the packages listed there.
Portal Content for SRM:

BP ERP05 BUYER 1.61

BP ERP05 COMMON PARTS 1.61

BP SRM 7.02

SRM JAVATOOLBOX 7.0

Group of Alternative Components
4.1.3.2 Business Packages for SAP Supplier Lifecycle
Management
To download a support package of the Business Package, use the Maintenance Optimizer in
SAP Solution Manager. By downloading a SP stack for the SAP SLC 1.0 installation you will
automatically get the corresponding version of the Business Package.
Alternatively, you can download the Business Package manually at
http://service.sap.com/patches → A - Z Index → S → SAP Supplier Lifecycle Mgmt. → SAP
Suppl.Lifecycle_Mgmt. 1.0. → Comprised Software Component Versions → BP_SLC_100.
4.1.4 Content of the Business Packages
For details on the roles, worksets, pages, and the iViews shipped with the Business
Packages, refer to the SAP SRM 7.0 EhP2 documentation on the SAP Help Portal at
http://help.sap.com/srm-main.
© SAP SE
Page 21 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
4.1.5 Deployment of the Business Packages
To deploy the Business Packages, use Java Support Package Manager (JSPM). For more
information on JSPM, refer to http://service.sap.com/jspm.
4.1.6 Check Business Package Deployment
To verify if all necessary Business Packages are deployed in SAP NetWeaver Portal,
navigate to
Content Administration → Portal Content Management
Business Objects
ERP Common Parts
SRM
Portal Content
Content Provided by
SAP
Specialist
Buyer
ERP60 EHP6
iViews
Pages
Roles
Transport packages
Wordsets
SAP SRM 7.0
Common
Core
Employee SelfService
PPS
Suite
Supplier Lifecycle
Management
iViews
Roles
In the Portal content structure (shown above), the standard structure (delivered by SAP) is
shown.
The highlighted solutions are available if the appropriate Business Packages were imported
successfully.
4.1.7 Check Portal Content Permissions
Check the Portal content permissions in all folders of the structure mentioned in chapter 5.1.6,
to see if the Business Package content is available for the objects in the following chapter.
To check permissions, select each end user content entry (which is shown on level SAP SRM
7.0 -> Common or Core or Employee Self-Service for example) right-click and select Open
(Permission.
© SAP SE
Page 22 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
Depending on the customer’s security policy, the user role group permission for SAP
SRM/SAP SLC-specific functionality can be assigned to SAP SRM users and roles.
4.2 Basic Configuration
4.2.1 Portal System Objects
To use the Business Package, create system objects in the Portal, which point to the SRM
server (definition of the connected SAP SRM system) and the SLC Sellside. You have to
assign the system alias SAP_SRM to the SRM server (for all SRM scenarios and Supplier
Lifecycle Management Buyside), SAP_SUS (for SRM decoupled bidding) to the SAP SUS
server and SAP_SLC to the SLC Sellside (Supplier Lifecycle Management Sellside) to this
system object.
The system landscape overview displays the current status of all systems in use by the
Portal. The overview acts as entry point for all system-related tasks, including assigning
system aliases, testing connections, configuring new systems, and editing the properties of
existing systems.
Procedure
1. Log on to the Portal as system administrator.
2. Navigate to System Administration → System Landscape.
3. Expand the Portal Content Structure
4. Select the appropriate folder (select the folder in which the system object should be stored
(Supplier Lifecycle Management for example), right-click on folder,
Or create a new Folder for your customer-specific content (right-click on Portal content,
Choose New → Folder
5. New → System to create a system by using a template (such as HTTP System, SAP
system using dedicated application server, SAP System with load balancing)
Depending on the system, either choose SAP system using dedicated application server
or SAP system with load balancing. A dedicated application server is used for test and
quality systems, system with load balancing is used for test, quality, and productive
system.
Fill the following parameter categories (entries are examples):
1. Maintain the System Name
2. The System ID
3. The Master language.
4. In the next step, you can maintain the Properties.
5. Select from the Properties following categories: Connector, User Management, and Web
Application Server (Web AS)
Connector
For template Connector (dedicated application server) maintain following required settings
(values mentioned in the table are just examples)
Application Host
© SAP SE
iwdfvm3364.wdf.sap.corp
Page 23 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
Gateway Host
iwdfvm3364.wdf.sap.corp
Gateway Service
3300
Remote Host Type
3
SAP Client
800
SAP System ID (SID)
AT1
SAP System Number
00
Server Port
3200
SNC QOP (Security Level)
0
System Type
SAP_R3
Trace Mode
0
For template ‘Connector (load balancing)’ maintain following required settings (values
mentioned in the table are just examples):
Group
SPACE
Logical System Name
SOLCLNT001
Message Server
dewdfias52.wdf.sap.corp
Remote Host Type
3
SAP Client
001
SAP System ID (SID)
SOL
SNC Mode
0
SNC QOP (Security Level)
0
System Type
SAP_R3
Trace Mode
0
User Management
For category ‘User Management’ maintain following required settings (values mentioned in
the table are just examples):
Authentication Ticket Type
SAP Logon Ticket
Logon Method
SAPLOGONTICKET
User Mapping Type
Admin, user
Web Application Server (Web AS)
For category ‘Web Application Server (Web AS)’ maintain following required settings (values
mentioned in the table are just examples):
Web AS Description
SR7 WAS
Web AS Host Name
Iwdfvm3414.wdf.sap.corp:8020
Web AS Protocol
http
6. Choose Save.
© SAP SE
Page 24 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
4.2.1.1 Assign a System Alias
Procedure
To assign a system alias, use the alias name that corresponds to each back-end system:
Component
Alias
SRM
SAP_SRM
SLC
SAP_SLC
SUS
SAP_SUS
BI
SAP_BW
ERP (MM)
SAP_ECC_Procurement
1. Navigate to System Administration → System Landscape.
2. Select the system object you have created before.
3. Choose Open → System Aliases.
4. Enter an alias from the table above and choose Add (for example, add the alias
SAP_SRM and mark this as default).
5. Save your entry.
4.2.2 Permission to the Portal Content
After the installation, only the Portal role super_admin_role has access to the Portal content.
To be able to use the Portal content in all scenarios, permissions on the folders Portal
Content and System Objects have to be set. You have to add the group Everyone, or a user
group which includes all users who are supposed to work with SAP SRM, SAP SUS, and SAP
SLC. Add this group, and set the permissions for content administration (Administrator
column) to Read and select the option End user.
4.2.3 Single Sign-On Configuration
For configuring SSO between SAP NetWeaver Portal and SAP SRM 7.0 refer to
http://wiki.sdn.sap.com/wiki/display/SRM/Enabling+SSO+for+SRM+and+Portal.
4.2.3.1 Export the Certificate
The export of the certificate is dependent on the SAP NetWeaver Portal stack.
SAP NetWeaver Portal 7.0x
Logon to SAP NetWeaver Portal with a user assigned to the Administrators group.
1. http://<FQDN>:<port>/irj/portal/
Full qualified domain name is required, for example,
http://vmw3180.wdf.sap.corp:58800/irij/portal/
2. Navigate to System Administration → System Configuration → Keystore Administration.
3. In the content area, choose the Download verfiy.der File button.
© SAP SE
Page 25 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
4. After downloading the file, un-zip it.
5. Save the file locally.
SAP NetWeaver Portal 7.30
Logon to SAP NetWeaver Portal with a user assigned to the Administrators group.
1. http://<FQDN>:<port>/NWA
2. Navigate to Configuration → Security.
3. Choose Certificates and Keys.
4. In the table, select the TicketKeystore line.
5. In the table below, select the entry SAPLogonTicketKeypair-cert.
6. Choose Export Entry.
7. Download in the format Binary X.509.
4.2.3.2 ABAP Stack
Check the profile parameters for Single Sign-On in the SAP SRM back-end system.
1. Logon to the ABAP system.
2. Start transaction RZ10.
3. Select the profile DEFAULT.
4. Select Extended Maintenance.
5. Choose Display.
6. Check the parameter.

“login/accept_sso2_ticket = 1”.

“login/create_sso2_ticket = 2”.
7. Double check the other profiles (for example, instance profile) and remove the two
parameters if they are included in any other profile.
4.2.3.3 Import Certificate
Import the SAP NetWeaver Portal certificate to the ABAP Server:
1. Logon to the ABAP system.
2. Start transaction STRUSTSSO2.
3. Select Import Certificate.
4. Choose the file you have downloaded before.
5. Confirm the dialog box that is displayed.
6. Choose Add to Certificate List.
7. Choose Add to ACL.
8. As the system ID, enter the System ID (SID) of the SAP Portal system.
9. As the client, enter 000.
10. Save your entries.
© SAP SE
Page 26 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
5 User Management Setup
5.1 Authentication
In most cases, you configure the Portal for single sign-on against the connected systems.
There is local assignment to roles, which means that every user needs roles in SAP
NetWeaver Portal as well as in SAP SRM.
The user name must be identical in the AS-ABAP (SRM) and the AS-JAVA (Portal). However,
in each system you have to assign individual roles.
SAP Logon ticket:
In the SAP Logon ticket-based communication, no password is used.
Certificate (X.509):

A PKI (Public Key Infrastructure) is required.

For all systems, which are involved in the communication, the base certificate has to be
installed. Therefore, trust the certificates signed by the certificate authority.

An individual certificate must be assigned to each user.
5.2 User Management Scenarios
There are a number of potential scenarios for user management:

Use an Application Server ABAP as data source.

Use the local SAP NetWeaver Portal database as data source.

Use a LDAP Directory as data source.
5.2.1 User Store: Database
After the installation of SAP NetWeaver Portal, the local database is set as the default user
store. Since SAP PI and SAP Solution Manager are still available as dual stack systems,
these are the only exceptions. After the installation of SAP PI or SAP Solution Manager, the
default user store of the Java stack is the ABAP system.
It is not recommended using the local database, as the maintenance effort is high.
5.2.2 User Store: ABAP
If SAP NetWeaver Portal is only used together with the SAP SRM system, you can configure
it to make use of the SAP SRM system users. This means the users created in the SAP SRM
system are automatically available in SAP NetWeaver Portal.
The roles created in the SAP SRM system are visible as groups in SAP NetWeaver Portal.
Therefore, the assignment of a user to an ABAP role leads to an assignment of a user to a
group in SAP NetWeaver Portal.
© SAP SE
Page 27 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
SAP SRM
SAP Netweaver Portal
User
User
ABAP
Role
Group
Virtual
representation of
ABAP user and
ABAP roles
Portal
Role
To set up the user store, follow the steps below:
1. Logon to SAP NetWeaver Portal with a user assigned to the Administrators group:
http://<FQDN>:<port>/irj/portal/
2. Navigate to System Administration → System Configuration → UME Configuration.
3. Choose the Modify Configuration button.
4. In the dropdown list of Data Source, select ABAP System.
5. After the screen has refreshed, select the ABAP System tab.
6. For general connection settings, enter a user ID and password of a user who has the role
SAP_BC_JSF_COMMUNICATION assigned in the ABAP system that you want to use as
the user store.
7. Specify the system data for the ABAP system you want to use as the user store. The
recommendation is to use a load balanced connection.
8. After performing the configuration settings, you have to restart SAP NetWeaver Portal to
activate the settings.
5.2.3 User Store: LDAP
The usage of a LDAP directory server is recommended in heterogeneous landscapes. This
reduces the maintenance efforts and guarantees a homogenous user management.
The configuration is akin to the configuration of the ABAP user store.
To set up the user store, follow the steps below:
1. Logon to SAP NetWeaver Portal with a user assigned to the Administrators group:
http://<FQDN>:<port>/irj/portal/
2. Navigate to: System Administration → System Configuration → UME Configuration.
3. Choose the Modify Configuration button.
4. In the dropdown list of Data Source, select the LDAP directory server which is in use.
5. After the screen has refreshed, select the LDAP Server tab.
6. Enter a user ID and password of a user who has the required permissions to modify
attributes in the LDAP. Additionally, you need to enter the FQDN of the server which is
hosting the LDAP services. In the fields User Path and Group Path, you do not need to
© SAP SE
Page 28 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
enter a valid LDAP path to the organizational units in the directory where the
corresponding objects are stored.
7. After doing the configuration, you have to restart SAP NetWeaver Portal to activate the
settings.
6 Universal Worklist Configuration
In SAP SRM, the Universal Worklist (UWL) is used as central inbox for all workflow items.
Features of the UWL are:

It provides a unified and centralized way to access your work and the relevant
information.

It aggregates workflow task items from multiple and different systems in one universal
list.

It displays additional information as required from document and object repositories,
including attachments and other details.

It enables you to make direct decisions and actions.

It helps you to personalize the way work items are presented.

It enables you to assign an additional user to your work items as a substitute in case
of planned or unplanned absence.
6.1 UWL Configuration
6.1.1 System Connection
To use the UWL, you have to set up a connection to all the SAP back-end systems whose
work items shall be collected. A system connection for the SAP SRM back-end system must
already exist.
1. Logon to the Portal.
2. Navigate to: System Administration (System Configuration.
3. In Detailed Navigation, select Universal Worklist & Workflow (Universal Worklist –
Administration.
Assign a system object to the UWL (for example, to integrate SRM inbox to Portal UWL)
1. Choose New.
2. Create a system connection with type WebFlow Connector and save your settings.
3. Create a system connection with type AlertConnector and save your settings.
4. Having created the two connections, choose Register for both connections in the UWL
system overview.
Before you use Register, read and process SAP Note 1133821.
Register will check the SRM user for required authorizations, for example,
SAP_ALL.
© SAP SE
Page 29 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
6.1.2 Set UWL Refresh Handling
The UWL keeps a cache of work items retrieved from the back-end systems. This cache is
invalidated every 5 min. whenever a user chooses Refresh. Automatic refresh of the UWL
from the cache is a separate setting.
6.1.2.1 Refresh Time from Cache
By default, the UWL waits 20 sec. before refreshing the display from the cache. In the
meanwhile, the message Waiting for refresh is displayed.
You can reduce this time to fit customer needs by changing the following attributes:

Wait duration before calling provider on loading preview

Wait duration before calling providers on loading of UWL

Wait duration for UI refresh while waiting for update
6.1.2.2 Cache Validity
To set the validity of the UWL cache, proceed as follows:
Logon to SAP NetWeaver Portal with a user assigned to the Administrators group.
1. http://<FQDN>:<port>/irj/portal/
2. Navigate to System Administration → System Configuration → Universal Worklist &
Workflow
3. Open the Universal Worklist Service Configuration tray.
4. Choose Edit.
5. Change the parameter Default Cache Validity Period, in Minutes as required.
6.2 Customizing the UWL iView
6.2.1 Hide Navigation Panel
For small screen resolutions, you might want to hide the navigation panel from the start page
or the page containing the UWL iView.
1. Open the page or role from the PCD folder, which contains the iView of the UWL.
2. The following attributes of the navigation panel need to be changed as follows:
iView Attribute
Recommended Value
Standard Value
Initial State of navigation panel
Close
Open
6.2.2 Hide Connection Errors
If there is an error in the connection to a system, the end user sees an error message. This
message can be switched off. This is not recommended.
1. Open the page or role from the PCD folder which contains the iView of the UWL.
2. The following attributes decide which information the user is shown in case of
connection errors:
© SAP SE
Page 30 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
iView Attribute
Recommended Value
Standard Value
Show connection status
None
ShowIndicateError
6.3 Customizing the UWL Configuration File
6.3.1 Download UWL Configuration File
With SAP SRM 7.0 EhP1, a separate UWL configuration file is delivered for displaying alerts
and tasks within the UWL iView.
The UWL configuration file is delivered as part of the SAP SRM 7.0 Business Package
(configuration name: com.sap.pct.srm.core).
1. Download the configuration file locally (in zip-format). Go to System Administration →
System Configuration → Universal Worklist & Workflow Universal Worklist Administration.
2.
Choose Manage Item Types and View definitions.
6.3.2 Upload Configuration File
1. After changing the XML file, put the XML configuration file into the .zip archive and upload
the modified version into the Portal.
2. Go to Upload New Configuration, specify the configuration name, select the .zip file, and
upload it to the portal. If you are asked to overwrite the current configuration, choose Yes.
3. Set the High Priority flag (default for new configuration).
6.3.3 Change Tab Order / Remove Tabs from UWL
In case of customer-specific requirements to change or remove tabs from the UWL, extract
the zipped file and edit the com.sap.pct.srm.core.xml file by opening the file with an editor. Go
to the end of the xml file where you can find the Navigation Definition part.
1. Change the order of the entries to have the Tasks tab as the first entry in the UWL
screen.
2. If you want to remove the tabs, then just remove them from the configuration:
© SAP SE
Page 31 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
In the above example, the Notification tab page is hidden by commenting the marked section.
6.3.4 Change Translations
The customer may want to change the names of the tabs. For example, they may want to see
My Alerts instead of Alerts or My Inbox instead of Tasks. The names of the tabs are specified
in the corresponding language files within the UWL configuration .zip file.
To change the names, open the corresponding language file from the .zip file. Here, the
English one serves as an example:
1. Open com.sap.pct.srm.core_en.properties.
2. The translations are referenced by the attribute ReferenceBundle in the XML
configuration file.
3. Open the language properties file with an editor like word pad. Change the name of the
Alerts tab to My Alerts.
Original Version:
com.sap.pct.srm.core.alerts=Alerts
com.sap.pct.srm.core.alertsLong=Alerts
New Version:
com.sap.pct.srm.core.alerts=My Alerts
© SAP SE
Page 32 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
com.sap.pct.srm.core.alertsLong=My Alerts
4. Save the language file, put it back to the UWL .zip file and upload the configuration.
6.3.5 Columns in the UWL
You can easily change the columns to be displayed in the UWL, and also their sequence.
To do so, open the UWL configuration XML file and follow the steps below:
1. Open the file com.sap.pct.srm.core.xml.
2. Look up the tag View. Look for the attribute ColumnOrder. In this attribute, all columns are
listed in the sequence they should be shown in the UI. Rework the file as needed and
upload it as described above.
6.3.6 Display Refresh Button
The refresh functionality is hard to find for new users, but you can set it to be displayed as a
separate button. The download configuration is as usual.
1. Go to the line View: Tasks and scroll down to the line </AllowedFilters>.
2. After that line, add a new action called Refresh.
3. Insert the closing tag.
4. Save your configuration and upload it into the Portal.
Now the button is displayed separately.
6.3.7 Remove Sections from Preview Pane
Some default sections in the UWL preview pane are not used by SRM. Open the page or role
from the PCD folder which contains the iView of the UWL. The following sections of the iView
can be hidden by filling in the following values.
iView Attribute
Value
List of preview sections to hide
Attributes, Attachments, Notes
6.3.8 Remove Actions from Preview Pane
The UWL preview pane offers actions to the end user, which are partly not applicable to SRM
workflow items. The following actions of the iView can be hidden by filling in the following
values:
iView Attribute
Value
List of UWL Actions to exclude
manageAttachments, launchSAPDetails,
viewSimilar
6.3.9 Remove Actions from Specific Workitems
If you want to remove actions not via UWL iView but specifically for single workitems, you can
do this in the UWL configuration file as well.
1. Download the file as usual.
© SAP SE
Page 33 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
2. Navigate to each of the workitems you like to change.
3. Within this ItemType section, you find the actions definition.
4. To disable the action Print, change the XML file as shown below:
5. Save and upload the file again.
© SAP SE
Page 34 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
7 Customize the Portal
In case customer-specific changes of the SAP standard are required you can make the
following customizing settings:
7.1 Standard Look and Feel
Having worked through chapter 2 and 3, the Portal is connected to the SAP SRM system.
Assuming the SAP SRM system is fully customized, and the Portal roles and SAP SRM roles
are assigned to your user, you should receive the following screen schema: Employee SelfService → Shopping → Shopping Area → Shopping cart.
7.1.1 Create a Folder for Customer Objects
For objects created during implementation, create a dedicated folder in the Portal content
directory. Do not give prefixes for folders, only for objects. The folder structure should reflect
the customer's needs. The folder structure must be defined during the project. One option of
structuring might be to collect all objects below one folder representing the customer. Another
option is to structure the folders based on projects which are using the Portal.
7.1.2 Customizing the Framework Page
Objective:
1. The help link in the Portal should point to a customer-specific help site.
2. The search engine might not be used by the customer, thus the search input field is to be
removed from the screen.
Do not modify the default framework page, but copy it to the customer namespace.
The default framework page is named:
pcd:portal_content/com.sap.pct/every_user/general/com.sap.portal.frameworkpage
The default components of the framework page are:
Portal Head
com.sap.portal.masthead
→ Change
Tool Area
com.sap.portal.toolAreaiView
Disable if you do not use
the search engine
Top Level Navigation
com.sap.portal.topLevelNavigationiView
Page header bar
com.sap.portal.pageToolbar
Desktop body
com.sap.portal.innerpage
7.1.3 Hide Search Field
Disable the following iView within the copied framework page:
Mark the iView in the framework page, uncheck Visible.
Object
Customer copy of com.sap.portal.frameworkpage
Property
Disable iView com.sap.portal.toolAreaiView
© SAP SE
Page 35 of 39
SRM – UI Integration (S06): Configuration Guide
SAP Best Practices
7.1.4 Change Portal Help Link
In the topmost part of the Portal you will find a link to the Help pages. To change this link
according to your needs, change the following properties of (delta-linked!) iView.
Mark the iView in the framework page, choose Properties, and change the Property “HelpUrl”:
Object
Customer copy of com.sap.portal.frameworkpage
iView
com.sap.portal.masthead
Property
HelpURL
Value
Absolute or relative <URL>
7.1.5 Portal Content Translation
This chapter describes the process for translating Portal content by which we can achieve
internationalization. SAP NetWeaver Portal provides a process for translating texts of Portal
objects (iViews, pages, worksets, roles, systems, and so on). A more detailed version is
available on the SAP SRM Wiki:
http://wiki.sdn.sap.com/wiki/display/SRM/Translation+of+Enterprise+Portal+Content
7.1.5.1 Create a Translation Worklist
To create a worklist, you need at least a read/write permission for the Portal Catalog folder in
which you want to create the object.
In the delivered role for content administration, choose Content Administration → Portal
Content → Translation Worklist Coordination.
Place the cursor on a folder in the Portal Catalog; choose New and right-click on the
Translation Worklist button.
For Step 1: General Properties, enter the following values:
1. Translation Worklist Name: Name of the worklist (required)
2. Translation Worklist ID: ID of the worklist (required)
3. Translation Worklist ID Prefix: You can enter an optional prefix for the worklist. We
recommend using a namespace prefix and only include objects in the worklist if they have
this prefix in their name.
4. Master Language: Master language (required)
5. Description: Description (optional)
In Step 2: Summary, you can check the entries you have made so far. Choose Finish.
If you do not want the worklist to be opened immediately after the generation process for
editing, deselect the option Open for editing when the wizard completes.
The wizard generates the new object and stores it in the indicated folder in the Portal Catalog.
7.1.5.2 Assigning Texts and Releasing Worklists
You can add a number of objects to a worklist at the same time. To do so, choose a folder in
the Portal Catalog and right-click on Add all objects to translation worklist.
The worklist with the list of all added objects is displayed as below. The worklist itself is also
part of the list.
© SAP SE
Page 36 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
You can either select the necessary objects from the list, or you can select all of them by
choosing Select all.
If you would like to include dependent objects when you generate the worklist (for example,
all objects that are in a role and their source objects), you must select the option Include all
objects on which the translated objects depend. Dependent objects are not included in the
default setting. If you want to include dependent objects, you can define a namespace filter so
that only objects having a certain namespace prefix are added. If the worklist has a
namespace prefix, it is automatically entered here.
7.1.5.3 Generate the Translation Data
To generate the translation data, select Generate Translation Data. You can now exclude
certain objects from the worklist by selecting and deleting them with the Remove objects
option.
7.1.5.4 Release the Worklist for Translation
The status of the worklist is now Released for translation.
In this case, you cannot add any more objects to the worklist. You can cancel the release. To
do so, choose Cancel Release. You then return to Step 3 of this procedure. The worklist
again has the status New. You can again add objects, generate the worklist, and then release
it for translation.
7.1.5.5 Searching for the Worklists and Uploading
translations
1. Choose Content Administration (Portal Content Translation (Worklist Translation.
2. Find a worklist by entering an ID or with a generic search. The worklists found are listed.
7.1.5.6 Define the Source and Target Languages
You can also define Raw Texts as the source and target languages. These are texts that
have no language code. For example, Raw texts can be used as source language when you
translate badly written English into standard English.
7.1.5.7 Choose Load for Translation
A list of all translated text strings is displayed, sorted in increasing order by number. You can
now translate the texts. Select the Load for Translation button.
7.1.5.8 Translating Texts
1. You see the list of texts to be translated. Sort the list by the text string number (increasing
or decreasing), source and target language, status, or object ID.
2. Select a text string with status Not Translated. The text string is placed in an area below
the list of texts to be translated.
3. Enter the source text in the reserved area. With Copy Source Text, you can copy the
source text directly into the area for the target language.
A worklist does not need to be completely translated before it can be set to status translated.
A worklist can be set to translated at any time, even if only part of a worklist has been
translated. To change the status, find the worklist, select it, and choose Mark as Translated.
7.1.5.9 Publishing Translations
Publishing a translation means that the translated texts are written back to the objects to
which they belong (for example, the translated title).
© SAP SE
Page 37 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
1. In the Portal Catalog, search for the worklist you want to publish and choose the
corresponding object with a right-click.
2. Choose Open (Object
3. When the translation worklist has opened, choose Publish Translation.
The texts are now imported into the database.
© SAP SE
Page 38 of 39
SAP Best Practices
SRM – UI Integration (S06): Configuration Guide
8 Where to Find More Information
1. RKT Material for SAP SRM: http://service.sap.com/rkt-srm
2. Training Courses:

SAPEP - SAP NetWeaver Portal Fundamentals

EP200 - SAP NetWeaver Portal System Administration

ADM200 - Administration AS Java 7.0

EP600 - Configuration of the Universal Worklist
3. Praxishandbuch SAP NetWeaver Portal (ISBN 978-3-8362-1077-5)
4. SAP NetWeaver Portal (ISBN 978-3-8362-1025-6) - German version
5. SAP NetWeaver Portal (ISBN 978-1-59229-145-8) - English version
9 Tips
9.1 Http or Https
You have to ensure that you do not switch between http and https.
In case you defined the usage of http in Portal (show path how to find the area in portal where
to define the setting) you should also define the http usage in the corresponding SAP SRM
system. Otherwise the system cannot be reached.
9.2 Switch between SAP NetWeaver Portal and SAP
NetWeaver Business Client
The authorization roles, defined and maintained in the Role Maintenance transaction (PFCG),
correspond to the SAP NetWeaver Portal roles as described in SAP Note1261825.
If you migrate from a system landscape with SAP NetWeaver Portal to a
landscape without a portal and you have customer-specific portal roles, you
cannot migrate these roles automatically. Instead, you can use the Role
Maintenance transaction (PFCG) to either adapt the roles delivered by SAP or to
model new roles that match the portal roles you were using previously.
© SAP SE
Page 39 of 39