How to debug Adobe form attached to Web Dynpro for ABAP

[Former Member]

Hi,

My developer has created an adobe form and rendered inside a Web Dynpro page in the SAP Portal. It communicates with the Web Dynpro framework in the backend SAP system (Web Dynpro for ABAP).

My question is, how would I know what infotype access this form requires, in the form of backend authorization role? Is there any way (not trace, ST01) to debug Abobe form on Portal or in backend SAP system?

Thanks,

Karan.

[WolfgangJanzen]

Debugging is more cumbersome and time-consuming that tracing.

I don't get the point of your inquiry ...

[Former Member]

Hi Wolfgang

During trace ST01, form process on Portal needs read access authorization for * infotype for P_ORGIN authorization object.

Adove form, which is rendered inside a Web Dynpro for ABAP, is specifically looking for a value * for infotype field. And so, I would like to debug the form on SAP side.

Thanks,

[Former Member]

Hello Karan,

I am not sure whether this will work in this case, but principally if your trace is recording a * value for a field in an authorization check, then it must be defined somewhere, and there is an option in the trace file to jump from the check to the source code location where it occurred.

You cannot do that for all traced checks, but it might be worth a try?

Cheers,

Julius

[WolfgangJanzen]

> I am not sure whether this will work in this case, but principally if your trace is recording a * value for a field in an authorization check, then it must be defined somewhere, and there is an option in the trace file to jump from the check to the source code location where it occurred.

Yes, that's possible since the trace also records the information on the ABAP source code location where the AUTHORITY-CHECK statement (or other ABAP statements which internally trigger authorization checks) is executed. If I'm not wrong then there is a button (in ST05) which allows a direct source code navigation. Alternatively you might just click on the ABAP source code information displayed in the ST05 trace results (for recorded authorization checks).

Cheers, Wolfgang

[WolfgangJanzen]

> During trace ST01, form process on Portal needs read access authorization for * infotype for P_ORGIN authorization object.

Well, that looks like a bad style (potentially indicating a common misunderstanding: requesting * when performing an AUTHORITY-CHECK is not identical to requesting "any value"; demanding "any value" is expressed by the "DUMMY" construct - see ABAP online help for the AUTHORITY-CHECK statement). Requesting a * value does not really make sense since this forces the administrator to assign extremely powerful authorizations to all users which are supposed to be able to use that functionality.