Automation Engine Script Guide > AE JCL for Applications > SAP > R3_CALL_TRANSACTION

R3_CALL_TRANSACTION

Calls an SAP transaction.

Transaction: -

Interface: AE

Syntax

R3_CALL_TRANS[ACTION]

CODE=...
[,UPDATE=...]
[,RACOMMIT=...]
[,NOBINPT=...]

Syntax	Description/Format
CODE=	Twenty-digit transaction code. Format: script literal
UPDATE=	Booking mode for this transaction. Format: script literal Allowed values: "A", "L" and "S" (Default) "A" - Asynchronous "L" - Local "S" - Synchronous
RACOMMIT=	End of transaction in commit work. Format: script literal Allowed values: "" (default value) and "X" "" - Transaction runs until normal transaction ends "X" - Transaction ends in SAP as soon as the ABAP script element COMMIT WORK has run through.
NOBINPT=	Processing in batch input mode. Format: script literal Allowed values: "" (default value) and "X" "" - Transaction is processed in BDC mode. "X" - Transaction is processed in SAP in the same way that transactions started by a dialog user are processed.

Comments

This script element calls an SAP transaction. The data required for the transaction has previously been defined with R3_SET_BDCDATA.

Note: For security reasons, this transaction is not executed using the RFC user rights (CPIC) with which AE usually logs on to SAP and schedules background jobs. For calling the transaction, the agent logs off of the SAP system and then logs back on under the user listed in the Login object for the corresponding AE job. Automic recommends applying a special user in SAP to be used for calling transactions out of AE. This user must have transaction rights.

We also recommend using the R3_SET_BDCDATA and R3_CALL_TRANSACTION script elements in separate AE jobs. This will prevent the user defined for R3_CALL_TRANSACTION from influencing other SAP JCL script elements (e.g. R3_ACTIVATE_REPORT).

Example

In the following example, the BDC data for the transaction "SA38" is defined. Subsequently, the "SA38" transaction is called in order to execute a data update.

R3_SET_BDCDATA PROGRAM="SAPMS38M", DYNPRO="0101", DYBEGIN="X"
R3_SET_BDCDATA FNAM="BDC_OKCODE", FVAL="=SSET"
R3_SET_BDCDATA FNAM="RS38M-PROGRAM", FVAL="RSEINB00"
R3_SET_BDCDATA PROGRAM="SAPLSVAR", DYNPRO="0302", DYBEGIN="X"
R3_SET_BDCDATA FNAM="BDC_OKCODE", FVAL="=CHNG"
R3_SET_BDCDATA FNAM="RSVAR-VARIANT", FVAL="UM-V1"
R3_SET_BDCDATA FNAM="RSVAR-FLAG1", FVAL="X"
R3_SET_BDCDATA PROGRAM="RSEINB00", DYNPRO="1000", DYBEGIN="X"
R3_SET_BDCDATA FNAM="BDC_OKCODE", FVAL="=SAVE"
R3_SET_BDCDATA FNAM="P_FILE", FVAL="test.txt"
R3_SET_BDCDATA PROGRAM="RSEINB00", DYNPRO="1000", DYBEGIN="X"
R3_SET_BDCDATA FNAM="BDC_OKCODE", FVAL="=VBAC"
R3_SET_BDCDATA PROGRAM="SAPLSVAR", DYNPRO="0302", DYBEGIN="X"
R3_SET_BDCDATA FNAM="BDC_OKCODE", FVAL="/EBACK"
R3_SET_BDCDATA PROGRAM="SAPMS38M", DYNPRO="0101", DYBEGIN="X"
R3_SET_BDCDATA FNAM="BDC_OKCODE", FVAL="=BACK"
R3_CALL_TRANSACTION CODE="SA38", UPDATE="S"