SAP BW Target

Create an SAP BW Target datastore to connect to an SAP BW Target database.

SAP BW database datastores support a number of specific configurable options. Configure the datastore to match your SAP BW 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.
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.
Type	SAP BW Target	Select the type of datastore to which you are connecting.
Application server	Computer name, fully qualified domain name, or IP address	The name of the remote SAP application computer (host) to which the service 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 service accesses the SAP application server.
Password	Alphanumeric characters and underscores, or blank	The user's password.
SNC library	Full file path and name of SNC security library	Enter the full path and name of the third-party security library to use for SNC communication (authentication, encryption, and signatures).
SNC name of Data Services	Refer to the requirements of the application	Enter the SNC name that the SAP system uses to identify .
SNC name of SAP system	Refer to the requirements of the application	Enter the SNC name of the SAP system for this connection.
SNC quality of protection	Max Available Authentication Integrity Privacy	With Max Available, the system obtains the maximum quality of protection supported by the target SAP system. This value is configured in the SAP Application Server profile parameter snc/data_protection/max. It could be configured to be Authentication, Integrity, or Privacy. With authentication, the system verifies the identity of the communication partners, which in this case is SAP Cloud Integration for data services. This is the minimum protection level offered by SNC. No actual data protection is provided. With integrity, the system detects any changes or manipulation of the data that might have occurred between the two end points of a communication. With privacy, the system encrypts the messages being transferred to make eavesdropping useless. Privacy protection also includes integrity protection of the data. This is the maximum protection level offered by SNC.
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.
Client number	000-999	The three-digit client number. Defaults to 800.
System number	00-99	The two-digit system number. Defaults to 00.
Routing string	Refer to the requirements of the application	Enter the SAP routing string used to connect to SAP systems through SAP routers.
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.
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 NOTE: You must specify a location on your Agent system where you want to store the RFC trace log file. To specify the location, do the following: On your Agent system, navigate to the conf directory under `<DS_COMMON_DIR>`. Open the DSConfig.txt file in a text editor. In the AL_Engine section, after the line "`AL_EngineMiscOptions =` ", add the following line: SAP_RFC_TRACE_DIR = `<rfc trace log directory>` Where <rfc trace log directory> is a directory on your agent system. For example, `SAP_RFC_TRACE_DIR = c:\temp`.
Load balance	Yes No	Select Yes to enable load balancing, which helps run tasks successfully in case the application server is down or inaccessible.
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	Must be a number that does not start with 0 (zero).	The port of the message server host name.
Server group	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.

To use the BW target datastore, you must configure the RFC destination with the Program ID defined. See the SAP Business Suite connectivity information in the SAP Data Services Agent Guide.

Data Flow Options

When you are setting up a data flow for a BW Target datastore, you can use the following options:

Option	Possible values	Description
Rows per commit	Positive integer Default: 1000	Enter the maximum number of rows loaded to a target table before saving the data. This value is the default commit size for target tables in this datastore. You can overwrite this value for individual target tables.
Column comparison	Compare by position Default: Compare by name	Specifies how the service maps the input columns to persistent cache table columns. Compare by position: Disregards the column names and maps source columns to target columns by position. Compare by name: Maps source columns to target columns by name.
Number of loaders	Positive integer Default: 1	Specifies the number of loaders the service uses. There are different types of loading: Single loader loading: Loading with one loader. Parallel loading: Loading with two or more loaders. When parallel loading, each loader receives the number of rows indicated in the Rows per commit option, and processes the rows in parallel with the other loaders. Example If Rows per commit = 1000 and Number of Loaders = 3: First 1000 rows go to the first loader Second 1000 rows go to the second loader Third 1000 rows go to the third loader Fourth 1000 rows go the first loader Each loader performs the necessary processing and, when complete, sends the data in a packet to the SAP BW system. Due to differences in processing, the loaders may not send the packets to the SAP BW system in sequential order. Note Parallel loading is not supported for a hierarchy BW data source.

Option

Possible values

Description

Rows per commit

Positive integer

Default: 1000

Enter the maximum number of rows loaded to a target table before saving the data. This value is the default commit size for target tables in this datastore. You can overwrite this value for individual target tables.

Column comparison

Compare by position

Default: Compare by name

Specifies how the service maps the input columns to persistent cache table columns.

Compare by position: Disregards the column names and maps source columns to target columns by position.
Compare by name: Maps source columns to target columns by name.

Number of loaders

Positive integer

Default: 1

Specifies the number of loaders the service uses.

There are different types of loading:

Single loader loading: Loading with one loader.
Parallel loading: Loading with two or more loaders.

When parallel loading, each loader receives the number of rows indicated in the Rows per commit option, and processes the rows in parallel with the other loaders.

Example

If Rows per commit = 1000 and Number of Loaders = 3:

First 1000 rows go to the first loader
Second 1000 rows go to the second loader
Third 1000 rows go to the third loader
Fourth 1000 rows go the first loader

Each loader performs the necessary processing and, when complete, sends the data in a packet to the SAP BW system.

Due to differences in processing, the loaders may not send the packets to the SAP BW system in sequential order.

Note

Parallel loading is not supported for a hierarchy BW data source.

Note

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.