Starting from version 8.0.0.2, you can configure multi-instance support in ABAP Extract
Stage which enables you to run multiple instance of an ABAP Extract Stage job.
About this task
Multi-instance support automatically ensures that each instance of the job run is provided
with the unique RFC destination name and program ID during run time. To achieve this, an RFC
destination with unique name and program ID will be created automatically for each instance. Hence
in case of multi-instance support, you cannot use pre-created RFC destination in SAP. The option of
Create RFC Destination option will always be enabled in case of multi-instance
support. Furthermore, you can use multi-instance support functionality only for parallel jobs with
RFC used as data transfer method. This functionality is not implemented for server jobs hence you
will find Multi-instance support check box disabled for server
jobs.
Procedure
You must select the RFC data transfer method to use the multi-instance support
functionality. Once you choose RFC in data transfer method, the Multi-instance
support check box appears on the GUI which must be selected.
-
Open the ABAP extract stage and go to Output tab.
-
Select RFC from Data Transfer Method tab.
-
Select the Multi-instance support check box.
-
On selecting Multi-instance support, Program ID and RFC destination name
fields will be automatically populated with job parameters, PROG_ID_PARAM, and
RFC_DEST_NAME_PARAM respectively. You can choose to edit the name of these job
parameters later.
Note: Parametrization of the fields is required for proper runtime behavior. The stage automatically
appends to the base parameter value an automatically generated unique runtime ID (based on the job
instance start time). Hence, different instances of the same multi-instance job use different values
for RFC Destination Name and Program ID.
-
Define the job parameters mentioned at step 4 in the job properties.
-
Observe that Create RFC destination name automatically and
Delete existing RFC destination check boxes are in selected state and
disabled.
-
If you select Run the ABAP Program as Background process which uses an SAP
Variant for providing run options, you must use job parameter for example,
#var_name_param# for the Variant Name and deselect Use existing
variant as for each instance ABAP Extract run time has to create a new Variant for the
background job. Hence you should provide a unique value to this job parameter for each instance (for
example, by attaching the invocation ID as a suffix to the default value of the job
parameter).