R3_CALL_TRANSACTION

The R3_CALL_TRANSACTION script element calls an SAP transaction. Before you can call this transaction, you must define the data that is required for it with the R3_SET_BDCDATA script element.

Important!

  • Use separate AE jobs for R3_CALL_TRANSACTION and R3_SET_BDCDATA. Otherwise, the user that is defined for R3_CALL_TRANSACTION might influence other SAP JCL script elements such as R3_ACTIVATE_REPORT. For more information, see R3_SET_BDCDATA

  • For security reasons, this transaction is NOT executed by using the RFC user rights (SAP system user). The AE usually logs on to SAP with these rights, and schedules background jobs. To call the transaction, the agent logs off the SAP system. Then it logs on again with the user that is listed in the Login object for the corresponding AE job.

  • Apply a special user in SAP that is used for calling transactions out of the AE. This user must have transaction rights.

Transaction: -
Interface: AE

Syntax

R3_CALL_TRANS[ACTION]

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

Parameters

  • R3_CALL_TRANS[ACTION]
    Calls an SAP transaction

  • CODE=
    Transaction code consisting of 20 digits
    Format: script literal

  • UPDATE=
    (Optional) Booking mode for this transaction
    Format: script literal
    Allowed values:

    • S (default)
      Synchronous

    • A
      Asynchronous

    • L
      Local

  • RACOMMIT=
    (Optional) End of the transaction when commit work is used
    Format: script literal
    Allowed values:

    • "" (default)
      The transaction continues until the normal transaction ends.

    • X
      The transaction ends in SAP when the ABAP script element COMMIT WORK has finished.
  • NOBINPT=
    (Optional) Processing in batch input mode
    Format:script literal
    Allowed values:

    • "" (default)
      The transaction is processed in BDC mode.

    • X
      The transaction is processed in SAP in the same way that transactions started by a dialog user are processed.

Example

The following example defines the BDC data for the SA38 transaction. Then, the SA38 transaction is called to process 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"

See also:

seealso

About SAP JCL