BW--- BW Connectivity(最佳实践适合BW3.5)
2007-07-20 09:33
85 查看
Content
Building Block – BW Connectivity. 6
1 Prerequisites. 6
1.1 User Roles. 6
2 Local Settings. 6
2.1 SAP R/3. 6
2.1.1 Define Client Administration (SAP R/3)6
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)7
2.1.3 Assigning Logical System to Client8
2.1.4 Creating an RFC User (SAP R/3)8
2.2 SAP SCM.. 9
2.2.1 Define Client Administration (SAP SCM)9
2.2.2 Defining a Logical System for SAP SCM (SAP SCM)10
2.2.3 Assigning Logical System to Client (SAP SCM)11
2.2.4 Creating an RFC User (SAP SCM)11
2.3 SAP BW.. 12
2.3.1 Define Client Administration. 12
2.3.2 Defining a Logical System for SAP BW (SAP BW)13
2.3.3 Assigning Logical System to Client (SAP BW)14
2.3.4 Opening Administrator Workbench. 14
2.3.5 Creating an RFC-User (SAP BW)15
2.3.6 Define RFC-USER as default (SAP BW)16
2.4 SAP CRM.. 16
2.4.1 Defining Logical Systems. 16
2.4.2 Assigning Clients to Logical Systems. 17
2.4.3 Creating RFC User18
2.5 SAP SRM.. 18
2.5.1 Define Client Administration. 18
2.5.2 Define a Logical System for SAP SRM.. 19
2.5.3 Assign Logical System to Client20
2.5.4 Create System Users. 20
3 Cross Connectivity. 21
3.1 Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM.. 21
3.2 SAP SCM with SAP BW.. 22
3.2.1 Connecting SAP SCM to the SAP BW system.. 22
3.2.2 Connecting SAP BW to the SAP SCM System.. 23
3.3 Connectivity File System in SAP BW.. 24
3.3.1 Defining Logical System.. 24
3.3.2 Creating the Source System in the Administrator Workbench. 24
Building Block – BW Connectivity
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
Then carry out the following steps:
1. Choose Display ® Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
· Automatic recording of changes
· Changes to Repository and cross-client Customizing allowed
· eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
To designate logical systems, apply the naming convention
<XXX>CLNT<NNN>
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
5. Save your entries.
2.2 SAP SCM
2.2.1 Define Client Administration (SAP SCM)
Use
This activity enables you to change Customizing settings.
Prerequisites
You have logged on to the system in English to start with the installation.
Procedure
Carry out the following steps:
1. Access the transaction using:
2. In the view Display View "Clients": Overview, choose Display ® Change and confirm the message The table is cross-client.
3. Select your SCM client.
4. Choose Details.
5. In the view Change View "Clients": Details set the flags for
Automatic recording of changes
Allow CATT processes to be started
Changes to Repository and cross-client Customizing allowed.
6. Save and choose Back twice.
2.2.2 Defining a Logical System for SAP SCM (SAP SCM)
Use
The purpose of this activity is to create a logical system for your SAP SCM System. To enable communication between systems within your system landscape, you must:
1. Define the systems as logical systems.
2. Assign the logical system for the SAP SCM System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined as cross-client.
Procedure
Carry out the following steps:
1. To define the logical system for your SAP SCM System, open the transaction using:
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
To designate logical systems, apply the naming convention
<XXX>CLNT<NNN>
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.2.3 Assigning Logical System to Client (SAP SCM)
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your SCM client and choose Details.
5. Enter the name of the logical system of your SAP SCM client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.2.4 Creating an RFC User (SAP SCM)
Use
To enable communication between the SAP R/3 Backend System and the SAP SCM System, you have to create an RFC user in the SAP SCM System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. To create the RFC user, open the transaction as follows:
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), “Automatic recording of changes” and “Changes to Repository object and cross-client Customizing allowed” is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View “Logical Systems”: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
1. In the view Display View "Clients": Overview, choose Display. ® Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
c. Choose the Logon data tab.
d. Enter the following data:
e. Choose the Profiles tab.
f. Enter the following data:
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
1. On the Administrator Workbench: Modeling screen choose Settings à Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View “RSADMINA Maintenance View”: Details screen:
Choose Display à Change.
Enter RFCUSER in the BW User ALE field.
Choose Save.
Leave the transaction in order to activate the entries you have made.
2.4 SAP CRM
2.4.1 Defining Logical Systems
Use
The distribution of data between systems makes it necessary to identify each system as a unique logical system.
A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.
Procedure
To carry out the activity, choose one of the following navigation options:
Then carry out the following steps:
1. Choose New entries.
2. Enter the following data:
· A name for the logical system that you want to create (Log. System)
· A clear description for the logical system (Name)
3. Save your entries.
2.4.2 Assigning Clients to Logical Systems
Procedure
To carry out the activity, choose one of the following navigation options:
Then carry out the following steps:
1. Choose Display <-> Change.
2. Select your CRM client.
3. Choose Details. The Client Details screen appears.
4. Enter the following data:
5. Save your entries.
These settings cannot be transported. When a new system is being set up, these settings must be made manually after the system installation has been completed.
2.4.3 Creating RFC User
Use
An RFC user is required for setting up the connectivity between systems.
Procedure
To carry out the activity, choose one of the following navigation options:
1. In the User field, enter RFCUSER.
2. Choose Create (F8).
3. Enter the following data:
4. Save your entries.
2.5 SAP SRM
2.5.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. Access the transaction using:
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. Check the entries for currency and client role.
6. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), Automatic recording of changes and Changes to Repository object and cross-client Customizing allowed is required.
7. In the Restrictions area, set the flag Allows CATT processes to be started.
This flag must be set. Otherwise, activities using CATT procedures cannot be used for the installation.
Result
Client administration has been defined to support the installation using Best Practices.
2.5.2 Define a Logical System for SAP SRM
Use
The logical system is important for the communication between several systems. This activity is used to define the logical systems for the Enterprise Buyer and back-end system.
Procedure
1. Access the transaction using:
2. For the activity type, select Cross-client.
3. The following naming convention is recommended:
4. Save your entries
You have to maintain at least two systems (local Enterprise Buyer system and the SAP R/3 back-end system)
Naming Conventions: XXXCLNT123 (XXX = system ID, 123 = client number)
2.5.3 Assign Logical System to Client
Use
The purpose of this activity is to define the
· Enterprise Buyer client you will be using
· Standard currency to be used
· Recording of changes
· Capability for your system to use CATT procedures
Procedure
1. Access the transaction using:
2. Switch to the Change mode.
3. Select your Enterprise Buyer client and go to the Client Details screen.
4. In the Logical system screen, choose the logical system for the client.
5. Set the currency in the Std currency field to a valid entry, such as USD or EUR.
6. Make the following settings:
7. Choose Save.
Using this transaction, you can change from the production client to the development client and back again in the Client role field.
Result
The logical system has been assigned to the client and CATT procedures can be executed now.
2.5.4 Create System Users
Use
This task creates remote users RFCUSER, BBP_JOB, WEBLOGIN for the SAP R/3 back-end system and for Enterprise Buyer.
Procedure
1. Access the transaction using:
2. Enter RFCUSER in the User field.
3. On the Address tab Choose Lastname RFCUSER.
4. Choose Create.
5. Enter the password LOGIN on the Logon data tab.
6. As User Type, select System.
7. Go to the Profiles tab.
8. Enter the profiles SAP_ALL ,SAP_NEW and S_BI-WX_RFC.
9. Save your entries.
10. Repeat this procedure to create the user BBP_JOB (Password: LOGIN).
11. Repeat this procedure to create the user WEBLOGIN (Password: SAPPHIRE).
Result
The following users have been created.
USER/Password from the Service File of the ITS Installation.
3 Cross Connectivity
This chapter describes all settings that are necessary to connect the components of the SAP.system landscape with each other. The settings for each combination of two components to be connected are described in a separate structure node. The separate section headings make it possible to identify the activities required to connect certain components with each other. The section headings for components that are not part of the installation can be skipped.
3.1 Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM
Procedure
To carry out the activity, choose one of the following navigation options in the SAP BW system:
1. Choose Modeling.
2. Choose Source Systems.
3. Select Source Systems in the window on the right.
4. Choose the Context menu (right mouse click).
5. Choose Create.
6. Select SAP System from Release 3.0E (Automatic Creation).
7. Choose Transfer.
8. Make the following entries:
9. On the dialog box Please log on as an administrator in the following screen choose Continue.
10. Log on to the Source System with your administrator user. Choose the correct client.
11. On the dialog box New Source System Connection choose Continue.
12. On the Replicate Metadata dialog box, choose Only Activate.
3.2 SAP SCM with SAP BW
3.2.1 Connecting SAP SCM to the SAP BW system
Procedure
To carry out the activity, choose the following navigation option in the SAP BW system:
Then carry out the following steps:
1. Choose Modeling.
2. Choose Source Systems.
3. Select Source Systems in the window on the right.
4. Choose the Context menu (right mouse click).
5. Choose Create.
6. Select SAP Business Information Warehouse.
7. Make the following entries:
8. In the dialog box Please log on as an administrator in the following screen choose Continue.
9. Log on to the Source System with your administrator user. Choose the correct client.
10. On the dialog box New Source System Connection choose Continue.
11. On the Replicate Metadata dialog box, choose Only Activate.
3.2.2 Connecting SAP BW to the SAP SCM System
Procedure
Carry out the activity in the SAP SCM system.
1. Choose Modeling.
2. Choose Source systems.
3. Select Source systems in the window on the right.
4. Choose the Context menu (right mouse click).
5. Choose Create.
6. Select SAP Business Information Warehouse.
7. Make the following entries:
8. On the dialog box Please log on as an administrator in the following screen choose Continue.
9. Log on to the Source System with your administrator user. Choose the correct client.
10. On the dialog box Check RFC destination choose Use.
3.3 Connectivity File System in SAP BW
This section describes all settings that are necessary for the connectivity for an external system - PC files on the Workstation (for example Excel files) or files on the application server in SAP BW.
3.3.1 Defining Logical System
Procedure
1. From the SAP IMG in the BW system, choose:
2. Choose New entries.
3. Enter the following data:
a name for the logical system that you want to create (Log. System).
a clear description for the logical system (Name).
4. Choose Save your entries
5. A transport request for workbench and customizing is displayed. Choose existing requests or create new requests.
3.3.2 Creating the Source System in the Administrator Workbench
Procedure
1. From the SAP Menu in the BW system, choose:
2. Choose Modeling.
3. Choose Source Systems.
4. In the right-hand window mark Source Systems.
5. Choose the context menu (right mouse click).
6. Choose Create.
7. Choose Enter.
8. Choose Enter.
9. Choose Back.
Building Block – BW Connectivity. 6
1 Prerequisites. 6
1.1 User Roles. 6
2 Local Settings. 6
2.1 SAP R/3. 6
2.1.1 Define Client Administration (SAP R/3)6
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)7
2.1.3 Assigning Logical System to Client8
2.1.4 Creating an RFC User (SAP R/3)8
2.2 SAP SCM.. 9
2.2.1 Define Client Administration (SAP SCM)9
2.2.2 Defining a Logical System for SAP SCM (SAP SCM)10
2.2.3 Assigning Logical System to Client (SAP SCM)11
2.2.4 Creating an RFC User (SAP SCM)11
2.3 SAP BW.. 12
2.3.1 Define Client Administration. 12
2.3.2 Defining a Logical System for SAP BW (SAP BW)13
2.3.3 Assigning Logical System to Client (SAP BW)14
2.3.4 Opening Administrator Workbench. 14
2.3.5 Creating an RFC-User (SAP BW)15
2.3.6 Define RFC-USER as default (SAP BW)16
2.4 SAP CRM.. 16
2.4.1 Defining Logical Systems. 16
2.4.2 Assigning Clients to Logical Systems. 17
2.4.3 Creating RFC User18
2.5 SAP SRM.. 18
2.5.1 Define Client Administration. 18
2.5.2 Define a Logical System for SAP SRM.. 19
2.5.3 Assign Logical System to Client20
2.5.4 Create System Users. 20
3 Cross Connectivity. 21
3.1 Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM.. 21
3.2 SAP SCM with SAP BW.. 22
3.2.1 Connecting SAP SCM to the SAP BW system.. 22
3.2.2 Connecting SAP BW to the SAP SCM System.. 23
3.3 Connectivity File System in SAP BW.. 24
3.3.1 Defining Logical System.. 24
3.3.2 Creating the Source System in the Administrator Workbench. 24
Building Block – BW Connectivity
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
| Technical name | Description | File name for upload |
| B02_01C | B02 - Connectivity Configuration Role (SAP R/3) | B02_01C.SAP |
| B02_03C | B02 - Connectivity Configuration Role (SAP BW) | B02_03C.SAP |
| C71_04C | B02 - Connectivity Configuration Role (SAP CRM) | C71_04C.SAP |
| B02_04C_SRM | B02 - Connectivity Configuration Role (SAP SRM) | B02_04C_SRM.SAP |
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
| SAP R/3 Role Menu | Define Client Administration (SAP R/3) |
| Transaction Code | SCC4 |
| SAP R/3 Menu | Tools à Administration à Administration à Client Administration à Client Maintenance |
1. Choose Display ® Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
· Automatic recording of changes
· Changes to Repository and cross-client Customizing allowed
· eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
| SAP R/3 Role Menu | Defining a Logical System for SAP R/3 (SAP R/3) |
| Transaction Code | SPRO |
| SAP R/3 IMG Menu | Basis Components (for R/3 Enterprisse: SAP Web Application Server) ® Application Link Enabling (ALE) ® Sending and Receiving Systems ® Logical systems ® Define Logical System |
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
| Log. System | Name |
| <Logical system 2>, for example DS7CLNT723 | SAP R/3 System |
<XXX>CLNT<NNN>
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
| SAP R/3 Role Menu | Assign Logical System to Client |
| Transaction Code | SCC4 |
| SAP R/3 Menu | Tools à Administration à Administration à Client Administration à Client Maintenance |
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
| SAP R/3 Role Menu | Creating an RFC User (SAP R/3) |
| Transaction Code | SU01 |
| SAP R/3 Menu | Tools à Administration à User MaintenanceàUsers |
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
| Address | |
| Last Name | |
| Function | |
| Logon data | |
| User type | System |
| Password | LOGIN |
| Profile | |
| Profiles | SAP_ALL SAP_NEW S_BI-WX_RFC |
| Defaults | |
| Logon Language | EN |
2.2 SAP SCM
2.2.1 Define Client Administration (SAP SCM)
Use
This activity enables you to change Customizing settings.
Prerequisites
You have logged on to the system in English to start with the installation.
Procedure
Carry out the following steps:
1. Access the transaction using:
| SAP SCM Menu | Tools à Administration à Administration à Client Administration à Client Maintenance |
| Transaction Code | SCC4 |
3. Select your SCM client.
4. Choose Details.
5. In the view Change View "Clients": Details set the flags for
Automatic recording of changes
Allow CATT processes to be started
Changes to Repository and cross-client Customizing allowed.
6. Save and choose Back twice.
2.2.2 Defining a Logical System for SAP SCM (SAP SCM)
Use
The purpose of this activity is to create a logical system for your SAP SCM System. To enable communication between systems within your system landscape, you must:
1. Define the systems as logical systems.
2. Assign the logical system for the SAP SCM System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined as cross-client.
Procedure
Carry out the following steps:
1. To define the logical system for your SAP SCM System, open the transaction using:
| SAP SCM IMG Menu | SAP R/3 Basis Customizing ® Application Link Enabling (ALE) ® Sending and Receiving Systems ® Logical Systems ® Define Logical System |
| Transaction Code | SPRO |
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
| Log. System | Name |
| <Logical system 2>, for example AS7CLNT001 | SAP SCM System |
<XXX>CLNT<NNN>
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.2.3 Assigning Logical System to Client (SAP SCM)
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
| SAP SCM Menu | Tools à Administration à Administration à Client Administration à Client Maintenance |
| Transaction Code | SCC4 |
3. Confirm the warning message The table is cross client.
4. Select your SCM client and choose Details.
5. Enter the name of the logical system of your SAP SCM client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.2.4 Creating an RFC User (SAP SCM)
Use
To enable communication between the SAP R/3 Backend System and the SAP SCM System, you have to create an RFC user in the SAP SCM System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. To create the RFC user, open the transaction as follows:
| SAP SCM Menu | Tools à Administration à User MaintenanceàUsers |
| Transaction Code | SU01 |
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
| Address | |
| Last Name | |
| Function | |
| Logon data | |
| User type | System |
| Password | LOGIN |
| Profile | |
| Profiles | SAP_ALL and SAP_NEW S_BI-WHM_RFC S_BI-WX_RFC |
| Defaults | |
| Logon Language | EN |
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
| SAP BW Role Menu | Local Settings ® Define Client Administration |
| Transaction Code | SCC4 |
| SAP BW Menu | Tools à Administration à Administration à Client Administration à Client Maintenance |
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), “Automatic recording of changes” and “Changes to Repository object and cross-client Customizing allowed” is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
| SAP BW Role Menu | Defining a Logical System for SAP BW (SAP BW) |
| Transaction Code | SPRO |
| IMG Menu | SAP Reference IMG à SAP Customizing Implementation Guide à SAP NetWeaver à Business Information Warehouse à Links to other Systems à General Connection Settings à Define Logical System |
2. On the Change View “Logical Systems”: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
| Field name | Description | R/O/C | User action and values | Note |
| Log. System | Technical Name of the Logical System | Enter a name for the logical BW system that you want to create | ||
| Name | Textual Description of the Logical System | Enter a clear description for the logical BW system |
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
| SAP BW Role Menu | Assigning Logical System to Client (SAP BW) |
| Transaction Code | SCC4 |
| SAP BW Menu | Tools à Administration à Administration à Client Administration à Client Maintenance |
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
| SAP BW | Modeling à Administrator Workbench: Modeling |
| Transaction Code | RSA1 |
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
| SAP BW Role Menu | Creating RFC User |
| Transaction Code | SU01 |
| SAP BW Menu | Tools à Administration à User Maintenance à Users |
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
| Field | Entry |
| User | RFCUSER |
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
| Field | Entry |
| Last Name | RFCUSER |
| Function | Default-User for RFC connection |
d. Enter the following data:
| Field | Entry |
| Password | LOGIN |
| User type | System |
f. Enter the following data:
| Field | Entry |
| Profiles | SAP_ALL , SAP_NEW and S_BI-WHM_RFC |
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
| SAP BW Role Menu | Define RFC-USER as default (SAP BW) |
| Transaction Code | RSA1 |
| SAP BW Menu | Modeling à Administrator Workbench: Modeling |
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View “RSADMINA Maintenance View”: Details screen:
Choose Display à Change.
Enter RFCUSER in the BW User ALE field.
Choose Save.
Leave the transaction in order to activate the entries you have made.
2.4 SAP CRM
2.4.1 Defining Logical Systems
Use
The distribution of data between systems makes it necessary to identify each system as a unique logical system.
A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.
Procedure
To carry out the activity, choose one of the following navigation options:
| SAP CRM Role Menu | Defining Logical Systems |
| Transaction Code | SPRO |
| CRM IMG Path | Customer Relationship Management à CRM Middleware and Related Components ® Communication Setup ® Set Up Logical Systems ® Define Logical System |
1. Choose New entries.
2. Enter the following data:
· A name for the logical system that you want to create (Log. System)
· A clear description for the logical system (Name)
| Log system | Name |
| <CRM system>CLNT<Client>, for example CS7CLNT200 | For example: “CRM Best Practices” |
| <R/3 OLTP System>CLNT<Client>, for example BECCLNT024 | For example: “OLTP R/3 System” |
2.4.2 Assigning Clients to Logical Systems
Procedure
To carry out the activity, choose one of the following navigation options:
| SAP CRM | Assigning Logical System to Client |
| Transaction code | SCC4 |
| SAP Menu | Customer Relationship Management à CRM Middleware and Related Components à Communication Setup à Set Up Logical Systems à Assign client to logical system |
1. Choose Display <-> Change.
2. Select your CRM client.
3. Choose Details. The Client Details screen appears.
4. Enter the following data:
| Field | Entry |
| Client | <Your CRM Client> |
| Logical system | <Logical System CRM>, for example, CS7CLNT200 |
| Client role | Customizing |
| Changes and transports of client specific objects | Automatic recording of changes |
| Client-independent changes | Changes to repository and cross-client customizing allowed. |
| Protection: Client copier and comparison tool | Protection level 0: no restriction |
| Restrictions | Allows CATT processes to be started |
These settings cannot be transported. When a new system is being set up, these settings must be made manually after the system installation has been completed.
2.4.3 Creating RFC User
Use
An RFC user is required for setting up the connectivity between systems.
Procedure
To carry out the activity, choose one of the following navigation options:
| SAP CRM | Creating RFC User |
| Transaction code | SU01 |
| SAP menu | Basis Tools à Administration à User Maintenanceà Users |
2. Choose Create (F8).
3. Enter the following data:
| Address Tab | |
| Last Name | RFCUSER |
| Function | Default-User for RFC connection |
| Password | LOGIN |
| Logon data Tab | |
| Password | LOGIN |
| User type | System |
| Profile Tab | |
| Profiles | SAP_ALL, SAP_NEW and S_BI-WX_RFCA |
2.5 SAP SRM
2.5.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. Access the transaction using:
| SAP SRM/ Role Menu | Local Settings ® SAP SRM ® Define Client Administration |
| Transaction Code | SCC4 |
3. Select your client.
4. Choose details.
5. Check the entries for currency and client role.
6. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), Automatic recording of changes and Changes to Repository object and cross-client Customizing allowed is required.
7. In the Restrictions area, set the flag Allows CATT processes to be started.
This flag must be set. Otherwise, activities using CATT procedures cannot be used for the installation.
Result
Client administration has been defined to support the installation using Best Practices.
2.5.2 Define a Logical System for SAP SRM
Use
The logical system is important for the communication between several systems. This activity is used to define the logical systems for the Enterprise Buyer and back-end system.
Procedure
1. Access the transaction using:
| IMG Menu Enterprise Buyer | Enterprise Buyer Professional Edition ® Technical Basic Settings ® ALE Settings (Logical System) ® Distribution (ALE) ® Sending and Receiving System ® Logical Systems ® Define Logical System. |
| Transaction Code | SPRO |
3. The following naming convention is recommended:
| Log. System | Name |
| YYYCLNTXXX | Enterprise Buyer System |
You have to maintain at least two systems (local Enterprise Buyer system and the SAP R/3 back-end system)
Naming Conventions: XXXCLNT123 (XXX = system ID, 123 = client number)
2.5.3 Assign Logical System to Client
Use
The purpose of this activity is to define the
· Enterprise Buyer client you will be using
· Standard currency to be used
· Recording of changes
· Capability for your system to use CATT procedures
Procedure
1. Access the transaction using:
| SAP SRM Role Menu | Local Settings ® SAP SRM ® Assign Logical System to Client |
| Transaction Code | SCC4 |
3. Select your Enterprise Buyer client and go to the Client Details screen.
4. In the Logical system screen, choose the logical system for the client.
5. Set the currency in the Std currency field to a valid entry, such as USD or EUR.
6. Make the following settings:
| Setting | Values |
| Changes and transports for client-specific objects | Automatic recording of changes |
| Restrictions when starting CATT and eCATT | eCATT and CATT allowed |
Using this transaction, you can change from the production client to the development client and back again in the Client role field.
Result
The logical system has been assigned to the client and CATT procedures can be executed now.
2.5.4 Create System Users
Use
This task creates remote users RFCUSER, BBP_JOB, WEBLOGIN for the SAP R/3 back-end system and for Enterprise Buyer.
Procedure
1. Access the transaction using:
| SAP Menu Enterprise Buyer | Basis Tools ® Administration ® User Maintenance ® Users |
| Transaction Code | SU01 |
3. On the Address tab Choose Lastname RFCUSER.
4. Choose Create.
5. Enter the password LOGIN on the Logon data tab.
6. As User Type, select System.
7. Go to the Profiles tab.
8. Enter the profiles SAP_ALL ,SAP_NEW and S_BI-WX_RFC.
9. Save your entries.
10. Repeat this procedure to create the user BBP_JOB (Password: LOGIN).
11. Repeat this procedure to create the user WEBLOGIN (Password: SAPPHIRE).
Result
The following users have been created.
| Client | User | Password |
| Enterprise Buyer | RFCUSER | LOGIN |
| Enterprise Buyer | BBP_JOB | LOGIN |
| Enterprise Buyer | WEBLOGIN | SAPPHIRE |
3 Cross Connectivity
This chapter describes all settings that are necessary to connect the components of the SAP.system landscape with each other. The settings for each combination of two components to be connected are described in a separate structure node. The separate section headings make it possible to identify the activities required to connect certain components with each other. The section headings for components that are not part of the installation can be skipped.
3.1 Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM
Procedure
To carry out the activity, choose one of the following navigation options in the SAP BW system:
| SAP BW Role Menu | Connecting SAP BW with SAP R/3, SAP CRM, SAP SRM |
| Transaction code | RSA1 |
| SAP BW Menu | Modeling à Administrator Workbench: Modeling |
2. Choose Source Systems.
3. Select Source Systems in the window on the right.
4. Choose the Context menu (right mouse click).
5. Choose Create.
6. Select SAP System from Release 3.0E (Automatic Creation).
7. Choose Transfer.
8. Make the following entries:
| Field | Entry |
| Target computer (server) | Server of the SAP R/3, SAP CRM or Sap SRM system |
| System ID | System ID of the SAP R/3, SAP CRM or SAP SRM system |
| System number | System number of the SAP R/3, SAP CRM or SAP SRM system |
| Background user in source system | RFCUSER |
| Password for source system | LOGIN |
| Background user in BW | RFCUSER (can not be changed in this activity) |
| Password for BW user | LOGIN |
10. Log on to the Source System with your administrator user. Choose the correct client.
11. On the dialog box New Source System Connection choose Continue.
12. On the Replicate Metadata dialog box, choose Only Activate.
3.2 SAP SCM with SAP BW
3.2.1 Connecting SAP SCM to the SAP BW system
Procedure
To carry out the activity, choose the following navigation option in the SAP BW system:
| SAP BW Role Menu | Connecting SAP APO to the SAP BW system |
| Transaction code | RSA1 |
| SAP BW Menu | Modeling à Administrator Workbench: Modeling |
1. Choose Modeling.
2. Choose Source Systems.
3. Select Source Systems in the window on the right.
4. Choose the Context menu (right mouse click).
5. Choose Create.
6. Select SAP Business Information Warehouse.
7. Make the following entries:
| Field | Entry |
| Target computer (server) | Server of the SAP SCM system |
| System ID | System ID of the SAP SCM system |
| System number | System number of the SAP SCM system |
| Background user in source system | RFCUSER |
| Password for source system | LOGIN |
| Background user in BW | RFCUSER (can not be changed in this activity) |
| Password for BW user | LOGIN |
9. Log on to the Source System with your administrator user. Choose the correct client.
10. On the dialog box New Source System Connection choose Continue.
11. On the Replicate Metadata dialog box, choose Only Activate.
3.2.2 Connecting SAP BW to the SAP SCM System
Procedure
Carry out the activity in the SAP SCM system.
| SAP BW | Modeling à Administrator Workbench: Modeling |
| Transaction code | RSA1 |
2. Choose Source systems.
3. Select Source systems in the window on the right.
4. Choose the Context menu (right mouse click).
5. Choose Create.
6. Select SAP Business Information Warehouse.
7. Make the following entries:
| Field | Entry |
| Available destination | Destination of your SAP BW system |
| Background user in source system | RFCUSER |
| Password for source system | LOGIN |
| Background user in BW | RFCUSER (can not be changed in this activity) |
| Password for BW user | LOGIN |
9. Log on to the Source System with your administrator user. Choose the correct client.
10. On the dialog box Check RFC destination choose Use.
3.3 Connectivity File System in SAP BW
This section describes all settings that are necessary for the connectivity for an external system - PC files on the Workstation (for example Excel files) or files on the application server in SAP BW.
3.3.1 Defining Logical System
Procedure
1. From the SAP IMG in the BW system, choose:
| SAP BW Role Menu | Connectivity File System in SAP BW à Defining Logical System |
| Transaction code | SPRO |
| BW IMG Menu | BW Customizing Implementation Guide à Business Information Warehouse à Links to other Systems à General Connection Settings à Define Logical System |
3. Enter the following data:
a name for the logical system that you want to create (Log. System).
a clear description for the logical system (Name).
| Log system | Name |
| e.g. HT_EXCEL | e.g. Excel File for HT |
5. A transport request for workbench and customizing is displayed. Choose existing requests or create new requests.
3.3.2 Creating the Source System in the Administrator Workbench
Procedure
1. From the SAP Menu in the BW system, choose:
| SAP BW Role Menu | Creating the Source System in the Administrator Workbench |
| Transaction code | RSA1 |
| SAP BW Menu | Modeling à Administrator Workbench: Modeling |
3. Choose Source Systems.
4. In the right-hand window mark Source Systems.
5. Choose the context menu (right mouse click).
6. Choose Create.
| Field name | User action and values |
| File System, Manual Meta Data, Data Using File... | X |
| Field name | User action and values |
| Logical source system | FILE |
| Source system name | File system |
9. Choose Back.
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- BW--- BW Connectivity(最佳实践适合BW3.5)
- BW--- BW Connectivity(最佳实践适合BW3.5)
- BW--- BW Connectivity(最佳实践适合BW3.5)
- BW--- BW Connectivity(最佳实践适合BW3.5)
- 【新书快讯】《ASP.NET 3.5最佳实践——使用Visual C#》上市！
- .NET 3.5 中WCF客户端代理性能改进以及最佳实践
- .net 3.5 c#构建动态类型最佳实践
- SAP BPC最佳实践-SAP BPC的OLAP引擎比较(MS OLAP&BW OLAP)
- .NET 3.5 中WCF客户端代理性能改进以及最佳实践
- SAP BPC最佳实践-SAP BPC的OLAP引擎比较(MS OLAP&BW OLAP)
- 【译】适合dba和开发者的mysql最佳实践
- ESX3.5硬盘扩容最佳实践方案
- Android和PHP开发最佳实践 适合PHP学习者的书籍
- JQuery最佳实践-精妙的自定义事件
- RESTful 最佳实践
- Cocos2d-x下Lua调用自定义C++类和函数的最佳实践
- java代码最佳实践
- 虚拟机最佳实践：单个 VM、临时存储和已上传磁盘
- 网页导航的最佳实践—北京高端网站制作
- Android最佳性能实践(二)——分析内存的使用情况