About this task
To install an RFC manually, you need to
consider installation prerequisites before you begin the installation.
The windows in the following sections may differ depending on your
SAP R/3 version.
Installation Prerequisites. To
install the Z_RFC_DS_SERVICE or the Z_RFC_DS_SERVICE_CTS (which
exposes the SAP CTS functionality to the product), RFC function codes
manually, follow these guidelines:
- You must be the SAP Administrator or an SAP user
with S_A.DEVELOP authorization to create the RFC function.
- You can create a function group or find an existing
function group. If you use an existing function group and you are
not the SAP Administrator, you must be the owner of the function group.
Installation Steps. To install the RFC
code:
- Log on to SAP R/3.
- Start transaction SE37. The Function
Builder: Initial window dialog opens. Do the following:
- Type Z_RFC_DS_SERVICE or Z_RFC_DS_SERVICE_CTS in
the Function module text box.
- Click Create to
open the Create Function Module dialog. The Create
Function Module dialog opens.
- To create a function module:
- Type the name of the function group in
which you want the RFC function code to be created in the Function
group field.
- Optional. Type Datastage General
Service Utility in the Short text field.
- Click Save to create
the module.
- The Attributes page
of the Function Builder: Change Z_RFC_DS_SERVICE(_CTS) dialog
opens.
Use these settings for the
attribute entries:
- Application: Z
- Short text: InfoSphere™ DataStage® General
Service Utility
- Processing type: Remote-enabled module
- Update module: Start immed.
If you need help determining which function
group to use, see step 2 in Troubleshooting for RFC installation for
SAP R/3.
- Click the Import page to enter the
import parameters. New service types exist in Z_RFC_DS_SERVICE so
that job parameters can be passed to ABAP programs that run in the
background. For details about running these programs in the background,
see Running programs in the background.
The Import page
opens.
Type the following values shown on this
sample Import page for the Parameter name, Type, Reference
type, Default value, Optional, and Pass value fields:
| Parameter name |
Type |
Reference type |
Default value |
Optional |
Pass value |
|---|
| I_SER VE_TYPE |
LIKE |
SY-TFILL |
|
|
Yes |
| I_TABLE_NAME |
LIKE |
DD02T-TABNAME |
|
Yes |
Yes |
| I_REPORT_NAME |
LIKE |
D010SINF-PROG |
|
Yes |
Yes |
| I_DELIMITER |
LIKE |
SONV-FLAG |
SPACE |
Yes |
Yes |
| I_NO_DATA |
LIKE |
SONV-FLAG |
SPACE |
Yes |
Yes |
| I_ROWSKIPS |
LIKE |
SOID-ACCNT |
0 |
Yes |
Yes |
| I_ROWCOUNT |
LIKE |
SOID-ACCNT |
0 |
Yes |
Yes |
| I_CURR_VARIANT |
LIKE |
RSVAR-VARIANT |
|
Yes |
Yes |
| I_VARI_DESC |
LIKE |
VARID |
|
Yes |
Yes |
Type the following values shown
on the Import page for the CTS specific service
type.| Parameter name |
Type |
Reference type |
Optional |
Pass value |
|---|
| I_DEV_CLASS |
LIKE |
TDEVC-DEVCLASS |
Yes |
Yes |
| I_REQUEST |
LIKE |
E070-TRKORR |
Yes |
Yes |
I_OVERWRITE
_OVERRIDE
|
LIKE |
TADIR_TMP-FLAG |
Yes |
Yes |
| I_REQ_DESCR |
LIKE |
KO020-AS4TEXT |
Yes |
Yes |
- Click the Export page to enter
the export parameters.
Type the
following values shown on the sample Export page
for the Parameter name, Type spec., Reference type,
and Pass val. fields:
| Parameter name |
Type spec. |
Reference type |
Pass value |
|---|
| O_TABLE_SIZE |
LIKE |
SY-TFILL |
Yes |
| O_ERROR_INCLUDE |
LIKE |
SY-REPID |
Yes |
| O_ERROR_LINE |
LIKE |
SY-INDEX |
Yes |
| O_ERROR_MESSAGE |
LIKE |
RSLINLMSG-MESSAGE |
Yes |
| O_ERROR_OFFSET |
LIKE |
SY-TABIX |
Yes |
| O_ERROR_SUBRC |
LIKE |
SY-SUBRC |
Yes |
| O_SAP_VER |
LIKE |
SVERS-VERSION |
Yes |
| O_DSS_VER |
LIKE |
SVERS-VERSION |
Yes |
| O_VARIANT |
LIKE |
RSVAR-VARIANT |
Yes |
Type the following values shown on the sample Export page
for CTS specific service type.| Parameter name |
Type spec. |
Reference type |
Pass value |
|---|
| O_DEV_CLASS |
LIKE |
TDEVC-DEVCLASS |
Yes |
| O_REQUEST |
LIKE |
E070-TRKORR |
Yes |
| O_TRANSPORT |
LIKE |
E070-TRKORR |
Yes |
| O_CTS_ACTION |
LIKE |
TADIR_TMP-FLAG |
Yes |
| O_REPORT_OWNER |
LIKE |
SY-UNAME |
Yes |
- Click the Tables page to enter the
table parameters.
Type the values shown
on this sample Tables page for the Parameter
name, Type spec., Reference type, and Optional fields
according to the following table:
| Parameter name |
Type spec. |
Reference type |
Optional |
|---|
| T_SQLCON |
LIKE |
RFC_DB_OPT |
Yes |
| T_PARAM |
LIKE |
RSPARAMS |
Yes |
| T_CODE |
LIKE |
PROGTAB |
Yes |
| T_FIELDS |
LIKE |
RFC_DB_FLD |
Yes |
| T_DATA |
LIKE |
TAB512 |
Yes |
| T_VARI_TEXT |
LIKE |
VARIT |
Yes |
Type the values shown on this sample Tables page
for CTS specific service type.| Parameter name |
Type spec. |
Reference type |
Optional |
|---|
| T_DEVCLASSES |
LIKE |
TDEVC |
Yes |
| T_REQUESTS |
LIKE |
KO020 |
Yes |
- Click the Exceptions page to enter
the exceptions parameters.
The Exceptions page
opens.
Type the following values shown on this Exceptions page
for the Exception field:
| Exception |
|---|
| TABLE_NOT_FOUND |
| WRONG_TYPE |
| TABLE_WITHOUT_DATA |
| OPTION_NOT_VALID |
| FIELD_NOT_VALID |
| DATA_BUFFER_EXCEEDED |
| REPORT_NOT_FOUND |
Type the following values shown on this Exceptions page
for CTS specific service type.| Exception |
|---|
| TRANSPORTS_NOT_ALLOWED |
| NO_DEVELOPERS_KEY |
| NO_AUTHORIZATION |
| CTS_ERROR |
| PROGRAM_LOCKED |
| INVALID_DEV_CLASS |
| DEV_CLASS_CANNOT_BE_CHANGED |
- Save the RFC interface definition.
- Click Source code. The
source code appears in the ABAP Editor window:
To replace this default code with the source code provided
on the CD, that is, the ZDSRFC.TXT file in the RFC directory:
- Choose Utilities > more utilities.
- Choose Upload/Download > Upload from
the ABAP Editor menu.
- Specify the path name for the ZDSRFC.TXT
file in the RFC directory on the CD. For example, type E:\Datastage\RFC\ZDSRFC.TXT in
the File name field.
- To add the global data code for CTS service:
- Choose Goto > Global data.
- Choose Upload/Download > Upload from the
ABAP Editor menu.
- Specify the path name for the ZDSRFC_CTS_TOPINCLUDE.txt
file in the RFC directory on the CD. For example, type E:\Datastage\RFC\ZDSRFC_CTS_TOPINCLUDE.txt in
the File name field.
- After the upload is complete, save the RFC function code,
and activate it.
IBM InfoSphere Information Server Pack for SAP R/3, Version 6.5.0.1
This topic is also in the IBM InfoSphere Information Server Integration Guide for IBM InfoSphere Information Server Pack for SAP R/3.
