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

R3_SET_BDCDATA

Defines BDC data

Transaction: -

Interface: AE

Syntax

R3_SET_BDCDATA

PROGRAM=...
,DYNPRO=...
[,DYBEGIN=...]  

Syntax

Description/Format

PROGRAM=

The program name, a maximum of 40 characters is allowed.
Format: script literal

DYNPRO=

The four-digit screen number.
Format: scriptA particular Automation Engine object type. literal

DYBEGIN=

The indication that a new screen is starting .
Format: script literal

Allowed values: "" (default value), "X"
"" = no new screen.
"X" = new screen.

 R3_SET_BDCDATA

,FNAM=...
,FVAL=...

Syntax

Description/Format

FNAM=

The field name, a maximum of 132 characters is allowed.
Format: script literal

FVAL=

The value that should be assigned to the field, a maximum of 132 characters is allowed.
Format: script literal

Comments

This script element serves to define BDC data (Batch Data Communication). You can use it to assign values to screen fields in batch mode. The SAP agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host initially saves these assignments in an internal table. R3_CALL_TRANSACTION initiates the actual processing. The internal table is reset afterwards.

R3_SET_BDCDATA is initially called with the parameters PROGRAM=, DYNPRO= and DYBEGIN=. The given values are then assigned to the selected fields with the parameters FNAM= and FVAL=. The definition of BDC data can be repeated for the same or other screens as often as required.

The names of the screens and individual fields can be determined online in the SAP system. In addition, the transaction can be started using the menu System - Status. For technical information, you can press F1. The transaction "SM35" chronicling routine provides the names of screens and fields.

Examples

The following example provides data of the screens of the entire transaction "SA38". The screens are called in a pre-arranged order and the fields obtain values. Subsequently, the transaction "SA38" starts in order to run 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:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH