You have made the following settings in Customizing, under SAP NetWeaver Business WarehouseLinks to Source Systems:
General connection settings
Perform automatic 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 results in changes in terms of system change options however. 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 Customizing, under SAP NetWeaverBusiness WarehouseLinks to Source SystemsGeneral Connection SettingsAssign Logical System to Client, select the client in question and choose GotoDetails. In the Cross-Client Object Changes field, select Changes to Repository and Cross-Client Customizing Allowed.
Changes to the local developments and Business Information Warehouse software components
You use transaction SE03 (Organizer Tools) to set the change options. Choose Organizer ToolsAdministrationSet System Change Option. Choose Execute. On the next screen, make the following settings:.
Changes to the customer name range
You also use transaction SE03 to set the change option for the customer name range.
Changes to BW namespaces /BWC/ and /BW0/
You also use transaction SE03 to set the change option for the BW namespaces.
If you want to connect an SAP Business ByDesign system: Make sure that you have the required information and that the required settings have been made in the BW system.
If you want to connect a source using SAP Landscape Transformation Replication Server (SLT), make sure that the connection to the data source has been set up on the SLT.
If you want to connect SAP S/4HANA Cloud: Make sure that secure communication between SAP S/4HANA Cloud and SAP BW∕4HANA is set up using communication administration in SAP S/4HANA Cloud.
In the source system tree of the Data Warehousing Workbench, select the ODP folder for the required context.
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.
The following folders are available:
ODP Folder
Context
ODP - BW
BW
ODP - SAP (Extractors)
SAPI
ODP - SAP HANA Information View
HANA
ODP - SLT Queue
SLT~<Queue Alias>
ODP - ABAP CDS View
ABAP_CDS
ODP - SAP Business ByDesign
BYD
In the folder context menu, choose Create.
A dialog box opens. Enter a technical name and a description for the source system under Logical System Name.
Wählen Sie .
A dialog box opens where you can configure the connection parameters. For most of the ODP contexts, RFC is used for the connection. For SAP Business ByDesign systems and SAP S/4HANA Cloud, HTTP/SOAP is used for the connection.
RFC
The destination maintenance screen for connection type ABAP opens. Specify the destination parameters. If the background user already exists in the source, enter this user when configuring the destination. Save and test your destination and then go back.
Another dialog box opens that guides you to the Web service configuration screen in SOA Manager (or lets you check whether a Web service configuration/logical port already exists).
In the Web service configuration screen, you create and configure a logical port for the default consumer proxy CO_RSDSPX_ODP_IN. Check and save the consumer proxy and go back.
The dialog box ODP Source System <Logical System Name> opens. Here you can make the following entries:
The system displays the context selected previously under ODP Context. Here you can change the context again if required. The source determines which contexts are available.
For SAP Landscape Transformation Replication Server (SLT), select the context for the required queue alias. The queue alias describes the source configuration for data provisioning in SLT.
Under Removed Tree, you can specify for specific sources, which deliver a hierarchical grouping of source objects (tree), whether the grouping should be copied to the DataSource tree for the source system. If you do not copy the tree from the source or the source does not deliver a hierarchical grouping, then the application components defined for the non-replicated source systems are used as the grouping for the DataSource tree.
Under BW Background User and User Password enter a background user and set a password. If the user already exists in the source system, enter the corresponding password.
The user is required for verification. The system uses the user name to create a destination with the naming convention <BW system ID>CLNT<client of BW system>. When settings are saved, the destination checks whether the source system only delivers data to one BW system or to multiple BW systems with the same name. if the source system delivers data to multiple BW systems with the same name, this can cause problems during a system copy.
Press (save settings).
The system now checks the source system to find out whether the BW system is a unique subscriber. If this is not the case, an error message is displayed.
The source system is now displayed under the relevant ODP folder in the Data Warehousing Workbench.
For HTTP/SOAP: Close the SOA Manager.
Results
You can now create DataSources for this source system.