An analysis reveals that your Business Automation Enabler (BAE) connection is not working, but the SAP Solution Manager integration is based on the BAE API.
Solution:
Please follow the steps described in SAP note 1265635
to setup the BAE connection between SAP CPS and SAP Solution Manager. This description is valid for SAP CPS releases lower than M33.
You don't have to create any RFC destination to SAP CPS in the Solution Manager system, because SAP CPS creates the destination automatically if the parameter SAP_EableRfcDestination is set to True.
The XBP communication user in SAP Solution Manager also needs the role
SAP_BC_REDWOOD_COMMUNICATION (if not already assigned).
If everything is correctly setup the tests of transaction EXTSDL should not longer
lead to error messages.
Typical errors are:
This is a configuration issue. The relevant Implementation Guide (IMG) activities are:
If the field Business Partner in the Job Request header area is empty your SAP user is not assigned to a Business Partner.
Solution:
If the value help for systems in the Job Request is empty your business partner is not assigned to any managed system.
The value help for systems get its data from the tab "Indentification"
of role "General". You use the External System Identifier (technical key CRM001) to assign (users in) managed systems to key users in SAP Solution Manager.
Solution: Follow the descriptions in IMG activity "Create key User".
In "ASCII art":
Role Employee External System Identifier
User ------------------------ BP ---------------------------------------- Managed
Systems
1:1 1:n
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
24 | |
14 | |
12 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 |