How to perform system trace for authorization

How to perform system trace for authorization

1.Execute t-code ST01

2.Check authorization Check (You may select more)

3.Click on Trace on (Make sure to turn it off  after you are done)

4.Now ask user to perform their task.

5.If there is more then one app server, go tcode SM51

6.*Then double click on the app server 

7.*Then repeat step 1 to 3 

8.Remember - Once user completed the test, turn of all trace from ST01

9.Now, click Analysis

10.Filter the trace like below (select what you need)

11.For authorization issue ,anything above RC=0 means there is missing authorization

How to Stop a running Transport

1.stms_import
2.Select transport
3.double click on transport or click on import monitor.
4.Right click your transport and delete entry.

Transport truck is hanging in SAP

Transport truck is hanging in SAP

Try Below checks

1.       SA38 > Reschedule Job RDDIMPDP via program RDDNEWPP or RDDPUTPP

2.       SM59 > Test connection and authorization for RFC TMSADM@SID. Give sap_all profile to user  TMSADM

3.       Go to OS level and Kill tp.exe process

4.       SA30  > Clear table TRJOB and TRBAT

5.       Or enter this parameter in STMS > System Over view > Select System > Transport Tool >

6.       Then add SYSTEM_PF with value \\<host>\sapmnt\<sid>\SYS\profile\default.pfl

7.       Back and update configuration (CTRL-F2)

RSTPTEST

Go to SE38 and execute RSTPTEST program to know TP status and STMS configuration check 

Transport Control Program TP Ended With Error Code 0247

Transport Control Program TP Ended With Error Code 0247

Target system was not defined in TMS configuration. 

After re-configuration the TMS it is working fine. 

SAP Router working condition checks

Logon to the SAP system which is already configured for SAP Router Settings.

Check – 1

SM59 –> open the defination SAPOSS –> Press the button “Connection Test”

If result returns with same as the picture below , then we can say SAProuter is working for us…

Check – 2

Open the service.sap.com web site, select the releated SAP system and check the “Connection” status under the“SAPRouter Status” area

If result is “Connected” then it means that SAPRouter is working….

Check – 3

Checking the UNIX systems

How To Change SAP Router Configuration File - Adding New Port

Scenario: 
SAP Global team unable to remote access your Solution Manager and require additional port to be configure on the SAP router configuration file.

Steps:

1) SAP Support team having problem to remote access the Solution Manager page (HTTP Access) for further remote support.

2) Initial finding shown the connection is ok.

3) Further finding shown, additional port required to be configure on the SAP router for HTTP access.

4) Sample of the configuration settings required.

5) To perform any changes on the SAP router configuration file, stop the SAProuter service.

6) Locate the "saprouttab" file (ex: c:/usr/sap/saprouter) and add the required ports.

7) Once the "saprouttab" changes complete, restart the "SAProuter" services.

8) SAP Global team should be able to remote access the page by now.

MAXDB Service Not Starting

Check for  'Application Event Log`in Windows' event viewer.

How to Reset "ddic" Password with SAP*

How to Reset "ddic" Password with SAP*

Scenario:

You have forgotten the ddic password on client:000 during patch activity and do not have any other login to reset the password.

The solution is to use the default "SAP*" user to reset the password

Steps:

1) Login to any other client -> execute TCODE: RZ10 -> change the parameter: "login/no_automatic_user_sapstar =0"  (this is to allow "SAP*" to access the system)

2) Save and activate the profile

3) Restart the SAP services

4) Now login into the client:000 with user: "SAP*" and password: "pass"-> execute TCODE: SU01 -> Reset the "ddic" password

5) Repeat the same step as step 1 and 2 by changing the "login/no_automatic_user_sapstar =1" (to disable "SAP*" access to system)

6) Restart the SAP services

7) System is secure and "SAP*" no longer accessible

Others:
1) SQL command to check whether "SAP*" exist in table: USR02

SQL>Select * from SAPSR3.USR02 where bname ='SAP*' and mandt='000';

Memory usage Grows in EP

Memory usage  Grows in EP

Web dynpro applications do not terminate when the browser is closed or navigation to the other applications /pages are triggered.Thus memory usage grows  as well as backend connections thus database locks keeps open until http session timeout occurs

A pop up blocker  e.g delivered with tool bar , is active and does not allow to open hidden browser window that sends the request to the SAP Web application server.Therefore termination session not reveived from the server.

Sol:

Deactivate that pop up blocker for those url that points to the SAP Web application servers and/or the EP

Partner Profile Configuration in SAP

Partner profile configuration:

WE20 General  t-code view

2.Partners could be SAP System or trusted non-sap systems.

Each partner would be assigned a partner number .The details of the agent are needed as and when you are creating the partner profile. A partner can receive data (set through inbound parameters) and send data (outbound parameters).

The outbound parameters are to be filled as follows:

Partner number, partner role, message type, receiver port, output mode (either transfer idoc immediately or collect idocs),basic type are mandatory. In case, you use the same message type for two different processes and there would be difference in data transmitted use message code and message function. This would act as a single point of differentiating the path of the code to be followed.

Pack size is to be used in case of ALE and when there are a bunch of idocs to be transmitted .In case you are using older release of idoc,then you need to mention this in seg release in idoc type .Also in that case, you need to fill segment application release version as well. In case, there is message control inputs, one needs to fill in the message control tab. The application, message type and process code needs to be updated. Rest of the tabs just adds information to the parameters. One can add as many outbound parameters or message control inputs as needed.

In case  of inbound process, needs to      just pass the process code .This one significant difference between inbound and outbound.

Note:Before creating partner profiles ,partners needs to created in SALE T-code .to Set partner type:

To know schema used in SAP

SQL Command to show schema used

SQL>select distinct owner from dba_objects;

Test FTP Connection On SAP

Test FTP Connection On SAP

1.Enter the t-code sa38 and enter the program name :RSFTP002

2) Enter the FTP username, password, IP, FTP command to be execute and the RFC connection. Click the "Execute" button.

3.Default RFC connection for FTP ,it will be there in TCP/IP connection

Ports required for FTP Connection

Dispatcher  3200--- 3299

Gateway 3300-3399

Secure Gateway 4800-4899

DMZ in SAP

Demilitarized zones in SAP while setting up network topology

SCC4 Change logs in SAP

Got o Se14 and view table T000 to get SCC4 change logs.

Device type cannot be switched error in printer SAP

Device type cannot be switched error in printer SAP

Change the Access Method or else  change the device type to some other , it will work.why because given specifications not supporting print.

SSL and SNC

SSL(Software Security Layer)  for internet protocols (HTTP for example)
SNC(Secure Network Connection) for SAP Protocols(RFC for example)

Display of the System configuration with SAP NWA

Display of the System configuration with SAP NWA

Configuration Management → Infrastructure → Java System Properties or via the quick link

/nwa/sys-config.

Names of the VM Parameters of the type Memory

Display name in the Config Tool Technical name

initialHeapSize Xms

maxHeapSize Xmx

permSize XX:PermSize

maxPermSize XX:MaxPermSize

newSize XX:NewSize

maxNewSize XX:MaxNewSize

newRatio XX:NewRatio

globalArea Xps

Bootstrap VM parameters

If you encounter problems with bootstrap VM parameters you need to raise a OSS message.

SAP Settings

SAP Settings

Number of Server processes

Runtime filters

Shared memory

Configuration of managers

Configuration of services

VM parameters

   Memory parameters

   System parameters

  Additional parameters

Log configuration

Configuration of applications

SAP MMC

SAP MMC provides following functionality

1.Evaluation of logs and traces.
2.Display of Start  profiles, profile parameters and environment variables
3.Displaying of monitoring alerts.
4.Display of information about JVM memory management (Garbage Collector History ,Heap memory)
5.Display of information about the Internet Communication Manager(ICM).

Possible Java stack Log file locations

Possible Java stack Log file locations

dev_jstart

dev_icm

dev_server0

jvm_bootstrap.out

std_server0.out

JSmon

JSmon resides in kernal directory

JSmon can be started using the command

JSmon pf=<SAP Instance Profile>

Load balancing

Load balancing

The SAP Web Dispatcher distributes inbound request across multiple SAP Netweaver As Java instances.

SAP Web Dispatcher

Note on the SAP Web Dispatcher (SAP Note 538405 and 1093023).

Message server profile parameters

Message server profile parameters

rdisp/mshost

ms/http_port

Java Server node couldn't come up in SAP

Java Server node couldn't come up in SAP

This is a known issue which is normally resolved by deleting the files under the "/server[X]/temp/cpt" directory. We are aware of this issue

however there is not much we can do about it since those files get corrupted in various scenarios (for example the system crashes while

the CPT library is writing data to those files and when the socket connection is unexpectedly terminated the files get damaged).

APPLICATION TRACE TRUNCATED

This happens if the XI application has an instance number other than 00

Add a new entry:

Name:xxxxx

Key: provider.servlet.server

Value:http:\\xxxx:XXXXX/

Transport running long time in SAP

Transport running long time in SAP

look for SLOG and ALOG located at oslevel 

SLOG can be viewed from SAP Level go to --->tp system logs and take proper action 

Cluster , Instance , ICM and Server process

The SAP NETWEAVER  as java is stored in the directory W:\usr\sap\<SID>
The instances (JAVA) are each stored in a separate directory

PASz.B . W:\usr\sap\GOD\J00
AAS z.B  W:\usr\sap\GOD\J01

The java part of an instance is stored relative to these instance directories in the directory  ~/j2ee
The server processes are in directory ~/j2ee/cluster in the directories server<n>.

The central services  are located in the directory W:\usr\sap\GOD\SCS02

PAS and AAS in SAP

PAS and AAS in SAP

PAS :Primary Application server

AAS: Additional Application server

Dispatcher

Dispatcher

Distributes the requests to the work processes ,if all processes are busy then request stored in Dispatcher queue.

Work process :Executes Abap code

Message server: is used to exchange messages in SAP netweaver as ABAP and to balance the load in the SAP system with sapnetweaver as abap  and sapnetweaver as  abap+java

Java server processes:are responsible for processesing java servlets and so on.

SAP System that contains SAP netweaver as java has  a central services  instance that contains    a  java message server and enqueue        server .The java message server is used to exchange messages in sap netweaver  as java t balance the load in sap systems without an abap stack.

The java eneque server responsible for lock management in sap netweaver as java.

No Archive log mode in Sql server

 No Archive log mode in Sql server

Set database to simple in properties of database for no archive log mode.

For archive log mode set it to Full in properties of database

Change ARCHIVELOG MODE to NOARCHIVELOG MODE in ORACLE database

Change ARCHIVELOG  to NOARCHIVELOG in oracle database

1. Login as ORA<SID>
2. sqlplus "/as sysdba"
3. select log_mode from v$database; - check if value is still as below:
4. Stop SAP (CI and Apps) and Database using scripts.
5. SQL> startup mount;
6. SQL> alter database noarchivelog;
7. SQL> alter database open;
8. SQL> select log_mode from v$database;

LOG_MODE
------------
NOARCHIVELOG