A logon to the OSS using Transaction OSS1 is not possible if the R/3 System is not running. However, a logon to OSS is often a very important factor in dealing with problems with R/3.
SolutionTransaction  OSS1 offers the option to display the parameters used when  calling up  the SAPGUI under Parameters -> Technical settings -> Parameters  -> PC Callup parameters
These parameters are strongly dependent on  the SAP routers defined, both  from the customer's point of view and  that of SAP. For this reason, no  general value can be entered here,  Transaction OSS1 will determine these parameters at runtime.
This  parameter string can then be copied to the command line of a new  SAPGUI  icon. You then can log on by simply starting the OSS with this icon,  without using R/3.
However, the installation of this special  SAPGUI icon is only necessary  on a few PCs and use should be limited to  emergencies as the most favorable OSS application server is not  determined, rather the  application server predefined in the parameter  string.
For interested experts: -----------------------The  parameter string supplied by Transaction OSS1 consists of blocks  with  the following structure:
/H/
You  can put as many of these block together as you like, each of which   describes one computer on the path from the SAPGUI to OSS.
As  
An example:
On  the computer 'Customer1' (IP address w.x.y.z), a SAP router runs  under  default Service '99'. The link to SAP is via the SAP router on   sapserv3 (IP address 147.204.2.5), Service '99' to the OSS on oss001  with instance number '01'.
The parameter string would then have the following layout:
/H/w.x.y.z/S/sapdp99/H/147.204.2.5/S/sapdp99/H/oss001/S/sapdp01
<------- 1 --------><---------- 2 ----------><------- 3 ------->
- 1. Computer 'Customer1' with SAP router on Service '99'
- 2. Sapserv3 for SAP with SAP router on Service '99'
- 3. Online Service System on 'oss001', Service '01'.
Note: You cannot use the above example as a parameter string.
No comments:
Post a Comment