Adding Radio Frequency Data Capture to SAP Software (SAP Console)
An Introduction to SAP Console
Most corporations who implement an ERP system are confronted with
the issue of how to simplify and streamline the logistics process utilizing
radio frequency (RF) technology. For SAP™ R/3® users in particular,
this issue has always been addressed by selecting and implementing a 3rd
party RF "Middleware" system. Since SAP did not offer any type
of RF solution, this became the only choice. In the latter part of 1999,
SAP quietly introduced a product named SAPConsole to finally address the
issue of supporting character-based RF devices from SAP R/3. The question
that now needs to be answered is, "What is SAPConsole and will it
work for my application".
This guide will clear up the mystery about SAPConsole and describe
the benefits and limitations when evaluating an "SAPConsole Approach" to
RF Data Collection.
For RF SAPConsole to work companies will need, along with the SAPConsole implementation, to also implement a WLAN network using the appropriate technology, frequency, compatibility and so on. The SAPConsole consultant should be able to provide advice on this.
History of SAP Console
Several years ago SAP partnered and subsequently purchased OFEK-tech, an Israeli company specializing in Warehouse Management and Control. As "SAP OFEK-tech", one of the main objectives of this new partnership was to develop native support for radio frequency (RF) devices for the SAP R/3 Warehouse Management Module.
Parallel to the OFEK-tech effort, SAP initiated a new more comprehensive Warehouse Management systems strategy starting with R/3 version 4.5 known collectively as the Logistics Execution System (LES). LES integrates the applications of Warehouse Management, Shipping and Transportation, and can operate in an integrated mode similar to all the other modules (MM, PP, etc.) or as a stand-alone system (Decentralized WM).
These two initiatives finally came together starting with LES in version 4.6B. The new RF solution for LES offers several new "Mobile Data Entry" transactions specifically designed for RF users and the supporting operations. This whole suite of functionality including business transactions, configuration, and RF device support is sometimes mistakenly referred to as SAPConsole, since it was first released with version 4.6B. Technically, it is more correct to call this RF solution the "SAPConsole Approach".
Secrets and Tips for a Successful SAP Console Implementation
Resources
Choose your consulting resources very carefully. You may be told that you need an SAP Console Consultant; but what does that really mean? Do you get an ABAP Programmer? Do you get a SAP Functional Consultant in, say, WM?
The answer is that you need both.
-
You need a very good ABAP Programmer. Do not fall in the trap which
some SAP "experts" may sell you a SAP Console specific ABAP programmer.There
is no special knowledge to program in ABAP for SAP Console than there
is for any other ABAP program. If the programmer knows ABAP then he/she
can
automatically create programs for SAP Console. The extra knowledge
that needs
to be known by an ABAP programmer specifically for SAP Console can
be learned within 20 minutes.
- You will also need an SAP Console Logistics Consultant. This SAP Consultant,
in addition to the SAP Console specific knowledge she/he should
also be an all-round good Logistics consultant as well. You may be told
that you need
a Functional WM Consultant. That is partially correct - you need
your SAP
Consultant to know WM, in addition to MM, IM, SD, QM, and PP. Why?
Because SAP Console processes involve the scanning and data collection of your
products
within and during the processes of all the above mentioned SAP
Modules.
- For example; when you do an Inbound from Purchasing you must
be able to link the SAP Console process to transactions within
IM and WM depending
on whether your warehouse is IM or WM managed.
- When you do an Inbound from Production then your SAP Console consultant
needs to know the PP procedures.
- When you do an Outbound with a Sales Delivery to your clients
then the SAP Console consultant needs to know the SD, WM
and IM processes.
- Of course there are many internal WM and/or IM transaction
- In addition if your organization uses QM for the quality
process then the SAP Console consultant must know QM which
also intervenes along many processes
within
MM, SD, and PP.
- Therefore, the SAP Console Consultant must be familiar with all the above modules.
- For example; when you do an Inbound from Purchasing you must
be able to link the SAP Console process to transactions within
IM and WM depending
on whether your warehouse is IM or WM managed.
- Do not fall for the trap that an ABAP programmer will be able to do
the SAP Console implementation on his/her own. Most ABAP programmers
lack the functional and configuration knowledge of all the above SAP Modules.
- A good SAP Console consultant should be able to provide advice on:
- all the above modules,
- on SAP Console,
- on the Hardware and Software choices and requirements that come
along with an SAP Console implementation,
- on WLANs requirements
- on Security and Encryption technology and implementation
of a Wireless environment
- all the above modules,
- Make sure that the SAP Console Consultant and the ABAP programmer work really closely - their offices physically in close proximity from each other in order to achieve rapid testing, error finding, resolution and retesting turn around cycles.
SAP Console hardware/software
Before you purchase your RF Barcoding equipment you need to first analyse your processes to find out how these equipment will be used. The RF Handheld Terminals must be user friendly to use and this really depends on your processes.
Some RF handheld terminals have many directly accessible buttons and functions on their keyboard, but this means that the buttons are pretty small and hard to see. This in turn would make it difficult for the Users to operate in a dark warehouse for example. On the other hand are other RF handheld devices which have fewer but larger buttons on their keyboards. While this may seem really user friendly, it also means that many functions in order to be performed they will have to be executed with a combination of key strokes on the RF handheld device. What does this mean for your training and making sure your users remember the key strokes? Belgravium have a range of hardware that has been optimised in design to cater for just these types of scenarios.
There are many other issues to consider when deciding for the hardware equipment such as the Wireless Access Points (brands, functionality, Wireless security), the servers to run SAP Console and so on, with 20 years+ experience of RF Belgravium can provide invaluable advice on all hardware issues.
There are also many issues to consider in relation to Software requirements and implementation such as Telnet server and Client, the SAP Console Text GUI, the OS and Emulation software implementation and configuration for the RF terminals and so on.
WLAN Choices And Security
Along with the any SAP Console implementation comes the implementation of a Wireless Local Area Network (WLAN). You need to make choices again on hardware equipment and technology (802.11b, 802.11a, 802.11g, or the upcoming 802.11i). There are numerous issues to consider in making the right decision.
What about Security? Implementing a WLAN without security for your data and your internal network is like leaving your house unlocked for anyone to walk in. A good SAP Console consultant would be able to advise you on these issues.
The Bottom Line
Along Be careful who you trust. Your SAP Console implementation can be extremely successful with good SAP Console Consultants and good ABAP programmers. More often than not, your processes will not be covered by the standard SAP Console processes - do not fall in the trap that the "standard works fine". There are companies in the market promising that they can implement SAP Console within 10 days - this is an outright wrong statement. If you want to do it right you will have to analyze your processes, configure, develop, test and train your users to your company's specification.
A successful and complete SAP Console implementation
which would include the tasks of Business Analysis
and Blueprinting,
Hardware/Software
RFQs and
Purchase, Implementation, Configuration, Testing,
Training and Go-Live realistically will take
anywhere from 5 to 9 months
depending
on the processes
you will
implement, the Purchasing flexibility, the openness
of the project, the amount of politics within
your organization, the speed
of
decision making, the degree
of good communication.

