SAPConsole 

SAP RF Console is used to translate GUI Screens to Character Based Screens which are commonly used with the handheld Radio Frequency devices used in modern warehouses. The idea behind SAPConsole was to enable SAP Customers to utilize the Standard SAP Radio Frequency transactions that became available with SAP R/3 46B. SAPConsole itself does not contain business logic. All functionality is maintained within R/3 and all development for SAPConsole transactions is performed inside the ABAP workbench. SAPConsole requires a Windows NT server and telnet software that supports VT220 emulation. SAPConsole empowers the thousands of workers who use mobile data capture devices in warehouses and distribution centers around the world everyday. SAPConsole can be used with new WM implementations or upgrades of your system.

 Following is the SAPConsole Architecture:  

The mobile transactions could be used with Tablet PC, Pocket PC, PDA and others. Please see the snapshot below:

The list of transactions that are available with use with SAP Console are listed here (click here)

How the transactions are shown in the RF devices:

Following is the snapshot of one of the Mobile transaction:

The above graphic screen is converted to character based screen and shown on the RF device:

Pocket PC  

SAPConsole Benefits

• Hardware independent: Supports any device that uses VT220 terminal emulation
• Free of charge for SAP customers
• Version 4.6B and above provide "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 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
• No 3rd party middleware
• Utilizes your existing ABAP resources
• Ability to customize Mobile Data Transactions through use of exits (every screen has one!)
• Is fully supported by SAP
• 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 complicated 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

SAPConsole Approach Limitations

• If the SAP system is not available, neither is SAPConsole (i.e., the Data Collection System). There is no inherent support for "store and forward" capability.
• No support for automated fail-over. If the SAPConsole machine becomes unavailable, establishing a client connection to another SAPConsole machine is a manual process.
• Standard transactions are currently limited to LES functionality. No IM, MM, SD, PP - although you can certainly add them yourself.
• No known ability to automatically switch between R/3 application servers (in case of failure, etc.)
• 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. (You can, but your users would not like it!)
• Native support for printing barcodes is still somewhat primitive.
• 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 on a non-Windows platform.
• By default, SAPConsole supports two screen sizes: 16 x 20 and 8 x 40. Other screen 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.