Show TOC

App Implementation: Look Up Retail ProductsLocate this document in the navigation structure

System Landscape Requirements

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. Depending on the database type serving as the basis in your system landscape, it has to be set up for SAP Fiori and has to meet the respective prerequisites:

Database SAP Fiori System Landscape Setup Prerequisites

ABAP environment

Setup of SAP Fiori System Landscape for SAP Business Suite with ABAP Environment

Installation Requirements (Transactional Apps)

HANA database

Setup of SAP Fiori System Landscape for SAP Business Suite with SAP HANA Database

Installation Requirements (Fact Sheets)

The SAP product version in the back-end system serving as the the basis for the app must be the following:

Required Back-End Product (Product Version Stack)
  • EHP4 FOR SAP ERP 6.0 - SPS 05 (11/2009)
  • EHP4 FOR SAP ERP 6.0 / NW7.01 - SPS 05 (11/2009)
  • EHP5 FOR SAP ERP 6.0 - SPS 08 (05/2012)
  • EHP6 FOR SAP ERP 6.0 - SPS 04 (08/2012)
Each SAP Fiori app consists of front-end components and back-end components:

  • The front-end components of the app consist of the user interfaces and content required for launching the app on the SAP Fiori launchpad. These components have to be installed on your front-end server.

  • The back-end components of the app mainly consist of the OData services required for the app. These components have to be installed in your back-end system.

The front-end and back-end components of the app are delivered with the following SAP product versions as part of the listed software components. The required software components for the app are contained in the listed product instances:

App Component

Required SAP Product Version (Support Package Stack)

Available Instances Containing Software Component

Software Component Required for App (Support Package)

Front-End Components

 SAP Fiori transactional apps 1.0 for SAP ERP ( 05 (07/2015) )
  • Retail UI ERP 6.04 NW740
  • Retail UI ERP 6.04 NW731

UIX02RT4 100 (0002 )

Back-End Components

SAP Fiori transactional apps 1.0 for SAP ERP (05 (07/2015))

Retail INT ERP 6.04

GBX02RT4 604 (0002 )

For more information about the installation of front-end components, see http://help.sap.com/fiori_implementation.

The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your respective back-end system and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information about virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.

Required SAP Notes

On the back-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

1962350 Information published on SAP site

FIORI Retail Store Product Lookup: Change History

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

1962350 Information published on SAP site

FIORI Retail Store Product Lookup: Change History

Implementation Tasks

The following sections list tasks that have to be performed to implement the required components of the app. The tables contain the app-specific data required for these tasks.

You can find the data required to perform these tasks in the SAP Fiori apps reference library at:

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0431

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

RETAILSTORE_PRODUCT_LKP_SRV (001 )

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAP UI5 Application

Component

Technical Name

SAP UI5 Application

 RT_PRODUCT_LKP

For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services.

Enable App for Access in SAP Fiori Launchpad

To define the access of single users to this app in the SAP Fiori launchpad, technical content is delivered, such as catalogs and example roles.

You can find an overview of the delivered technical content for this SAP Fiori app in the SAP Fiori apps reference library.

For more information about how to procede with this content, see Enable App for Access in SAP Fiori Launchpad.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

Note

Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server :

  • On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.

  • On the front-end server , you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.

OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server : Assignment to Authorization Role

RETAILSTORE_PRODUCT_LKP_SRV (001 )

In addition, this role contains authorizations to display the related business data.

  • SAP_STORE_PRDCT_LKP_APP

Note

In addition, this role contains authorizations to display the related business data.

OData service authorization must be assigned.
Prerequisites for Implementation

Before implementing the app, you must ensure the following:

  • Software component EA-RETAIL 604 is installed with the latest SP on the back-end server

  • Software component GBX02RT4 SP 02 is installed on the back-end server

  • SAP Enterprise Search is deployed and TREX-based models are imported

  • Software component UIX02RT4 SP 02 is installed on the front-end server

  • Business function Retail, In-Store Merchandise and Inventory Management is configured, and basic master data is prepared

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks in the back-end system:

Required Configuration Tasks

The following configuration tasks are required to enable the Look Up Retail Products app.

Set the VKPF pricing condition

In the Look Up Retail Products app, the retail store ruling price condition VKPF is required to read the most current price for products from the back-end system. You must customize this condition as follows:

  1. Add the VKPF condition type to the list of condition types. Create the VKPF condition type if it is not found.

    Start of the navigation path Sales and Distribution Next navigation step Basic Functions Next navigation step Pricing Next navigation step Pricing Control Next navigation step Define Condition Types End of the navigation path

  2. Assign the VKPF condition type to the VKP001 pricing procedure.

    Start of the navigation path Sales and Distribution Next navigation step Basic Functions Next navigation step Pricing Next navigation step Pricing Control Next navigation step Define and Assign Pricing Procedures End of the navigation path

  3. Assign the VKPF condition type to the ruling price.

    Start of the navigation path Logistics General Next navigation step SAP Retail Store Next navigation step Sales Prices Next navigation step Basic Settings for Sales Prices End of the navigation path

Enable SAP TREX-based enterprise search

Configure settings to enable TREX-based SAP Enterprise Search. Ensure that the MATERIAL model is available.

For more information, see Start of the navigation path SAP Service Marketplace Next navigation step Installation & Upgrade Guides Next navigation step SAP NetWeaver Next navigation step SAP NetWeaver Enterprise Search 7.3 End of the navigation path.

Optional Configuration Tasks

The following configuration tasks are optional and can be implemented according to your business needs.

Configure settings to download product images)

If you are using the Document Management System (DMS) provided by SAP as the product image provider, configure the required settings to enable product image downloads as follows:

  1. Create a document for a desired image.

    In DMS, execute transaction CV01N, and make the following settings:

    • Document Type = DRW

    • Document Part = 000

    • Document Version = -

    Press Enter and make the Document Status = WR (Work Request).

  2. Upload the desired image file.

    Defined storage category = DMS_C1_ST

  3. Link the document to a related product number in SAP ERP.

For more information, see .http://help.sap.com/businesssuite Start of the navigation path SAP Product Lifecycle Management Next navigation step SAP PLM as part of SAP ERP Central Component Next navigation step Application Help Next navigation step Document Management End of the navigation path .

If you are not using DMS as the product image provider, provide a BAdI implementation to specify your product image provider

Configure settings to retrieve supplemental product data

Use the following Business Add-ins (BAdIs) to retrieve supplemental product data such as warranty descriptions or more detailed product information.

You find the BAdIs in Customizing for SAP Retail Store under Start of the navigation path In-Store Merchandise and Inventory Management - UI5 Apps Next navigation step Look Up Retail Products End of the navigation path.

Note

When you define these BAdIs once, they can also be shared by the Adjust Stock app.

  • BAdI: DMS Configuration for Supplemental Data in Product Lookup

    You use this BAdI to retrieve configuration information for the Supplemental Data Query for Product Lookup BAdI.

  • BAdI: Supplemental Data Query for Product Lookup

    You use this BAdI to retrieve supplemental data for the product.

For more information, see App Extensibility: Look Up Retail Products

Provide information about nearby stores

Add information for nearby stores using transaction WSD_CBP.

Setup similar products (variants of generic articles)

Create variants of generic articles with transaction MM41. This transaction relates products to other similar products.

For more information, see SAP Library at help.sap.com then go to Start of the navigation path SAP for Industries Next navigation step SAP for Retail Next navigation step SAP Retail as Part of SAP ERP Next navigation step Enhancement Package 5 for SAP ERP 6.0 End of the navigation path. Choose Application Help then SAP Library. Choose Start of the navigation path Master Data Next navigation step Article Master Data Next navigation step Articles: Article Categories End of the navigation path

Additional Configuration-Related Information

The following are additional configuration-related details for the Look Up Retail Products app.

  • When users access the Look Up Retail Products app, the system first checks whether they are assigned to a store. If they are not, a list of stores is displayed. This list comes from authorization object W_SRS_APPL. Users can change their store assignment anytime through the Settings icon. The assigned store is persisted in table FPB_PERSPARM, which the app reuses from the SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM).

  • The following shipment and goods receipt document types are supported for incoming shipments:

    • Purchase order

    • Material document

    • Handling unit

    You can set the validity period for each document type through the following Customizing activity in Logistics - General:

    Start of the navigation path SAP Retail Store Next navigation step Goods Movement Next navigation step Basic Settings for Goods Receipt End of the navigation path.

    1. In the Control of PDC Procedures section, set the value of the Retail Store MDE Scenario to 2 and save this setting. This ensures that required fields related to customization for Retail Store are displayed.

    2. In the Other Fields for PDC Control section, set the value of the Days Following After Date field to reflect the required validity period in days.

    3. Assign the schema to the current store.

  • To integrate with SAP Jam, each user of the Look Up Retail Products app must have their own account in SAP Jam. They must also register their SAP Jam account email address on the SAP Gateway system and ensure that they use the same one for their SAP Jam account. For more information, see help.sap.com/sapjam.

  • You can use transaction SLG1 in the back-end SAP ERP Retail system to check the application log. Enter the settings as follows:

    • Object = W_SRS_MOB

    • Sub-object = MOBILE_PL

General Details About the Look Up Retail Products App

The following are general details about the Look Up Retail Products app.

  • A product search returns a maximum of 50 search results. This is to optimize app performance. If this is not sufficient to find the desired product, users should refine their search by entering a longer search text.

More Information

For more information about app implementation, see http://help.sap.com/fiori_implementation Start of the navigation path App Implementation Information for SAP Fiori End of the navigation path.