The original symptom that drove this issue and SCN discussion:
We have SolMan integrated with SAP CPS.
We are trying to setup the SAP standard functionality that generates a SolMan Job Documentation link in an instance of a job in SAP CPS. We found that while this worked for ADMINISTRATORS for other users the link was generated back to SolMan with a "0" ID and so was not working.
We checked the logs and found an error saying we didn't have the action "AccessSchedulerBusiness". We didn't know for sure if this was the cause but we couldn't see any other issues, so we tried adding it.
The effect of the action - adding AccessSchedulerBusiness action:
We added this action to the 1 test user in DEV - et voila - it worked. The Job Doc URL link generation in CPS worked. Super
The Problem that arose:
Once we rolled this out to all users they all, immediately, began to get the error message as follows:
![AccessSchedulerBusiness__Action__related__issues_001.png]()
So that is obviously a problem
- no one could login. So obviously we rolled this change out again.
The summary
So the problem here is a conflict around the AccessSchedulerBusiness action (which we added to all our roles, which previously ONLY had action AccessScheduler in the NetWeaver UME). Adding this Action fixes the Job Doc URL link generation issue..... but breaks user login to the system.
My normal route would be to dig to the detail level here.... but there is not much documentation for this Action that I can find. And there are no clear associated CPS level Security Privileges that I can seem to link back to it. Does anyone know anything about it?
A good fix would be either to work out a more granular & specific way of fixing the Job Doc URL generation issue.... or to stop the login issue - perhaps by changing our license? But I cannot see any logical link to our license in this error....
The Additional consideration...
An interesting additional consideration, not 100% tested yet, is that it seemed that local UME users could still login. This meant our community could not as they are LDAP users... however our few TEST local UME users (with the Action) seemed to be OK.
Any input and involvement in this discussion is very welcome! I will post updates on resolution to help the community