Repeated Login Prompts in PR05

[Lukas_Weigelt]

Hi,

for about one week, we have a strange occurence ( and unfortunately nobody can explain what could have led to it.. ).

Note: I reference Screenshots in the following text, I can't upload them at the moment for some reason. I will do so later when I have access to a more useful browser...

Edit: I inserted the screenhots.

System Information:

ECC 6.0 EHP 4, SP Level 46

Additional Information:

Public Sector, Germany

Problem:

On our DEV System ( only System where TRV is present by now, we haven't transported to QAS yet ) on our Client A, within the Transaction PR05; whenever

an action is taken...

...concerning a dedicated trip ( i.e. create new trip, show trip, change trip, simulate, etc. ) a login prompt for the DEV system is popping up:

It doesn't matter whether there is Login-Information entered into the prompt or whether it's just cancelled...

...the Program normally continues and processes as usual.

This is happening ONLY on our Client A ( Test-Client on DEV ) but not on Client B ( Customizing/Dedicated Development-Client ). Since this behaviour seems just totally 'nuts' to me I made a trace with ST01 on both Clients for the following Steps: Call PR05, Select a trip, Click show. The trace logs, however, are near to identical, only some SQL queries and buffers are not completely congruent. The AUTH and RFC statements, however, are completely identical, this means the Login Prompt Call isn't being recorded at all.

This is where I am completely lost. I don't know where to start analyzing, or whether it's even something I can analyze (could there be a Basis problem? If yes, why does this only happen in TA PR05?). ST01 is kind of my "last resort" when I don't know what to do and it didn't help me in this case.. I didn't find anything similar via Forum Search, Google or in SAPxSearch which really makes me feel uneasy 😕

If somebody has an idea what might cause this or where I could possibly analyze this deeper, it will be very very welcomed.

Best regards,

Lukas

Message was edited by: Lukas Weigelt

[Former Member · Accepted solution]

There is a authorization badi for check PERNR. Maybe this could cause this. But as you have debugged it I guess no.

Than this is Basis issues of the set up of the system. I had this once but not by opening P05. After showing this issues to a basis administrator the issue got solved.

Should definitely not come up from Travel development. If this will not help raise an OSS message. Maybe in parallel to get it fixed fast.

[Lukas_Weigelt · Accepted solution]

Solved. A logical system had been misconfigured in Basis, that's why an RFC check tried to get information from Client B instead of A, causing the Login prompt.

Cheers, Lukas