You have made the following settings in the Data Services system:
In the Administrator tool in the Data Services Management Console, you have created an SAP connection for every SAP application server by creating an RFC server interface and starting the RFC server interface connection. You will need the RFC program ID later when creating the reverse connection from BW to Data Services. Data Services can now receive RFC calls from the BW system.
To establish a secure connection between BW and Data Services, and to allow a logon check whenever a BW user calls a function in Data Services, you can make SNC settings when creating the RFC server. You need the BOE CMC user configuration to do this.
For more information on RFC Server Management in the Data Services system, go to the SAP Help Portal at http://help.sap.com/bods and choose <Your Data Services Release>Installation, Upgrade, Deployment in the Management Console Guide.
You have made the following settings in the BW system:
In BW Customizing, under Business WarehouseConnections to Other Systems:
General connection settings
Verify Workflow Customizing
As a rule, system changes are not permitted in production systems. Connecting a system as a source system to a BW or connecting a BW to a new source system makes it necessary to change the system change options though. In the client used in the BW system, you have therefore made sure that the following changes are permitted during the source system connection:
Cross-client Customizing and repository changes
In BW Customizing, under Cross-Client Object Changes field, select Changes to Repository and Cross-Client Customizing Allowed.
, select the relevant client and choose . In theChanges to software component "Local Developments and Business Warehouse"
You use transaction SE03 (Transport Organizer) to set the change options. Choose Execute. On the next screen, make the following settings:.
and pressChanges to the customer name range
You also use transaction SE03 to set the change option for the customer name range.
Changes to BI namespaces /BIC/ and /BI0/
You also use transaction SE03 to set the change option for the BI namespaces.
In the source system tree in the Data Warehousing Workbench, choose Create in the context menu for Data Services.
In the next dialog, under Logical Systen Name and Source System Name, enter a technical name and a descriptive text for the source system.
The source system connects to the source where the data is located. We therefore recommend giving the the source system a name that makes clear where the data comes from. If you want to use Data Services to transfer sales data from an external database for example, enter SALESDB / Sales Database.
Under Type and Release, enter an abbreviation to descrbe the source system type (MYSQL for example) and choose .
In the next screen, you create an RFC destination:
On the Technical Settings tab page, enter the RFC program ID that you created in the Data Services Management console as the Registered Server Program under Program ID.
Once you have made the SNC settings in the Administrator tool, in the Data Services Management Console in the RFC Server Interface, select the Logon and Security tab page and press Send Logon Ticket Without Reference to a Source System under Logon Procedure.
Save the connection, test it and then go back.
In the next dialog, enter the required data.
Attributes of the Data Services System (to select the data, a connection is set up to Data Services):
Select the Data Services repository.
Select the job server.
Connection from Data Services to BW (BW Target Datastore)
To allow Data Services data to be sent to the BW system, this must be set as the target in Data Services. This is done by creating a (target) Datastore. This is only possible if you enter the BW system background user - and password - that Data Services can use to log on with when sending data to to the BW system. All other connection information is already known to the system.
Third-party system that is connected using Data Services
Using a (source) Datastore, you define the external system containing the data to be transferred to the BW system with Data Services. A fixed source Datastore is suitable if you want to load a table from the source with a 1:1 assignment into a DataSource in BW.
If the system that the data will be loaded from is already known to Data Services, select the appropriate Datastore. If the Datastore does not exist, create it. More information: Creating Source Datastores in the SAP Data Services System.
If you do not specify or create a Datastore here, and you join multiple source tables in the Data Services system instead, cleanse the data or apply data quality measures, the source system will be created as the source system for the standard staging BAPI transfer.
Choose .
By making RFC calls to the Data Services system, the following actions are started in Data Services:
The encoded password is passed on to Data Services and saved there.
The BW target Datastore is created and validated with the information from the BW system. You will see the Datastore in the repository in SAP Data Services Designer and can view the properties of the Datastore by choosing Edit in the context menu. The naming convention for the Datastore is <Name of the Data Services source system>@<Logical name of the BW system>. For Data Services source system SALESDB in BW system XYZCLNT000 for example, the target Datastore would be called SALESDB@XYZCLNT000.
If you have made entries in the generic entry screen in the BW system to create the source Datastore, this will be created and validated in the Data Services system. You will see the Datastore in the repository in SAP Data Services Designer and can view the properties of the Datastore by choosing Edit in the context menu.
The source system has now been created.
For more information about Datastores, go to the SAP Help Portal at http://help.sap.com/bods and choose <Your Data Services Release>Installation, Upgrade, Deployment in the Designer Guide.