Drop Down is not Visible

[Former Member]

Hi All,

We have encountered an issue after Upgrade.  We have an BSP application in out portal(7.0). Through that HR persons are handling their activity.

We have upgraded ECC to EHP7 SP4 and UAT is going on. In UAT user is facing the issue.

One HR Manager is synching his id with another user id and then going to the Proxy link to change the employee information for the another user as a proxy manager. Here The user is not able see the drop down to select and Action item to complete  job.

User is able to do the same in production. We have checked user's role and Structural profiles in both UAT and production environment and Both are same.

Can anybody please suggest what is the issue?

[mvoros]

Hi,

is it a custom BSP app? It's really hard to say what is causing this issue. If it's a custom app then the logic might not be using only authorizations to determine what is visible to user. Have you traced it in ST01?

Cheers

[Former Member]

Rakesh Navandar wrote:
 One HR Manager is synching his id with another user id and then going to the Proxy link to change the employee information for the another user as a proxy manager. Here The user is not able see the drop down to select and Action item to complete  job.

The likelihood of the problem being in this part of the coding block and exchanges is very high.

You must consider that "drop downs" are also implemented from remote enabled search helps, and some user in some foreign system might now be subject to a new application authorization to display vendors etc which was not there before.

On EHP7 you can also use SU53 for non-SAPGui applications and get more results back than just the latest check. So run the errors, and then on the backend system check the trace and the Su53 for the connection user whether it can return the data.

Theory B is that the backend table of the dropdown has more records than what a dropdown supports, so a search help is needed but there is no search help passed to the BSP field.

Both are equally likely and cover 90% of EhP7 problems with such fields with remote search helps from the perspective of authorization problems which are "blamed" for the problem.

Cheers,

Julius

[Former Member]

Hi Julius,

We have run the trace in both production and UAT environment. Please find the Attached Trace result which is same for both environment.However, it is working in production nonupgraded system but not working UAT upgraded system.

[Former Member]

Then it is possibly a coding error which reacts to that rc=4 incorrectly in EHP7. PSIGN=* should have no meaning as it can either be I or E.

'*' should be ignored.

If both trace results are the same, then the coding in the function module must have changed in how it reacts to it, or the calling BSP (looks like it is coming in with a logon ticket from a portal) has implications on the BSP side that dropdowns are not supported anymore in the way it has been coded. Eg. the search help has changed or the structure for the output has changed.

I tip on incompatibility with your BSP. SAP made a few changes to this FM recently...

Is there no BAPI for this?

What we do here is that we classify data objects and have a list of APIs for them. Then we scan our code to check that the call stack comes from the stables APIs and not some FMs which happen to be remote enabled. Same for correct use of methods which contain correct validations and checks - particularly if the data model changes.

You could try to open a customer message with SAP and tell them which FM you are calling, but 90% sure they will say it is not supported and 99,9% sure they will say that your BSP code is the problem.

Try it and let us know (if you did not do that already).

Cheers,

Julius