sap connectivity

7/28/2019 SAP Connectivity

http://slidepdf.com/reader/full/sap-connectivity 1/26

• Expands SAP functionality• Profitability

• Productivity

Solv ing p rob lems at the source

Why RF Data Collection?



Five ways to connect mobile devices

• Terminal emulation (R/3)

• Create your own interface with SystemsEnablement Tools

• Traditional Middleware

• SAP Console as part of the LES, Warehouse

Module.

• Run SAP GUI wireless on the device



Create your Own With Systems Enablement Tools

Risk / Rewards

• 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



Traditional Middleware

Risk / Rewards

• 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%.



Middleware

• SAP uses…. – IDOC (Intermediate DOC)

– BAPI (Business API)

– Remote Function Call (RFC)



SAPConsole

Risk / Rewards

• 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



Goods

Receipt

Goods

Issue

Unloading

Unpacking

Putaway Interleaving

Replenishment

Picking

Packing

Loading

Delivery Split

Printing Labels Shipment Update

Inventory

Inquiry

Covered Business Processes



SAP Console and SAP GUI

SAP GUISAP

Console

SAP LES

Character-based RF DevicesGraphical RF Devices



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



What Is SAPConsole?

SAPConsole translates Graphical Based(GUI) screens into Character Based

screens.

This allows the translation of just about anySAPGUI screen into the character-based

screens used by RF devices, without the

use any RF middleware.



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.

Integrated RF Solution - SAPR/3 BAPI, Rfc, iDoc Solution

Integrated online solution (SAP Business

Logic)

Typically a synchronous offline solution

No middleware 3rd Party partner software

Immediate system response enables user

to react directly

Entry control in the SAP system only

possible with time delay

Latest functions available after each new

release Static solution

Standard screens can be customized to

meet end user requirements

Dialogs can be customized individually

using partner software



SAPConsole Example

Screens

SAPConsole Overview



SAPConsole Example Screens

SAPConsole Overview



Technical Requirements

Component Comment

Windows NT/2000 Workstation or Server attached to the network

Minimum Pentium III, 500Mhz, 128MB RAMfor 20 sessions.

Estimate between 2.5-4 MB per session.

SAPGUI 4.6B or higher Needed to install SAPConsole and supporting DLL files

SAPConsole application Consists of sapcnsl.exe application, supporting DLL files, and

SAPConsole Administrator control panel applet.

Telnet Server that supports VT220

emulation

Telnet Server (DVD by Georgia SoftWorks or Slnet from

Seattlelab is recommended.

RF device that supports VT220

emulation

All LXE Devices



Components of SAPConsole

Ethernet

RF TERMINAL

(TELNET CLIENT)

RF TERMINAL

(TELNET CLIENT)

RF ACCESS POINT

WINDOWS NT/2000

SAPCONSOLE

TELNET SERVER I/O ENGINE

INTERFACE TRANSLATION

SAP R/3 SYSTEM SAPConsole Administrator

SD

Pr of es s i onal Wor ks tati on6000

PR O



RF

Controller

Translation Data

Connection

RF front end (Windows NT)

Component SAPConsole

RFTerminal

RFTerminal

RFTerminal

RF

Controller/

Access

Point

I/O

Interface

Engine

Translation

Data

Connection

R/3

ApplicationServer

Telnet

server

Providedby SAP

Standard

programProvided

By Georgiasoft

Provided byIntercode

SAPConsole – Conceptual Architecture



GUI NonGUI

Hand held

Vehicle

mount

Single Transaction - Multiple Displays



RF user Interface



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

Benefits



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



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.



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.

Limitations

SAP / I t d



SAP / Intercode

Together we deliver one perfect solution to support our customers with the best in class Radio Frequency.

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

SAP GUI



SAP GUIRisk / Rewards

• 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



Which solution is the best for you?

• 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?



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

sap connectivity

Documents