SAP Business Suite Applications
Create an SAP Business Suite Application datastore to connect to an SAP Business Suite Application.
Datastores for SAP Business Suite Applications support a number of specific options. Configure the datastore to match your SAP Application configuration.
Option |
Possible values |
Description |
|---|---|---|
Name |
Alphanumeric characters and underscores |
The name of the object. This name appears in the datastores tab and in tasks that use the datastore. |
Description |
Any text |
The description of the datastore. |
Type |
SAP Business Suite Applications |
Select the type of datastore to which you are connecting. |
Agent |
The list of agents that have been defined in the agents tab |
Specifies the agent that should be used to access this data source. |
Application server |
Computer name, fully qualified domain name, or IP address |
The name of the remote SAP application computer (host) to which the software connects. |
Authentication |
Password SNC |
Specifies the authentication type used to connect to the datastore. |
User name |
Alphanumeric characters and underscores |
The name of the account through which the software accesses the SAP application server. |
Password |
Alphanumeric characters and underscores, or blank |
The user's password. Note If
you have problems connecting to a system that uses SAP_BASIS version
6.40 and earlier, the system might be expecting an uppercase
password. To prevent this issue, install the appropriate kernel
patch as described in SAP Note 792850 , “Preparing ABAP
systems to deal with incompatible passwords”. |
Language |
SAP-supported ISO three-letter language codes or <default> |
Select the language from the possible values in the drop-down list. The <default> option sets the language to the system language of the SAP Data Services Agent host system. |
Code page |
- |
Specify the character encoding of character data in the datastore. |
ABAP execution option |
Generate and execute Execute preloaded |
Select the task execution strategy. Your choice affects the required authorizations. Generate and Execute: The ABAP created by the task resides on the same computer as the SAP Data Services Agent and is submitted to SAP using the /BODS/RFC_ABAP_INSTALL_AND_RUN function. Select this option if the task changes between scheduled executions. This is the recommended option for non-production environments, such as sandbox or development. Execute Preloaded: ABAP resides on the SAP application server and is submitted using Data Services RFC function modules. Select this option if the task does not change between scheduled executions. This is the recommended option for production environments where the generated code from a non-production environment such as a sandbox or development environment has been reviewed and is uploaded to the production server. |
Client number |
000-999 |
The three-digit client number. Defaults to 800. |
System number |
00-99 |
The two-digit system number. Defaults to 00. |
ODP Context |
Refer to the requirements of the application |
The context in the ODP framework describes a non-local SAP repository that maps its metadata in the ODP framework. The context can be compared with a schema in a database. When setting up SAP BW/4HANA as a source, set this option to BW. |
Routing string |
Refer to the requirements of the application |
Enter the SAP routing string used to connect to SAP systems through SAProuters. |
Execute in background (batch) |
Yes No |
Specify whether the generated ABAP programs created by SAP application data flows defined with this datastore will execute in batch mode on the SAP server. Batch mode operation is slower than the normal console mode; however, choose batch mode if the application is too long to run during the console mode time frame. Defaults to No. |
Target host |
Computer name, fully qualified domain name, or IP address |
If you chose to execute ABAP programs in the background, specify the target computer (host). |
Job class |
A B C |
If you chose to execute ABAP programs in the background, specify the job class. |
Security profile |
By default, SAP Cloud Integration for data services does not use an SAP security profile. You can associate a security profile with a datastore so that data flows that access SAP application sources defined by the datastore include appropriate authorization checking. Specify any security profile defined in SAP (a predefined profile or a profile you defined). |
|
RFC trace level |
Brief Verbose Full |
Brief: Error messages are written to the trace log. (Default) Verbose: The trace entries are dependent on the SAP program being traced. Full: In addition to entries traced by verbose value, data blocks are also traced. Note You must specify a location on your Agent system
where you want to store the RFC trace log file. To specify the
location:
|
RFC destination |
SAPDS or <Destination name> |
For the RFC data transfer method, enter a TCP/IP RFC destination. You can keep the default name of SAPDS and create a destination of the same name in the source SAP system, or you can enter a destination name for an existing destination. |
Use sapnwrfc.ini |
Yes No |
Select to use an sapnwrfc.ini file, which overrides the datastore settings. Place the sapnwrfc.ini file in the current directory of the process being executed (%LINK_DIR%/bin). Defaults to No. |
Destination |
Refer to the requirements of the application |
If using an sapnwrfc.ini file, enter the destination name to reference. |
Load balance |
Yes No |
Select Yes to enable load balancing, which helps to run tasks successfully in case the application server is down or inaccessible. See Extract Data from a Load-Balanced SAP Application System. |
MS host |
Computer name, fully qualified domain name, or IP address |
Specify the message server host name. Overrides the setting in sapnwrfc.ini. |
MS port |
Refer to the requirements of the application |
Specify this parameter only if the message server does not listen on the standard service sapms<SysID> or if this service is not defined in the services file and you need to specify the network port directly. Overrides the setting in sapnwrfc.ini. |
Server group |
<User input> Public Space |
Optionally specify the group name of the application servers. Default: Public. Overrides the setting in sapnwrfc.ini. |
System ID |
Refer to the requirements of the application |
Name of the SAP system. Overrides the setting in sapnwrfc.ini. |
Upload attribute: Status |
P - SAP Standard Production Program K - Customer Production Program S - System Program T - Test Program |
Indicates whether the program is a test program, a system program, or a production program. Default is T - Test program. The parameter can have only the value code or the value code and description, separated by a space. |
Upload attribute: Application |
Refer to the drop-down list for available options |
Indicates the application area to which the program belongs (Basis, General Ledger, Sales, and so on). The default value is S - Basis. The parameter can have only the value code or the value code and description, separated by a space. |
Upload attribute: Development class (Package) |
Refer to the drop-down list for available options |
Indicates the name under which related objects in the ABAP Workbench are grouped together in a package. Default is $TMP. The program is created as a local (non-transportable) object. |
Upload attribute: Request ID |
Refer to the drop-down list for available options |
Indicates the Change and Transport System (CTS) request ID. The default value is blank. This option is populated by the Data Services Agent if a non-local program object is created in SAP. |
Upload attribute: Task ID |
Refer to the drop-down list for available options |
Indicates the CTS task ID. The default value is blank. This option is populated by the Data Services Agent if a non-local program object is created in SAP. |
When creating a task and the source is either a Business Suite Application datastore or a BW Source datastore, you cannot use a BW Target datastore as the target.
