Technical Background - Connection Strings
Connection String is a technical term used within SAPGUI for the Java Environment configuration. A connection string describes a connection address for a destination, e.g. an SAP system's application server, rather like an Internet URL describes a location for a web page.
Simple Connection Strings
In its simplest form, a connection string contains an IP address and a port number. These informations are sufficient for SAPGUI for the Java Environmant to open a direct TCP connection to a destination, e.g. an application server. IP address and port number are marked with the prefixes '/H/' (for host) and '/S/' (for service). Note that the portnumber for an SAP application server is by convention 3200 plus the two-digit SAP system number.
Example for a simple connection string with an application server's IP address (172.16.64.17) and portnumber (3200):
/H/172.16.64.17/S/3200
If your network environment supports DNS (Domain Name Services), a hostname can be used instead of the IP address in all kinds of connection strings. (This requires a correct DNS configuration at the frontend computer, e.g. via the /etc/hosts file).
Example with an application server's hostname (iwdf8997.wdf.sap-ag.de) and portnumber (3200):
/H/iwdf8997.wdf.sap-ag.de/S/3200
If your network environment supports symbolic service names for well-known ports, the symbolic service name can be used instead of the port number in all kinds of connection strings. (This requires a correct service configuration at the frontend computer, e.g. in the /etc/services file). Note that SAP application server ports are by convention named 'sapdp<SID>', where <SID> is the SAP system id.
Example with host name (iwdf8997.wdf.sap-ag.de) and symbolic service name (sapdpIWD):
/H/iwdf8997.wdf.sap-ag.de/S/sapdpIWD
Simple connection strings need not be resolved by the GUI application. Resolution of host names and symbolic service names is done by the operating system's network layer.
SAP Routers
In a WAN (Wide Area Network) environment, SAP routers are used to make connections to remote SAP systems that cannot be reached with a direct TCP connection. Passwords may be used for each SAP router to control access.
In order to make a connection, the frontend computer is responsible for providing the complete route to the destination, possibly including a chain of several SAP routers. Path information is not provided by the routers. (Strictly speaking, a SAP router is actually better described as an application level proxy with password capabilities and strict source routing).
The address for each router is specified by a simple connection string (with the router's host name and port number), optionally followed by '/P/' and the router password. The path from the current location to the destination is described by appending all router addresses together, followed by the address of the destination SAP system. Thus, a connection string with SAP routers generally has the form <router 1><router 2>...<router n><destination>.
Example with two routers (gate.acme.com, port 3299, and gate.sap.com, port 3298), the first using a password (secret), for a connection to the application server iwdf8997.sap.com, port 3200):
/H/gate.acme.com/S/3299/P/secret/H/gate.sap.com/S/3298/H/iwdf8997.sap.com/S/3200
<-------- 1st router ----------><---- 2nd router ----><------ app_server ------>
Connection strings including SAP routers are passed to the GUI's communication layer and resolved step by step by the routers on the path. If host names and symbolic service names are used, each router must have access to correct network configuration information to resolve them.
Message Servers and Logon Groups
For load balancing purposes, application servers from one SAP system are usually configured in logon groups, where each group serves a particular kind of user. The application servers in each group are assigned to users by a least-heavily-loaded strategy. This load balancing is done by message servers. Each SAP system has exactly one message server, which can be reached via TCP on a specific message server port.
Care should be taken that the application server's port number is not confused with the message server's port number. Although the message server's host name may in small installations often be identical to the hostname of an application server, the port number is always different. Symbolic service names for message servers by convention have the form 'sapms<SID>', where <SID> is the SAP system id.
Message server and group information can be used to address a SAP system in a connection string. The address of the message server is specified as a combination of message server host name, message server port and group name. These informations are marked with the prefixes '/M/' (message server host name), '/S/' (message server port) and '/G/' (logon group).
Example with message server (hostname alrmain, port number 4253) and logon group (SPACE):
/M/alrmain.wdf.sap-ag.de/S/4253/G/SPACE
Connection strings with message servers are resolved by SAPGUI for the Java environment by contacting the message server and retrieving the (simple) connection string of an application server for the specified group. This requires network access to the message server at the time the address is resolved.
SAP router connection strings may be used in combination with message server connection strings simply by specifying the router address before the message server address. The router is then used for contacting the message server as well as for contacting the resolved application server.
Symbolic System Names
The most user-friendly form of connection string addresses an SAP system only by its symbolic name (per convention, the system id) and the logon group name. These informations are marked with the prefixes '/R/' (for the symbolic SAP system name) and '/G/' (for the logon group name).
Example with SAP system (ALR) and logon group (SPACE):
/R/ALR/G/SPACE
Connection strings with symbolic system names are resolved by SAPGUI for the Java Environment by looking up the symbolic SAP system name in the Message Server List (a text file containing a mapping between symbolic system names and message server addresses) and replacing the /R/ part of the connection string with the resulting message server address. The result is a complete message server connection string which is then further resolved as explained above.
Formal syntax
For the technically interested reader, the following BNF grammar formally describes the syntax of connection strings:
<connection string> := [<router prefix>]<local>
<local> := <simple>|<message server>|<symbolic>
<simple> := "/H/"<host>"/S/"<service>
<host> := <hostname>|<ipaddr>
<hostname> := (any DNS hostname)
<ipaddr> := (any IP address, in dotted decimal form)
<service> := <servicename>|<port number>
<servicename> := (any IP service name)
<port number> := (any decimal number)
<messageserver> := "/M/"<host>"/S/"<service>"/G/"<group>
<group> := (any ASCII string not containing '/')
<symbolic> := "/R/"<system>"/G/"<group>
<system> := (any ASCII string not containing '/')
<router prefix> := <router>*
<router> := "/H/"<host>"/S/"<service>["/P/"<password>]
<password> := (any ASCII string not containing '/')
When you open the Automatic Updates tab in My Computer Property sheet, or from Control Panel, all of the Automatic Updates configuration options may be grayed out. This happens due to any of the following reasons:
You're not logged on as Administrator (or equivalent)
Automatic Updates Policy is enabled
Automatic Updates (and Windows Update) access is blocked via Group Policy
Resolution
To make the Automatic Updates options configurable by the user (only for stand-alone systems), remove the restrictions 2 & 3 above.
Click Start, Run and type REGEDIT.EXE
Navigate to this location:
HKEY_LOCAL_MACHINE SOFTWARE Policies Microsoft Windows WindowsUpdate AU
In the right-pane, delete the two values AUOptions and NoAutoUpdate
Navigate to this location:
HKEY_CURRENT_USER SOFTWARE Microsoft Windows CurrentVersion Policies WindowsUpdate
In the right-pane, delete the value DisableWindowsUpdateAccess
Using the Group Policy Editor - for Windows XP Professional
Click Start, Run and type gpedit.msc
Navigate to the following location:
=> Computer Configuration ==> Administrative Templates ===> Windows Components ====> Windows Update
In the right-pane, double-click Configure Automatic Updates and set it to Not Configured
Then, navigate to this location:
=> User Configuration ==> Administrative Templates ===> Windows Components ====> Windows Update
In the right-pane, set Remove access to all Windows Update features to Not Configured
Transport req. release hangs, only for a specific user and request.
I've found out what the problem was.
There were some warning message in SLOG0305.DEV file...
When a transport request is being released, a "semaphore" file (userid.LOS) is written in /usr/sap/trans/tmp, and deleted when the tp command is executed.
For some reason it wasn't deleted some time ago, so the user couldn't release nothing else. OSS note 12746 helped me.
Internal Error with background job scheduling XXXXXXXXXXXXX.
When run transaction MMPV with background, got error message " Internal Error with background job scheduling XXXXXXXXXXXXX.", Then check with transaction ST22, not found, and the SM21, got info. like this: When checking the job data for background processing, the system determined that a free server could not be found to execute a job dependent on start time:
Start time = 'immediately':
There is either no server configured for background processing or al available servers (for the required job class) are already busy.
Start time = 'date/time of day' or 'for operation mode':
Either no servers are defined for the required start time for background processing or no server is available for the required job class.
Start time = ' after event' or ' after predecessor job '
There is no server defined for background processing (for the requir job class).
Solution: run RZ04 Configure 3 BTC processes in daily operate mode temporarily and switch manually with RZ03.
2. Go To https://service.sap.com/saprouter-sncadd ==> choose apply now ==> choose saprouter ==> copy and paste certreq into the text area ==> we will get new certicate
3. create new file srcert on /usr/sap/saprouter then copy & paste the new certificate
4. Go to /usr/sap/saprouter
execute following command :
sapgenpse import_own_cert -c srcert -p local.pse
sapgenpse seclogin -p local.pse -O exdadm
sapgenpse get_my_name -v -n Issuer
Here are the other steps to renew SAP Router license :
1) make a new folder in your saprouter directory like <drive>:usrsapsaprouterbackup
Cut/Paste certreq, cred_v2, getcert.cer, local.pse, srcert in backup directory
2) Run the below command to generate new certificate request
Start Process Logs are handy during the troubleshooting the start process of the SAP system. These files are stored in the home directory of user <sid>adm.
The following list contains the log files which are created during the start process of the SAP service:
STDERR1: Information about the start process of the database system.
STDERR2: Information about the start process of the message server.
STDERR3: Information about the start process of the dispatcher.
The logged information can be set in 4 levels using the profile parameter rdisp/TRACE having values for this parameter:
Errors only
Error messages and warnings (Default)
Error messages and a short trace
Error messages and a complete trace
The four trace level has the highest amount information stored in the files so the file will be of large size. The trace level can be set separately for individual work processes in the process overview (SM50)
During startup of the operating system Windows NT, the NT Service Control Manager starts all the services in the service list that are configured for automatic startup. The information relevant to these services is stored in the registry and is read by the Service Control Manager during startup. Several services of type “SAP_” (the SAP service) and “Oracle Service”,but only one SAPOsCOL service, can be run on one computer. The SAP service, SAPOsCOL, and OracleService should be configured for automatic startup.
To start the Oracle database and the R/3 System, the administrator performs the following steps: Log on to the operating system Windows NT as user adm. To start the R/3 System, open the Microsoft Management Console (MMC) using the SAP R/3 Systems Snap-in. Right-click on the system icon and select Start. The sapstartsrv.exe executable sends a message using a named pipe to the SAP Service, SAP_. The SAP service starts the database by executing an NT script that calls the Oracle Server Manager. The Oracle Server Manager executes an SQL script that starts the database if it is currently not running. Once the database is up and running, the SAP service starts the Message Server (msg_server.exe) and the Central Instance dispatcher (disp+work.exe). The R/3 System has been started successfully when the icon for the central instance changes color to green. The colors displayed in the MMC have the following meanings: red - the process terminated abnormally; yellow - the process is being started; green - the R/3 System has been successfully started; gray - the process is not running, status unknown. You can also start the R/3 System with the NT scheduler called “at”. For this kind of start, SAP provides the executables startsap and stopsap which are executed locally. Use - startsap name= nr= SAPDIAHOST= to start an R/3 instance and - stopsap name= nr= SAPDIAHOST= to stop an R/3 instance (the executables sapstart.exe, sapsrvkill.exe and sapntwaitforhalt.exe must be in the same directory)
To provide a stable startup procedure, a parameter read sequence (also known as the parameter replace sequence) is defined during startup as follows: R/3 processes read the appropriate parameters from the R/3 kernel, from the NT system environment variables, and from the NT Registry environment variables. The default profile “sapmntSYSprofiledefault.pfl” is read. Profile values already defined in the R/3 kernel are replaced with the values in the default profile. The instance profile “sapmntSYSprofile__” is read. Profile values already defined in the default profile or in the R/3 kernel are replaced with the values defined in the instance profile. This procedure ensures that system parameter values reflect not only the instance profile but also the values in the default profile and the R/3 kernel. The SAP service reads only the start profile and the default profile. The R/3 kernel(disp+work.exe)reads only the default profile and the instance profile. If you change the default profile, you must restart the SAP service (including the R/3 instance). If you only change the instance profile, you only need to restart R/3 using the MMC.
R/3 work directories contain trace files and error files for messages relating to the startup of work processes. Each R/3 instance has a separate work directory containing information that may not be found in the R/3 System log. The work directory files are initialized in chronological order. During startup, the SAP service executable SAPSTARTSRV.EXE writes: Database logs to the file STDERR1 Message server logs to the file STDERR2 Dispatcher logs to the file STDERR3 To define the level of information written to the developer trace files, set the profile parameter “rdisp/TRACE” in the instance profile. The possible values for this parameter are: 0: Write only errors (no traces) 1: Write error messages and warnings (default) 2: Write error messages and a short trace 3: Write error messages and the complete trace
Run
transaction SSAA failed;
RFC_CONVERSION_FIELD
Conversion error between two character sets.
Conversion error "ab_rfccon" from character set 4103 to character
set " "
How do you find that an operation mode switch occurred?
How do you find that an operation mode switch occurred?There are many ways
1) Go to sm50. If the no of dialog work processes or background work processes changes then a operation mode switch took place.
2) Go to transaction sm63. Here you can see the time when the operation
mode is set. You can guess when the operation mode switch occurs.
3) Go to transaction RZ04, here you can see the list of operation modes and their time. You can guess that from here
4) Go to transaction rz03 , here you can see the current operation mode in which the server is running.
5) Call
transaction Code sm62. Then view system events. If there is an event
called SAP_OPMODE_SWITCH then operation mode switch occurred at that
time. If you click on activity log you can see the time and date when
the event was triggered. It is time and date of operation mode switch
Yogi Gunawan 09.16.2003
Rating: -3.84- (out of 5) Hall of fame tip of the month winner
How do you add/remove/modify several items in the SAP menu for
particular/all users? Login to the development client; make sure that
changes to repository or cross-client customizing are permitted. Use
t-code SE43N and you will see the Area Menu Maintenance screen. The
default area menu in SAP is S000, so if you want to change the items in
SAP Menu, it is better that you copy the S000 menu, for example copy it
to Y000 (Ctrl-F5). SAP screen will ask you which language the copy will
be created, choose English; for the development class fill it with one
of the default sap development class, exp. ZDEV; and click save. It will
prompt you to make a transportable Workbench request. You have to
create this because we will need to transport the new SAP menu to the
destination client. Click "create request" (F8) and fill in the short
description. It will create new request number. Click to continue. To
modify your new SAP menu, please click the change area menu button (F6).
In the Edit Area-menu you can select one of the node/sub-node and make
your changes by clicking one of the buttons on the screen: Add entry as
sub-node (Shift-F7), add entry at the same level (Shift-F8), change
nodes (Shift-F9), .etc. After you have finished your changes, click the
save button. Now that you have done the changes, the next thing is that
you have to transport your area menu to the destination client (the
client that you want to show the new SAP menu to your users). You can do
this by using t-code SE10 to release your change request, and use
t-code STMS to import your change request number that you have been
released (as usual transport). To apply your new SAP menu to the user,
all you have to do is login to the destination client. Use t-code SU01,
fill in the username and then click the change button (Shift-F6). Click
the default-tab and fill in your new SAP menu name in the start menu
textbox. Click save.
If you want to set your new SAP menu to several/all users at the same
time, use t-code SU10 (user maintenance: mass changes).
To store document / image in SAP, we can use Business Document Navigator. To
go to the Business Document Navigator, choose Office -> Business
Documents -> Documents -> Find (transaction code : OAOR).
SPRO:
SAP Customizing Implementation Guide -> SAP Netweaver -> Application Server -> Basis Services -> Business Document Service
When you are using transaction OAOR to store document manually, first you have to maintain table class in tcode SBDSV1
CAF:GP:MailConnector:run():insideCycle from J2ee_Guest user causes more CPU and Resources utilization is happening.
Followed procedure for stopping specified request:
Go to Visual Admin > Global Config > Services > caf/eu/gp/model
Set mailconnector.start_thread = false.
Needs a restart.
With the installation of a SAP® system, some standard users are
created in the individual clients or system environments. Some of these
users have already high authorizations from the beginning, and of
course most of them have standard passwords assigned that are generally
known.
These special users need special treatment and special protection.
1. SAP*
The user SAP* exists right after the installation in all clients. He
has the composite profile SAP_ALL assigned and with that all relevant
authorizations for the system set up.
SAP® has implemented a backdoor [coding] for this user.
If someone deletes the user SAP*, a login is possible with the standard
password PASS including the corresponding SAP_ALL authorizations.
To prevent a login of the SAP* after a deletion, the parameter login/no_automatic_user_sapstar can be utilized.
With a parameter setting to 0 the login is possible.
Any value higher than 0, prevents a login after the deletion.
The standard password for this user directly after the installation is 06071992.
The standard password after deletion is PASS.
The preferable method to protect this user is the deactivation of SAP* :
- Remove all authorizations from this user.
- Lock the user account.
- Set the parameter login/no_automatic_user_sapstar
to 1.
- Activate the audit log for this user.
You can also consider to assign this user to a user administration group that is protected by a dual control principle.
This report RSDELSAP deletes the user SAP*in the client 066. The corresponding source code is not active but available.
2. DDIC
The user DDIC is established in the client 000 and 001 with the installation
[and copies of these].
This standard user is uitilized to cover installation and release
updates including changes to the data dictionary. The use of the
transport management system is restricted to Display only.
This is the protection against direct developments.
As the technical steps related to this process are initiated in the
client 000, the DDIC only needs to be a dialog user in this client.
In all other clients he can be set to the user type “system”.
The standard password for this user directly after the installation is 19920706.
The report RDDPWCHK allows to check the password that is assigned to
the user DDIC. In case the password matches, the dialog window will be
closed. For mismatches the message False is displayed.
The counter for false login does not count these password detection attempts.
3. TMSADM
The user TMSADM is automatically created at the set up the change and transport management system in the client 000.
His user type is “Communication”, and he is utilized for transports by the CTS.
He has the profile S_A.TMSADM assigned that authorizes the use of RFC
with display of the development environment e.g. as well as writing to
the file system.
The standard password for this user directly after the installation is PASSWORD.
4. SAPCPIC
The user SAPCPIC is created as a “communication” user at the
installation and is utilized especially for EDI. The standard profile
S_A.CPIC restricts the access to the use of RFC.
This user is coded into the function module
INIT_START_OF_EXTERNAL_PROGRAM together with his standard password.
This needs to be considered in case of password changes for this user.
The standard password for this user directly after the installation is ADMIN.
5. EARLYWATCH
The user EARLYWATCH is created in the client 066 at the installtion. He
can be utilized for remote control by SAP® and is only set up with some
standard authorizations S_TOOLS_EX_A for performance monitoring. The
user is to be locked in general, and can be unlocked upon request.
Evaluation
For the evaluation of the passwords you may use the report RSUSR003.
6. SAP* in J2EE
The user is established with full authorizations for the administration.
With regard to security, the user has no standard password assigned.
To utilize this user as emergency user the properties in the UME need to be maintained.
Setting the ume.superadmin.activated property to true will activate the use of this user for emergency cases.
Setting a password in ume.superadmin.password will then activate the user finally after the restart of the engine.
While the user SAP* is in use, all other users will be inactivated during this time.
When the system is fixed, the deactivation can be achieved by setting the ume.superadmin.activated property to false.
7. J2EE_ADMIN_
This user is the Java standard user with full administration
authorization in this environment. The password is to be assigned
during the set up.
High complexity is recommended for this password.
8. J2EE_GUEST
This user is a Java standard user who can be utilized for anonymous access.
The user is locked per default. The password is assigned during the installation.
9. SAPJSF_
This user is a standard communication user for LDAP [Lightweight Directory Access Protocol] data sources.
10. ADSuser
This standard user is utilized for the communication between Java and ADS
[Adobe Document Service].
11. caf_mp_scvuser
This standard user is utilized in the context of the Composite
Application Framework (CAF) core transport system and communication
with other Java services.
This is normal and you will see it done by sapsys (internal) in your System Log SM21.
An SAP rollback is performed when a user backs out of a transaction losing previously entered data, therefore to maintain transactional consistency SAP does not partly save the data, it performs a rollback.
You can search the folder structure of portal installation under /usr folder. You should find the occurance's. Anyways here are the locations where I found the favicon. ./JCxx/j2ee/cluster/server0/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/favicon.ico
The following parameters for the transport control program and the
Change and Transport System (CTS) are set according to the chosen
transport strategy:
Parameter
Value for Mass Transports
Value for Single Transports
Value for Workflow-Controlled Transports
IMPORT_SINGLE_ONLY
0
1
1
NO_IMPORT_ALL
0
1
1
IMPORT_SINGLE_STRATEGY
0
1
0
WORKFLOW_STRATEGY
0
0
1
REPEATONERROR
9
8
8
STOPONERROR
9
9
9
You can display these parameters
in the TMS system overview. To do this, position the cursor on the
appropriate system and choose SAP System ®
Display. The tab Transport tool contains all the profile parameters.
Do
not manually change the parameters that are relevant to the transport
strategy. TMS generates these parameters each time the transport route
configuration is changed.
Please advise your system administrator that
all features must be regenerated.
Please note that this generation must take place
in client 000 first, and then in all other
clients (report RPUMKG00)
How to configure a firewall for domains and trusts
Windows Server 2003 and Windows 2000 Server
For
a mixed-mode domain that uses either Windows NT domain controllers or legacy
clients, trust relationships
between
Windows Server 2003-based domain
controllers and Windows 2000 Server-based domain
controllers
may necessitate that
all the ports for Windows NT that are listed in the previous table be
opened in addition to the following ports.
Note The two domain controllers are both in the same
forest, or the two domain controllers are both in a separate forest. Also, the trusts in the forest are
Windows Server 2003 trusts or later version trusts.
Collapse this tableExpand this table
Client Port(s)
Server Port
Service
1024-65535/TCP
135/TCP
RPC
1024-65535/TCP
1024-65535/TCP
LSA RPC
Services (*)
1024-65535/TCP/UDP
389/TCP/UDP
LDAP
1024-65535/TCP
636/TCP
LDAP SSL
1024-65535/TCP
3268/TCP
LDAP GC
1024-65535/TCP
3269/TCP
LDAP GC SSL
53,1024-65535/TCP/UDP
53/TCP/UDP
DNS
1024-65535/TCP/UDP
88/TCP/UDP
Kerberos
1024-65535/TCP
445/TCP
SMB
(*) To define RPC server ports that are used by the LSA RPC
services, see the "Domain controllers and Active Directory" section in the
following Microsoft Knowledge Base article:
832017
(http://support.microsoft.com/kb/832017/
)
Service overview and network port requirements for the Windows Server system
We can not upload image to SAPDB, when one session upload holding, all the other session can not access image in SAPDB, but when we restart SAPDB, we could read the image,...Finally, we found the cause is the data area full used to 99%, so add new datafile to add free space, but found something interested.
1, datafiles, or call data volume cannot delete;(From google search, SAPDB 7.6 should be support possible),
2, there are parameters to limit the datafile number and all size, if you want to add datafile, it should tune first.
An error occurred while the wizard was checking the current Windows product license. Error Code: 8: 0x8007007f
I found there was an error on SAPDL580 server, the message from event log display "An error occurred while the wizard was checking the current Windows product license. Error Code: 8: 0x8007007f".
When I tried to login the server four times this morning, it refused me login and hung black screen, I had to hard boot the server.
And I checked the Microsoft help, it seams that the error was caused by install the windows SP2 with RDP by you last night. Some suggestion said it should be right after reboot, other said it should be uninstall the SP2.
You have to
configure SAPconnect settings for every client that is used for send
processes.
·Default
Domain
Under
Settings®Default Domain, define the domain of
the SAP system client. This allows for the following to take place:
·The SMTP plug-in
logs on to the mail server using the domain as ID.
·The message ID of
the outbound e-mails is assembled with this domain.
·If an SAP user who
does not have an Internet mail address sends an e-mail, a sender address
consisting of the SAP user name and this domain is generated.
·Nodes
Each client
has an SMTP node. This node is created by the SAP system and cannot be
deleted. The following steps need to be carried out to configure the node so
that sending Internet mail is possible:
i.Make sure you are
in the Node view.
ii.Double-click the
node name.
iii.Choose Node in
use.
iv.In the Mail
Host and Mail Port fields, specify the mail server to which the
outbound mails are to be sent.
v.Next to
Internet, choose Settings.
vi.Enter the address
area of the recipient addresses that are to be reached using this node. In
general, * is used if all e-mails are to be sent using
SMTP.
vii.Enter the output
format for SAP documents. We recommend that you use the following
settings:
SAPscript/Smart
Forms
PDF
ABAP list
HTM
Business Object / Link
HTM
RAW Text
TXT
viii.Confirm your selection.
If you also
want to configure the node for sending faxes:
i.Next to Fax,
choose Settings.
ii.Enter the address
area of the recipient addresses that are to be reached using this node. In
general, * is used if all faxes are to be sent using
SMTP.
iii.Enter the output
format for SAP documents. We recommend that you use the following
settings:
SAPscript/Smart
Forms
PDF
ABAP list
PDF
Business Object / Link
TXT
RAW Text
TXT
iv.Enter the domain of
the fax server or fax provider under Conversion into Internet Address.
The system generates the local part of the Internet address automatically. The
address therefore takes this format: FAX=+RecipientNumber@Domain.
v.Confirm your
selection.
If you also
want to configure the node for sending text messages (pager/SMS):
i.Next to Pager
(SMS), choose Settings.
ii.Enter the address
area of the recipient addresses that are to be reached using this node. In
general, * is used if all text messages (pager/SMS) are to be
sent using SMTP.
iii.Enter the domain of
the text message (pager/SMS) server or provider under Conversion into
Internet Address. The system generates the local part of the Internet
address automatically. The address therefore takes this format: SMS=+RecipientNumber@Domain.
iv.Confirm your
selection.
·Send Job
E-mails sent
from an SAP application are first stored in a queue. A periodical background
process, the SAPconnect send job, gets the e-mails from this queue and sends
them over the Internet. To schedule this job in SAPconnect:
Administration, proceed as follows:
i.Choose View®Jobs.
ii.If no other job has
been scheduled, choose Job®Create.
iii.Enter a job name
and confirm it.
iv.Select the variant
SAP&CONNECTALL by positioning the cursor on it.
v.Choose
ScheduleJob.
vi.Choose
Scheduleperiodically.
vii.Select the interval
you require, such as 10 minutes.
viii.Choose Create.
·Inbound
If you want
incoming e-mails that have a particular address or particular content to
automatically start a program that processes these mails, you can configure
this under Settings® Inbound Processing.
If you want
incoming e-mails that have a particular address or come from a particular
sender to be automatically forwarded to another recipient or another
distribution list, you can configure this under Settings® Inbound Processing.
The description for Event ID ( 4 ) in Source ( UPService ) cannot be found. The
local computer may not have the necessary registry information or message DLL
files to display messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support for details.
The following information is part of the event: UPService: PDH FAILED
Solution:
This error can rack up considerable events in the Application Log. On my R&D
system I get 7 per 5 minutes when it occurs, then it maybe 6 weeks prior to
getting more.
Currently the best workaround for this event is to stop and
"disable" the following 2 services under Service Control Manager.
"HP
UtilProvider Data Collector" "HP UtilProvider WMI Provider"
These two
services are only used by HP Virtual Machine for Windows Guests (unlikely you'll
be using) and HP Capacity Advisor (again unlikely you'll be using).
We
are working on a fix for this issue which will be in a future version of the
SmartSetup Media (SSM).
Many times I have come across error in SM59 transaction saying the program is not registered on the gateway
RFC connection test in SM59 might give error similar to this
———————————————————————————————————
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program <program id> not registered
Error Details LOCATION: SAP-Gateway on host <hostname> / sapgw<instance no>
Error Details DETAIL: TP <program id> not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 16793
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Mon Sep 17 13:08:02 2007
Error Details VERSION: 2
———————————————————————————————————
The program in the above error should be
registered in the gateway for this connection test to complete
successfully. The server program rfcexec is responsible for its
registration on the gateway.
To register the program login into the OS level as sudo su - <sid>adm and execute the following command.
rfcexec is the server program name, the
<program id> can be obtained from SM59, it is case sensitive and
should match with the entry in SM59. The <gateway host name> and
<gateway service> can be obtained from the transaction SMGW. When
this command is executed it goes to a hanging loop.
The connection will fail once this command is terminated or the user executing this command logs off
To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
To do this, execute the following command
sudo su - <sid>adm
rfcexec –D<destination name>
<destination name> is the RFC destination name in SM59
So now we are done with registering the server
program, but how do we check it is registered, once a server program is
registered it is displayed in the Logged on clients in SMGW.
In transaction SMGW choose GOTO-> Logged on
clients. There should be an entry for the server program in the screen
that is displayed with system type Registered_TP (which indicates that
the program is registered)
There can be many reasons due to which we
might get this error saying server program is not registered, once such
instance which I faced was where in the TREX server, a new RFC
destination was defined, the TREX server creates a new program id each
time this RFC destination is defined. This program id was not changed
in TCP/IP connection is SM59 which was the reason why the destination
was failing
Timeout settings: There are several timeout values that are involved when using the internal ITS:
rdisp/gui_auto_logout:
This parameter applies to all kind of user sessions in the R/3 (SAPGui
and ITS services). This profile parameter should be set larger or equal
to the session timeout of the ITS service (see below).
Session
timeout of an ITS service: For each ITS service a dedicated timeout can
be set. Call transaction SICF => /sap/bc/gui/sap/its/ =>
<Service> => Service options => Session-Timeout:
<hh:mm:ss>.
Timeout values of the Internet Communication
Manager (ICM): There are two kind of timeout values that can be set in
the ICM: PROCTIMEOUT and TIMEOUT.
-
PROCTIMEOUT: The PROCTIMEOUT argument of the ICM parameter
icm_server_port_?? Defines the maximum processing time of a request in
the kernel (the default value for processing time is 60 seconds). You
should choose a value that fits to the runtime requirements of the ITS
services you are using.
- TIMEOUT: The TIMEOUT argument of the
ICM parameter icm_server_port_?? defines how long the connection
between the browser and ICM should remain open (the default value is
defined with the parameter icm/keep_alive_timeout and has the value
60). The parameter has no effect on the session/connection timeout but
is used to optimize the performance of the HTTP connection (HTTP/1.1).
For further details, please refer to note #705013.
2, To do this, start Tcode SMICM.
Then Menu: Goto->Services->Menu->Go To->Service->Define.
Specify a new port number, and a large “keep alive” time. When testing,
just change the port number in the URL to use the newly defined one.
or RZ10.
Parameter : icm/keep_alive_timeout
Short description : keep alive timeout for inactive connections
Parameter description :
If no communication takes place over an existing connection for more than a certain length of time, the connection is closed by ICM. The standard value for the timeout is set with this parameter, but can overridden for each service (see below).
A value of -1 deactivates the timeout. The connection is then never closed by the ICM. Caution: Note that the user context in the work process is not closed after this period of time. That timeout is defined using the profile parameter %%rdisp/plugin_auto_logout%%.
An
SAP portal installation, by default, selects a port for http and https
access based on your system number. For example, if your system number
is ##, then the default port for portal access would be
* 5##00 for http access
* 5##01 for https access ( aka SSL )
Many Project teams wish to shorten this long url
(http://yourserver.yourdomain.com:5##00irjportal). Fortunately, there
is an easy way to modify the portal http and https ports and keep it to
80 and 81 ( or anything you wish).
Follow the below given steps to achieve this.
1. Start the j2ee visual administrator tool
2. navigate to cluster -> dispatcher -> HTTP Provider
3. Choose Ports
4. Change the port number to 80 for http and 81 for https
5. Thats it - You’re done!!!!
One extra step that’s required if you’re also running IIS (for
example, if you’re using an ITS to communicate with an older R3 system
or running TREX), you need to make sure that your J2EE ports do not
conflict with any of the IIS ports (including the default web server).
The best way of doing that is to ensure that the IIS default web server
is pointing at different ports AND is stopped.
Actually,
its a bit of a cheat. What happens is that you’re telling the J2EE WAS
that if there is no page specified (such as …/index.html), then open
the page …/irj/portal.
1. Go to j2ee visual administrator
2. For each Server, Navigate to Cluster-> Server -> Services -> HTTP Provider
3. Enter /irj/portal in the Start Page Text Field
4. Click on Save Properties
5. Restart this service from visual administrator
Access http://yourserver.yourdomain.com and your portal login page should come up.
This means that your SAP J2EE Engine Start Page will still show up if you http://yourserver.yourdomain.com/index.html
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production PL/SQL Release 9.2.0.4.0 - Production CORE 9.2.0.3.0 Production TNS for 32-bit Windows: Version 9.2.0.4.0 - Production NLSRTL Version 9.2.0.4.0 - Production
I am installing ECC 6.0 as ABAP with System Copy method on Windows Server 2003
Standard Edition with MS-SQL Server 2005 as Database Server. I am
facing error at the phase "Create SAP stored Procedures" in the step
025 of 220 (sap_add_dbccjob).
When we imported a customize structure Z* which append for table RESB to QAS system, it worked; but imported to PRD system, so many users complained they could not run standard SAP programs, like CO13, CO14, CO15 etc.
Check with ST22, found a lot of ABAP runtime errors, LOAD_TYPE_VERSION_MISMATCH.
It seams that this causes an memory overflow, and then leads to an error. Based on Note 1010590, the solution was import Support Package SAPKB70012 or higher, or implement the correction instructions. But the copy of PRD, QAS system was not happen the error. So we decided to restart the PRD to try to solve this.
Why did SAP GUI for Windows 6.40 support end before SAP GUI for Windows 6.20 and 7.10 support does? The Microsoft
As of release 6.40 SAP usually ties the support duration for SAP GUI
for Windows releases to the support duration for the development
environment used. The reason for this is that we may require
corrections from Microsoft for solving an issue in SAP GUI, but
Microsoft does not provide us with corrections once support for a
development environment is stopped.
SAP GUI for Windows
6.40 was developed with Visual Studio 2003 which was de-supported by
Microsoft on 14th of October 2008. Consequently SAP GUI for Windows
6.40 was also supported until this very day.
SAP GUI for Windows 7.10 was developed with Visual Studio 2005 which will be de-supported by Microsoft on 31st of March 2011. Consequently SAP GUI for Windows 7.10 is supported until this very day.
SAP
GUI for Windows 6.20 is an exception to this rule. It was developed
with Visual Studio 98 which is out of maintenance since September 2005.
Since we had already announced support for this release to be
"longterm" in order to allow customers to reduce their Frontend
upgrades SAP GUI for Windows 6.20 is supported until 2010 even though
we had to restrict the support (see note 929300).
If you want to know the details, pls check note 147519.
* * Pop a Message to specific SAP users * * How to get a list of all the currently logged on users? * How to popup an instant message on a user's monitor? * How to get a specific user's details? * Usage of 'POPUP_GET_VALUES' function module to get data from user * without having to write GUI code * * Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff * http://www.sap-img.com * REPORT ZPOPUP NOSTANDARDPAGE HEADING. INCLUDE <ICON>.
DATA: L_LENGTH TYPEI,
T_ABAPLIST LIKE ABAPLIST OCCURS0WITHHEADERLINE, BEGINOF T_USER OCCURS0,
COUNTER TYPEI,
SELECTION TYPEC,
MANDT LIKE SY-MANDT,
BNAME LIKE SY-UNAME,
NAME_FIRST LIKE V_ADRP_CP-NAME_FIRST,
NAME_LAST LIKE V_ADRP_CP-NAME_LAST,
DEPARTMENT LIKE V_ADRP_CP-DEPARTMENT,
TEL_NUMBER LIKE V_ADRP_CP-TEL_NUMBER, ENDOF T_USER,
L_CLIENT LIKE SY-MANDT,
L_USERID LIKE UINFO-BNAME,
L_OPCODE TYPEX,
L_FUNCT_CODE(1) TYPEC,
L_TEST(200) TYPEC.
V~NAME_LAST
V~DEPARTMENT
V~TEL_NUMBER INTO (T_USER-NAME_FIRST,
T_USER-NAME_LAST,
T_USER-DEPARTMENT,
T_USER-TEL_NUMBER) FROM USR21 AS U JOIN V_ADRP_CP AS V ON U~PERSNUMBER = V~PERSNUMBER AND
U~ADDRNUMBER = V~ADDRNUMBER WHERE U~BNAME = T_USER-BNAME. ENDSELECT. MODIFY T_USER. ENDLOOP. SORT T_USER BY NAME_LAST NAME_FIRST. PERFORM DISPLAY_LIST.
TOP-OF-PAGE. PERFORM DISPLAY_MENU. * End of top-of-page
TOP-OF-PAGEDURINGLINE-SELECTION. PERFORM DISPLAY_MENU. * End of top-of-page during line-selection
ATLINE-SELECTION. IF SY-CUROW = 2. IF SY-CUCOL < 19.
T_USER-SELECTION = 'X'. MODIFY T_USER TRANSPORTING SELECTION WHERE SELECTION = ''. PERFORM DISPLAY_LIST. ELSEIF SY-CUCOL < 36. CLEAR T_USER-SELECTION. MODIFY T_USER TRANSPORTING SELECTION WHERE SELECTION = 'X'. PERFORM DISPLAY_LIST. ELSEIF SY-CUCOL < 50. PERFORM TRANSFER_SELECTION. PERFORM POPUP_MSG. ELSEIF SY-CUCOL < 67. PERFORM TRANSFER_SELECTION. SORT T_USER BY NAME_LAST. PERFORM DISPLAY_LIST. ELSEIF SY-CUCOL < 81. PERFORM TRANSFER_SELECTION. SORT T_USER BY NAME_FIRST. PERFORM DISPLAY_LIST. ELSEIF SY-CUCOL < 93. PERFORM TRANSFER_SELECTION. SORT T_USER BY MANDT. PERFORM DISPLAY_LIST. ENDIF. ENDIF. * End of line-selection
Try to reinstall EVA command view on new machine instead of source machine.
It must to install EVA Command View on new machine(Server A) with local group method, with Domain group method will failled with login error "insufficient privilege", and then add the user to HP Storage Admins as member manually.
Login with the user, and the initial screen with pop the following message, select 'OK' to continue,
"Storage System Managed by Another Agent
Another management agent on server XXXXX at IP address 123.123.134.123 may be actively managing storage system sap_eva.
Only one agent is allowed to manage a storage system at a time.
To disable other management agents, simply click the OK button and management will be redirected to this agent.
Click the Cancel button to leave this page without changing the management agent for this system. "
Have you ever ended up with amusement that your portal server is no more displayed in SAP Management Console on expanding.
In such scenarios how can we start the server and work .Before
proceeding towards solution ,lets know about the various reasons for
occurrence of such scenarios.
Mostly the cause is shutdown of the PC without stopping the
server.This usually happens as in major MMC automatic updates ,security
patches run weekly which restart your system timely.In such times ,if
the Portal server was up ,then due to dirty closure the SAP Instances
get flushed out from MMC and the interface between the instance and
DCOM will be lost.
Solution :
Initially check the services in PC ,run services.msc where you can observe that the SAP Portal components will be missing.
For a proper server the services running in your PC are as follows:
To start the missing services ,the first thing we can have to do is to add up the instances to MMC ,
The procedure to be followed is:
Goto
1.usrsap<SID>SCS00exesapstartsrv.exe ,start and give in details
SystemID - <SID> (for example example N06)
Nr - Central Instance Number ( example 00)
Profile - Go to usrsapN06SYSprofile , check for the
existence of file name starting with START_SCS, and mention full path
of this file name here. Last characters signify your host name.
for example : F:usrsapN06SYSprofileSTART_SCS00_H1A-2F143-81Z
User - .SAPService<SID> for example: .SAPServiceN06
Password - <>
- The instance gets installed successfully message is prompted.
2. Now Go to usrsap<SID>JC01exesapstartsrv.exe ,start and give the details the details as explained above..
SystemID - N06
Nr - 01
Profile - F:usrsapN06SYSprofileSTART_JC01_H1A-2F143-81Z
User - .SAPServiceN06
Password - <>
- The instance gets installed again successfully message is prompted.
Now reopen the SAP MMC,expand the SAP Systems node .Now the instances are added back to console.
list the contents of an archive: SAPCAR -t[vs][f archive] [file1 file2....]
extract files from an archive: SAPCAR -x[v][f archive] [-R directory] [-A filename] [-V] [file1 file2....]
verify the archive: SAPCAR -d[v][f archive] [-V] [file1 file2....]
append files to an archive: SAPCAR -a[v][f archive] file1 [file2....]
merge two archives: SAPCAR -m[v]f "source target"
check availability of files to be processed: SAPCAR -l [-A filename][-X filename] [file1 file2...]
other options: -a : append files to an archive -A FILE : get names to include from file FILE -C DIR : change to directory DIR -e : redirect output from stdout to file sapcar_output -f FILE : use archive file FILE (default DEFAULT.SAR) -g : ignore case of of archive names while extracting, testing or listing archives -h : do not change permissions of existing directories during extraction -i : ignore inaccessible files while creating an archive -l : check availabilty of files to be processed -lower : convert filenames to lowercase while extracting -m : merge two archives -n : print statistical information -p octalvalue : set permissions of all files in archive to value -P : use absolute path-names (use carefully) -r : do not resolve symbolic links/shortcuts while creating an archive -R dir : use dir instead of current directory -s : do free space check -T FILE : rename files to be included in FILE -v : verbosely list files processed -V : compute or verify checksum (obsolete, always set, for backward compatibility) -X FILE : get names to exclude from FILE
examples: create archive with all files and directories in the current directory including point files: SAPCAR -cvf MY.SAR .
create archive with all files and directories in the current directory without point files: SAPCAR -cvf MY.SAR * Note that SAPCAR treats "*" and "?" as wildcard characters. The former matches any character string, while the latter matches any single character.
create archive with a complete directory and directory rights: SAPCAR -cvf MY.SAR dir
create archive with all files of a directory without the directory itself: SAPCAR -cvf MY.SAR dir/* if during extraction with SAPCAR -xvf MY.SAR the directory dir does not exist it will be created with rights 755
create archive with only the files of a directory SAPCAR -cvf MY.SAR -C dir . or better (cd dir; SAPCAR -cvf ../MY.SAR .)
merge two archives: SAPCAR -mvf "a source-archive.sar target archive from 27.5.1999.sar"
append files to an archive: SAPCAR -avf archive.sar file1 file2 file3
extracting/verifying files: If you try to extract files from an archive that is not a valid SAPCAR archive according to the version 2 specification SAPCAR assumes an archive of the old format and automatically invokes the appropriate extraction routine. If it still cannot handle the archive it will stop execution. Notice that extracting out of old archives only works with the command options known to the old CAR application.
using absolute pathnames: If you create an archive with absolute pathnames the files will be extracted with exactly these pathnames! SAPCAR does not cut the first slash like the UNIX tool tar.
specifying a list of archives for extracting/verifying/listing: You may call SAPCAR with the following command line: SAPCAR -xvf "ARCHIVE1.SAR ARCHIVE2.SAR" thereby specifying a list of archives you want to extract. Note that you have to delimit archive names with "," if at least one of the archive names you call SAPCAR with contains at least one whitespace character; e.g. SAPCAR -xvf "ARCHIVE WITH BLANK.SAR, ARCHIVE.SAR, ARCHIVE2.SAR"
using A, T and X option: All entries in the specified files are treated relative to the current working directory unless the entry is an absolute pathname (in this case the relevant file will be archived with an absolute pathname). If you want to specify a directory path in these files use the slash ("/") as path delimiter.
Use the pipe sign ("|") to separate old and new names in a T file when these names contain whitespaces. If neither the old file name nor the new one contains any whitespaces you may use whitespaces as delimiter between old and new name (that means a valid CAR rename file is also a valid SAPCAR rename file and hence may be given with the -T option). Note that pattern matching is not supported for entries in -A, -T and -X files (i.e. "*.cpp" will not result in processing all cpp-files in the current directory).
Lines starting with "#" as the first non whitespace character will be ignored by SAPCAR (this also holds true of lines containing only whitespaces).
If you insert a directory name in the specified file the complete directory with the directory rights will be included in the archive.
If you specify dir/filename only this file will be included in the archive. During extraction the directory dir will be created if it does not exist.
using -C option: All relative filenames in the command line are treated as relative to the specified directory.
SAPCAR 2.0, build 410504
C:TEMPsp46c>
If you have a lot of .car files in the folder,which you want to upgrade the kernel, you can run the following command:
During an upgrade or the import of an Support Package, existing objects of
the SAP standard are overwritten with the objects redelivered. To help the
customer retain the objects modified in a previous release, SAP provides all
modified objects which are redelivered (in an upgrade or Support Package) in the
upgrade adjustment of transactions SPAU and SPDD. These transactions allow
customers to enter their modifications into the corresponding new objects being
delivered at upgrade. The Modification Assistant supports this process of
adopting customer modifications.
In the past, all objects modified by a customer and delivered again by SAP,
an IBU or an SAP partner, had to be manually re-modified during an upgrade. Now,
modifications are either automatically adopted or the system provides you with
an assistant for adjusting your modifications to the newly upgraded
configuration.
In general, objects altered using the Modification Assistant can now be
automatically accepted into the upgraded system if the modifications undertaken
in the original version do not directly overlap those made in the customer
version. If collisions occur between the two versions at upgrade (naming
collisions, or if SAP has deleted an object modified by a customer), the system
offers support during the upgrade, which means that a semi-automatic adjustment
is made. In some cases, however, you may still have to manually adjust objects
using ABAP Workbench tools.
Objects modified according to the old system used prior to the advent of the
Modification Assistant must be manually maintained after an upgrade has been
run.
Use transactions SPDD and SPAU during an upgrade to select these objects and
modify them manually.
Transaction SPDD allows you to adjust modifications to ABAP Dictionary
objects during an upgrade.
Check if you have activated:
1) With transaction SICF and locate the services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui
2)With Transaction SE80 locate from the menu, Utilities -->
Settings-->Internet Transaction Server (Tab)-->Publish (Tab) and
set On Selected
Site = INTERNAL.
This restricts the publication in the next step to the integrated (internal) ITS.
3)In SE80 only, Locate the Internet Services: SYSTEM and WEBGUI.
Publish these services with the Context Menu -> Publish -> Complete Service
4)Now Browse to http://<server>:<icmport>/sap/bc/gui/sap/its/webgui/! and login to the webgui.
use sm30 tcode and change the table ssm_cust and change the parameter:
ALL_USER_MENUS_OFF
NO (default), YES or 'X' - Do not Display User Menu on Easy Access Screen (Note 380029)
CUSTOMER_MENU_OFF NO (default), YES or 'X' - Do Not Display Customer Menu on Easy Access Screen (Note 380029)
SAP_MENU_OFF NO (default), YES or 'X' - Do not Display the SAP Menu on the Easy Access Screen (Note 380029)
The other method is use sm30 tcode and change the table users_ssm to determine whether or notusers are allowed to switch between the SAP menu and their user menus.
Apply:
If a user ask you based on the role menus, you can not find any key.
If a user has several roles assigned, then some functions can be repeated in different parts of the role-based user menu.
SAP delivers various
types of program corrections with Support Packages as part of the
software maintenance. Support Packages automatically correct a whole
range of errors by downloading corrections into the SAP System. Two
categories of Support Packages are available: ABAP Support Packages and Java Support Packages.
ABAP Support Packages
ABAP
Support Packages contain corrections and updates for the ABAP
components of the SAP system that were performed up to a certain point
in time. Each Support Package is based on the previous one. If you want
to import Support Package 10, for example, you must also import all
previous Support Packages (1-9). To import ABAP Support Packages, you
use the Support Package Manager.
All
SAP R/3 Releases up to 4.5 are supported by corrections in the form of
SAP R/3 Support Packages (formerly Hot Packages) or SAP R/3 HR Support
Packages (formerly Legal Change Patches HR) until the end of their
maintenance period.
SAP HR Support
Packages contain corrections or adjustments due to legal changes for HR
functions in SAP R/3. Up to SAP R/3 3.1I (and SAP R/3 4.0B up to LCP HR
53), SAP R/3 HR Support Packages contain corrections for SAP HR as well
as the same set of corrections as SAP R/3 Support Packages. As of SAP
R/3 4.5B (and SAP R/3 4.0B as of LCP HR 54), the content of the SAP R/3
Support Packages is no longer included in SAP HR Support Packages.
Component Support Packages
ABAP
Support Packages are available for all components of mySAP.com, such as
SAP Basis, SAP BW, or SAP Advanced Planner and Optimizer (SAP Basis,
SAP BW, SAP APO Support Packages).
Add-On Support Packages
Corrections
for add-ons, such as industry solutions, strategic development projects
or SAP R/3 Plug-Ins, are provided in Add-On Support Packages. For more
information on Add-On Support Packages, refer to SAP Note 160168
.
Conflict Resolution Transports (CRT)
CRTs
adapt Component Support Packages to add-ons, such as industry solutions
(IS components). If an add-on modifies objects in the SAP R/3 Core
components, conflicts with SAP R/3 Core Support Packages may arise. A
CRT resolves these conflicts. For more information on CRTs, refer to SAP Note 53902.
SPAM/SAINT Updates
SPAM/SAINT
Updates extend the functions of the Support Package Manager
(Transaction SPAM) and the SAP Add-On Installation Tool (Transaction
SAINT).
Java Support Packages
Java
Support Packages contain corrections and updates to Java components.
They are delivered in the form of Software Component Archives (SCA).
Unlike ABAP Support Packages, Java Support Packages always contain the
complete version of the Development Components for the application. You
therefore need to apply the latest Support Package only. If there are
dependencies with other Java Support Packages, these are specified in
an SAP Note.
As of SAP NetWeaver 2004s, you can apply Java Support Packages
using the Java Support Package Manager (JSPM). For more information
on JSPM, refer to the quick link /JSPM.
Java
Support Packages are available as of SAP Web Application Server 6.20.
For SAP Web Application Server 6.20 and 6.40, you apply Java Support
Packages using the Software Deployment Manager (SDM). The SDM is
contained in the SAP Web AS installation as of 6.20. For more
information on SDM, refer to SAP Note 544244.
Support Package Stacks
A Support Package Stack is a set of Support Packages and patches
for a specific product version that must be used in the specific
combination.
For more information on Support Package Stacks, refer to the quick
link /sp-stacks.
All corrective software packages, for SAP NetWeaver 2004s and SAP
Business Suite 2005 and beyond that are delivered after April 2nd, 2007
will ONLY be available via SAP Solution Manager's Maintenance Optimizer.
Profile Active value Change password N/A 0 login/password_expiration_time 60 YES login/password_expiration_time 120 NO delete the parameter from profile 0 NO login/password_expiration_time 20 NO login/password_expiration_time 60 NO login/password_expiration_time 120 NO
但如果要避免更改密码,似乎没什么好办法,但也不没有方法,只是不是针对所有用户: 1,前面有提到更改密码只涉及Dialog用户,所以可以将有需要的用户(如大BOSS)变成Service用户; 2,in the table USR02, just set a date far in the future for the field BCDA1 (password last change). For example, if you want to set it so user SMITH does not have to change his password until 2010, you can use the following SQL script : update USR02 set BCDA1 = '20101231' where BNAME='SMITH' Just replace the values for BCDA1 and BNAME with your own values ! This script is for MS SQL Server + R/3 46B and 46C, but the syntax should not be very different for other database systems and R/3 versions.
An overflow of the lock table occurred when you were setting the loc The lock table consists of several individual tables each of which can overflow individually. The subsequent line indicates which of th tables has overflowed. The lock table is contained in the memory of the lock server (-> enqueue server). Only the total size can be set. This is set with the profile parameter "enque/table_size" in the instance profile of the central locking server. Its value is entered in KB. The setting only becomes effective when the system is restarted. The default size of the lock table is 4096 KB. Please note that when increasing the size of the lock table, a disk requirement of approx. 1.5 x the size of the lock table is necessary in each case in the global directory for the reporting file and in the log directory for the backup file. Before you increase the lock table after an overflow, you should always check whether the overflow resulted from a program error or an operating error.
检查profile parameter "enque/table_size" with RZ10,
Short description: Size of lock table
by this parameter:
Parameter description :
This parameter defines the size of the lock table that is held in main memory by the enqueue server. The lock table contains all of the information about which locks are currently held, and by whom.
The size of the lock table limits the maximum number of lock entries, the maximum number of elementary lock names, and the maximum number of lock owners. In the case of an overflow of the lock table, you should check whether the update server is working correctly, since the lock table can grow in size very quickly if updates stop. If the cause is not update problems, you can use this parameter to increase the size of the lock table. The Computing Center Management System (CCMS) constantly monitors the status of the lock table, and issues warnings if the free space runs short.
The Computing Center Management System (CCMS) constantly monitors the status of the lock table, and issues warnings if the free space runs short. You can view the fill level of the lock tables using the statistics functions of lock management (transaction SM12 -> Extras -> Statistics).
like as other database of IDES, old version support package.
SAP Software Distribution Center
Search in SAP Software Distribution Center
Advanced Search
Change Search Method to All terms, default Context is restriction, change to no restriction, Max Search Result to 1000, select all the search object object, You will find you want to search. Good luck!
二是在激活DDIC object时出错,报错SQL error 2812 occured: Could not find stored procedure 'sap_get_object_type'.
设想:可能是错误的安装删除了SQL procedure
在现象二的帮助里,有The stored procedure must be created in the database. To do this, follow the instructions in SAP Note 460268.
Note Language: English Version: 1 Validity: Valid from 14.12.2001 Summary Symptom The following error message is displayed in the status bar or written to a log file when executing a DDIC function: SQL error 2812: Could not find stored procedure ... More Terms MSSPROCS Cause and Prerequisites As of Release 6.20, the access to the database for the return of system catalog data is executed with stored procedures. These are called in function modules of the SFMSS_SYSCAT group. If such a stored procedure is missing, the above SQL Server error message is issued. It is then transferred to the status bar or the log via the functions modules. Solution Solution Proceed as follows: o Execute the MSSPROCS report in SE38. o Choose the version of your SQL Server as the Database Release value and confirm with Enter. o Select the missing stored procedure in the table control. o Choose "Start". A log must be displayed notifying you that the procedure was successfully executed.
究根道底就是虽然用户解锁了,只要用户还没用正确的密码再次尝试登录前,作为管理员的你在SU01之类的程序看这个用户时,你会发现这个用户的状态居然是Password logon not allowed(too many failed logons),其实只需要用户的一次正确登录,这个状态就会清零(这就是cause of puzzle);如果用户再次用了错密码,要么找你,要么等一天再试,你说用户会选什么?
The following pronunciations are based on an approximation of U.S.
English. An understanding of U.S. English may be needed to understand
how to interpret a particular pronunciation rendering. If you know of a
term in information technology that people often stumble over or
mispronounce, please send us an e-mail and let us know!
Note:
In writing, many style editors prefer that the spelled-out version of a
term should be used in the first written occurrence of a term in an
article (for example, "wireless local area network (WLAN)" instead of
just "WLAN" or even "wireless LAN"). Thereafter, the abbreviated form
can be used.
In pronouncing an abbreviation or reading it
aloud, the pronouncer may want to convert the abbreviation into the
long form for the understanding of a listener (for example, reading
"wireless LAN" for "WLAN").
SAP server hung by "ERROR => New Process with the same PID".
I noticed the server was hung by unkown reason on 08:40AM today morning, so I decided to restart sap to solve this case ASAP. After that, I looked back the database log, system log and the other related files to find what happen, and found the clew in the dispatcher's trace files, "ERROR => New Process with the same PID". This error happened on almost dispatchers, so there was no dispatcher to handle user's session, then we got the server was hung at that time.
I Thu Jun 05 08:56:01 2008 I *** ERROR => New Process with the same PID (2732, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (7076, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (6056, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (7076, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (4112, Aktion: 1 [semnt.c 1920] I I Thu Jun 05 08:56:02 2008 I *** ERROR => New Process with the same PID (948, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (3900, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (6032, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (3900, Aktion: 1 [semnt.c 1920] I *** ERROR => New Process with the same PID (3900, Aktion: 1 [semnt.c 1920]
I checked SAP's note with the key word, and found a note named "Note 920530 - Error Message in Trace: New Process with the same PID ", this note is valid since 07.08.2007, and maybe we should consider to apply the last kernel patch on the server.
if you have a SAP release 4.7 or higher then use transaction sm36 ->
standard jobs button -> default scheduling.
This will create all the needed housekeeping jobs you need.
Or, with transaction ssaa, Overall vien, Execute,
Installation Follow-Up Work, Basis Settings, Scheduling Necessary Background Jobs
Most consultants just schedule the STANDARD jobs with SM37 (or SSAA), without checking any related SAPnotes.
See below latest overview.
Best regards,
Stefan
### R/3 JOB OVERVIEW
Job name : SAP_REORG_JOBS
Program : RSBTCDEL2
Variant : Yes
Parameters variant : 7 days (good value, but check in company)
Frequency : Daily
Description : Delete batch job logs
WARNING: Do not schedule job with program RSBTCDEL; much more jobs are deleted; see note 837691.
Job name : SAP_REORG_SPOOL
Program : RSPO1041
Variant : Yes
Parameters variant : 7 days (good value, but check in company)
Frequency : Daily
Description : Delete old spool requests.
Job name : SAP_SPOOL_CONSISTENCY_CHECK
Program : RSPO1043
Variant : Yes
Parameters variant : 7 days (good value, but check in company)
Frequency : Daily
Description : Spool data (TemSe) consistency check.
NOTE: Job must be scheduled an hour after SAP_REORG_SPOOL.
Job name : SAP_REORG_BATCHINPUT_<CLIENT>
Program : RSBDCREO
Variant : Yes
Parameters variant : 5 days (good value, but check in company)
Frequency : Daily
Description : Delete successfully processed BIM sessions and their logs from the TEMSE table.
WARNING: Job must be scheduled when no other jobs are running.
NOTE: Job must be scheduled for all customer clients (meaning each individual client).
Job name : SAP_REORG_ABAPDUMPS
Program : RSSNAPDL
Variant : Yes
Parameters variant : 30000 / 500
Frequency : Daily
Description : Delete short dumps from SNAP table.
Job name : SAP_REORG_JOBSTATISTIC
Program : RSBPSTDE
Variant : Yes
Parameters variant : 30 days
Frequency : Monthly
Description : Delete runtime statistics.
Job name : SAP_COLLECTOR_FOR JOBSTATISTIC
Program : RSBPCOLL
Variant : No
Parameters variant :
Frequency : Daily
Description : CCMS: Collector for Background Job Run-time Statistics
Job name : SAP_REORG_PRIPARAMS
Program : RSBTCPRIDEL
Variant : No
Parameters variant :
Frequency : Monthly
Description : Reorganization of Print Parameters for Background Jobs (see note 307970).
Job name : SAP_REORG_XMILOG
Program : RSXMILOGREORG
Variant : Yes
Parameters variant : 7 days
Frequency : Weekly
Description : Reorganization of XMI interface loggings.
Job name : SAP_CCMS_MONI_BATCH_DP
Program : RSAL_BATCH_TOOL_DISPATCHING
Variant : No
Parameters variant :
Frequency : Hourly
Description : Starts CCMS Method Dispatching in the background.
Job name : SAP_UPDATE_RECORDS
Program : RSM13002
Variant :
Parameters variant :
Frequency :
Description :
WARNING: Do not schedule this job !!!
Following parameter is set: rdisp/vb_delete_after_execution=1
types: beginof dswpclientkey,
INSTNO type num10,
DBID(3),
BUNDLE_ID(8),
SERVICE_KEY(40), endof dswpclientkey. *data: dswpclientkey_w type standard table of dswpclientkey. DATA: P_VALUE(10),
P_INSTNO(10).
PARAMETERS: P_SID(3),
P_SYSNO(2),
P_SERVER(15).
START-OF-SELECTION. PERFORM GET_SP_VALUE USING P_SID
P_SYSNO
P_SERVER
P_INSTNO CHANGING P_VALUE.
END-OF-SELECTION. WRITE P_VALUE. *&---------------------------------------------------------------------* *& Form get_sp_value *&---------------------------------------------------------------------* * text *----------------------------------------------------------------------* * -->P_PF_SID text * -->P_PF_SYSNO text * -->P_PF_SERVER text * <--P_PF_VALUE text *----------------------------------------------------------------------* FORM get_sp_value USING P_PF_SID
P_PF_SYSNO
P_PF_SERVER
P_PF_INSTNO CHANGING P_PF_VALUE.
During the remote client copy with profile SAP_USER, just saw the copy files was 90 of 90, so i considered the copy finished and tried to restart the instance caused by profile modified. But When I restarted and tried to logon, the system responding message with "The client is currently locked against logon" .
Logon client 000 with DDIC, run SCC4, the system remind the clinet 004 have lock due to copy failed.
Delete the lock and then logon client 004 and continue the remont client copy, wait the statistics said successful.
Before we can deliver any services, the
latest version of the SAP Service tools must be available in your system.
The last run of report RTCCTOOL was 11.04.2008. During the check, the tool
detected SAP Notes that were rated RED or YELLOW.
Recommendation: Run
report RTCCTOOL (review SAP Note 69455) and
implement the recommendations.
1. [Note 69455 ] Addon ST-A/PI 01K_ECC600 Description "Servicetools for Applications Plug-In" for ERP 2005 / ECC 6.00 Implementation From http://service.sap.com/supporttools download the addon file ST-A/PI 01K_ECC600. Upload the file to transaction SAINT 'Installation package > Load packages > From Frontend' and install as per note 69455 . Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'.
2. Note 539977 Description Addon supportpackage level 6 for ST-PI 2005_1_700 for 7.00 [patches up to level 6 for Basis tools for services] Implementation Open http://service.sap.com/supporttools-> ST-PI 2005_1_700 ->Supportpk. Add patch SAPKITLQI6 (and predecessors if not yet implemented) to download basket. Release basket via Maintenance optimizer. Upload from frontend into transaction SPAM, define a queue and import the queue.
You can move tempdb files by using the ALTER DATABASE statement.
1.
Determine the logical file names for the tempdb database by using sp_helpfile as follows:
use tempdb go sp_helpfile go
The logical name for each file is contained in the name column. This example uses the default file names of tempdev and templog.
2.
Use the ALTER DATABASE statement, specifying the logical
file name as follows:
use master go Alter database tempdb modify file (name = tempdev, filename = 'E:Sqldatatempdb.mdf') go Alter database tempdb modify file (name = templog, filename = 'E:Sqldatatemplog.ldf') go
You should receive the following messages that confirm the change:
Message 1
File 'tempdev' modified in sysaltfiles.
Delete old file after restarting SQL Server.
Message 2
File 'templog' modified in sysaltfiles.
Delete old file after restarting SQL Server.
3.
Using sp_helpfile in tempdb will not confirm these changes until you restart SQL
Server.
please check if the SAP parameter "login/no_automatic_user_sapstar"is set to 0
Parameter : login/no_automatic_user_sapstar
Short description: Control of the automatic login user SAP*
Parameter description :
If the user master record belonging to user SAP* is deleted, it is possible to re-log on with SAP* and initial password PASS. SAP* then has the following attributes:
- The user has all authorization, as authorization checks cannot be executed.
- You cannot change the standard password PASS.
Using profile parameter login/no_automatic_user_sapstar, you can deactivate the special attributes of SAP*.
Work area: Logon
Unit :
Default value: 1
Who is permitted to make changes: The customer
Limitations for operating systems: None
Limitations for database systems: None
Other Parameters Affected or Dependent:
The profile parameter login/no_automatic_user_sap* supported in SAP Releases 3.0 and 3.1 no longer have any effect.
is still only supported in Release 3.1.
Valid entries, formats, areas : 0, 1
0: Automatic user SAP* is permitted 1: Automatic user SAP* is deactivated
You want to use parallel processes for a client copy.
Summary
Symptom
You want to use parallel processes for a client copy.
Other terms SCCL, SCC5, SCC9Reason and Prerequisites1. How do I use parallel processes?2. How many parallel processes should I use?3.
Several clients must be copied into a system.Is it possible to run two
copies in parallel?How do I get the shortest runtimes?4. Why are no parallel processes used or why are less parallel processes used than required?5. How can I terminate a copy with parallel processes?6.
Why are some processes in the process overview (transaction SM50) or in
the Systemwide Work Process Overview (transaction SM66) not active or
not displayed?7. How many processes are used on the servers and which process has copied which table?8. The copy was scheduled in the background.Why does the client copy use dialog processes?9. The copy was scheduled on a specific server.Why are also processes active on other servers?10. Why does a change of the RFC server group not affect a current copy?11. Which data throughput can I can expect?12. Do the settings for the parallel processes of the client copy also apply to the client transport?Solution1.
You can select an existing RFC server group and the maximum number of
processes (not counting the main process) via the "Parameter for
parallel processes" button or the "Go to -> Parallel processes" menu
option.
From there, you can also go to the RFC
server group maintenance (transaction:Create an entry with the same
name for each application server to be used.For more information, refer
to the documentation (SAP Library) of the SAP Web Application Server
under:
Computing Center Management
System (BC-CCM) -> Background processing -> Parallel processing
of jobs with asynchronous RFC -> Define RFC groups for parallel
processing jobs
2. Two processes per available database CPU is a good guide value.
For
a remote copy, we even recommend that you use three processes per
target database CPU.Parallel processes are especially useful with
remote copies as you can use more different resources (source/target
database, source/target application server and network)
simultaneously.This applies in particular if a conversion is required
due to different character sets (code pages) or system formats (Little
or Big Endian) where CPU consumption on the application server
increases considerably.
3. You cannot use two copies from the same source client simultaneously. This may cause problems in the address management.
You
can use two copies from different source clients simultaneously.
However, we do not recommend this as the processes may lock each other.
Instead of executing several copies
simultaneously, you should preferably schedule the copies one after the
other and use parallel processes.
To avoid
disorganization in the database, you should, if necessary, delete all
target clients in advance.You should then reorganize the database and
update the statistics.The clients are then structured with ascending
client number.
We recommend that you proceed, for example, as follows:
1. Schedule the first copy in the clients with the smallest client number with a start of 10 minutes.
2. Determine the name of the background job via the SM37 transaction.
3. Schedule the second copy as successor of the first job and so on.
4. There are several possible causes:
Parallel
processes are only used during the actual copying phase.They are not
used, however, during the analysis and postprocessing phases.
The
resource management only assigns a limited number of processes to the
client copy.For more information, refer to the documentation (SAP
Library) of the SAP Web Application Server in the "Automatic protection
against capacity overload of resources" section of the following
document:
Computing Center Management
System (BC-CCM) -> Background processing -> Parallel processing
of jobs with asynchronous RFC
Towards the end of the
copying phase, the number the processes is reduced as the worklist is
divided but individual processes are still copying very large tables.
To
avoid this scenario, a "SINGLECOPY" copy function was introduced as of
WAS 6.10. Refer to note 446485 for more information.
5. The
processes monitor each other and restart terminated processes. You can,
therefore, not simply terminate the client copy by terminating the
processes. You must inform the client copy in advance that you want to
terminate the copy.
To terminate the copy, use
the 'Cancel copy' button in the SCC3 transaction of the system log
display.The processes auto-terminate once they have finished the
current task or the copying of the current table.After issuing the
Cancel command via the log display, you can also terminate the
processes manually (for example, via the process overview (transaction:
6. The relevant processes try to set a lock entry for a common
resource (for example, for the log header in the CCCFLOW table or for
the "CCLOG" file log).
If the first attempt fails
because the resource is already used by another process, the system
will repeat the action in intervals of one second until the relevant
resource is released.While the system is waiting for the resources, the
processes are not displayed.You can display the relevant lock entries
via the lock management (transaction:
7. you can display it,
for example, with the SE16 transaction. The PROCESS field contains the
application server and the number of the process. The same information
is also displayed in the file log of the copy at the beginning of the
copying phase.
The information which table was
copied by which process (STATUS = 'P') or which tables are contained in
the worklist of the process (STATUS = 'A') is listed in the CCSELTAB
table.
To monitor all current actions, you should preferably use the global work process overview (transaction:
8.
Only the main process of the client copy can use a background
process.The parallel processes are controlled via a RFC server
group.RFC processes, however, are always dialog processes.9.
The servers specified in the RFC server group are only used for the
additional parallel processes.They are not affected by the scheduling
of the main process on a specific server.10. The RFC server
group is only analyzed once at the beginning of the copying
phase.Changes, therefore, are only activated in a new copy or after a
RESTART. You must, therefore, terminate the current copy after step 5
and execute a RESTART if you want to change the distribution of the
processes.11. If the target client is empty and the source
database in good shape (updated statistics, little disorganization),
you can expect a throughput of approximately 500MB to 1GB per hour and
process on a modern database.That is, approximately 4GB to 8GB with 4
CPUs and 8 processes.12. No. The client export
(transaction:SCC8) only creates a transport request which then is
exported by the tools of the tp/R3trans transport programs.The settings
for the parallel processes of the client copy do not affect this
process nor the postprocessing in the target client (transaction:
2008年2月19日,微软公司宣布将向全球大学
生免费赠送SQL Server 2005,Visual Studio
2005 and 2008, Windows Server Standard Edition,
XNA Game Studio
2.0及其Expression的套装产品,此次赠送还将惠及到高中生
。
ICNV- Append old change log into LXP database(PRD)
1, Backup LXP; 2, ICNV; 3, During the append period, consultant found the G drive had no free space for log file to extend, because bulk insert data would cause the log file size increase quickly, you can see the log file size was 197GB on 2008/02/16, so I decided to add more space(100GB) from SAN to keep the append procedure to finished after discuss with consultant. That means the server use the SAN sapce is 1.4TB now, we should consider this status highly if we want to do some action on SAN environment on future like as snapclone, VOL extend, SAN schema change, etc. 4, The change document records have been transferred to the production system on 0:20AM 17-Feb-08; 5, Backup LXP, 6, Shrink log file.
BTW, User complained SAP can not save and update, lick QT update and Material create during the icnv period. That's OK.
User
complained SAP can not save and update, lick QT update and Material create.
Telnet
is now made an optional component in Vista and Longhorn Servers. This
means if you type telnet in command shell, you will be out of luck.
Why have we done it so?
As time has passed, fewer users use telnet. Thus, to decrease the
foot print as well as the attack surface, we decided to make it an
optional component.
Great, now how do I get telnet client/server working again?
Vista -
Use software explorer or Click Start, ControlPanel, Programs, and then Turn Windows Features on or off. In the list, scroll down and select Telnet Client. Click OK to start the installation.
The SAP Service Marketplace contains, in addition to the actual Support
Package file for the SAP GUI (for example, GUI610.EXE), another file
with a "pdb" extension (for example, 610_PDB.EXE). The PDB file is
ONLY required when requested by SAP Support (it contains important
debugging information for SAP GUI "crashes"). The OSS message issued
with each problem contains more information on how to handle the PDB
file.