Conflicts with Service File Settings
A special situation occurs when the login information specified for a service to be started conflicts with the login information already stored in a login context.
For example, a user may have logged on to service A with his/her username U1. ITS will therefore create a login context that is shared among all services. When a service B is requested, and B’s service file does not contain login parameters ( ~Login and ~Password ), the shared login context is used to establish the connection to the R/3 system. The user need not log on again.
However, if a service C is called and C does contain a login parameter with the value U2, this would constitute a conflict with the existing login context. In this case, ITS sends a new login page that the user will have to populate in order to log on to R/3.