cancel
Showing results for 
Search instead for 
Did you mean: 

IW32 System Status (Sys. Status) Field Empty for Certain User in Personas

awguthrie
Participant
0 Kudos

Greetings,

I am working on a flavor in IW32 and noticed an odd problem with the built-in Sys. Status field. The script checks the text content of this field to make some decisions. I noticed that under my account this works fine, however, under our test account it's not working. This leads me to believe it must be an access/role issue, but I'm not sure what to look for and would appreciate if you can point me in the right direction.

The Sys. Status field is visible on the flavor screen by both users and shows the same status values as usual. However, I put some alert and logging on the script (onAfterRefresh) to print the field contents, and for the test account it always shows an empty value.

For example, testing from my account it printed:
"TECO CSER NMAT PRC SETC"

From the test account, it printed:
""
But when viewing the standard screen/flavor from the test account, the status field shows up fine (screenshot attached).

Version 3.09 Patch 501

Accepted Solutions (0)

Answers (2)

Answers (2)

bwills
Contributor
0 Kudos

Hi Anthony,

If you run the SU53 transaction perhaps it will show if there are authorization issues for the test user.

Thanks,

Brian

awguthrie
Participant
0 Kudos

Although we worked around the issue with an FM, I'm wondering if this is related to another issue...

Why would a flavor look different for two different users? On my development account the flavor looks a certain way, but then on another test account, there's fields that are showing that should be hidden and the spacing is off (gaps that don't exist on my user).

bwills
Contributor
0 Kudos

I still think it's an authorization issue. Maybe temporarily give the test user id the same authorizations as your user id. Then log in with the test user id to see if it works like yours. Let us know how that works out.

Brian

cris_hansen
Advisor
Advisor
0 Kudos

Hi Anthony,

There is no screenshot attached.

If this is happening for only a few set of users, then you should compare their authorizations, their default settings and see whether there is a discrepancy there.

Another suggestion would be debugging your script with the test account, printing more information in the log and see whether you can find why it failed.

Regards,

Cris

awguthrie
Participant
0 Kudos

Thanks both for the suggestions. We started down the authorizations path but ended up getting the status data from an FM for expediency. So still not sure what caused it exactly.