Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Problem accessing IQS2 transaction. error shows S_DOKU_AUT with dummy val

Former Member

‎05-08-2009 9:16 AM

0 Kudos

Hello All,

when a user is trying to change some notification type using transaction IQS2,he gets an authorization error.

the SU53 taken soon after the error encountered shows the following auth obj missing with Dummy values.

S_DOKU_AUT SE61 Documentation Maintenance Authorization

DOKU_ACT Editing status <Dummy>

DOKU_DEVCL Package for which docu. auth. has been assigned <Dummy>

OKU_MODE Authorization to maintain, translate <Dummy>

Auth obj does not show up any values against above fiels, they are all dummy.

Can someone please help.

Note: Auth obj S_DOKU_AUT has the Status as CHECK in SU24 for IQS2.

4 REPLIES 4

Former Member

‎05-08-2009 12:20 PM

0 Kudos

Hi,

Mention the filed values as ' ' for dummy.

When there are no values passed to the program or sap can't determine the exact authorization, it shows as dummy.

Regards,

Gowrinadh

Former Member
In response to Former Member

‎05-08-2009 2:41 PM

0 Kudos

> When there are no values passed to the program or sap can't determine the exact authorization, it shows as dummy.

Actually, it does not just show as DUMMY: it checks the field ID as DUMMY in the program, as it cannot yet know which document the user is going to request so should not proceed to the field value itself in the check.

Go to transaction ABAPDOCU and click on the yellow ? icon. Then type DUMMY into the "Keyword" field and hit enter. It is an ABAP program language element.

Cheers,

Julius

Former Member
In response to Former Member

‎05-08-2009 2:50 PM

0 Kudos

Hi,

This tip is very helpful. thanks.

Regards,

Gowrinadh

Former Member

‎05-08-2009 2:37 PM

0 Kudos

Probably an misleading SU53 result, as this is the last failed check and the "real one" happened before this check.

This would also explain the DUMMY checks, as the user is not able to select the document, so there is no value for the system to check when it returns to the screen after throwing the error. Most likely it is checking S_DOKU_AUT when returning to the initial screen.

Just my guess at an explanation for this. Run a ST01 trace on the transaction to see what is missing and what is checked immediately prior to this object.

Cheers,

Julius