Process Runner DB can automate many processes between SAP and Database. Automation allows you to automatically upload or download information between SAP to Database 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 Database 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 Extraction
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 DB 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.
Transfer data between SAP and Database involves three broad steps:
For Transaction:
1. Record : Click on New Process and select Transaction option. Provide valid SAP Transaction code and proceed to Recording. Process Runner DB 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 through SAP GUI. Once you save, exit or terminate the transaction, control will be back to Process Runner DB. Process Runner DB will store your recording in appropriate file format and put you in Mapper.
2. Map: Process Runner DB presents Mapper in very flexible gird layout. If you need to move data between SAP and Database, use the appropriate mapping type to tell Process Runner DB how SAP fields are connected to Database table fields. In Process Runner DB, SAP fields can also take fix or system generated values. Once you mapped 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 click on run, Process Runner DB 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 DB. Process Runner DB displays the message returned by SAP into your Database table. Process Runner DB will repeat this process for each Database records. You can control how many records should Process Runner DB look at. Ideally, you should do one or few transaction test run before kicking off larger run.
For BAPI or RFM:
Steps involved in Using BAPI is similar to Transaction, except that instead of recording a transaction, Process Runner DB 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.