Show TOC

App Implementation: Print LabelsLocate 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

  • In-Store Fiori application for ad-hoc label printing

  • New oData Services for Label Printing Fiori App

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

SAP Note Number

Description

  • In-Store Fiori application for ad-hoc label printing

  • New oData Services for Label Printing Fiori App

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

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

RETAILSTORE_PRINT_LABELS_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

 rtst_prnt_label

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

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

  • SAP_ISR_STORE_TCR_T

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 SP09 is installed on the back-end server

  • Software component UIRT401 100 SP07 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:

User Authorization and Default Settings:

  • To use the Print Labels app, the user must be authorized for at least one store. The authorization needs to be carried out by assigning the corresponding stores to the user via the authorization object W_SRS_APPL in the SAP ERP backend; the app Print Labels checks for the values W_WSAM_SMA (Material Search) and LA (Labeling) of the field APPL_WSRS.

  • When users access the app, the system first checks whether they are assigned to a store. If they are not assigned to a store, a list of stores is displayed. This list comes from authorization object W_SRS_APPL, mentioned above. Users can change their store assignment at any time by using the Settings icon. The assigned store is persisted in table FPB_PERSPARM (in the SAP ERP backend), which the app reuses from the application SAP In-Store Merchandise and Inventory Management (Retail In-Store MIM); this means that changing the store assignment in the Print Labels app also changes the store assignment in the other Retail In-Store MIM apps, and vice versa.

  • Every user can define a default printer and a default label type, via the same mechanism.

Setup of Label Design Software

  • You need to set up your label design software so that you can print the labels via the SAP ERP backend. For example, you need to install the server of your label design software according to the label design software’s manual, and you also need to design your labels.

Set Up of BAdI Enhancements in the ERP Backend

The BAdI enhancements mentioned below can be found in the SAP ERP backend under Start of the navigation path Logistics General Next navigation step SAP Retail Store In-Store Merchandise and Inventory Management – UI5 Apps Next navigation step Print Labels End of the navigation path.

These BAdI enhancements, amongst others, are used to adapt the label types and the printers to your needs. You can use them to:

  • Connect your label design software to the SAP ERP backend, so that the app Print Labels can call the print service of the label design software

  • Define the label types

  • Define the SAP printers per store for the app Print Labels

  • Define the label type and printer compatibility matrix, if not every printer can print every label

  • Implement any special rules regarding how to find the printers located in a store

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.