Sap Guixt

 

GuiXT scripts in SAP Web Repository

GuiXT scripts, images (gif, jpg) and InputScripts can be stored in:

• local files, i.e. under C:\GuiXT\Scripts
• central fileservers, i.e.  \\p00145\GuiXT\Scripts
• http-servers, i.e. http://www.synactive.com/demo.d.45
• ftp-servers, i.e. ftp://synactive.com/demo.d.45
• SAP Web Repository (R/3 database), i.e. sapwr:z.guixt.demo

Each of these solutions offers specific advantages and drawbacks:

• local files are best used during development and for small user groups
• central fileservers offer easier administration without increasing the load on the R/3 database
• http and ftp servers are a good choice when using several local networks
• the SAP Web Repository offers a centralized administration with connection to the R/3 transport and correction system. The built-in cache mechanism of GuiXT will keep the  database and network load to a minimum  as each object will  be loaded only once per SAP session.

The name should start with the letter Z, as customer specific objects start with Z in the SAP Web Repository.

Example: sapwr:z.guixtobjects

Specification in a script
If you specify an image or an InputScript without indicating the path, it will automatically be searched for at the same place as where the script is located, in this case the Web Repository. You can also directly specify  the Web Repository, i.e.:

Image   … “SAPWR:Z.Images.logo.gif”

This notation is also possible in local scripts.

Optional specification of a different SAP system
If you want to access another SAP system, you can use the option dest=xxx to specify the identification of the selected system.

Example: sapwr,dest=S46:z.guixtobjects

In this case the access will be as specified in the file saprfc.ini (usually located in SAP workdirectory). Please refer to SAP documentation about Remote Function Call for additional details.

For the transport of objects between several R/3 systems (development/test/production) you need a development class which can be created with transaction SE80.

Transaction SE80 (create development class)

The name comprises the identification you previously specified in the GuiXT profile, i.e.: Z.GUIXT, a dot (.) and  the usual file name including the extension .txt, .gif,…

Examples:

Z.GUIXT.ELOGON.TXT
Z.GUIXT.SAPMF05A.E0100.TXT
Z.GUIXT.FB01BUCHUNG.TXT
Z.GUIXT.LOGO.GIF

Please note the following:

• select “binary data” in the initial screen of transaction SMW0
• do not modify type “binary” during download of files
• a meaningful title saves you time in later searches

Transaction SMW0 (SAP Web Repository)

Choose binary data and start overview

You can specify the name by using the generic format

You can copy and create objects from the list

xt/en/source/images/sapwr.smw0.4.gif" width="436" height="118">  

Make sure the object name is correct and that you choose a meaningful title.

You may need to assign a MIME type for the object (Settings, Maintain MIME types) 

Specify a development class or click on “Local object” in the case of a local object for tests

Release function WWW_GET_MIME_OBJECT
Depending on your R/3 version is might also be necessary to release the function  WWW_GET_MIME_OBJECT with transaction SMW0. GuiXT uses this function for  Web Repository access.

Choose  Internet release->Function modules(F7) . You can now display a list of all released functions:

If  WWW_GET_MIME_OBJECT is not yet contained in this click, then enter the name WW_GET_MIME_OBJECT und click on  the “Release” button.