Taxes and TemSe
Recently while supporting my current client, I was tasked with solving a rather puzzling issue an end user was experiencing. While using T-Code PU19, the user would receive:
Command Line Driven Transporting Using the ‘tp’ Command
STMS is a very powerful transaction in the BASIS world. The whole transport system in SAP is paramount to it’s functionality. 99% of the time, you will use STMS for your transport needs. What of that last 1%? Sometimes it becomes more efficient, or just safer, to have a little more manual control.
Excel Returns Blank Workbooks in SAPGUI
Don’t you hate it when you’re trying to view a report as a spreadsheet in SAPGui and it returns a blank workbook? The problem could be due a security settings inside of Excel that is preventing the data from being displayed. It is real easy to fix. Use the following instructions for your version Microsoft Office.
“Transporting” scheduled jobs
‘Transport’ is a touch misleading. In this example, we aren’t using STMS to move a job from one AS/CI to another, but we aren’t recreating it from scratch either.
Scenario:
Our SAP servers are running on HP-UX hosts with Oracle 10g databases. Recently, the client underwent SPS application to production servers. The process called for the stopping of scheduled jobs during update. The jobs were to be restarted as directed by team leads. When a request to restart job was executed, it was unable to be completed because the required job had “disappeared”. The job in this scenario was over 100 steps with different programs and variants being executed. Due to time constraints and the possibility of incorrect data entry, manually recreating the job in SM36 was not an option.
It is possible to extract a job definition directly out of the tables in which it is stored and then reinsert it into another instance (i.e. copy the job definition from your Q box and drop it back in Production). For demonstration purposes we will call our source server Q01 and our destination server P01. The job used in this example will be OUR_LOST_JOB.
NOTE: The steps used in this tip may utilize commands that access and modify data in ways not explicitly endorsed by SAP. Therefore, the use of this tip should be done at your own risk.
Issues with GuiXT and the SAP GUI
GuiXT is a scripting environment that allows for the creation of huge macros in the SAP GUI environment. The HP testing product LoadRunner uses GuiXT to generate user load for system stability testing purposes. This document is designed to show you how to install the GuiXT plug-in if it isn’t already, and how to fix some errors that are less than descriptive.
GuiXT is a SAPGUI plug-in that is selected during the launch pad install. If you don’t select it during the initial install, you can run the installer again and select only GuiXT.
If everything is working correctly when you open a GUI session, you will see “Activate GuiXT” under the “Customize Local Layout” menu.
WARNING: Neither the author of this article nor DataXstream can be held responsible if the reader breaks the registry while making this correction. Whenever working inside the registry, it is good practice to take a full back-up before continuing. Also break up any keys before directly editing them.
To open the registry editor click ‘Start’->’Run’ and enter regedit.
The registry editor window appears:
To take a full back-up of the registry, click ‘File’->’Export’ while ‘My Computer’ is highlighted:
Save the file somewhere you won’t forget and with a name you will easily recognize:
With the full backup, we can now feel safe as we make our changes. Drill down through the tree starting with HKEY_CURRENT_USER\Software\SAP\SAGUI Front\SAP Frontend \Server\Adminstration. Look for a key titled DisappearItems. If it exists, export by following the previous steps with just that key highlighted, then delete the key.
The option ‘Activate GuiXT’ should now be available in the Customize layout menu.
Another issue that I’ve seen with GuiXT in regards to LoadRunner is LR not being able to find the GuiXT Dynamic Link Library (.dll) when excuting a test script. The fix is easy; Copy ‘guixt.dll’ from the directory path C:\Program Files\SAP\FrontEnd\SAPgui\ to C:\WINDOWS\system32\.
These fixes assume that you have administrative access to your computer. If you do not, please contact your IT/Help Desk department to either gain admin rights or have a tech follow these steps for you.
