_________________________________

_________________________________
_________________________________
_________________________________
_________________________________

Managing qRFC
Traffic

_________________________________
_________________________________
_________________________________

Don Kehoe
Symmetry Corporation

_________________________________
_________________________________

2008 Wellesley Information Services. All rights reserved.

In This Session ...

_________________________________

We will go over the technology behind qRFC

Well look at the tools used to monitor and administer it
See examples of applications using qRFCs
Take a peek at the new bgRFC

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
1

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
2

Transactional RFC (tRFC)

An asynchronous communication method that executes the called

function module in the RFC server only once

_________________________________
_________________________________

The remote system doesnt need to be available when the RFC client
program is executing a tRFC
The tRFC component stores both the called RFC function and the
corresponding data in the SAP database under a unique transaction
ID (TID)

_________________________________
_________________________________
_________________________________

tRFC is always used if a function is executed as a Logical Unit of

Work (LUW)

_________________________________

_________________________________

Within a LUW, all calls are executed in the order in which they are called,
executed in the same program context in the target system, and run as a
single transaction: they are either committed or rolled back as a unit

_________________________________
_________________________________

Implementation of tRFC is recommended if you want to guarantee

preserving the transactional order of the calls

_________________________________
3

Transactional RFC (tRFC) (cont.)

_________________________________

tRFCs are transferred immediately to the target

_________________________________
_________________________________

Sending Application

Receiving Application

_________________________________
_________________________________
_________________________________
tRFC

tRFC

_________________________________
_________________________________
_________________________________
_________________________________
4

Queued RFC (qRFC)

_________________________________

To guarantee that multiple LUWs are processed in the

order specified by the application, you can serialize tRFC
using queues (inbound and outbound queues)
This type of RFC is called queued RFC (qRFC)

_________________________________
_________________________________
_________________________________

qRFC is therefore an extension of tRFC

It transfers an LUW (transaction) only if it has no predecessors
(in reference to the sequence defined in different application
programs) in the participating queues

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
5

Queued RFC (qRFC) (cont.)

_________________________________

Inbound and outbound queues

_________________________________
_________________________________
Receiving Application

Sending Application

_________________________________
Outbound Queue

_________________________________

Inbound Queue

_________________________________
tRFC

tRFC

_________________________________
_________________________________
Outbound

_________________________________
_________________________________

Inbound

Outbound Queues

qRFC is a layer between the application and tRFC

_________________________________
_________________________________

It only allows a LUW to be transferred to a target system if no

predecessor LUWs exist in the participating queues
After a qRFC LUW is executed, the QOUT Scheduler
automatically executes the next qRFC LUW waiting in the queue

_________________________________
_________________________________
_________________________________

qRFC with outbound queue enables serialization of the

LUWs in the sending system

_________________________________
_________________________________

You can use qRFC with outbound queue with every tRFCsupported target system, because the sequence of the calls is
established in the application program
f The target system therefore does not require any knowledge
about the serialization

_________________________________
_________________________________
_________________________________
7

Outbound Queues (cont.)

The queued RFC with outbound queue causes the pages

of the sending system to be serialized

_________________________________
_________________________________
_________________________________

The target system has no knowledge of the serialization in the

sending system
This means that it is possible to communicate with any SAP
target system from release 3.0 onwards

_________________________________
_________________________________
_________________________________

A LUW (transaction) can be distributed between more

than one queue

_________________________________

However, it is only transferred if all predecessor LUWs in all

participating queues have been processed
After a qRFC transaction has been executed, the system tries to
start all waiting qRFC transactions in sequence

_________________________________
_________________________________
_________________________________
8

Outbound Queues (cont.)

_________________________________

Outbound queue processing

qRFCs

System 1

_________________________________
System 2

_________________________________

qLUW 3

_________________________________
Queue1

_________________________________
_________________________________

Queue2
qLUW 2

_________________________________
Queue3

_________________________________
_________________________________

Queue4
qLUW 1

_________________________________

Queue5
9

Inbound Queues

_________________________________

You use qRFC with inbound queue if the application

itself determines when it processes the inbound qRFC
LUWs in the target system
You also use inbound qRFC if you want to remove the
connection between the transfer of LUWs and their
execution
qRFC with inbound queue always means that an
outbound queue also exists in the sending system

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
10

Inbound Queues (cont.)

Using an inbound queue separates the transfer of qRFC

LUWs from their processing

_________________________________
_________________________________
_________________________________

The outbound queue is used to write the qRFC LUWs to the

inbound queue of the target system
f This reduces the processing workload in the sending system
to the transfer of LUWs to the target system

_________________________________
_________________________________

LUWs arriving in the inbound queue are read and

processed from the queue either by the QIN Scheduler or
by program calls from an application program

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

11

SAP Web Application Server (WAS)

_________________________________

WAS infrastructure

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
12

qRFC Components

_________________________________

When an application uses qRFC it uses all the

underlying layers

_________________________________
_________________________________
_________________________________

Applications

_________________________________

qRFC

_________________________________

tRFC

_________________________________

RFC

_________________________________

CPIC

_________________________________

TCP/IP

_________________________________
13

Architecture

CPI-C (Common Programming Interface for

Communication)

Provides a cross-system-consistent and easy-to-use

programming interface for applications that require program-toprogram communication
The conversational model of program-to-program
communication is commonly used in applications
The model is described in terms of two applications
speaking and listening hence, the term conversation
f A conversation is simply a logical connection between two
programs that allows the programs to communicate with
each other
f From an applications perspective, CPI-C provides the
function necessary to enable this communication
f It is an Opens Group (X/OPEN) standard
14

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Architecture (cont.)

_________________________________

CPI-C (BC-CST-GW)
Gateway/CPIC (BC-CST-GW)

_________________________________
_________________________________

Standardized interface for system-wide communication

between programs
The protocol can be divided into four areas:
f Session setup
f Session control
f Communication
f End of session

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
15

Architecture (cont.)

_________________________________

Example CPI-C command: Send_Data (CMSEND)

_________________________________

A program uses the Send_Data (CMSEND) call to send data to a

remote program
When issued during a mapped conversation, this call sends
one data record to the remote program
f The data record consists entirely of data and is not examined
by the system for possible logical records
When issued during a basic conversation, this call sends data
to the remote program
f The data consists of logical records
f The amount of data is specified independently of the
data format

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

16

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
17

SAP Gateway

Each instance of an SAP system has a gateway

_________________________________
_________________________________

The gateway enables communication between work processes

and external programs
It also enables communication between work processes from
different instances or SAP systems

_________________________________
_________________________________
_________________________________

SAP also provides a stand-alone gateway for

external systems

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
18

Gateway Read Process

_________________________________

Gateway read (gwrd, gwrd.exe) is the main process in

the gateway system
It is started by the application server (dispatcher) and
checked by it periodically
The gateway reader receives and processes all CPI-C
requests
If the executable gwrd program is called without
parameters or with the switch -help, the program outputs
a description of the possible command parameters, as
well as all the patches

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

SAP Gateway speaks CPI-C

19

Gateway Monitor

Use the Gateway Monitor (gwmon, gwmon.exe) to

analyze and administer the SAP Gateway
When you start it, you initially get a list of active CPI-C
connections

_________________________________
_________________________________
_________________________________

You can call up the other monitor functions via a menu

_________________________________

You can monitor the gateway from the SAP system

(transaction SMGW) or from the operating system

_________________________________

_________________________________

_________________________________
_________________________________
_________________________________
_________________________________
20

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
21

qRFC Transactions

SMQ1

_________________________________
_________________________________

qRFC Monitor for the inbound queue

_________________________________

Outbound Queue Scheduler used to register, deregister, and

exclude destinations

_________________________________
_________________________________

SMQR

qRFC Monitor for the outbound queue

SMQS

_________________________________

SMQ2

_________________________________

_________________________________

Inbound Queue Scheduler used to register and deregister

queues

_________________________________

SMQE

_________________________________

qRFC Administration
22

SMQ1

_________________________________

SMQ1 Outbound Queue Monitor

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
23

SMQ1 (cont.)

_________________________________

SMQ1 Status Information

_________________________________

Double clicking some fields gives more information

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
24

SMQ1 (cont.)

_________________________________

SMQ1 qRFC data

_________________________________

This is a display of the LUW data being sent

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
25

SMQ1 (cont.)

BI NOSEND

_________________________________
Caution

_________________________________

LUWs of this queue are never sent but are retrieved by a special application
These queues are only used internally at SAP (BW or CRM during communication
with mobile clients)
Even if a LUW was read by the corresponding application (BW, CRM), this status
does not change
The LUW is only deleted from the queue if this application confirms collection
(collective confirmation possible)
Under no circumstances should this status be reset using transaction SMQ1 and the
queue activated

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
26

SMQ1 (cont.)

BI NOSEND (cont.)

_________________________________
Caution

Status changes depending on BI state of the data

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

27

SMQ2

_________________________________

Initial screen

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
28

SMQ2 (cont.)

_________________________________

Inbound queue

_________________________________

Double clicking on some fields gives more information

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
29

SMQ2 (cont.)

_________________________________

Queue entries

_________________________________

You can delete, display, and execute qRFCs from here

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
30

SMQ2 (cont.)

_________________________________

Inbound Queue Data

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
31

SMQS Outbound Scheduler

_________________________________

SMQS and registration

_________________________________

You can register and deregister queues here

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
32

SMQS Outbound Scheduler (cont.)

_________________________________

SMQS and deregistration

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
33

SMQS Outbound Scheduler (cont.)

_________________________________

SMQS and exclude

_________________________________

You can use SMQS to exclude a destination

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
34

SMQS Outbound Scheduler (cont.)

_________________________________

RZ12 RFC quotas

_________________________________

Quotas are used to limit resources used by qRFC

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
35

SMQS Outbound Scheduler (cont.)

_________________________________

SMQS RFC quotas

_________________________________

You can check on the resources allocated to qRFC

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
36

SMQS Outbound Scheduler (cont.)

_________________________________

SMQS RFC quotas (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
37

SMQS Outbound Scheduler (cont.)

_________________________________

RZ12 RFC quotas

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
38

SMQS Outbound Scheduler (cont.)

_________________________________

SMQS Change RFC Group

_________________________________

You can change the server group here

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
39

SMQS Outbound Scheduler (cont.)

_________________________________

SMQS Change RFC Group (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
40

SMQR Inbound Scheduler

_________________________________

SMQR and registration

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
41

SMQE qRFC Administration

_________________________________

SMQE

_________________________________

You can see and change log and trace settings

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
42

SMQE qRFC Administration (cont.)

_________________________________

SMQE logs and trace

_________________________________

You can also activate and view traces

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
43

SMQE qRFC Administration (cont.)

_________________________________

SMQE qRFC Log

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
44

SMQE qRFC Administration (cont.)

_________________________________

SMQE qRFC Trace

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
45

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
46

Other Tools

_________________________________

SMGW Gateway Trace

ST11 Developer Traces
ST05 RFC Trace
SLG1 Application Log
RZ20 CCMS Monitoring

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
47

SMGW Gateway Trace

_________________________________

The Gateway Trace File is an essential source of

information

_________________________________
_________________________________

You can display the file by clicking on the icon

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
48

SMGW Gateway Trace (cont.)

_________________________________

Gateway Trace File contains CPIC commands and data

_________________________________

Watch for the errors, data dumps, and time stamps

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
49

SMGW Increase Trace Level

_________________________________

There are three trace levels

_________________________________

You can change the trace levels here

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
50

ST11 Developer Traces

_________________________________

Developer traces narrow the trace scope

_________________________________

Including RFC information for each work process

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
51

ST11 RFC Trace

_________________________________

Developer RFC traces display data from a work process

_________________________________

Data is the same as in Gateway Trace

_________________________________

RSTR0006: Display Developer Traces

_________________________________

**** Trace file opened at 20080115 211237 EST SAP-REL 700,0,75 RFC-VER 3 852527
======> CPIC-CALL: 'ThSAPOCMINIT'
Timeout during connection setup. Please check partner availability
ABAP Programm: RSRFCPIN (Transaction: SM59)
Called function module: RFC_PING
User: XXXXXX (Client: 000)
Destination: SAPOSS (handle: 2, , {478D4BA3-4A07-02EC-0000-0000AC1600D0})
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2323
CPIC-CALL: 'ThSAPOCMINIT'
Timeout during connection setup. Please check partner availability
HOST =77.71.78.74
SERV =sap2224

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
52

ST05 RFC Trace

_________________________________

ST05 can be used to trace RFC

_________________________________

You can filter the trace and the display

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
53

ST05 RFC Trace (cont.)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
54

SLG1 Application Log

_________________________________

SLG1 shows logs written by the applications

_________________________________

This can show reasons for qRFC failures

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
55

RZ20 CCMS Monitor

_________________________________

QRFC errors can be viewed in CCMS

_________________________________

Alerts can be monitored and sent out

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
56

Other Tools

_________________________________

STAD Statistics Records

ST03N Workload Analysis
Tables ARFCRSTATE, ARFCRDATA, ARFCSSTATE, and
ARFCSDATA
SM21 System Log
SM50 Work Process Monitor and Trace File
SM04 User Trace
Solution Manger Business Process Monitoring
Solution Manager Diagnostics

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
57

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
58

Some Applications Using qRFC

_________________________________

PI (Process Integration)/XI (Exchange Infrastructure)

SCM CIF(Core Interface)
CRM Middleware
NetWeaver BI (Business Intelligence)
SAP Tax Interface
ALE (Application Linking and Enabling)

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
59

PI qRFC

_________________________________

Inbound queue of PI

_________________________________

Here the inbound queue has eight PI entries

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
60

PI qRFC (cont.)

_________________________________

PI provides tools for analyzing qRFC errors

_________________________________

You can use these tools in SMQ1 and SMQ2

Double clicking on Queue Name field shows diagnostic screen

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

61

PI qRFC (cont.)

_________________________________

PI LUW data diagnostic screen

_________________________________
_________________________________
_________________________________

1
2

_________________________________
_________________________________

_________________________________
_________________________________
_________________________________
_________________________________
62

PI qRFC (cont.)

_________________________________

PI Display Process 1

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
63

PI qRFC (cont.)

_________________________________

Display Message Monitor 2

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
64

PI qRFC (cont.)

_________________________________

PI Display XML Message

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
65

PI qRFC (cont.)

_________________________________

PI Display Trace 3

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
66

PI qRFC (cont.)

_________________________________

PI Manage Queues

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
67

PI qRFC (cont.)

_________________________________

PI provides a tool to manage its queues

_________________________________

You can use this tool to register and deregister PI queues

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
68

SCM Queue Manager

_________________________________

SCM provides a Queue Manager

_________________________________

SCM Queue Manager manages both SCM and R3 queues

Use transaction /SAPAPO/CQ

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
69

SCM Queue Manager (cont.)

_________________________________

/SAPAPO/CQ

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
70

SCM Using Inbound Queues to ERP from SCM

_________________________________

Inbound queues are configured in SPRO

_________________________________

Look in Integration with SAP Components

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
71

SCM Using Inbound Queues to ERP from SCM (cont.)

_________________________________

Queue Type field is used to set inbound queues

_________________________________

Blank is for outbound queues, I for inbound queues

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
72

SCM Using Inbound Queues from ERP to SCM

_________________________________

Queue Type field is used to set inbound queues (cont.)

_________________________________

Blank is for outbound queues, I for inbound queues

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
73

SCM qRFC

_________________________________

CIF Debugging can be set in SPRO

_________________________________

In Basic Settings for Data Transfer

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
74

SCM qRFC (cont.)

_________________________________

Debugging is off (blank), on (X) or NOSENDS (R)

_________________________________

An R setting will stop entries in the queue

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
75

SCM CIF

_________________________________

Planned Independent Requirements (PIR) sent to SAP R/3

_________________________________

These commonly have application errors

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
76

SCM CIF (cont.)

_________________________________

Planned Independent Requirements Error

_________________________________

SYSFAIL
f No Requirement Type found

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
77

CRM Middleware Queues

Outbound queues

_________________________________
_________________________________

CDB* Start queues for loads CRM to CDB

CRM_SITE* Load queues for Mobile Clients
CSA* Send queues of CRM Server Applications
EXT* Start queues for loads CRM to Ext.
R3AI/R* Start queues for loads from ERP Backend system
R3AU* Load queues CRM to ERP Backend system

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Inbound queues

_________________________________

CRI* Initial load queues CRM to CDB

CRM_SITE* Load queues from Mobile Clients
R3A* Load queues ERP Backend to CRM
CSA* Send inbound queues of CRM Server Applications

_________________________________
_________________________________
78

CRM Middleware Queues (cont.)

_________________________________

SMWP Monitoring Cockpit

_________________________________

Great overview and tool for CRM Middleware

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
79

CRM Middleware Queues (cont.)

_________________________________

SMW01 BDOC Messages

_________________________________

List all BDOCS processed by CRM

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
80

SAP Tax Interface

_________________________________

Documents with errors in qRFC queue

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
81

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
82

bgRFC

_________________________________

Classic qRFC

_________________________________

The classic qRFC model detects the dependencies among the

individual units only when the data is processed by the RFC
scheduler
f For each destination, the outbound scheduler starts a
scheduler that processes the data for this destination
The schedulers run on each destination only for a limited
period of time to ensure processing is consistent for all
destinations
f For this reason, the scheduler must determine the sequence
again every time before it processes a destination

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
83

bgRFC (cont.)

_________________________________

bgRFC

_________________________________

With the bgRFC (background RFC), dependencies are

determined when the data is stored
f In doing so, the RFC scheduler can find all units that can be
executed instantly with minimum effort and all dependencies
are detected only once
f The additional effort when storing the data is compensated to
a large extent by efficient algorithms and optimizations in the
database design
For each client, a defined number of outbound schedules are
started that process the queued load in parallel
f The load on the target systems is determined in shorter
intervals and is, therefore, more accurate than before

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

84

bgRFC (cont.)

_________________________________

bgRFC is configured in SM59 Special Options

_________________________________

0 is Classic RFC, 1 is bgRFC

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
85

bgRFC (cont.)

_________________________________

bgRFCmon

_________________________________

Selection screen

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
86

bgRFC (cont.)

_________________________________

bgRFCmon shows queue status and breakdown for bgRFC

_________________________________

Detailed breakdown of bgRFC units

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
87

bgRFC (cont.)

_________________________________

bgrfcperfmon bgRFC Performance Monitor

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
88

What Well Cover

_________________________________

qRFC and underlying architecture

SAP Gateway
qRFC transactions
Other tools
Example applications using qRFC
bgRFC
Wrap-up

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
89

Resources

RFC Monitoring Best Practices for Solution

Management

_________________________________
_________________________________

http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_O
BJECT=011000358700000657512007E
Or search Service Marketplace for Best Practices RFC
Monitoring

SAP Professional Journal: May/June 2007

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

Wolfgang Baur, Increase the Efficiency of Your RFC

Communications with bgRFC A Scalable and Transactional
Middleware Framework

_________________________________
_________________________________
_________________________________
90

7 Key Points to Take Home

qRFC is a basic method for inter-system communication

SMQ1 is the main tool for qRFC monitoring as outbound
queues are default; SMQ2 is the main tool for inbound
monitoring

_________________________________
_________________________________
_________________________________
_________________________________

There are many other tools you can use for qRFC administration

Most activities with qRFC are automatic

Additional activities are normally directed by SAP
Do not delete or change queues or qRFCs unless you
know exactly what the data is
Pay attention to bgRFC as it may be used in many
applications using qRFC in the future
Keep a close watch on changes to SAP communication
architecture

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

91

Your Turn!

_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________

How to contact me:

Don Kehoe
dkehoe@sym-corp.com

_________________________________
_________________________________
92

Wellesley Information Services, 990 Washington Street, Suite 308, Dedham, MA 02026

Copyright 2008 Wellesley Information Services. All rights reserved.