cancel
Showing results for 
Search instead for 
Did you mean: 

Certification not allowing start at an operation

0 Kudos
345

I added a certification, assigned it to an operation and confirmed that the test user cannot start an SFC.

Then I added the cert to this user in User Certification Maintenance. Back in the POD, I still get the message "User 119274 not certified to perform the operation L_ETCH (Message 13039)". I remove the cert from the operation and tried again and it allows a start, so I know the mapping to the operation is correct.

What am I missing?

Accepted Solutions (0)

Answers (2)

Answers (2)

fishehead
Explorer

Hi Barry,

I suppose you may forget to save the configuration when you maintain in User Certification Maintenance.

You can verify it by retrieving the user in that page again after you maintain it.

BR,
Teson

0 Kudos

Yes, I've tried that many times, as well as looking at the record in the database.

sergiy_katerinich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Barry,

Certification should work in accordance with SAP Note 1618564.

Regards,

Sergiy

0 Kudos

Sergiy,

That note deals with a slightly different issue from what I'm experiencing. If I add the cert to the operation, there seems to be nothing I can do to allow a given operator to start an sfc at that operation. I've tried every combination of user group assignments in Cert Maintenance and adding/removing the cert from user maintenance.

I'll schedule an ask an expert session.

Thanks,

Barry

sergiy_katerinich
Product and Topic Expert
Product and Topic Expert
0 Kudos

The "Cause" section of the Note describes how it should work. So, there could be 2 cases: with User Group assignment and without User Group assignment. Both should work correctly. If either does not, then it is likely a bug.

0 Kudos

For some reason, this is now working as expected, without any changes to configuration, upgrades, restarts, etc.

sergiy_katerinich
Product and Topic Expert
Product and Topic Expert
0 Kudos

In case of sudden recovery, it might be a cache issue. Cache can be flushed by means of Notification webservice or by ME restart. Just in case you face it again.