Show TOC

App Implementation: Transfer StockLocate 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)
  • SAP enhancement package 7 for SAP ERP 6.0 (11 (01/2016))
  • SAP enhancement package 8 for SAP ERP 6.0 (01 (01/2016))
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 1.0 for SAP ERP ( 09 (01/2016) )
  • UI for Retail NW731
  • UI for Retail NW740
  • UI for Retail UI 2.0

UIRT401 100 (0009 )

Back-End Components
  • SAP enhancement package 7 for SAP ERP 6.0 (11 (01/2016))
  • SAP enhancement package 8 for SAP ERP 6.0 (01 (01/2016))
  • Retail
  • Central Applications

EA-RETAIL 617 (0011 )

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

2094865 Information published on SAP site

Release Information Note for the FIORI application Transfer Stock

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

SAP Note Number

Description

2094865 Information published on SAP site

Release Information Note for the FIORI application Transfer Stock

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=F0753

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

RETAILSTORE_TRF_STOCK_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_TRF_STOCK

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_TRF_STOCK_SRV (001 )

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

  • SAP_STORE_STOCK_COR_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 617 SP 11 is installed on the back-end server

  • Software component UIRT401 SP 09 is installed on the front-end server

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 Transfer Stock app.

Set the retail store ruling price condition

Sales prices are retrieved from the SAP ERP back-end system in the following order of priority:

  • VKPF - Retail store ruling price (Highest priority)

  • VKAO - Promotion price condition (High priority)

  • VKPO - Normal sales price condition (Lowest priority)

In the Transfer Stock 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 configure this condition as follows:

  1. Add the VKPF condition type to the list of condition types.

    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 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

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

You can use Business Add-ins (BAdIs) to retrieve supplemental product data such as warranty or other relevant information for the product. You find these 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

The Transfer Stock app shares the BAdIs for supplemental data with the Look Up Retail Products, Adjust Stock and Count Stock apps. If you have defined one of these BAdIs for one app, you do not need to define it again to use it for any of the other apps.

For more information, see App Extensibility: Transfer Stock.

Operational Details About the Transfer Stock App

The following section describes details that can help users manage the app.

  • You can control the recency of data in the transfer list by defining a validity period in the Define Basic Settings for Stock Transfer Customizing activity under Start of the navigation path SAP Retail Store Next navigation step In-Store Merchandise and Inventory Management - UI5 Apps Next navigation step Transfer Stock End of the navigation path. This ensures that only transfers in the defined validity period are displayed in the list.

  • You can remove transfer documents that no longer fall within the defined validity period from the list by using the RETAIL_ST_TS_CLEANUP_STAGE_TAB function. You can create a report and schedule it in a background job to execute this task. You can set the cleanup frequency according to your business needs, however you should consider that the longer your validity period, the more records will accumulate in the table. If you schedule the cleanup to run less frequently this will impact the performance of the Transfer Stock app.

  • You can use transaction SLG1 in the back-end SAP ERP Retail system to check the application log. To do so, make the following settings:

    • Object = W_SRS_MOB

    • Sub-object = MOBILE_GM

General Details About the Transfer Stock App

The following are additional details about the Transfer Stock app that can help users understand how the app works.

  • When users access the Transfer Stock app, the system checks whether they are assigned to a site. If they are not assigned to a store, the first thing they will see in the app is a site list. This list comes from authorization object W_SRS_APPL. Once assigned to a site, users can change their assignment anytime by choosing the Settings icon. The assigned site is persisted in table FPB_PERSPARM, which the Transfer Stock app reuses from the SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM).

  • For stock transfers to a different site, providing the receiving storage location is optional. For stock transfers within the same site, the receiving storage location must be provided in the Create Transfer screen.

  • Only products listed in a particular storage location for a sending site are available for product searches against that storage location-sending site.

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.