Why RF Data Collection?

1. Expands SAP functionality Profitability Productivity Why RF Data Collection? Solving problems at the source

2. Terminal emulation (R/3) Create your own interface with Systems Enablement Tools Traditional Middleware SAP Console as part of the LES, Warehouse Module. Run SAP GUI wireless on the device Five ways to connect mobile devices

3. Risk / Rewards Create your Own With Systems Enablement Tools • Resources are internal or could be external, can be employed using familiar environments • Very resource intensive • Develop completely or use interface tools to help you create your own solution • Partners off LXE provide tools • People skills required • Functional SAP, Application, Operations, ABAP knowledge • Programming, ADC, & SAP transaction knowledge • Maintenance and upgrades with your SAP solution • Internally spent dollars • High risk to the customer. Big investment of resources • You Own source • Control your destiny • Make modifications internally 5

4. Can Augment SAP functionality with additional code or bolt-on applications Can be pricey & require long implementation cycles Two types Multi-tier Client server base Move and maintain data away from the host Remote validation capabilities Continue running should connection go down Terminal Emulation Running 5250, 3270, VTANSI type connection on mobile device Easier to interface to R/3 Can be less costly than Client Server solutions Creates less risk of implementations, relies on SAP being up 100%. Risk / Rewards Traditional Middleware

5. SAP uses…. IDOC (Intermediate DOC) BAPI (Business API) Remote Function Call (RFC) Middleware

6. A SAP Standard solution No third party interfaces to manage Delivered solution as part of the SAP warehouse LES module Brings price issue of software lower New transactions being supported with each new release TE Solution Needs SAP to be up 100% No remote validation Still need some implementation services Supported with SAP future releases New offering limited functionality today requires exit routines and ABAP programming for significant modifications or additional functionality Risk / Rewards SAPConsole

7. Covered Business Processes Goods Receipt Unloading Unpacking Putaway Interleaving Replenishment Inventory Picking Inquiry Packing Warehouse Goods Issue Loading Delivery Split Printing Labels Shipment Update

8. SAP Console and SAP GUI SAP LES SAP GUI SAP Console Character-based RF Devices Graphical RF Devices

9. SAP’s Solution for Radio Frequency • Support of all major warehouse processes provided by SAP Logistics Execution System • RF terminals communicate data directly • to the SAP system - no middleware required • “Ready-to-use” solution • Works for graphical as well as for character RF terminals • Execution of functions by using • pushbuttons on a touch screen • function keys on a character-based device • scanners for transferring information and verifying data • Hardware-independent functionality

10. What Is SAPConsole? SAPConsole translates Graphical Based (GUI) screens into Character Based screens. This allows the translation of just about any SAPGUI screen into the character-based screens used by RF devices, without the use any RF middleware.

11. SAPConsole vs. Middleware • SAP AG has developed SAPConsole; a wireless native connectivity product for connecting RF devices to SAP systems: • SAPConsole enables RF devices to communicate with SAP’s enterprise software in a real-time manner without middleware. • SAPConsole eliminates delays and programming complexity associated with previous “middleware” based products.

12. SAPConsole Overview SAPConsole Example Screens

13. SAPConsole Overview SAPConsole Example Screens

14. Technical Requirements

15. Components of SAPConsole S D P R O P r o f e s s i o n a l W o r k s t a t i o n 6 0 0 0 Ethernet RF TERMINAL WINDOWS NT/2000 (TELNET CLIENT) SAPCONSOLE RF ACCESS SAP R/3 SYSTEM POINT SAPConsole Administrator TELNET SERVER RF TERMINAL I/O ENGINE TRANSLATION (TELNET CLIENT) INTERFACE

16. RF Controller R/3 Application Server RF Controller/ Access Point SAPConsole – Conceptual Architecture RF front end (Windows NT) Component SAPConsole RF Terminal Data Connection Translation Telnet server I/O Interface Engine Data Connection RF Terminal Translation RF Terminal Standard program Provided By Georgiasoft Provided by SAP Provided by Intercode

17. Single Transaction - Multiple Displays Vehicle mount NonGUI GUI Hand held

18. RF user Interface

19. Benefits Benefits • Hardware independent: Supports any device that uses VT220 terminal emulation • Free of charge for SAP customers • Version 4.6B and above provides “ready to use” RF transactions • All development is accomplished using ABAP in SAP’s development environment • Real time connection to SAP. You get instant response and the actual SAPGUI error messages. • Transactions and screens can be tested in GUI environment without requiring RF devices • Ability to select your own Telnet software and possibly enhance it for your own business needs • Extends the SAP business logic

20. More Benefits • No 3rd party middleware • Utilize your existing ABAP resources • Ability to customize Mobile Data Transactions through use of exits (every screen has one!) Is fully supported by SAP • Far less complex than most middleware systems • Works well with slower connections due to minimal data transmission from server to client • Transactions support both GUI (Win95, WinCE, etc.) and character devices (DOS), since both environments use the same set of screens. • Less complications when upgrading. Most, if not all, of your ABAP code will upgrade. • Menu and screen management is available in the customizing application (IMG) and does not require modifying ABAP code. • Customizable support for various barcode standards

21. Limitations • For a GUI screen to appear on a 16 row x 20 column character screen, the GUI screens must be developed with that in mind, similar to reformatting legacy screens to fit RF terminals. You cannot translate a full GUI screen onto a 16 x 20 text screen. • SAPConsole by default supports two screens sizes, 16 x 20 and 8 x 40. Other screens sizes can be accommodated, although it requires using a screen exit for every Mobile Data Entry transaction to accomplish this task. If you create your own transactions, you only need to keep in mind what will fit on your custom screen size. • Currently, SAPConsole only runs on a Windows platform. There is no support at this time for Linux or Unix. • Note: The SAP database and servers may be a non-Windows platform.

22. Limitations • If the SAP system is not available, SAPConsole (i.e. The Data Collection System) has very limited support for “store and forward” capability. • No known ability to automatically switch between R/3 application servers (in case of failure, etc.) • Standard transactions are currently limited to LES functionality (No IM, MM, SD, PP) – although you can certainly add them yourself.

23. SAP / Intercode • SAP OR Partner responsibilities: • Functionality (ABAP applications) • SAP GUI for graphical terminals • SAP Console for character terminals (Telnet) • Intercode responsibilities: • equipment / installation • technical knowledge / project management • warehouse analysis Together we deliver one perfect solution to support our customers with the best in class Radio Frequency.

24. Simple Nothing more than running SAP GUI from your desktop Hardware requirements are higher Pentium 133 recommended 200 + Windows 95/98/2000/XP 48 MB recommended 64 MB Wireless Data cards in PCMIA port No additional people skills required No additional dollars Low risk No additional 3rd party interfaces to manage mySAP.com mobile apps and workplaces allow more portable application development Risk / Rewards SAP GUI

25. A Few More Questions To Ask Are you using an SAP R/3 implementation partner, who is it? How many sites do you have and what are the locations? Do you need to be on-line all the time? Have you looked at any of the ADC offerings out there? If yes, who? If You are an existing SAP customer, do you have had a previous experience within an ADC implementation? Was it positive or negative and who was the partner involved in that previous solution? Which solution is the best for you?

26. 5 Steps to Success 1. Consider the users — collect data that users really need. 2. Organize data with reports and charts. 3. Use RF for two-way communication. 4. Move to real-time information. 5. Don’t automate outdated procedures. Tips on Your Project