Guixt issue

[Former Member]

Hello all,

We are experiencing the following problem with Guixt:

Some transactions such like VA02, vA42,.. are "enhanced" using Guixt.

When the scripts are tested by our developers, no problem occur. The

scripts are read from the Sap Web Repository and are running well.

When these scripts are used more intensively by end-users, from time

to time, the scripts are not excuted anymore leaving the standard Sap

screen. The end-user has then to leave his sap sessions, sometimes a

reboot is necessary.

Does anybody have an idea of what is going wrong ?

Here are some version informations:

Sap ECC6

Sapgui 620 (Patch level 77)

Guixt 2009 Q3 3

Windows Xp

[Former Member]

I hope you have assigned the GuiXT script in somoe transaction variant. So have you made any Z transaction code with this transaction variant or directly accessing the standard tcode?

If possible please create a Z transaction code with that transaction variant and check.

Regards

Shiba Prasad Dutta

[Former Member]

Thank you for your fast answer.

Our Guixt scripts are only used to modify the display of screens (i.e hidding or protecting fields, add push-buttons,..) and

they are working when standard report are executed. So we don't use transaction variant

Please note that scripts are running very well in a test phase. The problem occurs sporadically during the day-to-day work of some end-users.

Best regards

Philippe Grégoire

[Former Member]

I think it is better to use GuiXT in transaction variant.

But as you told it is not assigned in any transaction variant.

Then Please ensure that the Activate GuiXT is ticked for the end user log in and hope they are not changing it manually.

Apart from that when end users are logging in the sap logon then GuiXT is staring in Hidden mode or minimized mode?

Please ensure that it should be in hidden mode for the end user else they can close the GuiXT script editor window.

Regards

Shiba Prasad Dutta

[Former Member]

Shiba Prasad Dutta,

Here is the typical Guixt profile (guixt.ini) delivered to all end-user:

//----

-

---

/

// PROFILE GUIXT /

//----

-

---

/

IgnoreRegistry Yes

//----

-

---

Directories

Directory1 sapwr:zgxt

Directory2

Directory3

Directory4

History

InputSets

Docu

Domains

Directory0

UserCatalog

//----

-

---

File cache

Replication Yes

//----

-

---

Installed components

Component GuiXT

//----

-

---

Icon ID

Icon_Tip_Field OL

Icon_Tip_Box 35

//----

-

---

System trace

Trace No

//----

-

---

History

HistoryUpdate No

HistoryOnRightButton No

HistoryOnMiddleButton No

//----

-

---

Start Window

StartMinimized No

StartHidden Yes

//----

-

---

User Option

//----

-

---

Rfc User

RfcUser RfcUser

RfcPasswordEnc RfcPasswordEnc

The Guixt is actived by default and the registry key DisappearItems with Activate GuiXT prevent the end-user to change it manually.

Best regards

Philippe Grégoire

[Former Member]

Hi

The scripts will be read from bottom to top. So mention the script location in Directory 4.

Regards

Manish Bansal

[Former Member]

Are you using any role based scripts in your GUIxt screens?

If yes, then check that RFC user ID is not locked by BASIS.

Regards

Manish Bansal

[Former Member]

Hi,

I had not tested it yet...

Thank you.

Regards,

Philippe Grégoire

[Former Member]

Hi,

SInce the problem occurs for some end-users, not for all,

the rfc user is not locked.

Regards,

Philippe Grégoire

[Former Member]

Hello Friends,

I'm new to using guiXT. I could successfully hide some of the fields in ME23 transaction. However, what i dont know is, how we implement this to a user group. When I test the changes I have to check/uncheck the 'Activate GuiXT' and keep the window open in order that the changes are working each time when I go out and into the transaction. I would appreciate any help on this.

Thanks,

AS

[Former Member]

Pl check www. synactive.com

Manish