How we are going to achieve this? What are the options available.

To achieve the above requirement, following steps needs to be followed

1. Storage type configuration

2. WPT configuration

3. Put away strategies

4. Product Master

5. Testing

1. Storage type config in which destination should not be determined

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Master Data – Define Storage Types

In storage type in the put away control section select WT GENERIC as 2-Only Storage Type, that means when-ever our put away strategy search for the storage type, section and bin it will search till storage type only so that user can put away the material what ever the bin he wants to put away in that particular Z030 Storage type.

2. WPT config for put away

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Cross Process Settings – Warehouse Task – Define Warehouse Process Type

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Cross Process Settings – Warehouse Task – Determine Warehouse Process Type

3. Put away strategies

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Define Put away Control Indicator

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Define Storage Type Search Sequence for Put away

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Assign Storage Types to Storage Type Search Sequence

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Specify Storage Type Search Sequence for Put away

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Master Data – Activity Areas – Define Activity Areas

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Master Data – Activity Areas – Assign Storage Bins to Activity Areas

4. Product Master (/N/SCWM/MAT1)

5. Testing:

1. Create Purchase order (ME21N)

2. Create Inbound Delivery (VL31N)

3. /N/SCWM/PRDI

Unloading and GR in /N/SCWM/RFUI

Hit Enter

click on F3-New HU

Scan the destination bin and hit Enter

Put away by HU in /N/SCWM/RFUI

Hit Enter

You can see in the above picture; the destination storage bin is blank. User Enter storage bin where he wants to Put away.

Put away is done.

The post Determine Storage bin Blank while Put away-SAP EWM first appeared on ERP Q&A.

As part of this blog, I am going to discuss the functional aspects for RF menu changes, Function code key changes & addition of new screen in the RF Flow.

Menu changes –

We need to create new Presentation profile and assign it to Warehouse.

All other RF Menu configurations are done with respect to new Presentation profile created here.

RF Menu manager can be accessed with following Navigation.

The Standard SAP presentation profile- ‘****’ & Personalization profile – ‘**’ can be copied to own Presentation/Personalization profile.

Standard SAP Presentation profile – **** and Personalization profile – ** Menu

In the Copied Presentation profile – Z001 and Personalization profile – ZP We added few additional menus’ in the Node – ‘Manual Selection’.

You can do all your Menu node changes in this configuration path i.e. Addition of New Node in the Menu path (Just Drag it from left pane where there are all the logical transactions and drop it in the right pane in the required Menu path), Renaming the description, Changing the existing sequence (UP/DOWN) or Deletion of any irrelevant node/sub node etc.

E.g. Renaming the Description

Function Key Changes –

We had business requirement to have 8 Function keys in the screen instead of standard SAP delivered 4.

In order to achieve it, we copied standard Display profile – ** and created new one.

While copying it, we can change the No of Push Button’s Quantity, Screen height/Width, Push button’s length Etc.

We need to assign the Display profile created above to Presentation device in easy access – /N/SCWM/PRDVC.

We can create separate Presentation device for RF scanner’s, Voice terminals and assign the Display profile to them.

When Standard Display profile-** is assigned to Presentation device, it derives 4 Function keys.

The Presentation device is assigned to Resource in /N/SCWM/RSRC.

When Display profile- ** is assigned to Presentation device, it derives 4 Function keys.

Now if we assign the Display profile – ZP which was configured to have 8 Push button’s then RF processing shows 6 Push buttons i.e. Maximum 8 can be shown on the screen.

The Push buttons can be added or Changed in the Configuration node – ‘Define function code profile’.

We can get Logical transaction in RF Menu screen with ‘Ctrl+Shift+F1’.

Go to Customizing, Select the logical transaction and further go to Define function code profile.

You need to select the entry as per Logical transaction/step with respective presentation profile/personalization profile/push button Quantity.

As you can see here there are entries with Push button Qty – 8 and Push button Qty – 4 so you need to make the changes for the respective combination of Presentation profile/display profile/Push button qty. and then all the Corresponding Function keys will be available in the particular RF transaction.

The Sequence for Push button’s from PB1 to PB16 can be assigned or changed here.

The 6 Push button’s available above are assigned in the below config node.

Addition of new Logical transaction

Business asked to add new RF screen’s/Menu’s in the existing flow to print the Bin/Product label. We had separate development for this Product/Bin label print and as part of this Blog I am going to discuss as how we added that in the Existing RF flow.

Separate logical transactions were created for Bin Label & Product label.

We need to assign the Transaction step flow for all the relevant Function keys.

E.g. Push button Print was a trigger for Bin label print so that function code needs to be configured here and Function module needs to be assigned.

SAP EWM RF flow needs PBO (Process before output) and PAI (Process after Input) Function modules for every RF screen and corresponding Function module needs to be assigned in this Node.

Function Code – INIT is to initialize the screen so it has PBO Function module and next when Push button ‘Print’ is triggered the assigned function module here will take of the printing logic.

The Validation for particular Field e.g. in this case we got Material validated after entry and corresponding FM /rest of the details needs to be assigned here.

The required function keys can be assigned here.

In the Node – ‘Map logical transaction Step to Sub-screen’, the Sub screen no and FM can be assigned.

Once above Steps are done, the Screen development is done by developer and result is following RF screen – 9204 for logical transaction – ZPRNTB.

Small trick when working with Web browser link to test RF flows –

Some times when we are working on the RF flow with Web browser link then reading a screen’s detail is not feasible. So instead of navigating to Tcode – /n/scwm/rfui and getting the screen details with ‘Ctrl+Shift+F1’ we can read screen program and screen number as follows.

Click ‘Ctrl+C’ on your web browser link. Click on Properties tab and ‘Ctrl+F’. Then Search keyword – Template and you would get the details for RF screen program- /scwm/saplrf_picking and screen no – 302 in this case.

The post SAP EWM RF Developments first appeared on ERP Q&A.

During a project, we had to study the implementation of the RF voice functionality within SAP EWM. Throughout our research, we didn’t found lots of documentation about it. Thus, i wrote this blog post in order to explain step by step how to implement a pick by voice solution in a SAP EWM environment.

First of all, it is important to define the RF voice limition within SAP EWM. RF voice functionality comes naturally with the EWM core, however, important limitation are listed below :

• Pick by voice can only be used in a system guided environment for warehouse orders. This means only movement from bin A to bin B can be done. There is no possibility for packing or other functionality.
  
• SAP EWM can control the “grammar”, e.g what the operator needs to say to confirm and what the system told to the operator. SAP EWM do not support voice recognition & collection. Dedicated software such as Lydia, Vocollect or others must be used.

The second limition is quite important. It means for our customer that they need to buy SAP EWM, RF devices and a middleware to collect voice.

setting-up pick by voice must follow below steps:

• Create internet service
  
• Create ICF service
  
• Create and publish dedicated HTML template
  
• Manage master data for radio-frequency processing

Create the internet service

In transaction SE80, an internet services is to be created:

enter the transaction name. For vocal pick, it is /SCWM/RFUI_PBV. Once saved, the internet service is created for the transaction:

Create ICF service

After creating the internet service, an ICF service is to be created. In transaction SICF, go to path default_host/sap/bc/gui/sap/its, select node ITS and clic on the wizard:

Below pop-up will appear, just clic on continue :

Then continue:

Select service and continue:

Name your service and continue:

Add the handler CL_HTTP_EXT_ITS:

And complete:

Add the package and save. The entry is added in the node :

You need now to add properties to the service. To do so, double clic on it. On page Service data, clic on GUI Configuration :

Add following entries:

~SOURCES has to point toward the internet services created in SE80 at the first step.

Then, navigate to page Error Pages, tab Logon errors :

Make sure system logon is selected. On Logoff Page, select Redirect to URL and add URL /sap/public/bc/icf/logoff. This will make users completely disconnected from the system at RF log-off.

Create HTML template dedicated to pick by voice

Once the ICF services is created, HTML template must be generated for each dynpro used within the warehouse process. Template generation avoid dumps due to HTML template not found such has the one below:

Dynpro needs to be generated by function group. In EWM, only four function group contains vocal function:

/SCWM/RF_TMPL

/SCWM/RF_SSCR

/SCWM/RSRC_DYNPRO

/SCWM/RF_PBV

Vocal templates need to be generated with style MOBILEXV – Mobile device with speech input.

Generate vocal HTML template

/SCWM/RF_TMPL :

Generate template for dynpro 0011 only. To do so, open screen file, right clic on dynpro 0011, navigate to Additionnal functions then Create HTML Template:

Select your internet service and your theme. For Generating style, be sure to select MOBILEXV Mobile device with speech input and click on save :

You’ll have to repeat this operating for each and every dynpro. To speed up the process, you can do it for all dynpro in a function group. If your warehouse use both vocal and standard RF, you have to generate vocal HTML template only for the corresponding dynpro.

/SCWM/RF_SSCR :

For this function module, generate vocal HTML template only for dynpro 0011/ 00012:

/SCWM/RSRC_DYNPRO:

Here, generate vocal HTML template only for dynpro 0005 / 00011 / 0012 & 0013:

/SCWM/RF_PBV :

This function group is the only one dedicated to pick by voice, hence, you can select all dynpro and generate HTML templates for all.

Publish the internet service

Once all the HTML templates are created, you have to publish the internet service within ITS. In SE80, select internet service, enter your service. Right clic on it and navigate to publish complete service :

Below message indicates a successful creation. You can now proceed to the test of the service.

Test the ICF service

In order to test the ICF service, you need to get back to SICF transaction. Once in it, navigate to the service you have created, right click on it and select test service:

Below pages will open in your default web browser. My apologies, the RF langage of the system is french :

You can notice some texts above. This text is the one of the vocal. You have now to enter resource and device profile wich are created just below.

Master data for Radio-frequency

In standard, EWM offers two different personalization profile :

– ** Standard Personalization

– *1 Pick-by-Voice

required presentation profile is to be assigned to the device. First, device needs to be created, then resource must be created and assigned to a user.

Create the mobile device

Tcode /SCWM/PRDVC is used to create devices profile used in the warehouse. There must be a device for pick by voice and a device for regular RF process. Corresponding display profile is to be assign to the device :

Create a resource and assign it to a user

In order to be able to use the radio-frequency framework, resources has to be created. You can then assign it to a user if you want to set default value.

You create and maintain resources in tcode /SCWM/RSRC. You also assign default value to it. Here, default device YE01 is assign for voice pick.

In a second time, resources can be assigned to a user. This is done in tcode /SCWM/USER. This tcode is used to assign default value to a user when he connects to the RF framework :

Use the RF framework in a vocal way

As explained in the introduction, SAP can conduct the way vocal pick works, but a software to read and collect vocal needs to be used. The way we found out in freeware is with opera browser and text to speech extension.

extension text to speech can be installed

once it is done, you can logon to the environment :

once validated, there is only one menu in the RF framework :

Pick by voices works in a system guided logic. Thus, it will follow the WO assign to the queue of the resource. To make vocal works, you can use text to speech functionality on the screen by pressing ALT + highlight the zone you want to hear :

I hope this paper will be useful to guide you with the PBV functionality. However, some part of this paper are no longer used in S/4 2021. The new EWM_MOBGUI added in S/4 2021 no longer requires HTML template.

The post Setting up pick by voice in EWM first appeared on ERP Q&A.