App Implementation: Receive Products
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 |
|
HANA database |
Setup of SAP Fiori System Landscape for SAP Business Suite with SAP HANA Database |
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) |
|
-
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.
|
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) ) |
|
UIRT401 100 (0009 ) |
|
Back-End Components |
|
|
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.
On the back-end server, the following SAP notes must be implemented for this app:
|
SAP Note Number |
Description |
|---|---|
|
General Information: Receive Products App |
On the front-end server, the following SAP notes must be implemented for this app:
|
SAP Note Number |
Description |
|---|---|
|
General Information: Receive Products App |
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=F1248Front-End Server : Activate OData Services
|
Component |
Technical Name |
|---|---|
|
OData Service (Version Number) |
RETAILSTORE_RECEIVE_PRODUCT_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_RECV_PROD |
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.
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.
-
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_RECEIVE_PRODUCT_SRV (001 ) |
In addition, this role contains authorizations to display the related business data.
Note
In addition, this role contains authorizations to display the related business data. |
OData service authorization must be assigned. |
Before implementing the app, you must ensure the following:
-
Software component EA-RETAIL 617 SP08 is installed on the back-end server
-
Software component UIRT401 SP06 is installed on the front-end server
To be able to implement the app, you must perform the following configuration tasks in the back-end system:
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. Users can change their store assignment at any time by using the Settings icon. The assigned store is persisted in table FPB_PERSPARM, which the app reuses from the application SAP In-Store Merchandise and Inventory Management application (Retail In-Store MIM).
To integrate with SAP Jam, each user of the 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.
To check and adapt the delivered Customizing, see Receive Products
under 
Logistics – General 
SAP Retail Store In-Store Merchandise and Inventory Management – UI5 Apps Receive Products 
.
For more information about Customizing for the display of images, see App Implementation: Article, section "Configuration Tasks, Display Functions, Display of Images".
Configure the app behavior as system administrator:
-
Review the standard settings for all stores.
- Create profiles for groups of stores with the same settings.
-
Check and adapt the delivered settings in Customizing for Logistics – General, under
SAP Retail Store In-Store Merchandise and Inventory Management – UI5 Apps Receive Products Define Basic Settings for Receive Products Receive Products Basic Customizing Settings . -
GR Movement Type for PO Reference Document (Mvmnt Type Ref Doc): Maintain goods movement type for goods receipt with reference to purchase order. Delivered default: 101.
-
GR Movement Type for Delivery (Mvmnt Type Delivery): Maintain goods movement type for goods receipt without reference to purchase order. Delivered default: 605.
-
Proposed Received Quantity (Proposed Receive Qty): If users should count each piece/each packing unit, propose zero as the receive quantity. If you mostly trust the suppliers, and rough checks are sufficient, let the system propose the expected quantity as the receive quantity. Delivered default: 0 Zero.
-
Proposed Received Quantity Time for Purchase Order (PO Prop Rec Qty Time (Hours)): For receipt of purchase orders with multiple schedule lines, maintain a time in hours after which the expected quantity should be proposed again, under the assumption that after this time a new delivery will be processed. Otherwise, the app assumes continuation after interruption.
-
Default Unit for DocItem Quantity Fields (Default UoM): Choose the default unit of measure from the purchase order item, delivery or handling unit item (if available), or sales unit of product. Delivered default: 0 Unit of Measure from Purchase Order Item.
-
GTIN Scan Increases Count (GTIN Scan Incr Count): Decide whether scanning GTINs will count/increase the receive quantity.
For more information about Customzing settings for certain use cases, see User Information: Receive Products.
For more information about
app implementation, see http://help.sap.com/fiori_implementation
App Implementation Information for SAP Fiori .