Basic Concepts of Process Runner DB

Process Runner DB can automate many processes between SAP and Database. Automation allows to upload or download information between SAP and Database without interference from any programming, scripting, or coding. After you set up a process, you can use the process for any number of calls between SAP and Database without any additional effort.

Following processes are supported:

• SAP Transaction (RFC methods)
• Business API (BAPI) and Remote Function Module (RFM)
• SAP Transaction (GUI Scripting method)
• Data Extractor (Extract Table data from SAP)

Transactions can be automated either as RFC or as GUI Scripting. RFC method is faster and preferred. However, some of the newer and Enjoy transactions do not fully support RFC record and run method. For such transactions, GUI Scripting method would be more suitable. To automate using GUI Scripting method, SAP server should have GUI Scripting enabled.

BAPI and RFM works same way. BAPIs are generally released by SAP so that customer can use them freely. However, not all RFMs are released and intended to be used by customer or by external programs. By default, Process Runner DB is delivered with RFM functionality disabled.

Note: Throughout this documentation, BAPI and RFM words are used interchangeably; when you see BAPI, it usually covers RFM also, unless RFM is clearly excluded.

Transfer of data between SAP and Database

Transfer of data between SAP and Database involves three steps:

• For Transaction or GUI Scripting:

  1. Record:
     1. Select New Process and select Transaction or GUI Scripting.
     2. Enter valid SAP Transaction code and proceed to record the transaction. Process Runner DB asks you for logon information and then starts SAP GUI.
     3. Enter your information and navigate through your transaction. All your steps and data are captured as you walkthrough SAP GUI.
     4. When you save, exit, or terminate the transaction, Process Runner DB stores your recording in the appropriate file format and displays the Mapper tab.
  2. Map:Process Runner DB presents Mapper in a gird layout. If you must move data between SAP and Database, use the appropriate mapping type to tell Process Runner DB how SAP fields are connected to Database fields. In Process Runner DB, SAP fields can also take fixed or system-generated values. When you have completed mapping how the data is going to flow between SAP, Process Runner DB, and Database, you are ready to run this file.
  3. Run: When you select Run, Process Runner DB looks at your mapping and your transaction sequence, and then prepares and sends the data packet to SAP. SAP executes this data packet and sends the message to Process Runner DB. Process Runner DB displays the message returned by SAP in your Database table and repeat this process for each Database records. You can control how many records Process Runner DB should look at. Ideally, you should perform a test run on a few transactions before starting run on a bigger set of transactions.

• For BAPI or RFM:

  Steps involved in using BAPI is similar to Transaction, except that instead of recording a transaction, Process Runner DB generates a full BAPI interface automatically as defined in your SAP system.

Unlike Transactions, BAPIs are not used by users on a daily basis; BAPI interface is not dependent on the screen sequence (like Transaction) and is usually much faster than Transaction. BAPI method is also ideal for extracting data or downloading information about business objects.