dswp -> edit --> Fetch SAP Components

[Former Member]

I'm customizing the Help Desk (Solution Manager 4.0) and the next step is : dswp -> edit --> Fetch SAP Components.

But I receive the error message : "RFC Error: User SXXXXXX has no RFC authorization for function group BC_SOLMAN".

Thank's in advanced

[Former Member]

Dear all,

I suggest that you try to change the credentials of the SAPOSS connection to the following:

User: OSS_RFC

Password: CPIC

I hope this helps.

Best regards,

Andreu

[Former Member]

Thanks Andreu,

My problem is solved after I replaced the S user IDs in RFCs with the OSS_RFC user.

-Anupom

[Former Member]

Hi

Please let me how you resolved this issue am i also facing the same error and checked all RFC to saposs and maintained the RFC by oss1 still getting the same error.

please help

thanks

Swetha

[Former Member]

Hi Fancesc

Were u able to find the solution to this problem?

[Former Member]

Hello,

We have the same problem in our Solution Manager 4.0 system.

We have tested the transactions described in the precedent message, all is set ok, and we still have the problem.

We have set the correspondance between the sol manager user and the S-user in transaction AISUSER. The user in Sol manager have the profiles IN CLIENT 000 and 001 : SAP_ALL, SAP_NEW, S_TRANS_RFC, S_USER_RFC, Z_TRANS_RFC.

Please help us in solve this problem.

Thank's in advance,

Cristina Geana

[DoloresCorrea]

Hi Cristina,

Firstly regenerate the SAP-OSS connection according to note 982045.

Run DSWP and menu Edit- Fetch SAP Components is triggering the run

of the report dswp_get_csn_components in SOLMAN system.

Run the report directly and if you get a logon screen for SAP system

O02, this means that connection SAPOSS is not working well bacause

this report connects to Oss system without any logon screen and download the complete Components list into your SM table DSWP_CSNCOMP and DSWPCSNCOMPTXT.

If you enter your S-user in O02 and you can not logon something is not correct w

ith the Suser you are using.

Check in transaction OSS1->Technical setting and the saprouter area

is empty. Also in SM59 you can choose SAPOSS connection and click in

Remote Logon, the connection must connect without asking you for the

user and password, please check note 766505.

Hope this helps,

Dolores

[Former Member]

Thank you for your answer.

Please verify which is note for regenerate SAP-OSS connection because i can't find the note 982045 in service.sap.

Thanks again,

Cristina Geana

Message was edited by:

Christina Geana

[DoloresCorrea]

Hello Cristina,

The note 982045 is good, however is being in Checking process just now so you can not see it. I enter t:i

Long text

Symptom

The connection test or the authorization check for the SAP-OSS

destination in transaction SM59 is not always successful.

Other terms

Reason and Prerequisites

The physical connection between the SAP Solution Manager system and the

OSS no longer corresponds to the technical settings of the destination,

for example because another internal SAPRouter was activated.

Solution

Regenerate the SAP-OSS destination. Do not maintain any manual changes

for the SAP-OSS destination in transaction SM59. Proceed as follows:

1. Use transaction SM59 to carry out the connection test for the SAPOSS

destination. If this test does not return any error, proceed with

step 4.

2. Call transaction OSS1, choose the menu option 'Parameter ->

Technical Settings', and maintain them as described in Note 33135.

3. When you save the entries, the system regenerates the SAPOSS

destination . As a result, errors should no longer occur for this

destination in the connection test in transaction SM59. If errors

still occur, check the entries.

4. Regeneration of the SAP-OSS destination in transaction DSWP, menu

option 'Settings -> Global Settings', tab page 'Connection to SAP':

Re-enter the user (S user for your customer number) and the password

and save your entries. When you save, the system regenerates the

SAP-OSS destination. The system uses the technical settings of the

SAP-OSS destination.

5. Carry out the connection test for the SAP-OSS destination in

transaction SM59 again.

6. If the connection test works, but the authorization check fails,

make sure the password is correct by logging on directly on the SAP

Support Portal. If there are no problems when you use the same

password, SAP has to unlock the user that was locked due to several

failed logon attempts in OSS and to replicate the password from the

SAP Support Portal to OSS, if necessary.

Best regards,

Dolores

[Former Member]

Dolores, thank you very much for your help.

Only today i had the time for this problem.

I've regenerated all the 3 rfc connections liked you told me and additionally I've applied for SAP passport in sap market place.

I finally have the SAP components in our system solution manager.

Thanks once again,

Cristina Geana

[adrian_welsh]

Dolores,

I have the same RFC authorisation error, I have recreated the rfc destinations as you suggest, checked the user assignment in aisuser, checked the connection settings and it all connects to oss ok, but when i run the function module i still get the following error;

RFC Error: User S0001453792 has no RFC authorization for function group BC_SOLMAN .

Message no. SOLAR009

Any ideas?

Thanks,

Ade

[former_member342758]

hi,

i'm trying to add new entrie for assign a S-user with trasax AISUSER, but without succès.

i have this message:

Partner 000123456(my suser) not found.

Partner 0001068365 not found - see longtext

Message no. AI_SC_EN093

Diagnosis

Partner number 0001068365 was not found in table AICONTACTS.

Procedure

Please check if you entered the correct number (S-User without S) or use the value help for this field. If the value help doesn't provide any data the report AI_SC_REFRESH_READ_ONLY_DATA has not been run yet. It should be scheduled daily with transaction SM_CONFIG_JOBS as job REFRESH_ADMIN_DATA_FROM_SUPPORT. However if you want to run this job successfully the user who created the job must be maintained in this table first. So you should ignore the warning for this purpose, maintain the partner for this user and continue maintaining this table after the job has fetched the contact data for the value help from SAP Support Portal successfully.

Even then it can happen, that you don't find the partner number in the value help. The reason for this may be, that the user doesn't have enough authorizations for some actions, since only users with certaine authorizations are downloaded from SAP Support Portal. So you also may ignore the warning in this case, as long as there is no typo in the partner number.

i have do all that, but i have usullay the same problem.

thanks for your help

Hassan

[Former Member]

Hi

Press "ENTER" after first time displaying "Partner 0001068365 not found - see longtext"

It will be save your S-user

Vadim

Edited by: Vadim N. Barchuk on Mar 11, 2008 1:33 PM

[Former Member]

???????????

Edited by: Sandeep Gadwe on Mar 19, 2008 2:23 PM

[Former Member]

You need to generate some RFC connection for OSS

SAP Solution Manager IMplementation guide >SAP Solution Manager>Basic Settings

>SAP Solution Manager System>Connection to system

Execute the following

* Maintain User for Communication with SAP Service and Support

• Check New Connections to SAP

then goto Tx DSWP >Edit> Global Settings -->

Maintain the required details

Hope it helps you,

Prakash,

-

---

Rewards if helps

Message was edited by: Prakash N