Basic Concepts of Process Runner

Process Runner can automate many processes between SAP and Excel. Automation allows you to automatically upload or download information between SAP to Excel without involving any programming, scripting or coding. Once you setup a process, you can use that for one or few calls to thousands or millions of calls between SAP and Excel without any additional efforts.

Following processes are supported in this release:

1.SAP Transaction (RFC methods)

2.Business API (BAPI) and Remote Function Module (RFM)

3.SAP Transaction (GUI Scripting method)

4.Data Extractor (Extract Table data from SAP)

prormodules

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 those, 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 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 is delivered with RFM functionality disabled.

➢Note: All through out this documentation BAPI and RFM are used interchangeably. When you see BAPI, it usually covers RFM as well unless RFM was clearly excluded.

1.Record: Click on New Process and select Transaction or GUI Scripting option. Provide valid SAP Transaction code and proceed to Recording. Process Runner will ask you for logon information and start SAP GUI for you. Once you see SAP GUI, you should type in your information and navigate through your transaction. All your steps and data will be captured as you walk thru SAP GUI. Once you save, exit or terminate the transaction, control will be back to Process Runner. Process Runner will store your recording in appropriate file format and put you in Mapper.

2.Map: Process Runner presents Mapper in very flexible gird layout. If you need to move data between SAP and Excel, use the appropriate mapping type to tell Process Runner how SAP fields are connected to Excel columns or cells. In Process Runner, SAP fields can also take fix or system generated values. Once you mapped how the data is going to flow between SAP, Process Runner and Excel, you are ready to Run this file.

3.Run: When you click on run, Process Runner will look at your mapping and your transaction sequence, it will then prepare and send the data packet to SAP. SAP executes this data packet and sends message back to Process Runner. Process Runner displays the message returned by SAP into your Excel file. Process Runner will repeat this process for each Excel rows. You can control how many rows should Process Runner look at. Ideally, you should do one or few transaction test run before kicking off larger run.

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

Unlike Transactions, BAPIs are not used by end user on daily basis, hence this methods needs more efforts than Transaction. However, extra efforts usually pays off as BAPI interface is not dependent on 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.

Refer to tutorials section for detailed information and step-by-step instructions.