Pick by Voice Cookbook

Cookbook
Extended Warehouse Management

Document Version: 1.0 2013-05-21
Pick-by-Voice SCM 9.0

How to build a voice enabled transaction in EWM
PUBLIC
Document History
Version
Date
Change
1.0
<2013-05-21>
First version
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.

Document History
Table of Contents
Objective ......................................................................................................................................................... 4
2
2.1
Overview .......................................................................................................................................................... 5
Generation of XHTML+Voice template .................................................................................................................. 5
2.1.1
Integration into SAP EWM RF Framework ............................................................................................6
Details .............................................................................................................................................................. 7
3.1.1
Screen / Dynpro ...................................................................................................................................... 7
3.1.2
Function Modules (used in RF Framework) .........................................................................................11
3.1.3
BAdI (Business Add-In) ........................................................................................................................ 15
3.1.4
RF Framework ....................................................................................................................................... 16
3.1.5
ITS (Internet Transaction Server) ...................................................................................................... 20

Table of Contents
PUBLIC
Objective
As of release SCM 9.0, EWM uses the existing functionality of RF (Radio Frequency) Framework, RF Picking
transaction and ITS (Internet Transaction Server) template generator 'Mobile Devices with Speech Input' and put
it all together into a new voice enabled RF transaction. The transaction will support picking process and internal
moves in the warehouse. The transaction will support multi-modal data input like keyboard input, barcode
scanning and voice.
The transaction will only use elements of XML language extension XHTML+Voice (X+V) which are support by ITS
Mobile generator.
RF Framework and RF Picking transaction are available as of release SCM 5.0.
ITS Mobile generator for voice is available as of release
o NetWeaver 7.1 from SAP Basis 7.10 SP5; Kernel patch 81
o NetWeaver 7.0 from SAP Basis 7.00 SP15; Kernel patch 132
o NetWeaver 04 from SAP Basis 6.40 SP22; Kernel patch 210
o R/3 Enterprise from SAP Basis 6.20 SP64; ITS patch 28
This cookbook will explain which parts in EWM and ITS are used to create the voice enabled transaction.
PUBLIC

Objective
Overview
2.1
Generation of XHTML+Voice template
1. Create dynpro with its speech attributes on field level.

2. Use of ITS HTML Template Generator Mobile Devices with Speech Input.
3. Get HTML template.
Note
Speech attributes can be found in dynpro on screen and field level. Use SE51 or SE80 to change them.
ITS HTML generator can be found in SE80. On the screen object use context menu 'Other Functions' ->
'Create Template'. Use generating style 'Mobile Devices with Speech Input'.

Overview
PUBLIC
2.1.1
Integration into SAP EWM RF Framework
4. Create new logical transaction in RF Framework (incl. Step flow, validation, )

5. Start ITS service in browser which supports XHTML+Voice
Caution
Please keep in mind that SAP EWM does not offer any voice recognition software. On the devices must be
some software provided by other companies which interpret the XHTML+Voice page coming from SAP
and handle the voice output and voice input to the user.
There are several software and hardware provider which can connect to EWM. Nevertheless there are
different approaches which make use of different parts of the development. One company uses all parts
including the XHTML+Voice templates. Another company uses the ABAP part and create own templates.
PUBLIC

Overview
3.1.1
Details
Screen / Dynpro
The voice attributes are realized as properties either on dynpro level or field level.
On the screenshot below you can see how to trigger the 'Properties' screen on dynpro level.
On the screenshot below you can see how to trigger the 'Properties' screen on field level.

Details
PUBLIC
PUBLIC

Details
The property itself is named 'Speech'.

On the screenshot below you can see how the properties dialog looks like.

Details
PUBLIC
On 'Details' screen you have to switch on the property effect. Either use Effective without additional attributes or
Effective; additional attributes possible. If you use No Effect (Deletion of Property) the property is ignored
even if you maintain additional attributes.
If you want to use the additional attributes, you can maintain them on the 'Additional Attributes' part of the
'Details' screen.
The available attributes are the same on screen and field level.
Available attributes are:
Attribute
Description
Prompt Text
Text to prompt input for a field, such as Enter the client or text spoken to the user
if the screen is displayed.
Filled Text
The text is spoken to the user if speech input was successfully detected. E.g. to
repeat an entered quantity.
Help Text
Help text for speech input. The text is read if no speech input was detected or
validation fails on client side.
Grammar
Grammar for identifying the speech input on client side.
GrammarLnk
Grammar for identifying the speech input that is loaded as an external file on client
side.
TimeOut
Time in seconds until the help text is read, if no speech input is made.
NextField
Specifies the next field with speech input. Will override the default field sequence.
10
PUBLIC

Details
Note
The HelpText is triggered if the X+V events nomatch, noinput and help are raised. This could be
optimized in a custom projects. For some fields a different text for event nomatch and for event help
could be useful.
For an attribute you must define the origin of the attribute value.
0
You enter the value directly
Value is taken from a variable
Value is taken from a text element
After the origin you have to maintain the corresponding column to the right.
3.1.2
Function Modules (used in RF Framework)
3.1.2.1
PBO (Process before Output)
In the function module which is processed before the screen is displayed, you fill the speech attributes by filling
corresponding fields of structure /SCWM/S_RF_SCRELM_PBV.
You prepare the GRAMMAR or GRAMMARLNK.
You fill the PROMPT (on screen or field level).
You fill the HELP.
You add special logic there e.g. splitting the storage bin into aisle, stack and level.
There are some methods available to help you in this. They are all in class /SCWM/CL_RF_BLL_SRVC.
Method
Description
BUILD_HELP_TEXT
Prepare the help text for a field. You pass fieldname (VLENR) and table name
(/SCWM/ORDIM_O) to the method and you get the help text Invalid Source
Handling Unit Verification
BUILD_GRAMMAR_FOR_HU
Prepare grammar for a HU. You pass warehouse number, HU number and
storage bin to the method and you get the possible grammar values as a string.
E.g. HU 80001234 returns 34|234|1234|01234|001234|0001234|80001234.
We need the storage bin to check if grammar conflicts with other HU on this bin.
E.g. if there is another HU 82340034 on the bin, grammar 34 is not unique
and cant be used. In this case the string would look like
234|1234|01234|001234|0001234|80001234.
BUILD_PROMPT_FOR_FIELD
Add space between each figure e.g. 8001234 -> 8 0 0 1 2 3 4
GET_DATA_ENTRY
Reads field DATA_ENTRY from global structure SS_RF_STATIC. Value 1

means Voice Recognition Device.
SET_DATA_ENTRY
Set field DATA_ENTRY in global structure SS_RF_STATIC.

Details
PUBLIC
11
Method
Description
BUILD_INDEX_PBV
Creates an entry in global table ST_RF_INDEX_PBV. This table is only used in

the BAdI / SCWM/EX_VOICE_ATTRIB where you can change the voice
attributes just before the screen is displayed.
GET_INDEX_PBV
Return content of global table ST_RF_INDEX_PBV.
SET_INDEX_PBV
Override complete content of global table ST_RF_INDEX_PBV.
In the PBO function modules two different kind of information are prepared for later use.
- Structure /SCWM/S_RF_SCRELM_PBV contains all voice properties for all screens fields which will are voice
enabled. This must be a structure otherwise it could not be used for the definition on the field or dynpro property
(see chapter Screen / Dynpro). This limits the use of voice enabled fields per screen. You can use up to 10 fields
which have a 'Pompt', 'Grammar' and 'Help' property but only 5 fields can have a 'GammerLnk' or 'Filled' property.
- Table /SCWM/TT_RF_INDEX_PBV contains for each voice enabled field an entry which links to the used fields in
structure /SCWM/S_RF_SCRELM_PBV for this single field. This table is used in BAdI /SCWM/EX_VOICE_ATTRIB
to know what have to be changed
Example
The below example show you that screen field 'PICKHU' has its 'Prompt Text' in field 'FLD_PROMPT_8' of
structure /SCWM/S_RF_SCRELM_PBV and uses ABAP message /SCWM/RF_EN 555 with value
800000053 in message variable 1 as text which is spoken to the user.
Example of screen elements (structure /SCWM/S_RF_SCRELM_PBV) (PBO of step PVMTTO)
Field
Value
SCR_PROMPT
FLD_PROMPT_1
Storage type T020 go to aisle 01
FLD_PROMPT_2
Go to stack 01
FLD_PROMPT_3
Go to level D
FLD_PROMPT_4
FLD_PROMPT_5
Search batch
FLD_PROMPT_6
Take 2 each
FLD_PROMPT_7
Enter remaining quantity
FLD_PROMPT_8
Into HU 800000053. Enter 2 digits
FLD_PROMPT_9
Into position
FLD_PROMPT_10
MSG
LIST_VALUES
GRAMMAR_1
12
01
PUBLIC

Details
Field
Value
GRAMMAR_2
01
GRAMMAR_3
GRAMMAR_4
GRAMMAR_5
GRAMMAR_6
GRAMMAR_7
EWM_NUMERIC.JSGF
GRAMMAR_8
53 | 053 | 0053 | 00053 | 000053 | 0000053 | 00000053 | 800000053
GRAMMAR_9
GRAMMAR_10
GRAMMAR_LNK_1
GRAMMAR_LNK_2
GRAMMAR_LNK_3
GRAMMAR_LNK_4
GRAMMAR_LNK_5
HELP_1
Invalid Aisle verification
HELP_2
Invalid Stack verification
HELP_3
Invalid Level verification
HELP_4
HELP_5
Invalid Batch verification
HELP_6
HELP_7
Enter remaining quantity
HELP_8
Invalid Destination Handling Unit verification
HELP_9
Invalid Logical Position of Handling Unit verification
HELP_10
FILLED_1
FILLED_2
Quantity
FILLED_3
Quantity
FILLED_4
FILLED_5
Example of index table (structure /SCWM/S_RF_INDEX_PBV) (PBO of step PVMTTO)

Details
PUBLIC
13
INDEX
_FIELD
PROPERTY
_TYPE
STRUCT
_FIELD
MSGTY
MSGID
MSGNO
MSGV1
AISLE
FLD_PROMPT_1
/SCWM/RF_EN
559
01
AISLE
GRAMMAR_1
AISLE
HELP_1
/SCWM/UI_RF
020
Aisle
STACK
FLD_PROMPT_2
/SCWM/RF_EN
551
01
STACK
GRAMMAR_2
STACK
HELP_2
/SCWM/UI_RF
020
Stack
LVL_V
FLD_PROMPT_3
/SCWM/RF_EN
552
LVL_V
GRAMMAR_3
LVL_V
HELP_3
/SCWM/UI_RF
020
CHARG
FLD_PROMPT_5
/SCWM/RF_EN
558
CHARG
GRAMMAR_5
CHARG
HELP_5
/SCWM/UI_RF
020
Batch
QTY
FLD_PROMPT_6
/SCWM/RF_EN
554
QTY
GRAMMAR_6
QTY
HELP_6
/SCWM/RF_EN
582
QTY
FILLED_2
/SCWM/RF_EN
703
KQUAN
FLD_PROMPT_7
/SCWM/RF_EN
569
KQUAN
HELP_7
/SCWM/RF_EN
569
KQUAN
FILLED_3
/SCWM/RF_EN
703
KQUAN
GRAMMAR_7
PICKHU
FLD_PROMPT_8
/SCWM/RF_EN
555
800000053
PICKHU
HELP_8
/SCWM/UI_RF
020
Destination
Handling
Unit
PICKHU
GRAMMAR_8
LOGPOS
FLD_PROMPT_9
LOGPOS
GRAMMAR_9
LOGPOS
HELP_9
000
000
000
Level
000
000
000
000
I
/SCWM/RF_EN
570
000
/SCWM/UI_RF
020
Logical
Position of
Handling
Unit
The property type can have the following values:
14
PUBLIC

Details
1 = Prompt Text
2 = Help Text
3 = Filled Text
4 = Grammar
5 = GrammarLnk
In include /SCWM/LRF_PICKINGPBV you can find lots of examples.
3.1.2.2
Validation
We have to distinguish between frontend validation (directly on the device without round trip) and backend
validation.
Frontend validation is done by the software on the device which compares the spoken value of the user with the
'Grammar' or 'GrammarLnk' property value. Software speaks the text of 'Help' property to the user in case of an
invalid validation or the text of 'Filled' property in case of a valid validation.
Backend validation is either done by the RF Framework with a 1 to 1 validation or by a function module maintained
in the validation profile customizing. The function module must also be able to handle the new HU verification
where user only speaks last 2 digits. In function module /SCWM/RF_PICK_PICKHU_CHECK you can find an
example for this
Note
Backend validation is only necessary if the validation is too complex to handle it by frontend validation
with the use of 'Grammar' or 'GrammarLnk' property.
Backend validation is always necessary in a multi modal transaction. Only voice input use the 'Grammar'
and 'GrammarLnk' property for validation. All other input sources must be validated in the function
modules linked to the RF Framework.
3.1.3
BAdI (Business Add-In)
BAdI /SCWM/EX_VOICE_ATTRIB (Enhancement spot /SCWM/ES_RF_FLOW) can be used to change the voice
attributes before a screen is displayed.
BAdI contains a default implementation where e.g. the value of the handling unit number is changed to influence
how the number is spoken to the user. Without the BAdI implementation HU number 8001234 is spoken as
Eight Million One Thousand Two Hundred Thirty-Four, with the BAdI implementation it is spoken as
Eight Zero Zero One Two Three Four.
Implementation can be found in class /SCWM/CL_EI_VOICE_ATTRIB in method
/SCWM/IF_EX_VOICE_ATTRIB~MODIFY_VOICE_PROPERTIES.

Details
PUBLIC
15
3.1.4
3.1.4.1
RF Framework
Structures
/SCWM/S_RF_SCRELM_PBV
RF Presentation Screen Elements for Pick by Voice
/SCWM/S_RF_INDEX_PBV
Index Table of Screen Properties
How the structures are using is explained in PBO (Process before Output).
Structure /SCWM/S_RF_SCRELM_PBV contains a customer include which can be used to add more fields if
needed.
Example
You have more than 10 voice enabled fields on your screen or you have own voice attributes. In this case
you can enhance the structure /SCWM/S_RF_SCRELM_PBV and fill the new fields in the BAdI mentioned
in chapter BAdI (Business Add-In).
3.1.4.2
Table Types
/SCWM/TT_RF_INDEX_PBV
3.1.4.3
Index Table of Screen Properties
Data Entry
To be able to distinguish within RF Framework and transaction coding if we process a voice enabled transaction
we introduce new value '1' for the data entry.
The following coding is influenced by the data entry:
Desription of a field is taken instead of medium field label for an error message
Trigger the BAdI call before the screen is displayed
Remove the automatic menu item numbering (e.g. 1. Pick by Voice -> Pick by Voice)
Remove the automatic list box item numbering
Control field input on RF logon screen (e.g. if warehouse number is defaulted by /SCWM/USER, user have not
to enter / speak it again)
Control the system guided work to trigger transaction 'PVSYSG' instead of 'PISYSG'
Data entry is an attribute of the presentation device (Use transaction /SCWM/PRDVC to maintain).
Initial value means 'General data entry type' (scanner and keyboard based), '1' means 'Voice recognition'.
16
PUBLIC

Details
Caution
Make sure that the 'Shortcut' attribute of the presentation device is initial. The 'Shortcut' functionality is
not supported for the voice enabled transaction.
3.1.4.4
Display Profile
The display profile implies the template screens used in the RF Framework. As we need new template screens
which are voice enabled and contain the needed numbers of push buttons, we needed to introduce a new display
profile '*1'.
Display profile is customizing of the RF Framework (Use transaction /SCWM/RFSCR to maintain).
Data entry is an attribute of the presentation device (Use transaction /SCWM/PRDVC to maintain).
The new display profile *1 is defined with the following data.
Description
Field
Value
Screen Height
HEIGHT
16
Screen Width
WIDTH
40
Pushbutton Text Length
PUSHB LEN
40
Number of Pushbuttons Available

on the Screen
PUSHB QTY
16
Menu Item and Logical Transaction

Text Length
MENU LEN
40
Message Display
MSG VIEW
0 (=Pop-up message screen)
Template Screen Program
TMPL PROGR
/SCWM/SAPLRF_TMPL
Template Screen Number
TMPL NUM
11
Template (with Bottom Message)

Screen Program
TMPL MSG PROGR
/SCWM/SAPLRF_TMPL
Template (with Message Line)

Screen Number
TMPL MSG NUM
0002
Template Screen Title Program
TMPL TITL PROGR
Template Screen Title Number
TMPL TITL NUM
Text
TEXT

Details
Pick-by-Voice
PUBLIC
17
3.1.4.5
Personalization Profile
The personalization profile controls a lot of things in RF Framework.

We introduced new value '*1' to trigger not the RF standard menu ('MAIN') but the specific menu ('PBV') with the
new voice enabled transaction.
Personalization profile is customizing of the RF Framework (Use path 'Extended Warehouse Management' ->
'Mobile Data Entry' -> Radio Frequency (RF) Framework -> Define Steps in Logical Transactions to maintain).
You must assign the personalization profile to the EWM user table (Use transaction /SCWM/USER to maintain).
There you create an entry with key value 'Data Entry' equal '1'.
3.1.4.6
Transaction
New transaction '/SCWM/RFUI_PBV' as starting point for the RF Framework is created. The new transaction set
the right data entry 1 in the beginning to support voice.
Note
Do not use transaction existing transaction '/SCWM/RFUI'. With this transaction voice enabled specific coding is
not processed. If you want to use voice enabled transaction and scanner enabled (RF) transactions in parallel, use
the new transaction.
If you want to use voice enabled picking and scanner enabled picking, use the new transaction AND change the
data entry at the beginning of the scanner enabled picking to space and back to '1' if you leave the transaction. Use
method SET_DATA_ENTRY from class /SCWM/CL_RF_BLL_SRVC.
If the voice enabled picking is not started please re-try with the following settings:
o Assign presentation profile to Warehouse (IMG: Extended Warehouse Management -> Mobile Data Entry
-> Assign Presentation Profile to Warehouse). Set 'Pres. Prof." to default '****'.
o Create presentation device (SAP Menu: Extended Warehouse Management -> Master Data -> Maintain
Presentation Devices). Set "Disp. Prof." to '*1', "Data Entry" to '1' and "Default" to 'X'.
o Create user (SAP Menu: Extended Warehouse Management -> Master Data -> Resource Management ->
Maintain Users). Set "Data Entry" to '1' and "Prsn. Prof." to '*1'.
3.1.4.7
Supported functionality
Beside of the voice enabled picking the following parts of the RF Framework are also voice enabled:
Logon
Menu
List box
Logoff
18
PUBLIC

Details
3.1.4.8
Exception Handling
We use the same business context as the standard RF Picking transaction (TIM and TPI) but have own execution
steps for RF Pick-by-voice transactions.
P1
PbV HU WT Action on Source Data
P2
PbV HU WT Action on Target Data
P3
PbV Product WT Action on Source Data
P4
Pbv Product WT Action on Target Data
Also the available exceptions are different between RF Picking and RF Pick-by-Voice.
Note
For a detailed list of available exceptions, please check directly in customizing. (Path: IMG > Extended
Warehouse Management -> Cross-Process Settings -> Exception Handling -> Maintain Business Context
for Exception Codes; Maintain Exception Code Context; Use Business Context TIM or TPI and the above
mentioned execution steps)
3.1.4.9
3.1.4.9.1
Others
Function keys
Normally the functions on the pushbuttons are shown together with their related function key. E.g. F1 PRINT. We
can do this of course also in voice enabled transaction but this would mean that the user has to speak also the F1
to trigger the PRINT function. Therefore we decided to remove the function key value. This can be done in RF
Framework customizing. In the function code profile leave the function key field empty.
3.1.4.9.2
Repeat of messages/prompts
If a user didnt understand the message there should be a possibility to repeat the message or the prompt (in
general the last instruction from the system).
In standard there is no command foreseen. But each Pick by Voice provider offers such functionality (E.g.
command 'Repeat').
3.1.4.9.3
Changed screens
This is an overview of the new screens:

Details
PUBLIC
19
Function / Where-used
Function Group
Screen number
Template
/SCWM/RF_TMPL
0011
Message
/SCWM/RF_SSCR
0012
List
/SCWM/RF_SSCR
0013
Logon
/SCWM/RSRC_DYNPRO
0011
Logoff
/SCWM/RSRC_DYNPRO
0012
Menu
/SCWM/RF_SSCR
0011
Semi-System Guided
/SCWM/RF_GENERAL_EN
0501
Pick-by-Voice
/SCWM/RF_PBV
0200, 0301, 0302, 0420, 0430,

0501, 0502, 0503, 0504
3.1.4.9.4
Memory parameter
Parameter 'PBV_DENTRY' is created and used at the beginning of the report /SCWM/RF_UI_START. The
parameter is set according to the start transaction and later on used for the data entry of the logon screen.
3.1.5
ITS (Internet Transaction Server)
3.1.5.1
ITS service
New ITS service 'RFUI_PBV' is created. This ITS service calls transaction /SCWM/RFUI_PBV.
Note
Use transaction 'SICF' to maintain ITS service. Follow path 'default_host' -> 'sap' -> 'bc' -> 'gui' -> 'sap' ->
'its' -> 'scwm'
3.1.5.2
MIME objects
The files used for property 'GrammerLnk' are 'EWM_ALPHANUMERIC.JSGF' and 'EWM_NUMERIC.JSGF'. They
are stored as language dependent MIME objects. At the moment only German and English MIME objects exist.
They contain the description of the validation in Java Speech Grammar Format (JSGF)
20
PUBLIC

Details
EWM_NUMERIC.JSGF
#JSGF V1.0;
grammar com.sap.speech.ewm.num
<digits> = 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9;
public <ewm_numeric> = <digits>+;
EWM_ALPHANUMERIC.JSGF
#JSGF V1.0;
grammar com.sap.speech.ewm.alpha
<digits> = 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9;
<letters> = A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z;
public <ewm_alphanumeric> = ( <digits> | <letters> )+;
As you see the grammar contains single letters. Therefor it is needed to speak the letters and digits one by one.
For the letters often NATO alphabet is used.
Example
The value for warehouse AB01 must be spoken 'ALFA BRAVO zero one'.
3.1.5.3
Difference between field input and command
If user speaks something into the microphone it could be a field input or a command. In ITS there are some
predefined commands available. The most important one is 'COMMAND' this changes from field input into the
command mode. In command mode the frontend is taken against the given commands and not against the field
value. All pushbuttons are interpreted as a command where the text on the button is the command literal.
ITS default commands:
Command
Result
COMMAND
Change from field input to command mode
SEND
Trigger a round-trip
LOG OFF
Trigger a log off from the system (Send /nex to the system)
EWM default commands

Command
Result
OKAY
Trigger a round-trip

Details
PUBLIC
21
Command
Result
BACK
Trigger the previous step of the transaction (Go back one step)
CLEAR
FIELDS
Clear the already entered values and continue from the first field
LIST
Trigger the list box screen for the current input field (e.g. warehouse number list on the logon
screen)
EXCEPTION
Trigger the list box screen for the existing exceptions
22
PUBLIC

Details
General Disclaimer
SAP does not represent or endorse the accuracy or reliability of any of the information, content, or
advertisements (collectively, the "Materials") contained on, distributed through, or linked, downloaded, or
accessed from any of the services contained on this Web site (the "Service"), nor the quality of any products,
information, or other materials displayed, purchased, or obtained by you as a result of an advertisement or any
other information or offer in or in connection with the Service (the "Products"). You hereby acknowledge that any
reliance upon any Materials shall be at your sole risk. SAP reserves the right, in its sole discretion and without any
obligation, to make improvements to, or correct any error or omissions in any portion of the Service or the
Materials.
THE SERVICE AND THE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY
DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE
SERVICE OR ANY MATERIALS AND PRODUCTS. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES OF ANY KIND WHATSOEVER WITH
RESPECT TO THE SERVICE, THE MATERIALS, AND THE PRODUCTS.
SAP encourages you to exercise discretion while browsing the Internet using this site.
SAP makes no representations concerning any endeavor to review the content of sites linked to this site or any of
the Materials, and so SAP isn't responsible for the accuracy, copyright compliance, legality, or decency of material
contained in sites listed in the directory or in the Materials.
SAP respects the rights (including the intellectual property rights) of others, and we ask our users to do the same.
SAP may, in appropriate circumstances and in its sole discretion, terminate the accounts of users that infringe or
otherwise violate such rights of others.
If you believe that your work has been copied in a way that constitutes copyright infringement, please follow the
instructions at the top of this page.
Copyright 2008 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of
other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10,
System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400,
AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN,
DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity,
Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium,
Massachusetts Institute of Technology.

Details
PUBLIC
23
Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP
products and services mentioned herein as well as their respective logos are trademarks or registered trademarks
of SAP AG in Germany and in several other countries all over the world. All other product and service names
mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an additional warranty.
24
PUBLIC

Details
www.sap.com/contactsap
Material Number
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies (SAP Group) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are
set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP AG in Germany and other countries. Please see
www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.

Pick by Voice Cookbook

Uploaded by

Copyright:

Available Formats

Pick by Voice Cookbook

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pick by Voice Cookbook

Uploaded by

Copyright:

Available Formats

Cookbook

Extended Warehouse Management

Pick-by-Voice SCM 9.0

Pick-by-Voice SCM 9.0

Pick-by-Voice SCM 9.0

Pick-by-Voice SCM 9.0

Generation of XHTML+Voice template

1. Create dynpro with its speech attributes on field level.

Pick-by-Voice SCM 9.0

Integration into SAP EWM RF Framework

4. Create new logical transaction in RF Framework (incl. Step flow, validation, )

Pick-by-Voice SCM 9.0

Pick-by-Voice SCM 9.0

Pick-by-Voice SCM 9.0

The property itself is named 'Speech'.

Pick-by-Voice SCM 9.0

Grammar for identifying the speech input on client side.

Pick-by-Voice SCM 9.0

You enter the value directly

Value is taken from a variable

Value is taken from a text element

Function Modules (used in RF Framework)

PBO (Process before Output)

You prepare the GRAMMAR or GRAMMARLNK.

You fill the PROMPT (on screen or field level).

You fill the HELP.

Add space between each figure e.g. 8001234 -> 8 0 0 1 2 3 4

Reads field DATA_ENTRY from global structure SS_RF_STATIC. Value 1

Set field DATA_ENTRY in global structure SS_RF_STATIC.

Pick-by-Voice SCM 9.0

Creates an entry in global table ST_RF_INDEX_PBV. This table is only used in

Return content of global table ST_RF_INDEX_PBV.

Override complete content of global table ST_RF_INDEX_PBV.

Storage type T020 go to aisle 01

Enter remaining quantity

Into HU 800000053. Enter 2 digits

Pick-by-Voice SCM 9.0

53 | 053 | 0053 | 00053 | 000053 | 0000053 | 00000053 | 800000053

Invalid Aisle verification

Invalid Stack verification

Invalid Level verification

Invalid Batch verification

Enter remaining quantity

Invalid Destination Handling Unit verification

Invalid Logical Position of Handling Unit verification

Example of index table (structure /SCWM/S_RF_INDEX_PBV) (PBO of step PVMTTO)

Pick-by-Voice SCM 9.0

The property type can have the following values:

Pick-by-Voice SCM 9.0

BAdI (Business Add-In)

Pick-by-Voice SCM 9.0

RF Presentation Screen Elements for Pick by Voice

Index Table of Screen Properties

Index Table of Screen Properties

Trigger the BAdI call before the screen is displayed

Remove the automatic list box item numbering

Pick-by-Voice SCM 9.0

Pushbutton Text Length

Number of Pushbuttons Available

Menu Item and Logical Transaction