App Implementation: Adjust Stock

System Landscape Requirements

In order to be able to run this app in SAP Fiori Cloud, your system landscape has to be prepared for and connected to SAP Fiori Cloud:

Required System Landscape Setup

 Prerequisites

SAP Fiori Cloud: System Landscape and Architecture

Prerequisites for Implementing SAP Fiori Cloud

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

Required Back-End Product (Product Version Stack)
  • SAP enhancement package 8 for SAP ERP 6.0 (03 (08/2016) FP)
  • SAP enhancement package 7 for SAP ERP 6.0 (12 (07/2016))

In addition, the back-end components of the app (such as the OData service) have to be available in your back-end system. These back-end components are delivered with the following SAP product version as part of the listed software component. The required software component for the app is contained in the listed product instances:

Required SAP Product (Support Package Stack)
  • SAP enhancement package 8 for SAP ERP 6.0 (03 (08/2016) FP)
  • SAP enhancement package 7 for SAP ERP 6.0 (12 (07/2016))

Available Instances Containing Software Component
  • Central Applications
  • Retail

Software Component Required for App (Support Package)

EA-RETAIL 617 (0003 )

Required SAP Notes

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

SAP Note Number

Description

2030061 Information published on SAP site

2030061 - Release Information Note for the FIORI application Adjust 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=F0586

SAP Gateway System: Activate OData Services

Component

Technical Name

OData Service (Version Number)

RETAILSTORE_STOCK_CORR_SRV (001 )

For more information about how to activate the OData service, see Quick Guide for Implementation: External Access Point.

Enable App for Access in SAP Fiori Launchpad on Cloud

The SAP Fiori launchpad on cloud is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those apps that have been assigned by an administrator to the catalog designed for this user's role.

SAP delivers preconfigured catalogs for groups of SAP Fiori apps as repositories to create your own catalogs. Along with these catalogs, more technical content is delivered for each SAP Fiori app.

For more information about how to proceed with this content, see SAP Fiori Configuraton Cockpit.

SAP Gateway System 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 in the SAP Gateway system:

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

  • In the SAP Gateway system, 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)

SAP Gateway System: Assignment to Authorization Role

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

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

Caution

If you try to connect version SP02 of the front-end software component UIRT401 with version SP05 of the back-end software component EA-RETAIL, you will not see the sales price for a product, or the last time it was updated in the product detail view. This is due to changes made to improve the performance of the app. To see these fields, you must implement the Enhancement of Product Details BAdI (RETAIL_ST_SC_PRODUCT_ENH) in enhancement spot ES_ODATA_RETAIL_ST_STOCK_COR and populate the two fields.

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 Adjust 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 Adjust 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 each desired image.

    In your system, 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, and make the following settings:

    • 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 ERP 6.0 EHP 7 Next navigation step Application Help Next navigation step SAP ERP Cross-Application Functions Next navigation step Cross-Application Components 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 for BAdI: DMS Configuration for Supplem. Data in Product Lookup to specify your product image provider. This BAdI is available under Customizing for Start of the navigation path Logistics - General Next navigation step SAP Retail Store Next navigation step In-Store Merchandise and Inventory Management - UI5 Apps Next navigation step Look Up Retail Products End of the navigation path.

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

Alternately, you can also associate an image to a product through a URL reference. To do so, implement BAdI: Definition of Product Image Retrieval Format available under : Start of the navigation path Logistics - General Next navigation step SAP Retail Store Next navigation step In-Store Merchandise and Inventory Management - UI5 Apps End of the navigation path.

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 Adjust Stock app shares the BAdIs for supplemental data with the Look Up Retail Products, Transfer 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: Look Up Retail Products.

Additional Configuration-Related Information

The following are additional configuration-related details about the Adjust Stock app.

  • When users access the Adjust Stock app, the system 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. Users can change their store assignment anytime by choosing the Settings icon. The assigned store is persisted in table FPB_PERSPARM, which the Adjust Stock app reuses from the SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM).

  • To integrate with SAP Jam, each user of the Adjust Stock app must have their own account in SAP Jam. They must also register their SAP Jam account email address on the SAP Gateway system. For more information, see http://help.sap.com/sapjam.

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

  • To integrate with an SAP Customer Activity Report system, the following is required:

    • Set the RFC connection from the back-end system to the SAP Customer Activity Repository system in Customizing for Sales and Distribution under Start of the navigation path POS Interface Next navigation step Inbound Next navigation step SAP Customer Activity Repository Integration Next navigation step Define Basic Settings for Integration with SAP Customer Activity Repository End of the navigation path.

      Note

      This setting links the back-end system to the SAP Customer Activity Repository (CAR) system and only needs to be set once for each back-end system. Once it is set, any of the UI5 apps can take advantage of integration with SAP CAR without having to configure this setting again.

    • Activate integration with SAP CAR by implementing BAdI: Activate Integration with In-Store MIM UI5App under Sales and Distribution Start of the navigation path POS Interface Next navigation step Inbound Next navigation step SAP Customer Activity Repository Integration Next navigation step Business Add-Ins End of the navigation path.

      Note

      This activates integration with the SAP Customer Activity Repository (CAR) system and only needs to be set once for each back-end system. Once it is set, any of the UI5 apps can take advantage of integration with SAP CAR without having to implement the same BAdI again.

General Details About the Product List in the Adjust Stock App

The following section describes specific details about the product list.

  • You add products to the list by pressing the '+' icon and then entering text into the Search field. You can add a single or multiple products to the list this way.

  • You delete products from the list by pressing the checklist icon at the top of the page. You can delete a single or multiple products from the list this way.

  • The Open section contains a list of products for which a count or an adjustment was started, but no data was submitted to the SAP ERP backend.

  • The Completed section contains a list of products that have been counted or adjusted and submitted to the SAP ERP backend.

  • You can control the recency of products displayed in the product list by defining a validity period in the Define Basic Settings for Stock Adjustment 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 Adjust Stock End of the navigation path. This ensures that only products in the defined validity period are displayed in the product list.

  • You can predefine a product list for a user by importing records into table ARTICLE_SC_HEAD or by writing a report. The business key of the product list consists of the store ID, the user ID, and the product number.

  • You can remove products that no longer fall within the defined validity period from the product list by using the RETAIL_ST_SC_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 and if you schedule the cleanup to run less frequently this will impact the performance of the Adjust Stock app.

General Details About the Counting Feature in the Adjust Stock App

The following section describe specific details about the counting feature.

  • The counting function is product-based. Users enter counts for one product at a time and submit the counts per product.

  • Any product that already has an existing counting document cannot be selected for counting again or to receive a stock adjustment, regardless of its storage location.

  • The stock quantity displayed for a product comes from SAP ERP for Retail and includes the counted or adjusted values applied by the Adjust Stock app.

  • For ad-hoc counting, the process is based on unplanned counting and it uses the MB_PHYSICAL_INVENTORY function module in a two-step process. The second step is the posting of the inventory in the back-end ERP system.

  • If the user changes the storage location or stock type for a product, the old values will not be retained. Any product counts or adjustments are applied to the new storage location or stock type.

  • Document numbers generated after users submit a product count or an adjustment to the back-end system are not visible on the UI. If required, you must get it from the back-end ERP system.

  • Counts are saved under the product location, for example a specific shelf. Users can create as many locations as they want by choosing the Add Product Location button.

General Details About the Adjustment Feature in the Adjust Stock App

The following section describes specific details about the stock adjustment feature.

  • Adjustments are product-based. Users can enter an adjustment quantity for one product at a time and submit the adjustment per product.

  • The movement type is displayed and selected in the Reason for Adjustment field.

  • The system uses the configuration of the current retail store to process stock adjustments. This Customizing is available under Start of the navigation path Logistics - General Next navigation step SAP Retail Store Next navigation step Goods Movement Next navigation step Grouping of Business Transactions for Other Goods Movement End of the navigation path. The Adjust Stock app uses the one-step goods movement process, and movement types such as 551 and 331. This allows stock quantity in the ERP system to be adjusted immediately. BAPI_GOODSMVT_CREATE is used to create the goods movement document.

  • Document numbers generated after users submit a product count or an adjustment to the back-end system are not visible on the UI. If required, you must get it from the back-end ERP system.

More Information

For more information about app implementation, see Quick Guide for Implementation: External Access Point.