Question:
I am creating a source system from a productive R3 46C system to our production BW 3.0B system.
When I create the source system, I am challenged to log onto the R3 system with the admin user, and then the source system creation bombs out with 'Source system connection was terminated'
I think the user authorisations are ok for the users being used, but can anyone tell me what client settings are required on R3 and BW systems to allow source system creation, when I did these in Dev & QA they were fairly open, but in the prod systems client settings for cross client and client specific are set for 'no changes'.
Thanks.
Answer:
Hi basisbw2,
this answer may be a bit late but perhaps it helps some other people.
I can't help you about your specific problem because the error description is too rough. From my experience there's alway some little problems when connecting a sourcesystem.
I think the most important issue is, that your sourcesystem HAS to be open for changes (SCC4). There's definitly no other chance.
Below I post the SAP Help description. Please excuse the bad format, but I'm just too lazy to put it right. If you want to read it in a nicer look and with colors please go to http://help.sap.com. There you'll find this fairly good documentation.
Best regards,
Stefan
Creating an SAP Source System
Prerequisites
1. You have made the following settings in the BW Customizing Implementation Guide under Business Information Warehouse  Connections to other Systems.
o General connection settings,
o Connection between SAP systems and BW,
o Verify workflow customizing.
2. You have made the following settings in the implementation guide of the source system under the node Cross-Application Components  Distribution (ALE)  Basic Settings.
 Set up logical system
 Maintain logical system
 Assign logical system to the client
 Make workflow basic settings
The name you used for the source system (logical system) must be used again for the creation of the source system in the Administrator Workbench for the SAP Business Information Warehouse.
3. You have taken the server name from the source system under Tools  Administration  Monitor  System Monitoring  Server. It is displayed as follows:
Server_<SAPSID>_<instanceno.>
pswdf090_IDF_90
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
see below
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
4. As a rule, no system changes are permitted in productive systems at all. Connecting a system as a source system to a BW or connecting a BW to a new source system will, however, mean changes as far as the system change option is concerned. You will have therefore made sure that the following changes are permissible in the relevant clients of the system when you connect the source system.
 Cross-client Customizing and Repository changes
In the BW Customizing Implementation Guide, select the relevant client under Business Information Warehouse  Connections to Other Systems  General Connection Settings  Assign Logical System to Client, then choose Goto  Detail. Choose the entry Changes to Repository and Cross-Client Customizing Permitted in the field Changes to Cross-Client Objects.
In the source system, make this setting in the Implementation Guide under Cross-application Components  Distribution(ALE)  Basic Settings  Set Up Logical System  Assign Logical System to Client.
 Changes to the software components local developments and Business Information Warehouse.
You can set up the changeability with Transaction SE03 (Organizer Tools). Choose Organizer Tools  Administration  Set Up System Change Option, then Execute. Make the settings in the subsequent screen.
 Changes in the customer name area
Again, you can set up the changeability for the customer name area with Transaction SE03.
 Changes to BW namespaces /BIC/ and /BI0/
Again, you can set up the changeability of the BW namespace with Transaction SE03.
Procedure
• Creating an SAP Source System Manually
• Creating an SAP Source System (from Release 3.0E) Automatically
Result
The ALE settings, which are needed for the communication between a BW System and an SAP System, are created in the background with the use of the created destinations. These settings are made in BW as well as in the source system. The BW settings for the new connection are created in BW.
If the new SAP source system has been created, Metadata is requested automatically from the source system
See below
Creating an SAP Source System Automatically
1. In the BW Administrator Workbench choose Source System Tree  Context Menu (right mouse button)  Create and choose the radio button for creating an external system.
2. Enter the information on the server name previously taken from the source system.
Application server: pswdf090
System ID: IDF
System number: 90
3. Enter a password for the background user in the source system and confirm this in the next input row. If the user already exists in the source system, enter the valid password.
4. Enter the password that you defined for the SAP BW background user in the BW Customizing Implementation Guide under Business Information Warehouse  Links to Other Systems  Link Between SAP Systems and BW  Background User for Links to SAP Systems, and confirm.
5. Choose Copy. You get to the remote login in the source system.
6. Select the relevant clients and logon as system administrator. Make sure beforehand that you have the authority to create users and RFC destinations.
The RFC destinations for BW and the background users are thus created automatically in the source system. You can find additional information on the RFC destinations in the Basis Documentation in the section Maintaining Removed Destinations.
Profile assignment for the user is also carried out automatically. If the user already exists in the source system, check the accuracy of the profile If the RFC destination already exists in the source system, check its accuracy too. You can carry out an RFC destination test with the function Test  Links and Test  Authorizations.
The RFC destination for the source system is now created automatically in BW with the information read in the source system.
You can find more detailed information under:
Creating an SAP Source System
Answer:
Thanks for the detailed setup on this, but i have one fairly fundamental question.
What user type should the user in the source system be? (Dialog, service, Reference or System)
When i try to restore the source system link from dev bw to a dev r/3 client & put in the passwords for both users, a box flashes up temporarily with the source system userid in it & some other info I cant read, as its then overwritten with a box saying "Please log on as an administrator in the following screen".
when i click ok another message appears saying "no connection to system DEVCLNT520 possible". This had been working for ages & now appears all the time.
SM59 test connections works ok, so I'm stumped.
The only thing i can think of is the user has changed.
Any thoughts would be appreciated.
_________________
Rooflessdriver.
Change is inevitable, except from a vending machine!!
www.collinsphotographic.co.uk
Answer:
The user (ALEREMOTE, or whatever you have called it) should be 'System' user. It is possible that someone has changed the password for this user, either in SU01 or in SM59.
_________________
Keep smiling
Answer:
Thats what i thought & had tried.
The type is "system" & i reset both the su01 & sm59 passwords, but still comes up with the same message.
Whats really interesting now is 2 other clients, 500 & 530, which were working, have also stopped and get the same problem.
_________________
Rooflessdriver.
Change is inevitable, except from a vending machine!!
www.collinsphotographic.co.uk
Answer:
I've just gone back into SM59 in BW & clicked both test connection & test authorisation to the Dev Client, and both work.
Very strange.
_________________
Rooflessdriver.
Change is inevitable, except from a vending machine!!
www.collinsphotographic.co.uk