cancel
Showing results for 
Search instead for 
Did you mean: 

No User Mapping for SAP system user when delivering reports.

avishek_gorai2
Participant
0 Kudos

Hi,

We are getting an error 'No User Mapping for SAP system user XXXX' when delivering reports or user subscription for WF. I came across a [thread|; where the solution given was to create a user mapping using the BAdI 'Simple bulk user mapping' in SIMGH. However we have diffrent user name schemes in SharePoint and SAP and hence we have used "SharePoint Integration bulk user mapping' from a CSV file. The user mapping entries can also be seen in the view VUSREXTID. Inspite of this we are getting the above error when SCL is trying to deliver reports or when we try to authorize uses from SharePoint for Workflows.

Please suggest a solution.

Regards,

Avishek.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

can you see Report templates or any other SAP data from SharePoint? If so, this maybe still a problem with the mapping. Can you open the table USREXTID (via SE16) and display the details of one user who is not working? Do you see the filed ISSUERH filled?

If this is empty, then the Single Sign On from SharePoin to SAP will work (that is why you would see for example Report templates or a list of Customres), but you would not be able to use Workflow (or Reporting).

There might be a problem with the CSV approach (as a matter of fact due to possible security concerns we are not recommending this approach anymore). So if the ISSUERH field is empty, let us know and we will try to think of something

Holger.

Answers (1)

Answers (1)

avishek_gorai2
Participant
0 Kudos

The issue has been resolved.

The problem as pointed by Holger was related to the ISSUERH field, which as we learnt creates a hash based on the entry of the field 'Issuer Certificate' string maintained in SIMGH->SCL Administration-> Connection Settings->SCL to Consumer->Define customer issuer certificate. This is what was maintained incorrectly and hence the value of the field of ISSUERH of user mapping table. Changing this value and re-doing the user mapping resolved the issue.