SAP SRM User Interface Add-On 1.0 Configuration

Transcription

SAP SRM
User Interface Add-On 1.0
Configuration
Version 5.2.3
Product version : SAP SRM User Interface Add-On 1.0 SP02
Copyright
© 2014 SAP AG 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 AG. The information contained herein may be changed
without prior notice.
SAP and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany
and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices. Some software products marketed by SAP AG
and its distributors contain proprietary software components of other software vendors. National
product specifications may vary.
These materials are provided by SAP AG or an SAP affiliate company for informational
purposes only, without representation or warranty of any kind, and SAP AG or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP AG 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 AG 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 AG’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 AG 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.
History of Changes
Version
Important Changes
1.0 (July 3, 2013)
First version
2.0 (July 30, 2013)
Catalog extraction and indexing for cross catalog
search explained.
MDM Catalog Importing Improvements. Document is
now based on SP02 of SRM UI Add-on 1.0.
Corrections to the topic ‘Enable Search Results for
Product Categories Assigned to a User’
Version updated with configuration specific to Fiori
3.0 (Sep 12, 2013)
4.0 (Sep 24, 2013)
5.0 (Jan, 27,2014)
5.2 (Feb 5, 2014)
5.2.2 (April 16, 2014)
5.2.3 (Jan 12, 2016)
Version updated with services related to Fiori AppMy Shopping Cart (section 1.4.1)
Corrections to services related to My Shopping Cart
(1.4.1)
Topic Control Advanced Features added
Table of Contents
1
Basic Settings for Configuring SRM User Interface Add-On 1.0 ............................................................ 6
1.1
Configure SAP NetWeaver Gateway ............................................................................................. 6
1.1.1
Pre-requisites ........................................................................................................................ 6
1.1.2
Set Profile Parameters .......................................................................................................... 7
1.1.3
Manage System Alias ............................................................................................................ 7
1.1.4
Maintain Gateway Services ................................................................................................... 7
1.1.5
Activate ICF Services ............................................................................................................. 9
1.1.6
Setting Virus Scan profile for SAP Netweaver Gateway ..................................................... 10
1.2
Manage Roles .............................................................................................................................. 10
1.2.1
Generate Authorization Profiles ......................................................................................... 10
1.2.2
Assign Roles to Users .......................................................................................................... 10
1.2.3
Enable/Disable Advanced Features to Selected Users ....................................................... 11
1.3
Setting Number Ranges .............................................................................................................. 12
1.3.1
Define Number Range for Temporary Shopping Cart ......................................................... 12
1.3.2
Define Number Range for Search Terms ............................................................................ 12
1.4
Enable SICF Services .................................................................................................................... 13
1.4.1
Activate SICF Services.......................................................................................................... 13
1.4.2
Maintain External Alias ....................................................................................................... 15
1.5
Enhanced Search Settings ........................................................................................................... 16
1.5.1
Enable Enhanced Search ..................................................................................................... 16
1.5.2
Maintain Common Currency ............................................................................................... 17
1.5.3
Enable Search Results for Product Categories Assigned to a User ..................................... 18
1.6
Setting UI Visibility ...................................................................................................................... 19
1.6.1
Maintain Tool Tips for Main Menu Tabs ............................................................................. 19
1.6.2
Manage the visibility of My Catalogs .................................................................................. 20
1.6.3
Control Advanced Features................................................................................................. 22
1.6.4
Display Approver Name in Review Cart .............................................................................. 23
1.6.5
screen
Control Maverick Buying by Controlling Free Text Item Shopping Carts using “Can’t Find”
23
1.6.6
Enable/Disable Web Dynpro Confirmation......................................................................... 24
1.6.7
Setting UI Visibility for All Users (UI Configuration for Administrators) ............................. 25
2
1.6.8
Setting UI Visibility for Individual Users (UI Configuration for Employee) ......................... 26
1.1.1
Enable Navigation Links from My Carts .............................................................................. 27
1.7
Determine Launch URL of the SRM UI Add-on ........................................................................... 27
1.8
Enable Customer Fields............................................................................................................... 28
Enable Cross-Catalog Search ............................................................................................................... 28
2.1
2.1.1
Set up Catalogs.................................................................................................................... 29
2.1.2
Set up MDM ABAP API ........................................................................................................ 29
2.1.3
Import Logs ......................................................................................................................... 32
2.2
Settings for Embedded Search/Indexing the Data ...................................................................... 32
2.2.1
Enterprise Search Introduction ........................................................................................... 32
2.2.2
Assign Roles to Indexing Administrator .............................................................................. 33
2.2.3
Maintain RFC Destination to TREX Server ........................................................................... 33
2.2.4
Create a Connection between TREX and Embedded Search .............................................. 34
2.2.5
Activate Web Dynpro Services ............................................................................................ 34
2.2.6
Set up Search Templates and Search Object Connectors .................................................. 34
2.3
Configure Content Management Service (CMS) ......................................................................... 38
2.4
Extract Catalog Data / Import to SRM ........................................................................................ 39
2.4.1
Introduction ........................................................................................................................ 39
2.4.2
Enable Customer Fields on Catalog Items........................................................................... 40
2.4.3
Catalog Data Import Formats .............................................................................................. 40
2.4.4
Import Catalog Data ............................................................................................................ 40
2.5
3
Settings Required for Catalog Data ............................................................................................. 29
Index the Imported Catalog/Product Data ................................................................................. 45
2.5.1
Index Data for Cross-Catalog Search ................................................................................... 45
2.5.2
Delta Indexing of Data......................................................................................................... 47
2.5.3
Customize Search Results – BAdI for Search Ranking ......................................................... 48
Other Settings ..................................................................................................................................... 50
3.1
Catalog Data Enrichment while Adding Items to Cart ................................................................ 50
3.1.1
Catalog Data Enrichment while adding items to cart (Transferring items from mini cart to
PD cart) 50
3.1.2
Punchout Catalog Data Enrichment while adding items to cart (Transferring items from
mini cart to PD cart) ............................................................................................................................ 50
3.2
Customer Fields and other Enhancements ................................................................................. 51
3.2.1
Customer Fields................................................................................................................... 51
3.2.2
Pre-exit and Post-exit Enhancement Concept .................................................................... 51
4
Important SAP Notes .......................................................................................................................... 51
5
Basic Settings for Configuring SAP SRM Fiori Apps ............................................................................. 52
1 Basic Settings for Configuring SRM User Interface Add-On 1.0
This document describes the configuration settings required for the implementation of SRM User
Interface Add-On 1.0 SP01 (SAP SRM UI Add-On 1.0).
1.1 Configure SAP NetWeaver Gateway
The SAP SRM UI Add-on 1.0 requires SAP NetWeaver Gateway to be deployed in the local deployment
mode. Local deployment is also called embedded deployment as the deployment is performed in the
local application backend system. For example, here it is the SAP SRM system. Hence, there is no
separate hardware required for SAP NetWeaver Gateway thus incurring lower TCO. For more
information on deployment of SAP NetWeaver Gateway, refer to link.
1.1.1
Pre-requisites
You need to have the following information before proceeding with the configuration :





Fully qualified Domain name of the SAP NetWeaver AS ABAP system or the load balancing
device
Login information of the Administrator of NetWeaver AS ABAP system
HTTP/HTTPS port of the ABAP central instance
System details of the SRM system to which SAP NW Gateway is connected
Set the authority object S_ICF_ADM to the user who configures gateway
1.1.2
Set Profile Parameters
To set the profile parameters:
1.
2.
a.
b.
Enter transaction codeRZ10
Maintain the following profile parameters in SAP SRM system:
login/accept_sso2_ticket 1
login/create_sso2_ticket 2
For more information, refer link1, link 2
1.1.3
Manage System Alias
After you install SAP NetWeaver Gateway, you need to maintain the system alias ofthe SRM server on
the upon which SAP NetWeaver Gateway is installed.
1. Enter transaction SPRO SAP Implementation Guide  SAP Web Application Server  Gateway 
OData Channel  Configuration  Connection Settings SAP Netweaver Gateway to SAP System
 Manage SAP System Alias
2. Click Create a new entry.
3. In the SAP SYSTEM ALIAS field, enter LOCAL or use the SID of the SRM server as the alias name
4. Select Local GW checkbox
5. In the RFC Destination field, enter NONE
6. In the Software Version field, enter DEFAULT
1.1.4
Maintain Gateway Services
In this step, you activate the SAP Netweaver Gateway services delivered by SRM UI Add-On 1.0.
1. Enter transaction SPRO.
2. Go to SAP Implementation Guide  SAP Web Application Server  Gateway  OData Channel
 Administration  General Settings  Activate and maintain Services
3. Click Add Service
4.
In the System Alias field, enter the the name provided in the previous step, for example LOCAL
and search.
5. Select every service with namespace “/SRMNXP/” and click the service hyperlink.
6. In the Activation Popup, enter the proposed technical service name and technical model name
and click ok.
7. The activated services appear on the main page.
1.1.5
1.
2.


Activate ICF Services
Enter transaction code SICF
Activate following Gateway services along with sub-nodes:
/sap/public/opu : Used for loading resources such as images from MIME repository
/sap/opu/odata : This is the standard mode for all new applications. When a service is created, a
new node for each service is maintained here. For example, all the services created in previous
step can be seen here under sub-node srmnxp here.
1.1.6
Setting Virus Scan profile for SAP Netweaver Gateway
You need to disable the virus profile for SAP Netweaver Gateway OData services so that you do not
receive the error message “No virus profile available…” while ordering a shopping cart.
1. Enter transaction SPRO
2. Go to SAP Implementation Guide  SAP Web Application Server-> Gateway -> Odata Channel
 Administration  General Settings  Define Virus Scan Profile
3. Select Virus Scan Switched Off
1.2 Manage Roles
You need to generate authorization profiles for the new roles and assign these roles to the users.
1.2.1
Generate Authorization Profiles
The new roles you create in SRM UI Add-on 1. 0 should be regenerated to ensure that the profiles
belonging to these roles are assigned all required authorizations.
1. Enter transaction code : PFCG
2. Generate role profiles for the following roles:
 /SRMNXP/EMPLOYEE
 /SRMNXP/CONTENT_MGMT
 SAP_BC_TREX_ADMIN
 SAP_ESH_CR_ADMIN
1.2.2
Assign Roles to Users
You can assign many users to a role using the transaction PFCG
Alternatively, you can assign the following roles to a user in user maintenance:
1. Enter transaction code SU01 and assign the following roles:
Role
/ SRMNXP/EMPLOYEE
Assign to
New shopping cart users
Remarks
Role
SAP_BC_TREX_ADMIN
Assign to
Catalog & Search Content administrators
SAP_ESH_CR_ADMIN
/SRMNXP/CONTENT_MGMT
Remarks
Catalog content administrators
then have the rights to execute
Catalog data and product data
extraction, schedule Catalog
data Index updates, and change
Enterprise Search template
modeling.
2. Add the following authorization object to the roles assigned to catalog content administrators.
This is required to see the logs of catalog import.
Authorization object: /SAPPO/ORD
Field Values:
.0
.1
.2
1.2.3
/SAPPO/CMP = ‘SRM-EBP-SHP’
/SAPPO/BPR = ‘CTLGIMPORT’
ACTVT = 02, 03
Enable/Disable Advanced Features to Selected Users
The SAP SRM UI Add-on provides additional authorization objects to enable/disable certain features to
selected users. You can maintain additional roles appropriately to enable/disable these features to all or
selected users.
The authorization object S_SSP_ADV with Activity SSPUX_ADV with many authority values is provided
for this purpose. Assign this authority object to the roles as required. The effect of various authority
values is described in the following table:
Authority Value
S_PCAT
S_CFTL & S_CF_L
S_CRCP
Effect
More details in this document
Enable ‘all category search’ to improve search Explained in section Search for All
performance.
Product Categories to improve search
performance
Control the usage of free text item shopping
Explained in section Control Maverick
cart creation by showing/hiding “Can’t Find”
Buying by Controlling Free Text Item
screen or by controlling access only from
SCs using “Can’t Find” screen
search screen
Show/Hide Confirm Receipt Button to
Explained in section Enable/Disable
enable/disable WebDynpro Confirmation
WebDynpro Confirmation
1.3 Setting Number Ranges
1.3.1
Define Number Range for Temporary Shopping Cart
Every user of the SAP SRM UI Add-On 1.0 has a temporary shopping cart or mini cartcreated by default.
Items that the user picks and adds to cart are added to the temporary shopping cart with minimal
details. When the user clicks Review Cart or Order Cart, a shopping cart with all details is generated and
the items from temporary shopping cart are transferred to the shopping cart. A temporary shopping cart
is maintained for each user and shop-on behalf-of user combination. A sequential number generation is
required for temporary shopping cart to maintain their identity in the system.
2. Go to SAP Implementation Guide  SAP Supplier Relationship Management  SRM User
Interface Add On  Number Range for Temporary Shopping Cart
3. Enter the number 10 for the temporary shopping cart number range.
If number range is not assigned, review cart screen and temporary shopping cart may not appear.
You can also do this configuration using the transaction code SNRO for number range object,
/SRMNXP/SC.
1.3.2
Define Number Range for Search Terms
OCI 5.0 provides an option for catalogs to send specific search terms for each catalog item. To enable
extraction of search terms data from catalogs, you need to maintain number ranges.
1. Enter transaction SNRO
2. Assign number ranges for number range object/SRMNXP/IS
In SP01, there is no IMG node for this setting. You can implement note 1875571 to get the IMG node
for this setting.
1.4 Enable SICF Services
Various services are required to trigger the SAP SRM backend operations from the new SAP SRM UI AddOn 1.0. Activate these services and maintain external aliases as required.
1.4.1
1.
2.




Activate SICF Services
Enter transaction Code : SICF
Activate the following services along with subnodes:
default_host sap  srmnxp
default_host sap  bc  bsp  srmnxp
default_host sap  public  bc  ui5_ui5
default_host sap  bc  ui5_ui5
Service
default_host sap  srmnxp
default_host sap  bc  bsp  srmnxp
default_host sap  public  bc  ui5_ui5
default_host sap  bc  ui5_ui5
Remarks
Punch out catalog related services, images and
attachments and print preview related services
Shopping cart BSP application
UI5 services
UI5 services
If you face issues in punchout catalog, loading images/attachments or print preview, verify whether
you have activated services under node default_host sap  srmnxp.
Activate the following services, if you are using cross-catalog search:




default_host sap  bc webdynpro  sap  ESH_ADMIN_UI_COMPONENT
default_host sap  bc webdynpro  sap esh_eng_modelling
default_host sap  bc webdynpro  sap esh_eng_wizard
default_host sap es cockpit
Activate the following services, if you are using the Fiori My Shopping Cart app:







/SRMNXP/SRMSHOPPING_CART
/SRMNXP/GETDEFUSRSET
/SRMNXP/SHOPPING_CART
/SRMNXP/CROSS_CATALOG_SEARCH
/SRMNXP/COUNTRY_SH_SERVICE
/SRMNXP/ACC_ASS_SEARCH_HELP
/SRMNXP/ACC_ASSIGN_CATEGORY
Explanation of services under the node default_host sap  srmnxp
Punch out Catalog related services: The services catalogpoll, terminatepoll and inbound_hdlr are used in
punch out catalog process.
The punch out process flow is described with the following diagram:
Punch out
catalog called
Catalog web service URL obtained
& called in new window
SRM polling ICM server via service
“catalogpoll”
Items transferred from catalog
Timeout in 10 Min
Validate transferred catalog items
with service “inbound_hdlr”
Terminate poll with service
“terminatepoll”
1. When you click on a punch out catalog, it triggers a call to the backend to fetch Catalog Service
URL and Catalog Polling URL.
2. Based on the service response, the catalog service URL is launched in a new window and polling to the
ICM server starts (service: Catalogpoll).
3. The polling continues until the transfer happens. The polling has to be terminated after 10 minutes if
the transfer has not happened (service: terminatepoll).
4. When you check out, the call comes to the new SRM NXP inbound handler (service: inbound_hdlr).
Within this service, all validations and unit conversions are performed.
Explanation of Other services related to images, attachments and print preview
SRM UI Add-on exchanges data between the UI and the SRM backend through SAP Netweaver Gateway
services. Due to certain constraints, binary data cannot be exchanged via SAP NetWeaverGateway
services. Images or file attachments are binary data. Hence, own HTTP/HTTPS services are used for
images/attachments that need to be activated.
Service
imageloader
Attachments
printpreview
1.4.2
Description
This service is used to load the images on the
screen from the image URL. In SRM UI Add-on,
catalog products images are stored in content
server and corresponding image URLs are stored
along with product data & indexed. Whenever
products are displayed in SRM UI Add-on,
corresponding images are also displayed on the
screen.
SRM UI Add-on uses this HTTP/HTTPS service for
storing & retrieving attachments.
SRM UI Add-on uses this HTTP/ HTTPS service to
launch print preview of Shopping Cart.
Maintain External Alias
Create an external alias for the following services and maintain the client of the SRM system being used.



default_host sap  srmnxp  attachments
default_host sap  srmnxp  imageloader
default_host sap  srmnxp  printpreview
Perform these steps to create an external alias for the service default_host  sap  srmnxp 
attachments :
1.
2.
3.
4.
5.
6.
7.
8.
9.
Enter transaction SICF.
Press <F8> key .
Click on External Alias button
Select default_host and click on the Create New External Alias icon
Specify a name for the external alias and a description For example, /sap/srmnxp/attachments
and Attachments ExternalAlias 002
On the Trg Element tab page, follow the path e.g. default_host sap  srmnxp and double
click on attachments
Select the Logon data tab page
Specify the Client for example. 002
Save the external alias
Follow the above steps for other services for which you need to create external alias.
1.5 Enhanced Search Settings
1.5.1
Enable Enhanced Search
In this setting, you can enable enhanced search options.
Interface Add On  Enable Enhanced Search
3. Select the search options based on their use as explained in the following table:
Setting Desc
Fuzzy Search
Setting Values
Select the check-box if you want to enable
fuzzy search
Remarks
Points to consider:
Fuzzy search is sometimes not
favorable. If your data consists of
large number of similar values (fo r
Setting Desc
Search Options
Max Search
Results
Setting Values
On: Allows searching even when you
misspell a word or enter partial words.
Off: searches exact words.
Start search on selecting drop down:
When you select a category from the drop
down, the search results showing all items
in the category are displayed.
Start search on selecting drop down &
pressing enter: In addition to selecting a
category from drop down, you have to
press <Enter> key or click ‘Search Glass’
icon to show results. You can also get all
items in the category by using wild card
“*”.
Blank : Wild card “*” search to display all
items in the category is not allowed. You
must enter a search term and press
<Enter> key to get results.
Default value is 1000.
The maximum number of search results
that will be shown can be controlled here.
Remarks
example, cCategories defined as
A001, A002, A003 etc), fuzzy search
returns data containing all such
values. For example, if . you want
to search items of category A005,
but results may contain items of
A001, A002 etc.
Fuzzy search also adversely impacts
performance of search.
You can influence the fuzzy logic
search behavior using BAdI
/SRMNXP/BDI_SRCH_RANKING.
This setting controls the behavior
of “Category drop down and search
bar” in search screen.
If you have large number of items
in any categories, recommend to
use Blank option to get good
search performance.
The system performance can vary
depending on the maximum
number of hits to be returned. The
higher the number of hits
expected, the slower is the
performance.
If you enter 0 here, no search
results will be displayed.
1.5.2
Maintain Common Currency
In this customizing, you can maintain common currency. You must activate a common currency if you
want to enable the price filter for search items. By activating a common currency, you also ensure
accuracy when sorting search items by price. The price of the catalog items in different currencies is
converted to a common currency by the system during extraction. This price is then used to filter and
sort catalog items by price during the search.
Interface Add On  Maintain Common Currency
3. Select the checkbox Activate Common Currency
4. Maintain a Common Currency
As shown in the screenshot below, the common currency EUR is used in filters though search results
contain items with both USD and EUR prices.
We recommend that you activate and maintain the common currency in the system before extracting
catalog data and do not change the common currency after the data is extracted. If you change the
common currency after the extraction of data, run the program /SRMNXP/CTLG_EXT_COM_CUR_UPD,
to apply and adjust the new currency to all the catalog items that were extracted. You must re-index the
data after this activity.
1.5.3
Enable Search Results for Product Categories Assigned to a User
When you search for items based on All Categories, the results displayed are restricted to the product
categories created in the organizational plan using transactionPPOMA_BBP. However, when a user
selects and orders an item from a product category not assigned to that user, an error message appears.
You can switch-off the search based on All Categories and enable search based on product categories
assigned to a user. If you assign many product categories to a user, the search performance becomes
slower as Enterprise Search tries to filter the search results based on the records indexed against the
product categories.
This feature is ideal when the number of product categories assigned to a user in an organizational plan
inPPOMA_BBP is minimal.
Setting:
An authorization object S_SSP_ADV with Activity SSPUX_ADV and value S_PCAT is provided to enable
search based on PPOMA assigned categories and to switch-off search results for All Categories.
Steps:
1. Create a Z-role using transaction code PFCG
2. Assign Authority Object S_SSP_ADV with Activity SSPUX_ADV and value S_PCAT to the role.
3. Assign the role to users for whom you want to enable search based on PPOMA assigned
categories to improve search performance.
1.6 Setting UI Visibility
This section explains the configuration settings that influence UI visibility. Some of the settings also
influence the performance.
1.6.1
Maintain Tool Tips for Main Menu Tabs
In this setting, you can maintain tool tips/hover texts for navigation tabs like “Search”, “Can’t Find” etc.
These texts appear on hovering over the navigation tab providing additional information to user.
1. Enter transaction SOTR-EDIT
2. Create an OTR for every navigation tab. You can also maintain translation into multiple
languages in SOTR_EDIT. You can also choose an already existing OTR text instead of creating a
new one.
Interface Add On  Extension and Field Controls  Maintain Additional texts for Navigation
Paths
5. Enter the OTR text in Additional text column for each of the View keys given under:
View Key
Wi_home_assist
Wi_home_catalogs
wi_home_oTemp
wi_home_oTrack
wi_home_search
wi_home_slists
1.6.2
Navigation Tab
Can’t Find
Catalogs
Templates
My Carts
Search
My Favorites
Manage the visibility of My Catalogs
Punchout catalogs are displayed in My Catalogs in a structured manner.



You can categorize the catalogs and show them in different sections. For example,e.g. all
services catalogs can be shown under ‘Services’ section
You can determine which catalogs to be shown and which are not shown
You can maintain an image for each catalog e.g. Logo of the catalog
Product catalog Category
Punch Out Catalog Link
Image from Webservice
Id settings
Step1: Maintain External Web Services
2. Go to SAP Implementation Guide  SAP Supplier Relationship Management  SRM User Interface
Add On  Master Data  Define External Web Services
You might have already defined punchout catalogs during your SRM implementation. Add any additional
catalogs; you might have in this setting.


You can maintain an image URL or MIME path for each web service.
Ensure that inbound handler and outbound handler are not switched-off in standard call
structure parameters (i.e. BYPASS_OUTB_HANDLER & BYPASS_INB_HANDLER are not be used).
Step 2 : Define Catalog categories
Interface Add On  Master Data  Define Categories for Product Catalog
In this setting, you can maintain categories to group catalogs so that they are displayed together in
different sections for better usability.
Step 3: Maintain Additional Attributes for Catalogs
In this setting, each catalog web service is mapped to a catalog category. You can also maintain its
visibility in SRM UI Add-on Catalogs section and specify whether the catalog is used for extraction of
data using OCI 5.0.
Interface Add On  Master Data  Define Additional Attributes for Product Catalog Categories
3.
3. Select the web service from drop down list and map to a catalog category.
 4. Don’t Show: Select the check box, if you do not want to show in Catalogs tab.
 5. OCI Extr: Select the check-box, if you want to extract data of this catalog using catalog data
extraction.
1.6.3
Control Advanced Features
In Customizing for SAP Supplier Relationship Management, choose SAP SRM User Interface Add-On ->
Control Advanced Features, perform the following steps:
1. In the column 'Adv Ftrs', maintain entries for all the options provided in the drop down
2. Select 'Active' based on your business requirement
Note: It is mandatory to maintain entries for all the options provided in the drop down. You can
choose to activate them based on your requirement.
1.6.4
Display Approver Name in Review Cart
Approver name is displayed in the header section of review cart. Whenever review cart screen is
refreshed or launched, a service to get approver name is triggered. If you want to improve the
performance of launching the review cart screen, then the service to get approver name can be
disabled.
Interface Add On  Control Advanced Features
3. Select “Display Approver Name/Multiple Approvers in Header Section”, if you want to show
approver name in Review Cart Header section.
4. Deselect “Display Approver Name/Multiple Approvers in Header Section”, if you want to
improve performance by disabling the relevant service and not showing approver name in
Review Cart Header section. You can still see approver details by clicking on the link “Approval
details
1.6.5
Control Maverick Buying by Controlling Free Text Item Shopping Carts using “Can’t
Find” screen
Non-catalog and non-product buying increases maverick buying. Users can create a shopping cart
without searching for the requisite item in a catalog or product using the free text item shopping (Can’t
Find screen in SRM UI Add-on). Some organizations may want to control usage of this feature. Currently,
“Can’t Find” screen can be accessed as link from search screen when there are no results found or as a
menu tab.
In this setting, you can


Control usage of free text item shopping cart creation by only selected roles/users i.e. “Can’t
Find” Tab and Link in Search screen can be accessed only by selected users (or no users).
Control usage of free text item shopping carts only after doing cross-catalog search i.e. “Can’t
Find” screen can be accessed only from link in search screen. When you click on the link, Can’t
Find screen appears as a pop-up so that you can create a free text item-shopping cart.
Setting:
Assign authorization object S_SSP_ADV with Activity SSPUX_ADV to selected roles using PFCG
transaction. The authority values S_CFTL and S_CF_L control the availability of Can’t Find screen. Effect
of these authority values is described in the table below:
Authority Value
S_CFTL
S_CF_L
S_CFTL and
S_CF_L
Blank
1.6.6
Effect
Both Can’t Find Tab and Link
in search screen are
available
Can’t Find Tab is not
available. Only Link in search
screen is available.
in search screen are
available
in search screen are NOT
available
Enable/Disable Web Dynpro Confirmation
You can trigger confirmation for a shopping cart (WebDynpro Confirmation) by clicking on ‘Confirm
Receipt’ button from My Carts in SRM UI Add-on. You can also do one-click express confirmation for all
item quantity from My Carts by clicking confirmation icon at item level.
You may not want to enable WebDynpro confirmation for occasional users to avoid confusion and to
keep it simple for them.
In this setting, you can

Show/Hide Confirm Receipt button to selected users e.g. only semi-professional or professionals
users may get ‘Confirm Receipt’ button to do WebDynpro Confirmation and disable the feature
for occasional users.
Setting:
Assign authorization object S_SSP_ADV with Activity SSPUX_ADV to selected roles using PFCG
transaction. The authority value S_CRCP control the availability of Confirm Receipt button and hence
WebDynpro confirmation feature from My Carts. Effect of these authority values is described in the
table below:
Authority Value
S_CRCP
Blank
Effect
Confirm Receipt Button will be visible.
Confirm Receipt Button will NOT be visible.
Setting UI Visibility for All Users
1.6.7
Setting UI Visibility for All Users (UI Configuration for Administrators)
The SAP SRM UI Add-On 1.0 software consists of several UI views that are by default visible to all users.
The administrator through this configuration can control each UI view’s visibility to all users.
Refer SAP Note 129260.
Interface Add On  UI Configuration for Administrators
You may not see any entries in this view in a newly set-up system client.
3. Copy the entries from the Client 000 to your relevant client.
All SAP SRM UI Add-On 1.0 software UI view names and their relative paths in the SRM Shopping
Cart BSP application with its default “Visibility” settings are maintained.
4. You can choose to switch off or swtich on the visibility of the view by selecting or deselecting the
checkbox “Administrator Visibility.”
If you select ‘override’ for any view, then employee users can override the administrator settings in the
configuration setting “Setting UI visibility for individual users”.
1.6.8
Setting UI Visibility for Individual Users (UI Configuration for Employee)
All the UI views in SAP SRM Shopping Cart UI Add-On 1.0, names, and their relative paths in the SRM
Shopping Cart BSP application with their default “Visibility” settings for all users are maintained in “UI
Configuration for Administrators”.
If an user with role employee needs to override the administrator settings, then he/she should maintain
visibility settings in the UI configuration For Employee configuration. Only the views where administrator
allowed ‘override’ can be changed here.
Steps
This has to be performed for an employee for whom the UI configuration is being done.
Interface Add-On  UI Configuration for Employee.
3. Create a new entry for every view that the employee wants to customize (for example,
SourcesOfSupply).
4. Maintain the UI visibility configuration for all employees in this configuration. The UI visibility
configuration for administrators is maintained as per requirements.
1.1.1
Enable Navigation Links from My Carts
My Carts screen has navigation links to follow-on procurement documents like purchase order and
confirmation. You can even trigger confirmation of goods receipt from My Carts screen. For navigation
links to work, you have to either enable NWBC (SAP NetWeaver Business Client) or maintain the
Enterprise Portal configuration.
a) Enable NWBC with the following configuration activity:
2. Go to SAP Implementation Guide  SAP Supplier Relationship Management  Technical basic
Settings  Portal Independent Navigation Frame  Activate/Deactivate Portal Independent
Navigation Frame
3. Activate the customizing switch SRM_700_LOCAL_MENU
OR
b) Maintain the Enterprise portal configuration with following activity:
2. Go to SAP Implementation Guide  SAP Supplier Relationship Management  Technical basic
Settings  Maintain Portal Information
3. Maintain data for following entries
 Port of the SAP Portal (Internal)
 Full Qualified Domain Name (Internal)
 Protocol (Internal)
 Root Path of iView/Application
1.7 Determine Launch URL of the SRM UI Add-on
You can launch new shopping cart in standalone mode (without using Portal or NWBC). You can
determine the URL to launch shopping cart as follows:
1. Enter transaction SE80
2. From the drop down, choose BSP application
3. Choose BSP application /SRMNXP/SHOPPINGCART
4. Check the properties page of defaults.htm. Scroll down to see the URL. You will notice
something like https://xyzxyz.sap.com:44333/sap/bc/bsp/srmnxp/shoppingcart/index.htm
1.8 Enable Customer Fields
You can enable customer fields in SRM UI Add-on.
Supported Controls : Input fields, Dropdown fields, check-box fields
Supported Screens : Item Details screen in some sections (Identification, Organization, Service Delivery,
Accounting), Can’t Find screen, Review Cart screen (Header overview and Items sections), User Defaults
screen.
A cookbook to enable customer fields is provided as an attachment in SAP Note 1830075.
2 Enable Cross-Catalog Search
SRM UI Add-on 1.0 provides cross-catalog search thus simplifying the experience for users. Now, users
need not determine which catalog link they need to click for their requirement; they do not need to go
to a third party catalog user interface to select catalog items.
Users can now search for any catalog items or product master items from the simple search bar
provided as shown in above screen.
Pre-requisites



Set up catalogs (WebService ID and other settings)
Set up MDM ABAP API if you are using SRM-MDM Catalog
o If you use SRM-MDM Catalog then native replication of MDM catalog data is available
using MDM_TECH (MDM ABAP API).
Install and connect TREX; set up SAP NetWeaver Enterprise Search in ABAP AS (i.e. Embedded
Search).


Configure SAP CMS (Content Management Service) for loading images/attachments
Catalog data is available in OCI 5.0 format as a JSON file or through HTTP service from your
catalog partner
o If you are using SRM-MDM Catalog, then native replication of MDM catalog data is
available. You need to install MDM_TECH (MDM ABAP API) for this.
To process the data perform the following steps:
1. Catalog Data/Product Master Data Extraction
a. Catalog data (in OCI 5.0 format) is replicated to SRM staging tables.
b. If you have SRM-MDM catalog, extract catalog data using MDM ABAP API.
c. If you have product master data, extract the same into SRM staging tables.
2. Index the data to be made available for cross-catalog search
The settings required for the above steps are explained in details in the following sections.
SAP Fiori SRM Shopping Cart Create Apps need setting up Cross-Catalog search and hence
setting up cross-catalog search is mandatory for these SAP Fiori Apps.
2.1 Settings Required for Catalog Data
2.1.1
Set up Catalogs
Required settings have been explained in section Manage the visibility of My Catalogs
2.1.2
Set up MDM ABAP API
This section is relevant only if you have SRM-MDM Catalogs.
You need to have MDM_TECH Add-On installed in your SRM system for the scenario to work.
MDM ABAP API set-up is required to enable native replication of SRM-MDM catalog data into SRM
server for indexing so that cross-catalog search feature in SRM UI Add-on can be used.
For more information, please follow the link Configuring MDM API
Configure MDM Server
You need to include entries in mds.ini file to set up trusted connection between MDM server and SRM
systems.
2.1.2.1.1 Mds.ini entries
You need to configure the SRM Server as a trusted system on the MDM side. In the mds.ini file of the
MDM server installation config folder, you have to define/modify the “SAP RFC Gateways” and “Trusted
SAP Systems” entries.
For example, you are connecting to two SRM systems abc & xyz, ensure the following:
SAP RFC Gateways=GWHOST=abc.wdf.sap.corp GWSERV=3324; GWHOST=xyz.wdf.sap.corp
GWSERV=3329;
Trusted SAP Systems=abc; xyz;
Note: You can get the GWHOST and GWSERV values from the SMGW transaction -> GoTo -> Logged on
Clients and find for the entry “Local Web AS”. Give the Host Name as GWHOST and TP Name as
GWSERV.
2.1.2.1.2 Maintain Users
You need to add the user who would be performing MDM data extraction/import as a user for the
particular repository on the MDM side. The user should be maintained in CAPITAL LETTERS else you may
not be able to import data.
2.1.2.1.3 Enable Delta Importing
MDM Delta import set-up enables importing only delta content from last successful import. Enhance
the SRM-MDM Catalog schema to include an additional field to capture last changed timestamp of the
catalog record. You need to perform this step in all repositories that are in use. Refer to SAP Note
1897364 to perform this setting.
Configure MDM APOI on the SRM system
You have to configure the MDM API connection using MDMAPIC transaction on the SRM side. This step
will create a tRFC connection to MDM Server.
2.1.2.2.1 Create MDM DBMS Hosts
1. Launch Transaction Code MDMAPIC
2. Select folder “MDM DBMS Hosts”
3. Click on New Entries
4. In the MDM DBMS field, provide a unique name
5. In the DB Type field, select appropriate DB
6. In the Host Name field, provide the host nameSave your entries
2.1.2.2.2 MDM Server Connection
1. Launch Transaction Code MDMAPIC
2. Select folder “MDM Server Connections”
3. Click on New Entries
4. In the MDM Connection field, provide a unique name
5. In the Host Name field,provide the host name
Save your entries.The entry generates an RFC destination for the host.
2.1.2.2.3 MDM Repositories
In this setting, a link between SRM-MDM Catalog Webservice ID and MDM ABAP API is established.
Define an entry for all your MDM Catalogs (as defined in External WebServices configuration).
1.
2.
3.
4.
Launch Transaction Code MDMAPIC
Select folder “MDM Repositories”
Click on New Entries
In the Object name field, provide the WebService ID of SRM-MDM Catalog. (Note that a Valid
Webservice ID should be provided here else MDM data import will not work)
5. In the MDM Repository field, provide a unique name
6. In the MDM Connection field, select the MDM connection created in previous steps
7. In the MDM DBMS field, select the MDM DBMS created in previous steps
8. In the MDM Provider field, select 71_SP00_PL00 entry for MDM Provider (using search
help)Save yourentries.
Test Trusted Connection Setup
Once you configure the MDM Server and the SRM System, restart the MDM Server and the SRM Server
once. After performing the restart, check whether the RFC connection is working successfully by
performing the following steps:
1. In the SRM sytem, enter transactionMDMAPIC
2. Select the MDM Repository and click on RFC destination to verify whether RFC connection is
working
2.1.3
Import Logs
All the import logs are stored in the Post Processing Office (PPO). You need to activate two BC sets in
order to configure PPO logs for the catalog import. These BC sets should be activated in a sequence for
activation without errors. For more details, refer SAP Note 1882385. Ensure that the user has necessary
authorizations in authorization object /SAPPO/ORD.
2.2 Settings for Embedded Search/Indexing the Data
2.2.1
Enterprise Search Introduction
SAP NetWeaver Enterprise Search is a search solution providing unified, comprehensive, and secure
real-time access to enterprise data and information from within and outside of a company. The search
returns data from SAP systems and other search providers and allows direct access to the associated
applications and actions.
Embedded Search: Embedded Search serves SAP Business Suite applications as a basic search
technology platform for searching business objects using the TREX engine (starting with SAP Business
Suite 2008). Embedded Search is the Enterprise Search component in the AS ABAP.
Search object connectors are used to connect search providers to SAP NetWeaver Enterprise Search to
make objects of a specific type that are stored on them available for searching. Depending on the type
of search provider involved, the connectivity data can be an RFC destination, URL, or repository address,
etc.
NW Enterprise Search in ABAP AS (Embedded Search) configuration steps are explained in help
documentation of NW Enterprise Search. Also, refer the sap Note for Embedded search 1164979.
Enterprise Search with SAP SRM UI Add-on
SAP SRM User Interface Add-On 1.0 relies on the following data providers for essential master data and
they need to be indexed for search access by Enterprise Search
a) Catalog content from Supplier Catalogs
b) SRM-MDM Catalog data
c) Product Master Data from SRM
SAP SRM User Interface AddOon 1.0 delivers Enterprise Search(ESH) business templates (Search Models
) for the above mentioned master data . The administrator has to build search object connectors from
these business templates and run index over these search object connectors to enable Enterprise
Search for the above mentioned master data.
2.2.2
Assign Roles to Indexing Administrator
Assign the following roles to the administrator user who shall work with embedded search configuration
and indexing activities.


SAP_BC_TREX_ADMIN
SAP_ESH_CR_ADMIN
2.2.3
Maintain RFC Destination to TREX Server
Verify whether a TREX server is already connected to your SRM system where UI Add-on is deployed
using transaction code SM59 (hint: check TCP/IP connections).
If not, follow the steps below to maintain a TREX server.

Connect TREX with SRM system. Following link explains the TREX config settings required. Once
this setup is done, an RFC destination (TCP/IP connection) is created in SRM system.
Connecting TREX with an ABAP application
2.2.4
Create a Connection between TREX and Embedded Search
Run the report ESH_ADM_SET_TREX_DESTINATION using transaction code SE38 and set the correct RFC
destination that points to the TREX server here. This will create a connection between TREX and
Embedded search.
Search Object Connector
2.2.5
Activate Web Dynpro Services
Activate Web Dynpro services using transaction code SICF. If you have already activated the services
required as explained in Activate SICF Services section in this document, then you can ignore this.
Activate the following services:




default_host sap  bc webdynpro  sap  ESH_ADMIN_UI_COMPONENT
default_host sap  bc webdynpro  sap esh_eng_modelling
default_host sap  bc webdynpro  sap esh_eng_wizard
default_host sap es cockpit
2.2.6
Set up Search Templates and Search Object Connectors
SAP delivers Enterprise Search Templates (i.e. Business Templates within the Enterprise Search Screens).
A search template includes the description of the selection attributes for search and the structure of the
result data. Using Search Template, a Search Object Connector can be created. The search object
connector delivers the result data in a predefined form for the specified selection attributes.
ESH Search Connectors are not available on the customer system by default and the administrator needs
to create one search connector for each business template (Search Model).
You can mass create search object connectors using a report or from ESH_COCKPIT. Both the options are
explained below.
NW 7.3x and above only: Adjust the Catalog Model
In NW 7.3x and above, the ESH_COCKPIT has a different user interface. The settings described in this
section are relevant for NW 7.3x version and aboveonly. In this setting, attribute search for all model
requests are activated.
1. Enter transaction ESH_COCKPIT
2. Click Modeler
3. Select SRMNXP01  SRMNXP02_CATALOG and click on Edit
4. Enter the package ‘/SRMNXP/CATALOG_ES’ and press ‘Next’.
5. Click on 4th step in guided navigation Model Requests
6. For all requests, select the check-box in column ‘Attr.Search’.
7. Click on Save and Finish button to go back to initial screen.
Mass Creation of Search Object Connectors using Report
Follow the steps below to create all search connectors for SRM UI Add-on.
1.
2.
3.
4.
Run the report ESH_ADM_INDEX_ALL_SC using transaction code SE38
Select “Delete All Search Connectors” to delete older search connectors
Select “Create all Search Connectors”
Ensure “Schedule Initial Indexing” is not selected
5.
Enter the product name SRMNXP01. This includes all search connectors for the SRM UI Add-On
1.0 application
Click on Execute (or F8 on key board) to create connectors
6.
Create Search Object Connectors from ESH_COCKPIT
You can create search object connectors using ESH Administrator Cockpit instead of creating using a
report (ESH_ADM_INDEX_ALL_SC) as explained above. If you have already created using report, then
you may ignore the settings explained in this section.
Select Template and choose “Create Connector”
Steps:
1. Enter transaction ESH_COCKPIT
2. Click Switch to Modeler. You can see all the templates for SRM UI Add-On 1.0 under the
software component SRMNXP01
3. Search for the right business template (or model) for example SRMNXP02_CATALOG for
xatalogitem data.
5. Select this line and click on the button “Create Connector”. The Search object connector is
created. Repeat steps 3-4 to create connectors for other templates under component
SRMNXP01. Other search templates are:
Search Template
SRMNXP02_CATALOG
Description
Search Results Model (Catalog Item
Main Data)
SRMNXP_ATTACHMENTS Images and Attachments
SRMNXP_ATTRIBUTES
Attributes
SRMNXP_CUST_FIELDS
Customer Fields
SRMNXP_PRC_CONV
Converted Price Data (Prices in
Different Exchange Rates)
SRMNXP_PRC_SCALE
Price Scales
SRMNXP_SRCH_TRMS
Search Terms
2.3 Configure Content Management Service (CMS)
SRM UI Add-On 1.0 requires content management service to be configured for storing the images during
extraction. The content management repository is SRMNXP_IMG and the contents are maintained in the
table /SRMNXP/CAT_IMG.
Please maintain the entries for the physical path for storage and HTTPS requirement for loading images
(if any)
This is a cross-client setting. Verify the client allowed for cross-client settings and make settings in that
client. You need cross-client customizing authorizations to maintain configuration for CMS.
1. Enter transaction SPRO 
2. Go to SAP Implementation Guide  SAP Web Application Server  Knowledge Management 
Settings in the Knowledgewarehouse System  Content Management Service  Define Content
Repositories
3. Select content repository SRMNXP_IMG and click on Edit
4. Maintain Phys.Path
5. Maintain HTTPS requirement in fields HTTPS on frontend and HTTPs on backend
2.4 Extract Catalog Data / Import to SRM
2.4.1
Introduction
Cross-catalog search in SRM UI Add-on is performed by syndicating all catalog items data and
product master data into a single source of data for search, index the data and use embedded
search APIs to search for the items. Syndicating all catalog data into single source is performed by
importing catalog content from various catalogs (either internal or 3rd party) and storing the data
after validation in SRM UI Add-On 1.0 catalog data tables. The imported catalog items data & SRM
product master data is stored in SRM tables .For more information, see tables in the package
/SRMNXP/CATALOG_ES Some of the important tables are listed here:
Table
/SRMNXP/CAT_ITM
/SRMNXP/PRC_CONV
/SRMNXP/LNG_TXT
/SRMNXP/DESC_TXT
/SRMNXP/PRCSCALE
/SRMNXP/ITM_SRCH
/SRMNXP/MATGRTXT
/SRMNXP/ATT_MAIN
Description
Catalog items main data.
Price Converted to common currency
Long text
Description
Price scales
Search terms description
Material group text
Attachments Main
/SRMNXP/ATTCHMNT
/SRMNXP/ATT_THMB
/SRMNXP/ATT_TXT
/SRMNXP/ITM_ATTR
Attachments
Thumbnail Attachment
Attachment text
Attributes for catalog Items
Product master data from SRM also can be imported using extraction reports provided to form single
source of data for search.
The following diagrams depict the steps involved in preparing the data for cross-catalog search.
Catalog Providers
(OCI 5.0 compliant)
JSON file
HTTPs
webservice
Import data into
SRM Staging DB
Index catalog
Data
SRM-MDM Catalog Data
Import data into
SRM Staging DB
Index catalog
Data
Import data into
SRM Staging DB
Index catalog
Data
Native
ABAP API
SRM Product Master
Data
Report
For importing data into SRM staging DB, a catalog import cockpit has been provided.
2.4.2
Enable Customer Fields on Catalog Items
Starting with OCI 5.0, multiple customer fields are supported in open catalog interface. The
customer fields can be specified in the INCLUDE structure /SRMNXP/INCL_CAT_ITM of the table
/SRMNXP/CAT_ITM.
2.4.3

Catalog Data Import Formats
3rd party catalog providers can supply the data according to OCI 5.0 specification in 2 ways:
 JSON file
 HTTP(s) Webservice.
OCI 5.0 specifications can be downloaded from SAP service market place at the link below:
https://service.sap.com/srm  open catalog interface


SRM-MDM Catalog data can be imported using MDM ABAP API.
SRM Product data can be imported using a report.
2.4.4
Import Catalog Data
Thecatalog import cockpit facilitates importing data from OCI 5.0 compliant catalogs through
HTTP(s) web service or JSON files, importing data from MDM catalog using MDM ABAP API or
importing product master data from SRM.
You should have /SRMNXP/CONTENT_MGMT role assigned to import catalog data.
Catalog Data Import – File Upload
This section explains the procedure to importing the catalog data from JSON files.
4
2
3
1
5
6
1.
2.
3.
4.
5.
6.
7.
8.
9.
Enter transaction /SRMNXP/CAT01
Add a catalog web service ID or select an existing catalog webservice id.
Select Import Action applicable - File
Provide the file path of Import file.
SelectImport Image checkbox, if you want to import images.
Provide the folder path for the folder containing images in Image Folder.
Click on Schedule Job button.
Define Job to start immediately or schedule to start at a specified date/time.
For Delta import, use “Reschedule Delta” or “Schedule Delta with CTI” indicators. The use of
these indicators are explained in the table below:
Importing Type
Full Load or Initial
Load
Values of Indicators
Reschedule delta : OFF
Schedule with CTI : OFF
Delta load
Reschedule delta : ON
Delta Load –
replace data
completely
Schedule with CTI : ON
Remarks
Use when you are importing data into a
catalog first time. All catalog items are
added to tables.
Use when you want to change some data or
add additional items in already imported
catalog
Use when you want to erase the existing
data in a catalog completely and replace
with new data
Upon successful importing, the catalog data is stored in SRM UI Add-On 1.0 tables for indexing.
Catalog Data Import –Upload from Webservice
This section explains the process of importing the catalog data by connecting to a supplier provided
HTTP(s) webservice.
1.
2.
3.
4.
5.
6.
7.
8.
Add a catalog web service ID or select an existing catalog webservice id.
Select Import Action applicable - HTTP/HTTPS
Provide the URL, User name, password and page size. Give a requested page. If the catalog
Webservice ID configuration has a user and password details, you need not enter here. If you
enter user and password, system will access the URL using the given user id and password in this
screen. You can also provide a transaction ID and requested page if you like to resume a stalled
transaction from a desired page.
Click on Import Image checkbox, if you want to import images. Provide the folder path for the
folder containing images in Image Folder. If you use proxy server, then you need to implement
the BAdI SRM_CAT_GETPROXYINFO to provide proxy info (This BAdI is also available in SRM core
.If you have already implemented this BAdI, then you do not need to implement again).
Define Job to start immediately or schedule to start a specified date/time.
For Delta import, use “Reschedule Delta” indicator. The use of these indicators are explained in
the table below:
Importing Type
Remarks
Full Load or Initial Reschedule delta :
Use when you are importing data into a catalog
Load
OFF
first time. All catalog items are added to tables.
Delta load
catalog
SRM-MDM Catalog Data Import
This section explains importing the catalog data from internal catalogs, managed using SRM-MDM
Catalog. The extraction from MDM Catalog is done using native MDM ABAP APIs.
Launch transaction code /SRMNXP/CAT01.
1.
2.
3.
4.
5.
6.
Enter the transaction /SRMNXP/CAT01.
Add a catalog web service ID or select an existing catalog web service id.
Select Import Action applicable - MDM
For Delta import, use “Reschedule Delta” or “Schedule Delta with CTI” indicators. The use of
these indicators are explained in the table below:
Importing Type
Full Load or Initial
Load
Delta load
Delta Load –
replace data
completely
Schedule with CTI : ON
Remarks
Use when you are importing data into a
catalog first time. All catalog items are
added to tables.
Use when you want to change some data
or add additional items in already
imported catalog. This picks the records
from MDM catalog that have been
created, modified or deleted since last
successful extraction.
DO NOT USE this combination as MDM
ABAP API picks the changed records in
Delta.
Additional considerations while importing MDM Catalog data:
1. You can choose a language while scheduling so that data in the selected language only is
imported. This improves import performance. The list of languages is displayed directly from the
MDM repository at run time. You can also schedule different jobs for different languages thus
improving import performance. (This feature imade available with SAP Notes 1899986 and
1900543)
2. If the MDM catalog item has both contract price and normal price, contract price will be given
preference (this feature is available with SAP Note 1896675). If you have multiple contract
prices maintained for a single catalog item, the first price that is maintained will be chosen at
the time of extraction. If you want to extract the other price maintained for a catalog item, use
the BAdIs /SRMNXP/MDM_FIELD_MAPPING and /SRMNXP/CATALOG_TRANSFER_DATA for
enriching the data. For more information, refer Catalog Data Enrichment during Import to SRM.
3. Images maintained in MDM repository cannot be imported to SRM. Only image URLs that are
maintained as hyperlinks in the MDM repository for the catalog item and given as Type
“Rendered” will be treated as images during import. These links will show up as images in the
search results. URLs maintained as hyperlinks in the MDM repository and Type “Links” will be
treated as attachments in catalog results. You also need to ensure proper MIME types for the
URLs given.
4. Named searches and masks maintained are not considered while importing. The import
transfers all the data in the MDM repository to SRM. If you want to filter the data set available
for a set of users, TREX authorization concept based on ABAP authorization objects can be used.
Import SRM Product Master Data
This section explains importing the SRM Product Master data. The extraction from SRM product
master is done via ABAP report.
Launch transaction code /SRMNXP/CAT01.
1.
2.
3.
4.
5.
Select PRODUCT MASTER.
For Delta import, use “Reschedule Delta” indicator. The use of these indicators are explained in
the table below:
Importing Type
Remarks
Full Load or Initial Reschedule delta :
Use when you are importing data into a catalog
Load
OFF
first time. All catalog items are added to tables.
Delta load
catalog
Upon successful importing, the relevant product master data is stored in SRM UI Add-On 1.0 tables for
indexing.
Catalog Data Enrichment during Import to SRM
BADIs have been provided to enrich data before importing into SRM tables. If you face any issue in
importing catalog data or if the data is not imported due to errors, suggest you to verify the catalog data
and determine the need for converting the data to suit your organizational requirements. Remember
that catalog data is validated before importing and hence ensure that your catalog data is correct.
1. BAdI to enrich 3rd party Catalog Data
You can use these BAdI to alter data according to your organizations’ requirements or to fill
customer fields from OCI data.
Enhancement Spot: /SRMNXP/CATALOG_TRANSFER
BAdI Definition: /SRMNXP/CATALOG_TRANSFER_DATA
The interface method ENRICH_ITEM_DATA provides access to catalog item data, search terms,
attributes, price scales, images and customer fields. You can enrich any of this data by
implementing the BAdI.
2. BAdI to enrich MDM Catalog Data
BAdI /SRMNXP/MDM_FIELD_MAPPING is provided to do MDM field mapping during import
from SRM-MDM Catalog and fill OCI data.
Note that BAdI /SRMNXP/CATALOG_TRANSFER_DATA implementation is also called after this
before importing into SRM tables.
2.5 Index the Imported Catalog/Product Data
Index administrator needs to index the data imported into SRM UI Add-On1.0 staging tables to enable
cross-catalog search on this data.
Ensure that you had all settings for embedded search done as explained in section Settings for
Embedded Search.
2.5.1
Index Data for Cross-Catalog Search
The steps to index catalog/product data are explained here:
1. Enter transaction ESH_COCKPIT.
Embedded search Administration cockpit is launched.
2. If you see Switch to Cockpit button, click on the button
3. Select Search Object Connector Search Results Model. This model indexes catalog/product
main data.
Select Search Object
Connector
Schedule Indexing on
the Search Object
Connector
4. Select Actions  Schedule Indexing
5. Start indexing immediately or schedule indexing job at a certain date/time. You can
schedule the job to run on recurrent basis also. For delta indexing, refer Delta Indexing
section.
NOTE: When the Delta Indexing check-box is not selected, it is considered as FULL INDEX. In a Full
Index, the data in TREX tables (data that was indexed earlier), if any, is deleted first and all the data in
the SRM staging tables is indexed again. It is recommended that Full Index should be run when you
index for the first time. Subsequent indexing should be run with Delta Indexing ON.
3.Start indexing Immediately OR
Schedule Job (or schedule
recurrent job
Relevant for NW 7.3x only: The user interface for scheduling indexing in NW 7.3x is different from the
one explained above. See the screenshot below. There are 3 options available in Full Indexing Mode :



Keep Index Content : Use this for Delta indexing.
Clear Index Content : Use this for Full Indexing.
Blank
: This means- Automatic section. If the index already exists, Delta indexing
is done. Full Indexing is done, if the index is new.
6. Last index operation status can be seen from the administrator cockpit.
Last Index time,
number of records
indexed and status can
be found on the main
7. Index Job log can be found on the bottom display area.
Job Log Messages
8. Repeat the above steps for other search object connectors
 Attachments
 Attributes Model
 Price Conversion table
 Price Scales
 Search Terms
2.5.2
Delta Indexing of Data
Once full indexing is done, all subsequent indexing should be done in Delta indexing mode.
While scheduling indexing, select the Reschedule check-box (to choose scheduling options i.e.
whether to start immediately or schedule at a specific time) and Delta Indexing check-box (to
indicate that you want to do Delta indexing) to initiate delta indexing.
IMPORTANT NOTE:
Always perform Full Indexing in the following cases:
 When you import data in to catalog tables for the first time and index the data first time
 When search connector is created for the first time
 When search connector is deleted and recreated
 When search connector needs to be completely refreshed of its old index data.
Perform Delta Indexing in the following cases:

Indexing is already done at least once before and you want to retain already indexed data
Note that if Full Index is done on a search connector that has already been once indexed, the
earlier indexed data is cleared.
Relevant for NW 7.3x only: The user interface for scheduling indexing in NW 7.3x is different from the
one explained above. See the screenshot below. There are 3 options available in Full Indexing Mode :



Keep Index Content : Use this for Delta indexing.
Clear Index Content : Use this for Full Indexing.
Blank
: This means- Automatic section. If the index already exists, Delta indexing
is done. Full Indexing is done, if the index is new.
Delta indexing in the Back ground : You can run report ESH_IX_PROCESS_CHANGE_POINTERS to
schedule delta indexing for several or all search object connectors of a software component as a back
ground job. Report checks whether or not application data has been modified and in such events, delta
indexing is triggered. For more details, click on the link.
2.5.3
Customize Search Results – BAdI for Search Ranking
The search keyword provided in the search box searches across indexed catalog item data on all data
(e.g. Description, manufacturer name, long description, material group, vendor name etc). Some of the
catalog data is more relevant than other data. The system searches the relevant columns first and then
searches on other columns. The final search results are consolidation of search results from both more
relevant columns and less relevant columns with search results from more relevant columns showing up
on the top. You can also influence Fuzzy logic behavior using the BAdI (For example, you do not want
the fuzzy logic on product code while you want fuzzy logic on few other fields).
This search behavior can be influenced by BAdI /SRMNXP/BDI_SRCH_RANKING.
Default BAdI Implementation
Default BAdI implementation provided: /SRMNXP/IMPL_SRCH_RANKING
The default implementation does two levels of search :
HIGH : Does search on columns “DESCRIPTION, MANUFACTNAME, MATNR, SEARCH_ERM”
LOW : Does search on rest of the text columns (“LONG TEXT, CATALOG NAME, CONTRACT, VENDOR (ID),
VENDOR_NAME, MATGROUPTEXT etc”)
Result set of ‘HIGH’ will be shown on the top followed by result set from ‘LOW’.
This is done by defining two search requests in Embedded search.
To check the definition of search request, one has to view the business template for catalog items where
request IDs are defined.
1.
2.
3.
4.
Enter transaction ESH_COCKPIT
If you do not see Template Modeler, click on ‘Switch to Modeler’ button.
Select the template SRMNXP02_CATALOG and click EDIT.
Go to the last step “Define Requests” and find the request ID “DEFAULT”, “HIGH” and “LOW”
and respective configuration. (Note the user interface changed from NW 7.3x onwards. Pl see
SAP Note for the new UI details for NW 7.3x and above)
The screen shot below shows the configuration for the request ID “HIGH”.
NW 7.3x and above: The user interface changed for NW versions 7.3x and above.
5. Click on 4th step “Model Requests”
For all requests apart from DEFAULT request, the check-box in column ‘Attr.search’ should be selected.
Custom BADI Implementation
You can change the behavior of the search and the result set by custom implementing the BAdI for
search ranking. For example, you can implement search over different set of fields for request ID
“HIGH”. You can also define your own search request IDs (define in search object connectors business
template) or define more levels of search request IDs. A new BAdI implementation for BAdI
/SRMNXP/BDI_SRCH_RANKING is to be written calling for enterprise search over new request ID. (Refer
the default implementation /SRMNXP/IMPL_SRCH_RANKING for technical help).
3 Other Settings
In this section, we discuss other important useful settings including few customizations using
Enhancements and BAdIs.
3.1 Catalog Data Enrichment while Adding Items to Cart
Catalog data may need to be enhanced to ensure that correct data is used for shopping cart creation.
Catalog data can be used to create shopping cart from search results or punch out catalog.
Typically, when a user adds items to cart from search or punch-out catalog, the items are added to minicart. Mini cart has just basic item data with minimal validations. Once all the required items are included
in mini cart, user has two options:


Order the cart : User wants to order the shopping cart with selected items with default cart data
(account assignment, shipping address )
Review Cart : User may want to review and make changes to the cart data
When a user clicks on any of the above actions, a Shopping Cart (in technical terms, PD Shopping cart) is
created. This shopping cart is same as the one created during Web Dynpro shopping cart creation also.
All the validations and checks are done during this shopping cart creation. It is important to have all
master data and organizational data accurate here.
You may want to enhance the catalog data transferred for creating the shopping cart.
3.1.1
Catalog Data Enrichment while adding items to cart (Transferring items from mini
cart to PD cart)
BAdI /SRMNXP/CATALOG_ENRICH_DATA can be used to enhance catalog data when items are
transferred from mini cart to Shopping cart.
Enhancement spot: /SRMNXP/CATALOG_TRANSFER
BadI name: /SRMNXP/CATALOG_ENRICH_DATA
3.1.2
Punchout Catalog Data Enrichment while adding items to cart (Transferring items
from mini cart to PD cart)
Punchout catalogs can be accessed from SRM UI Add-On 1.0 and users can add items from punchout
catalogs into Mini-cart. While reviewing or ordering, a shopping cart is created. You can enrich data
while creating shopping cart (PD Shopping cart) using BAdI.
BAdI : BBP_CATALOG_TRANSFER
Interface method ENRICH_ITEM_DATA is provided to enrich punch out catalog data before creating PD
shopping cart.
Note : If you had implemented this BAdI before, you can continue to use it in SRM UI Add-On 1.0 also.
Remember that the BAdI is called two times in SRM UI Add-On 1.0. BAdI is called initially when catalog
items are transferred to mini cart. As mini cart has only few shopping cart fields, the enrichment and
validation is done only for few fields. The second call is made when a PD shopping cart is created from
mini cart. This time, enrichment and validation of all fields happen according to the BAdI
implementation. Note that this could result in errors during PD cart creation while there were no errors
during mini cart creation. You may want to adjust your code in BAdI to ensure as many errors are caught
in the first call itself so that catalog items are not transferred to mini cart also. Refer consulting
SAPNnote 1891371.
3.2 Customer Fields and other Enhancements
Customer fields and enhancements in Web Dynpro or CLL layer are not automatically enabled in SRM UI
Add-On 1.0. The enhancement concept in SRM UI Add-On1.0 enables you to include your
enhancements.
3.2.1
Customer Fields
You can enable customer fields in SRM UI Add-on 1.0.
Supported Controls: Input fields, dropdown fields, check-box fields
Supported Screens: Item Details screen in some sections (Identification, Organization, Service Delivery,
and Accounting), Can’t Find screen, Review Cart screen (Header overview and Items sections), and User
Defaults screen.
A cookbook to enable customer fields is provided as an attachment in Note 1830075.
3.2.2
Pre-exit and Post-exit Enhancement Concept
SAP Note 1879766 explains pre-exit and post-exit approach to include your UI related enhancements in
SRM UI Add-On 1.0.
4 Important SAP Notes
Few important SAP Notes
Note
1760438
1752753
1874689
1874690
1830075
1879766
1848843
Description
Release Information for SRM UI Add-on 1.0
Release Strategy for SRM UI Add-on
Info on planning/installation
Readiness check report
Extensibility Cookbook (Customer Fields)
Extensibility using pre-exit and post-exit
Sizing Info
5 Basic Settings for Configuring SAP SRM Fiori Apps
For configuring the My Shopping Cart Fiori app, perform the configuration steps in the following order:
1.1 Configure SAP Netweaver Gateway
1.3 Setting Number Ranges
1.4 Enable SICF Services
1.5.1 Enable Enhanced Search
1.6.3 Display Approver Name in Review Cart
2.1 Settings Required for Catalog Data
2.2 Settings for Embedded Search/ Indexing Data
2.2.4 Create a Connection between TREX and Embedded Search
2.5 Index the Imported Catalog/Product Data

SAP SRM User Interface Add-On 1.0 Configuration

Transcription

Similar documents

The 1897 Sears, Roebuck and Co. Catalog

NAEIR Fact Sheet

Formerly, Zygen Technology

Efficient project management – Although employees are

Supply Chain Through Mobility

High Voltage Maintenance

The Space Catalog Mission and Conjunction Analysis

Early Childhood Inte..

SAP Enhanced Warehouse Management Project