3708 Implementing ITSmobile at Johnsonville Sausage

8/13/2019 3708 Implementing ITSmobile at Johnsonville Sausage

1/43

]

Orange County Convention CenterOrlando, Florida | May 15-18, 2011

Implementing ITSmobile at Johnsonville Sausage,Radio Frequency in SAP

Paul Krier Johnsonville Sausage, LLC.

Mirela Sotropa itelligence, Inc.


2/43

Real Experience. Real Advantage.

[

2

Agenda

Introduction

The Team. The Project.

Background of Radio Frequency (RF) Technology in SAP

Implementing RF Applications using ITSmobile

Learning Points

Best Practices Appendix


3/43


[

3

Johnsonville Sausage, LLC.

Established in 1945 by Ralph and Alice Stayer

Johnsonville is the most popular brand of sausage in the United States and is

available in Japan, Canada, China, France, Mexico & over 30 other countries

Still privately held

1400+ Members


4/43


[

4

Johnsonville Sausage, LLC. (Contd.)

On SAP since 2005

HCM, FI/CO,PPPI, MM, SD, QM, WM, PLM, DMS

Portal, APO, BI, BOBJ, CRM

ITSmobile is running on SAP ECC 6.0. EHP 4

MS SQL Server 2005, 1.4 TB Database

Windows Server 2007 running on VMware


5/43


[

5

itelligence, Inc. More than 20 years of SAP experience

We are one of the leading international full-service provider exclusively focused on

SAP solutions

History

1989 Founded as SVP, in Bielefeld, Germany

2000 Merger of Apcon AG and SVC AG to form itelligence AG

2007 Cooperation with NTT DATA / NTT Communications

Scope of Services

SAP Software Reseller to SME Market SpaceSAP Global Implementation Partner

SAP Global Managed Hosting Partner

SAP Global Support

StaffMore than 1,900 employees, worldwide

Clients

More than 3,000 clients in various industries


6/43


[

6

itelligence Facts

SAP Business Partner & Alliance Partner Services

One of the 12 worldwide Global Partner Services

Channel Partner and Solution Partner

Largest Global SME Software Reseller

One of the 10 worldwide Global SAP Hosting Partners

SAP Alliance Partner Support

SAP Pinnacle Award Winner 2006 2008

2010SAP Overall Partner of the Year

Most successful international and German medium-sized business

partnership with SAP


7/43


[

7

The Implementation Team

Chris Galica Project Manager

Paul Krier SAP Technical Lead/Architect

Mirela Sotropa SAP Platinum NetWeaver Consultant

Bob Meyers WM/MM User Advocate

Mark Hembel Sr. Systems Analyst

Brian Cudworth Shipping Team Lead


8/43


[

8

The Project

Migrate existing RF Applications from SAPConsole to

ITSmobile

Take advantage of the long-term supported ITS technology

Access ABAP Dynpro based applications using a web browser

Provide users with a more user-friendly interface

No change to application business logic

Old RF scanner replacement


9/43


[

9

Initial Expectations

ITS would be slower than Telnet

ITS would not handle movement between access points as wellas sap console with Georgia Softworks

We would not change ABAP as part of this project

We would use Internet Explorer for the browser


10/43


[

10

Background of RF Technology in SAP


11/43


[ Mobility (RF) in SAP Is it Possible?

Why do I care?

How can you do it?

What are the magic ingredients?

Learning points

11


12/43


[ Mobility (RF) in SAP Why do I care?

SAP running on mobile devices

RF Guns scan goods

Information is entered through SAP transaction screens on Guns Data is stored in SAP system

Increase efficiency of Warehouse Management processess

Goods Receipt and Goods Issue

Inventory and Picking

Load and Unload

Simple interface on minimal real estate

Rugged, reliable

12


13/43


[

13

SAP Mobility (RF) in SAP How can you do it?

Four Approaches:

SAPConsole

Web-enabled SAP Console (SAP recommends to use ITSmobile as of Basisrelease 4.6c and higher instead)

ITSmobile (Internet Transaction Server for Mobile Devices)

Mobile Web Dynpro


14/43


[

14

Implementing RF Applications in SAP - SAPConsole

SAPConsole - Allows character based devices to connect to SAPjust like a GUI based client

SAPConsole Server

Telnet

SAP

All Data FLow


15/43


[

15

Implementing RF Applications in SAP (ITSmobile)

ITSmobile - Internet Transaction Server for Mobile Devices

Refer to OSS note 325616 (Platform Availability Matrix: http://service.sap.com/pam)

Internet Explorer on Windows

Internet Explorer 6.0 MozillaFirefox1.X

Windows, Linux, Mac OS X


16/43


[

16

SAPConsole vs. ITSmobile: Side-by-side comparison

CHARACTERISTICS SAP CONSOLE (1999) ITSmobile (2007)

SOLUTION

PROFILE

First SAP native RF solution

Focused on industrial mobile

devices

ABAP-based

Replacement forWeb SAP Console

Any web-based application

ABAP and HTML

SOLUTION

MATURITY

Most installations, stable, wellunderstood.

Long history (~25 years) of using

industrial RF devices

ITS technology in use for many years (~1998);became part of the SAP kernel (~2004)

ITSmobile formally introduced in 2007

Ready for prime time


17/43


[

17

SAPConsole vs. ITSmobile: Side-by-side comparison(Contd.)

CHARACTERISTICS SAP CONSOLE ITSmobile

SOLUTION

ARCHITECTURE

Requires a Windows based machine

(Telnet and SAP Console)

Telnet over TCP

Mobile devices running a client browser

HTML over HTTP/HTTPS

DEVICE

COMPATIBILITY

Supports any device that has the VT220

terminal emulation.

Supports any device with an HTML

browser.


18/43


[

18



USER INTERFACE &

EASE OF USE

Text-based interface.

Simplistic interface.

Screen navigation driven by function

keys.

Browser-based interface.

Screen navigation, supports both function

key and touch screen input,

UI enhancements possible.

DEVELOPMENT

ENVIRONMENT

Entirely done in ABAP Workbench.

SAP Console solutions are developed

in ABAP and rely on the RF screens

(SAPGUI Dynpro screens).

Entirely done in ABAP Workbench (ABAP

and HTML editors).

ABAP and HTML-based. The HTML

conversion is supported by the ABAP

Workbench.


19/43


[

19



FUNCTIONAL

COMPONENTS

(WM, EWM, IM)

Can be used with any SAP functionalarea (WM, IM, EWM, etc.)

Can utilize the RF transactions in WM

as they are written in ABAP.

Can be used with any SAP functional area(WM, IM, EWM, etc.).

Can utilize the RF transactions in WM as

they are written in ABAP.

PERFORMANCE

Primarily dependent on the SAPbackend system where the ABAP

program is running.

In general, better than browser-based

solutions due to less overhead and less

complex screens.

Primarily dependent on the ITS core

engine and the SAP backend system where

the ABAP/HTML program is running.


20/43


[

20

RF Applications: Magic Ingredients

One transaction Different Display

Screen size 8X40:

Function keys have a maximal

length of 9 digits SAPConsole:

- Does not

display frame

with

additional

information

-Suppresses

empty linesScreen size 8X40:

Screen size 16X20:


21/43


[

21

RF Applications: Magic Ingredients (Contd.)

Menu Path: SPRO /Mobile Data Entry/ Define Menu Management


22/43


[

22

RF Menu Configuration

Menu Path: Logistics Entry > Mobile Data Entry > Define Menu

1. Warehouse number The warehouse number for which this menu will be valid

2. Dynamic menu Name of the menu you will assign to the user(s)

3. Sequence The order placement of the menu item within the dynamic menu

4. Menu / Trns. 1 executes a menu, 2 executes a transaction


23/43


[

23

Create an RF Queue

Menu Path: Logistics Entry > Mobile Data Entry > RF Queue Management

1. Queue - Relevant to the group of functions this queue will use

2. Queue Name - Text that may appear on the handheld for users assignedto the queue


24/43


[

24

Assign RF Queue and RF Menu to RF Users

Menu Path: Logistics Entry > Mobile Data Entry > RF Queue Management


25/43


[

25

Assign RF Queue and RF Menu to RF Users (Contd.)

1. Warehouse - Warehouse number

2. User - RF User ID

3. Status - Check if user is active

4. Screen Format - Screen format Size of anticipated device5. Main Menu - Menu name defined in step 4 above


26/43


[

26

ITSmobile Implementation: Customer Guide

Select an RF network and appropriate devices

Decide if an Industrial Browser is needed

Plan how bar-coded documents and labels will be printed Check OSS note 325616 (Platform Availability Matrix:

http://service.sap.com/pam)

Continue as for any other project


27/43


[

27

ITSmobile Implementation: Customer Guide (Contd.)

Map the functional process to standard SAP transactions. . Finalized

business processes are key;

Review the list of RF transactions delivered by SAP

Determine any RF transactions not delivered by SAP or not usable as

delivered

Determine the exact SAP transactions and associated input that will be

executed during the custom processes. Do not use Enjoy style

transactions such as MIGO. Use old transaction codes if necessary; Identify any processes that can not be managed by standard SAP

functionality

Execute the project as any other functional and technical project with

technical design, functional configuration, development, testing, etc.


28/43


[

28

Review custom development to ensure compatibility with

mobile devices and browsers

Additional customization needed to run existing RF Application

on the new mobile devices (e.g. eliminating scroll bars, white

space, and other navigational challenges)

Perform extensive and ruthless testing of all RF transactions in

the new environment

Learning Points


29/43


[

29

Make sure deployment expectations are realistic.

It is easier to deploy a few functions or functional areas at a time

rather than a big-bang approach.

Seek the minimum if you are inexperienced in RF.

Select mobile devices, their configuration (including O/S) and

determine if an industrial browser is needed as early aspossible.

We decided to use an industrial browser for getting all the

functionality of the mobile device used. Transactions needed to be re-tested on final configuration.

Learning Points (Contd.)


30/43


[

30

Functional process design needs to be complete and

completely understood

Have full development environments including an available RF

network, however small, and bar-code printers

Do not overcomplicate the RF device configuration.

We started out with many packages being deployed to the

device.

We achieved better performance by narrowing it down to acouple of packages.

Learning Points (Contd.)


31/43


[

31

ITS Mobile performance was not an issue

ITS Connection issues did not materialize We had issues, but mostly due to new devices and new APs

Resolved by finding sweet spot of device and AP configuration

We had to enhance existing ABAP screens

SAP Console-enabled transactions had to be tweaked for use

with ITSmobile

Enhanced RF screens for improving navigation on RF screens(remove white space, scroll bars)

What really happened


32/43


[

32

We chose to use Wavelink industrial browser.

Quick Scan functionality

Easy to lock down

Devices used: LXE MX7, LXE MX9, Intermec CV30

What really happened (Contd.)


33/43


[

33

Simplification of environment through removal of SAPConsole

server

Eliminating number of licenses for Georgia Softworks

Transaction title shown in the browser heading

Nice feature, was planned as future project to add through

coding

ITS functionality exposed for other uses

SAPConsole no longer maintained

New uses outside of warehouse envisioned

Return on Investment


34/43


[

34

References

Demo / Q&A


35/43


[

35

Appendix

References

Transaction Codes

Tips & Tricks


36/43


[

36

References

Online References

http://help.sap.com

www.sdn.sap.com (Search key ITSmobile in SAP Developer Network)

General ITSmobile Notes 1070064 Comparison of Web SAP Console with SAP ITSmobile

1037715 ITSmobile: Supported screen elements (SMP login required) 705013 Timeout for ICF services based on ITS

737625 Parameter recommendations for the ICM

742048 Integrated ITS, memory requirement in application server

885580 Integrated ITS: Configuration Parameters

Find further related SAP notes using search key "ITSmobile" in CSS.


37/43


[

37

References

Printed References (SAP-Press.com)

Optimize your Mobile Applications in Warehouse and Shipping with SAPWM

Author(s): Dirk Eichholz, Jan-Martin Lichte, and Hans-Georg Nvemann

SAP Warehouse Management: Functionality and Technical Configuration

Author(s): Martin Murray


38/43


[

38

References

Transaction Codes

SICF HTTP Service Hierarchy Maintenance SIAC_REGENERATE_TEMP Regenerate IAC Templates

SIAC_PUBLISH_ALL_INT Publish All ITS Services

LRF1 RF Monitor, Active

LRF2 RF Monitor, Passive LRFMD Maintain RF user master data

SITSPMON Monitor for Internal ITS

SE80 ABAP Development Workbench

[


39/43


[

39

Tips & Tricks

Customize the LogOff Page in SICF

(Maintain the Explicit Response Page Body in SICF)

References

[


40/43


[

40

Tips & Tricks



References

[


41/43


[

41

Tips & Tricks



References

[


42/43


[

42

ICF parameters changed: ms/http_timeout from 20 to 120

icm/max_threads from 50 to 200

Icm/keep_alive_timeout from 60 to 600

em/global_area_MB from 512 to 1024

ms/http_timeout from 20 to 120

rdisp/plugin_auto_logout from 1800 to 2600 icm/min_timeout_mpi set to 30000

icm/max_timeout_wp set to 2000

See notes: 705013, 737625, 742048, 885580.

References

[


43/43


[

]Thank you for participating.

SESSION CODE: 3708

Please remember to complete and return your

evaluation form following this session.

For ongoing education in this area of focus, visit www.asug.com.

Documents

3708 Implementing ITSmobile at Johnsonville Sausage