on 10-23-2013 6:17 PM
Hi Gurus,
I have made some changes to screen using GUIXT and they are visible for all clients (Servers for Client , A Client B... ).
This should not happen..
Is there any way to restrict changes to particular server of a client only..
Please suggest. Also let me know disadvantages of using GUIXT.
Regards,
Sachin
Hi Sachin,
I work in such cases as follows:
if V[_user=Adak]
//Here follow the GuiXT commands.
endif
The disadvantages of using GUIXT are the same in about how the disadvantages of using SAP Screen Personas. 😉
Regards,
ScriptMan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sachin,
then there are other system variables that you could use.
for example: http://www.synactive.de/docu_e/doc_systemvariables.html
Regards,
ScriptMan
Hi Sachin
Kindly refer the SAP Note 338750 - GuiXT: Delete "Activate GuiXT" option from SAP GUI
Regards
Sriram
Hi Sachin,
Please see the following link: http://www.synactive.de/docu_e/doc_profile_options.html
On the server where the user will not see the window screen element, is in the path c: \ program files (x86) \ sap \ frontend \ sapgui \ an INI file called guixt.ini. There is the parameter StartHidden No, that prevents the display.
Regards,
ScriptMan
Hi Sachin,
Sorry:
StartHidden No => display
StartHidden Yes => no display
Our guixt.ini looks for example as follows.
//------------------------------------------------------------------------------------------------------
// GuiXT profile parameters
//
// - Set Profile parameters via Edit->Profile in GuiXT for single installations
// - Use .ini file for general rollout
//
//-------------------------------------------------------------------------------------------------------
IgnoreRegistry Yes // Ignore local GUiXT profile
//-------------------------------------------------------------------------------------------------------
Component GuiXT // Component selection: GuiXT
Component InputAssistant // Component selection: InputAssistant
// Component Viewer // Component selection: Viewer
// Component Designer // Component selection: Designer
//-------------------------------------------------------------------------------------------------------
Directory1 k:\guixt\scripts // Script Directory 1
// Directory2 directory // Script Directory 2
// Directory3 directory // Script Directory 3
// Directory4 directory // Script Directory 4
//------------------------------------------------------------------------------------------------------
StartMinimized Yes // Start with a minimized window
StartHidden Yes // Start with a hidden window
//------------------------------------------------------------------------------------------------------
History z:\history // InputAssistant: History Directory
HistoryUpdate Yes // InputAssistant: History Update active
Domains k:\guixt\domains // InputAssistant: Local value help
HistoryOnRightButton Yes // InputAssistant: History on right mouse button
HistoryOnMiddleButton Yes // InputAssistant: History on middle mouse button
//------------------------------------------------------------------------------------------------------
// Icon_tip_field xx // R/3 icon id for field tips, default: 0L
// Icon_tip_box xx // R/3 icon id for field group tips, default: 35
//------------------------------------------------------------------------------------------------------
// Option xxx1 // User Option (see "if Q[Option=xxx]")
// Option xxx2 // "
// Option xxx3 // "
//------------------------------------------------------------------------------------------------------
// Replication Yes/No // File replication active
// Directory0 directory // Directory for replicated files
Key xyz.123.abcdef // Licence key, not required for component GuiXT on R/3 Rel. 4.0
// Testkey xxxxxxxx // Test licence key
// Trace Yes/No // Internal tracing active (only for error analysis)
// Docu directory // GuiXT Documentation
// Linksapurl Yes/No // Viewer: Support SAP-Url in normal html display
RfcUser RFCUSER
RfcPasswordEnc APBINKNROKFJIHBQORIOKVCLLQCKATILEGHVPIAPDKKJIMMB // Password for RFC calls
//------------------------------------------------------------------------------------------------------
// FileAccessTimeout x // Maximum x seconds for ftp://, http:// or external file server access
//------------------------------------------------------------------------------------------------------
Texteditor GuiXTEditor
Regards,
ScriptMan
hi
F4 search help is working fine but when i double click the value that the value was triggered correctly bt it skip to next screen ???? how to solve this issue kindly help
Regards,
SathiyaPriya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
I have some queries in guix??? Is this possible to avoid enter functionality while in search help?????
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Priya,
You can try this. Generate a GuiXT Script for the Search Help window. Inside that, use the following code:
////////////
on "enter" process="do_nothing.txt"
///////////
Create an input script, named "do_nothing.txt" and use the following line of code:
/////////
return
////////
Word of caution: Please be careful while deploying the scripts, as Search Help is a common window used in multiple context.
Let me know if this works OR if you have more queries.
Best,
Vishal
Hi Eric,
The Documentation link provided by you is Broken.
Regards,
Sachin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.