Show TOC

App Implementation: Count 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:

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

2169107 Information published on SAP site

Release Information Note for the FIORI application Count Stock

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

SAP Note Number

Description

2169107 Information published on SAP site

Release Information Note for the FIORI application Count 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=F1512

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

retailstore_count_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_COUNT_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_count_stock_srv (001 )

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

  • SAP_STORE_COUNT_STOCK_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:

After you implement the Count Stock app, you can perform the following configuration tasks according to your business needs:

Configure settings to download product images (Optional)

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.
    • WSAPPLICATION = LIM

    • 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 Count Stock app shares the BAdIs for supplemental data with the Look Up Retail Products, Adjust Stock and Transfer Stock apps. If you have defined one of these BAdIs for one app, you do not need to define it again for use in any of the other apps.

Operational Details for the Count Stock and Manage Stock Counting Apps

The following section provides operational details about the Count Stock app.

● The Count Stock app provides access to the Manage Stock Counting (manager version) app through activation of an additional role SAP_ISR_STORE_BCR_STORE_MGR.

●Validity period for items in the inventory count list

You can control the recency of items in the inventory count list by defining a validity period according to your business needs in the Define Basic Settings for Count Stock Customizing activity under SAP Retail StoreIn-Store Merchandise and Inventory Management - UI5 AppsCount Stock . This allows only inventory count items in the defined validity period to be displayed in the list.

● The Past Days and Future Days settings allow you to define the date range for items to appear in the inventory count list. The items are derived from Physical Inventory (PI) documents retrieved from the back-end system. Only documents with a planned count date that falls within the defined range are displayed in the list.

For optimal performance of the app, set a validity period that allows required documents to be retrieved in one counting cycle but not so wide as to retrieve a volume of data that is too large. By default SAP sets the following validity period: Past days = 2, and Future days = 2.

● Cleanup of staging table

The validity period you define for items in the inventory count list can also be used in a background job that periodically cleans up the system staging tables. Any records dated beyond the range you define are removed from the staging table.

You can create a report to use the FM RETAIL_ST_CS_CLEAN_STAGING_TBL function and schedule it as a background job to carry out the cleanup. You can set the cleanup frequency to occur according to your business needs, however the longer the validity period, the more records will accumulate in the table and, if you schedule the cleanup to run less frequently, the performance of the Count Stock app will be impacted.

● Preloading of inventory and product data on the app

The Count Stock app allows you to preload details about the inventory count items or products in the count items when the app is started, or when an associate selects the first item to count. This is done through the Preload Inv Products and Preload Inv Details settings in Customizing for Count Stock . By default, SAP delivers the app with these settings turned off. This means that instead of loading when physical inventory documents are retrieved from the back-end system, the data is loaded the first time a count item is selected. You can achieve a faster response from the app by turning on these settings and avoiding ongoing requests to the back-end system during the counting process as long as the volume of items to count is not too large. A large volume of data may impact the app response time.

● Checking the application log

You can check the application log in the back-end ERP system by using transaction SLG1 and making the following settings:

○ Object = W_SRS_MOB

○ Sub-object = MOBILE_PI

General Details About the Count Stock and Manage Stock Counting Apps

The following are general details about the Count Stock app:

● Site selection

When associates access the Count Stock app, the system checks whether they are assigned to a site. If they are not, 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, associates can change their assignment anytime through the Settings icon. The assigned site is persisted in table FPB_PERSPARM , which the Count Stock app reuses from the SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM).

● The inventory count list

Although the Count Stock app uses Physical Inventory (PI) documents from the ERP system as a source for items in the Inventory Count List , the actual PI document is not directly displayed to the user. When items to be counted span several PI documents, as they usually do for an annual physical inventory count because the maximum number of products that can be included in a single document is 333, the documents are grouped under a common PI number and presented as one count item in the Inventory Count List .

For cycle counting, since the volume of products to be counted is smaller, all products to be counted can often be included in a single count item. No grouping of multiple documents under a common PI number is necessary.

Having too many products in one inventory count item may cause performance issues in the app when the products are loaded for that count item. You can prevent this by creating PI documents with fewer productsin one count item. For example, create one PI document for each distinct category such as fresh items department.

●The Inventory Count List displays a maximum of 1000 items but you can use customize this value by implementing an extension point.

●Local recount

The local recount activity is created in the manager app as a way to conduct a recount without involving the back-end ERP system. It is derived from an original inventory count item which is created from a PI document in the ERP system, but beyond that it has no further connection to the ERP PI document. Managers can issue local recount requests while reviewing stock counts if they see questionable count results that they wish to validate and correct before sending the final count results to the ERP system.

●Count by zone and count by product

All counting activities are considered counts by zone except the following:

○Recount PI documents created in the ERP back end and transmitted to the store

○Local recount requests created in the Manage Stock Counting app.

You can use the RETAIL_ST_CS_CA_HEADER_ENH BAdI to change the count type.

In physical inventory counting of the entire store, products are usually counted by zone . When a count activity is set as a count by zone, associates must enter or scan a zone id to start the count. Then they can either scan or manually add products into the count list. A validation process checks that the product entered is valid for that count activity. Each associate can only count one zone at one time and they must submit the count for each zone before they can start a new zone. One associate cannot take over a zone that is being counted by another associate.

In cycle or daily counting, products are usually counted by product . When a count activity is set as count by product, the associate does not need to enter or scan a zone to start the count. All the products in the count activity will be displayed in the item list. Associates cannot scan or add any new products to the list and they cannot add a new zone when counting by product.

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.