Full SAP BASIS

End of Transport Queue in stms_import

noreply@blogger.com (Anonymous) — Wed, 07 Jan 2015 13:01:00 +0000

What to do if we get our Transport Reques in End of Transport Queue?

Basically we are getting this, as we have Schedule import job at some fixed duration. Say for example 30 mins, so once it has passed that limit, it will take all those requests which fall in 30 mins bracket & truck (Import) will be started. So whatever next set of requests are there they will come after the end mark, which means those transports are ready for next Interval.

So we don’t need to do anything, this is due to Automatically Import job, so if you don’t want do happen this, then you can remove import job,

How to change auto generated RFCs settings

noreply@blogger.com (Anonymous) — Wed, 07 Jan 2015 12:10:00 +0000

We will open the suto generated RFC (from Tcode SM59) which you want to change.
Now we will go inside the RFC as shown in below screen.

Now we will enter togl

After that we can see that RFC will become editable

Message Server

noreply@blogger.com (Anonymous) — Sat, 07 Jun 2014 20:08:00 +0000

The task of the message server is to inform all the servers (instances) belonging to an SAP System of the existence of the other servers. It can also be contacted by other clients (for example, SAPlogon, RFC clients with load balancing) to get information about load balancing.

The SAP Message Server runs as a separate process mostly on the same host as the central instance.

Only one message server can run on each SAP System.

If the messages server stops working, it must be restarted as quickly as possible, to ensure system continues to operate trouble-free.

Monitoring the Message Server in the SAP System

To monitor the message server, you can use the Message Server Monitor (transaction SMMS) in the SAP System. You can check and change all the important settings, create and view traces, read statistics, and so on.

Monitoring the Message Server from the Browser

You can display details of the servers and logon groups from the Web browser too. To do this, in the URL use the host of the message server and the HTTP port of the message server (profile parameterms/server_port_<xx>).

Monitoring and Testing the Message Server at Operating System Level

To monitor the message server at operating system level you need access to the host on which the message server is running. You can log on here with user <sid>adm.

At operating system level there are various programs available, which are delivered with the standard system.

You will usually find the test programs in the executable directory /usr/sap/<SID>/SYS/exe/run.

SAP Web Dispatcher

noreply@blogger.com (Anonymous) — Sat, 07 Jun 2014 20:02:00 +0000

Purpose

The SAP Web dispatcher lies between the Internet and your SAP System. It is the entry point for HTTP(s) requests into your system, which consists of one or more Web application servers. As a "software web switch", the SAP Web dispatcher can reject or accept connections. When it accepts a connection, it balances the load to ensure an even distribution across the servers.

You can use the SAP Web dispatcher in ABAP/Java systems and in pure Java systems, as well as in pure ABAP systems.

Recommendation

It is also beneficial to use the SAP Web dispatcher, if you do not need security functions (entry point in the DMZ, SSL, URL filtering), but you simply want to balance the load between several SAP Web AS instances.

Introductory Comments

The SAP Web dispatcher is recommended when you use an SAP system with several SAP Web Application Servers for Web applications.

The SAP Web dispatcher is a program that you can run on the machine that is connected directly to the Internet. It requires minimal configuration - you just have to enter the following data in the profile file:

· Port, on which the HTTP(s) requests are to be received (parameter icm/server_port_<xx>)

· Host and HTTP port of the SAP message server (parameter rdisp/mshost and parameter ms/http_port)

Example

If you want to be able to call the Web application externally, for example using the URL www.shop.acme.com, this host name must be mapped internally to the SAP Web dispatcher. This then forwards the HTTP(S) request to a suitable SAP Web AS.

Functions

The SAP Web dispatcher performs the following tasks:

· Selects an appropriate application server (persistence with stateful applications, load balancing, ABAP or Java server), see Server Selection and Load Balancing Using the SAP Web Dispatcher.

· Filters URLs – you can define URLs that are to be rejected, see SAP Web Dispatcher as a URL Filter

· Depending on the SSL configuration, forwards, terminates, and (re)encrypts requests. See SAP Web Dispatcher and SSL

Restrictions

The SAP Web dispatcher is only useful in the Web environment. In the classic SAP system, load is balanced by the message server.

The SAP Web dispatcher forwards only incoming HTTP(S) requests to the Web application server and the response is then returned to the client.

Outgoing requests (such as requests to a different SAP Web Application Server) are not sent via the SAP Web dispatcher. They are sent via the proxy server for the appropriate intranet.

Source: https://help.sap.com/

Why do we do Index rebuild?

noreply@blogger.com (Anonymous) — Sat, 07 Jun 2014 20:00:00 +0000

When an indexed field in a table is changed repeatedly, the data is deleted from the index and re-inserted at a new block in the index. The new entries are always added to the right side of the index tree and therefor deletion is relatively to the left. When the index elements are deleted and added repeatedly, the left side of the index tree tends to be sparse and the right side keeps growing.
Fragmented index results in increased usage of database space and more blocks being read into the buffer. This can be avoided by rebuilding the index.
One can measure index fragmentation using the report RSORATAD or using DB02 --> Detailed Analysis --> Enter Index --> Detailed Analysis --> Analyze Index --> Storage Quality. If storage quality is less than 50% you may need to reorg the index.
If you wish to run an analysis on all the indexes, run the report RSORAISQN. Check SAP note 970538 for more details for more information on the restriction with using this report. Do not run the report without reading the note. You can also get an idea on the amount of fragmentation by comaring the size of the table and the index. If the size of the index is larger than that of the table, the index is fragmented.
Source: sapnwnewbie.blogspot.com

Do we need to shutdown database also during kernel upgrade?

noreply@blogger.com (Anonymous) — Wed, 21 May 2014 03:11:00 +0000

Generally, Kernel Upgrade means upgrade of DB Dependent files and DB InDependent files in your kernel directory.

The DB Dependent files consist of DLLs in Windows and similar other library files for other OS as well. So, logic, common sense and SAP recommends that Database should be down when you are doing a manual* Kernal Upgrade.

Lets say, you have not shut the DB and some file from kernel directory is in use. You will just get an error - "File is in use".

Again, the recommendations here is stop the DB, so that the file is no longer in user, instead of figuring out which PID is using that file and then just killing that process.

So, bottom line - get downtime approval for SAP and DB for Kernel Upgrade.

But stopping of database is not mandatory. Just stop Instance & services.

If there is no database activity like online backup going on, you can as well stop database since there is no user activity.

- If you have Java, Using JSPM for Kernel Upgrade is Generally a good option

Check status of Business Process Engine (BPE) via SWF_XI_ADM_BPE_DISP

noreply@blogger.com (Anonymous) — Sun, 20 Apr 2014 12:55:00 +0000

The Business Process Engine (BPE) executes integration processes at runtime
Recently I got an issue that one of our XI production system’s Business Process is not working correctly.
So to check the Business Process status we can use the TCode : SWF_XI_ADM_BPE_DISP or SWF_XI_ADM_BPE
Below is the screenshot of tcode SWF_XI_ADM_BPE_DISP
Here in the below screen, we can see that all the BPE components are running (green status) along with the BPE status.

The status display shows the status of the BPE and its components.

Green: Component running
Red: Component stopped
Amber: Component currently being stopped or started

This can take a few minutes. Wait until the status display changes.

Error icon: Error when starting or stopping the component.

You can decide whether you want to continue with the procedure or terminate. For example, if a component cannot be stopped, you can decide whether you want to attempt to stop the BPE again, or whether you want to restart the BPE completely.
We need to have below 2 roles for accessing these tcodes:

SAP_XI_BPE_MONITOR_ABAP
SAP_XI_BPE_ADMINISTRATOR_ABAP

We can also check the BP status from portal from RWB
http://<host name> <j2ee port>/rwb
Go to Component Monitor in Runtime Workbench. Now select Integration Server > Business Process Engine

Transport Tables form one SAP System to another SAP System

noreply@blogger.com (Anonymous) — Thu, 27 Mar 2014 14:20:00 +0000

Transport Tables form one system to another
Lets say we have to transport below mentioned systems from one SAP system to another.
/SAPAPO/ATYPES
/SAPAPO/ATUID
/SAPAPO/ATYPEST
Note: Client must be opened for this
Method 1:
Go to TCode: /nsm30
Enter the table name and keep all the settings as it is.

After entering click on display button

Now go to the change mode
Select all the alert types

Go to Table View menu and click Transport

Now it will prompt for transport request.
Either select the “Own Request” which is already created by you else create a new transport request right now (depending on the condition)

Click Include in Request

Now we can see a message as shown below.

Then Save

*****************************************************************************************
Method 2
Go to SE10 TCode
Create a new transport

Double click and go inside the TR as shown in below screen.

Add program ID, Object Type and Object Name manually.
We can check table via SE16

Click on execute button present on top.

Now we can select all by giving field as *012*

So it means that it will take all those fields who is having mandit as 012.

How to delete released Transport Request from SAP system?

noreply@blogger.com (Anonymous) — Mon, 24 Mar 2014 20:07:00 +0000

Remove released TR
Go to TCode SE16

Enter table name E070
Enter Transport Request number and click execute button

Select the Transport Request and double click and go inside

Write /h and hit enter
For going to debugging mode

Then we get a notification that ‘Debugging switched On”

Select TRSTATUS and hit enter

Now double click on code

Now it will be shown here

Edit it and change SHOW to DELE (note: it’s not DEL, its DELE)
So now selected transport request got deleted from the system.

Sample SAP BASIS Resume

noreply@blogger.com (Anonymous) — Sat, 08 Feb 2014 21:25:00 +0000

I have attached one sample resume (only for information purpose)
SAP BASIS Consultants can create their own resume by referring this resume.

Summary:

Overall 5 years of experience in IT industry out of which nearly 3.3 years of experience in SAP-R/3 environment as a SAP BASIS Administration..

Skills @ SAP R/3:

§ Installation of SAP servers and post installation activities

§ Applying Support packs and Kernel Up gradation

§ Generating Solution manager key for the Landscape as required

§ Time based and event based Scheduling of background jobs and monitoring them

§ Client Administration including client copy / export / import / delete

§ User Management like User Creation, deletion of user, users locks

§ Analyzing of missing authorizations and assigning Roles to users

§ Profile maintenance through PFCG

§ Transport setup and management

§ Download and applying Support Patches and SAP Notes

§ Performance monitoring and fine tuning

§ Maintaining Profile parameters

§ SAP spool configuration

§ Analyzing short dumps

§ Transports in ABAP and Java Environments(Using SDM)

§ Performing Pre & Post System Refresh activities

§ CUA Configuration

§ Core Knowledge in DBA

§ Publishing Internal ITS

§ Installing WebAS Java as add-on

§ Worked with Configtool and Visual Administrator

§ Apply java patches through SDM

Academics:

Ø M.I.T MAHE, Manipal In the Year 2003

Ø B. Sc Nagarjuna University In the year 2000

Technical Skills:

Ø Operating System Windows9x/NT4.0/2000/XP/2003, Unix

Ø ERP SAP R/3 4.6C/4.7E, ECC 5.0 and ECC 6.0

Ø New Dimensional Products of SAP Solution Manager 4.0

Ø RDBMS Oracle, Ms SQL

Job Profile:

Ø SAP Basis Consultant Infotech Enterprises Ltd, Hyderabad June 2008 to present.

Ø SAP-Basis Consultant Intelligroup, Hyderabad Jun-06-May 08

Ø Systems Engineer Softrain Maintenance Systems, Hyderabad Jan 05-May 06

Ø Lab Faculty Shri Chaitnya Enterprises, Bapatla Dec 03- Dec 04

Work Experience:

Project#1 Get Engine Manufacturing

Client Pratt & Whitney, Canada

Role SAP Basis Consultant -Support

Organization Infotech Enterprises, Hyderabad

Duration June 2009 to till date

Role Description

Created users and assigned the roles to the users.
TMS configuration and Change request management.
Monitoring Background jobs, re-scheduling, canceling long running jobs
File system monitoring
Spool & print management
Checking Failed update record & system logs
Short dump analysis, managing lock entries, lock/unlock transaction codes, displaying and monitoring of Database and Application servers, managing user sessions

· Configured Operation Modes and Profile parameters maintenance

Implemented Kernel Upgrade and Applied Support Packs
Set up Central User Administration (CUA) to manage multiple systems/clients

· System Refresh Activities, JAVA Schema Export & Import

· Package deployment using SDM

· Trouble shooting and monitoring with printers and system hardware

· Contribute to the documentation for the various tasks that we perform for daily monitoring

Project#2 Get Engine Manufacturing

Client Pratt & Whitney, Canada

Role SAP Basis Consultant- Implementation

Organization Infotech Enterprises, Hyderabad

Duration June 2008 to May 2009

Role Description

· Installed Dev -> QA -> Prod systems

- Sandbox -> Refreshed from production every month

- QA -> Refreshed from production system every month

- Training System -> Refreshed from production System on Requirement base

- Environment: ECC 6.0, Oracle 10g, Windows

· Performed System refresh activities for the landscape.

Performed Post installation activities for the system landscape.
Change request transport, Transport management
Monitoring Background jobs, re-scheduling, canceling long running jobs
File system monitoring
Providing Missing Authorizations to the users
Spool & print management
Checking Failed update record & system logs
Short dump analysis, managing lock entries, lock/unlock transaction codes, displaying and monitoring of Database and Application servers, managing user sessions
Handling Transports from one System to another System. (DEV, QA & PRD)

· Maintaining of Operation Modes and Profile parameters

Implemented Kernel Upgrade and Applied Support Packs
Set up Central User Administration (CUA) to manage multiple systems/clients
CUA for all systems from SOLMAN

· Contribute to the documentation for the various tasks that we perform for daily monitoring

· System Refresh Activities, JAVA Schema Export & Import

· Package deployment using SDM

· Trouble shooting and monitoring with printers and system hardware

Project#3 GCM

Client GE Capital Modspace

Role Associate SAP Basis Consultant

Organization Intelligroup, Hyderabad

Duration June 2006 to May 2008

Role Description

§ Day to day monitoring of systems and reporting to the Management

§ Monitoring application servers up and running

§ Monitoring work processes and their statuses from time to time

§ Maintaining the instances using operation mode and assigning time intervals

§ Monitoring the background jobs and their status

§ Scheduled standard background jobs periodically

§ Monitoring Logged Users locally and globally

§ Monitoring activities like system status, analyzing system logs, system traces, ABAP dumps, SAP System Buffers and Database Buffers, workload analysis

§ Reporting problems like Startup, Background jobs, updates, System status, work processes, System logs, ABAP dumps, Memory issues

§ Creation of Single and mass users

§ Performing User comparison and Utilizing SU53 to optimize missing Authorization

§ Creating and testing the RFC destinations

§ Client administration which include creation, deletion, export and import

§ Maintaining system profile parameters and Dynamically customizing profile parameters

§ Created system messages when downtime is scheduled

§ Involved in applying of SAP Support Patches, R/3 Kernel Patches and upgrade of other SAP executables for fixing SAP bugs and smooth system runtime.

Sort Files in SAP Directory (OS Level, UNIX)

noreply@blogger.com (Anonymous) — Sat, 08 Feb 2014 20:56:00 +0000

Below are two commands to sort files in UNIX:

du -xak . | sort -n | tail -100
it finds me the biggest 100 files or directories on the filesystem I’m in

If you want to see which sub-directory of your home directory is the largest, go to your home directory and enter,
du -sk *

How to Configure Printer in SAP and check via LPSTAT Command

noreply@blogger.com (Anonymous) — Sun, 22 Dec 2013 19:30:00 +0000

Create Printer
Enter the T Code -SPAD.
In Spool Administration screen, click on Display against Output devices. This will list out all output devices configured in SAP system.
Click on Create button to add new printer.

In Device Attribute Screen below, put name of Output device, Device type, Device Class, Model and Location of Printer.
output device = put name of the printer
short name = put any short name
device type = select printer type like epsio,hp etc.
spool server = select spool server name
device class = select class otherwise standard

In Access method screen, select Host Spool Access Method and Host Printer.
In Host Printer you can attach default printer of the machine where user has logged in, by writing "__DEFAULT".
Check or uncheck "No Device Selection at Frontend" as per requirement.
host spool access method = S: Print using sap protocol
host printer = printer name which is given by you
destination host = ip address of the printer
connection option
connection time = 0
port number = 515 may be differ as per printer
response time = 0

Output attributes
host spool cover page = do not print host spooler cover page
in below of process request sequentially
press copy counter to host spool system
print mode = default printer default setting
printer tray = default tray
Click on save button to save settings.
If you have not selected short name in device attribute screen then system will show below message. Click yes to go ahead.
System will show below Message.

Delete Printer
In Spool Administration screen, click on Display against Output devices. This will list out all output devices configured in SAP system
Select the printer you want to delete and click on delete button.

Delete Old Spool Log
Enter the T Code -SPAD.
In Spool Administration screen, go to admin tab.
Click on Delete Old Spool requests.
Check "Old Spool requests older than the maximum set age". Enter the minimum age. And press Enter. It will delete the old spool requests.
System will display log as below.

LPSTAT Command
The status of the Print Queue in using the command LPSTAT
lpstat -p < Print Queue Name>
There you will get status of Print (Ex: Running, Sending and failed).
Commands like lpstat -p and lsque -q or for that matter lssrc -g spooler (AIX) will be valid also on the Type of Printing you use (Access method)

For more information, please read S Note 118057 - Flexible Configuration of the Spool Service

Source: wiki.scn.sap.com

Print request are stuck in the queue

noreply@blogger.com (Anonymous) — Sun, 22 Dec 2013 19:30:00 +0000

Print request are stuck in the queue
If this is the case how we going to resolve the problem? Shall we reset the print queue ? How?
You will need to re-enable the queue, again you can write a simple program to use command enable <printer> queue. But at the end of the day if you don't hold administration rights for the OS you need to rely on your "server admin team" to solve the issues with the print server.
How to Configure Printer in SAP?
Check printer via LPSTAT

How does NRIV table (Number Range) works?

noreply@blogger.com (Anonymous) — Sun, 01 Dec 2013 17:48:00 +0000

NRIV is number range. It’s a general table for all number range.

Now what’s number range buffer?
Number range buffer is used to enhance the performance during assigning numbers. Instead of fetching numbers each time from database (db), it just access from buffer. Only when buffer is empty, its refilled from database. (NRIV table)

What’s number range server?
If the number range interval which we want is not present in the buffer or we can say number stock is exhausted, then the number range buffer must fetch new numbers from the NRIV table from the database. It’s called number range server. Another additional workprocess (WP2) is required for this. It runs on same server on which WP1 runs.

SMLG load balancing

noreply@blogger.com (Anonymous) — Sun, 01 Dec 2013 17:27:00 +0000

What’s the use of SMLG load balancing?
Dynamic logon load distribution should ensure that the load is distributed as evenly as possible over all available application servers in a logon group. To achieve this, a program runs automatically every five minutes, determines the logon quality for each application server, and writes the quality to a table on the message server. This quality is a numerical value that is calculated from various performance values, such as the number of users logged on and the response time. The server with the best quality within a logon group is used for the next logon
Log on load balancing is configured when we have more number of application servers.
Advantage of SMLG load balancing:
Effective utilization of buffers.
Failover and Load balancing
Effective utilization of resources/work process

Average response time in sap (ST03N)

noreply@blogger.com (Anonymous) — Sun, 01 Dec 2013 17:01:00 +0000

Ways to improve performance.
Analysis:
- do a response time breakup using ST03 statistics, to see which component is taking most time
- analyze your database I/O performance in ST04
- analyze top response time transactions in more detail (ST03, STAD)
- analyze top expensive SQL statements in more detail (ST04, ST03, EarlyWatch alert report)
- analyze CPU usage (ST06, OS07, OS dep. tools)
- analyze RAM usage and paging (ST06, OS07, OS dep tools)
- check whether your SAP memory parameters are OK (ST02)
- check whether DB parameters are OK (DB specific notes)

Optimizations:
- create indexes according to SQL analysis
- let ABAP programmer take a look at heavy transactions and report (especially Z-code)
- increase CPU processing power
- increase server RAM
- adjust database parameters
- adjust SAP instance profile parameters

SAP benchmarks (www.sap.com/benchmark) use 1000ms as reference.
All hardware benchmarks have 1s response time.
Some organizations have set KPIs to response time values. Normal values are 500ms and 750ms

Most important SAP system performance analysis transactions

noreply@blogger.com (Anonymous) — Sun, 01 Dec 2013 17:00:00 +0000

Most important system performance analysis transactions
Following is a list of the few most important performance analysis transactions and brief explanation of their purpose of various systems (BW, ECC, SCM, SRM, ERP, CRM etc)

ST02
SAP Memory Configuration monitor checks the SAP Buffers and SAP Memory areas for problems such as swapping. Here we can check the utilization of SAP shared buffers, extended, roll, paging and heap memory can be obtained from the SAP memory configuration monitor

ST03N:
General performance statistics such as response time. This workload monitor can show response time daily/weekly/monthly and is mainly used for checking dialog/background/update/spool/rfc response times

ST04:
It gives a picture of databuffer/cache quality, SQL cache catalog/pin ratio. For further detailed analysis click button 'Detail Analysis Menu'

ST06:
The Operating System Monitor is used as a snapshot of CPU utilization, RAM, Swap space. For further detailed analysis click button 'Detail Analysis Menu'

SM66:
Mainly used for monitoring current system activity via the Global Work Process Overview

ST22:
It’s a store for ABAP Dumps such as –
TSV_TNEW
DBIF_RSQL_SQL_ERROR
DBIF_RSQL_INVALID_SQL_ERROR
TSV_INDEX_INDEX_NO_ROLL_MEMORY
SYSTEM_NO_ROLL
SYSTEM_ROLL_IN_ERROR
TABLE_HASH_NO_MEMORY
STORAGE_HASH_NO_MEMORY
STORAGE_PARAMETERS_WRONG_SET
SAPSQL_ARRAY_INSERT_DUPREC

SM21:
All remote system lock
System locks
Failed logon attempts
Look for messages like: -
Process message
Printer problems
Signal 11
Short dumps
Time-outs
Matchcode problems
Aborted postings

SM04:
Active Users and its sessions. Also check memory, page, roll, priv usage via goto –>memory

By clicking on session, we can have detailed analysis. If we want we can end user session from here.

AL08:
The number of active users can be obtained from the Global User Monitor

SARFC: An overview of server resources and under column description whether there is a problem

AL11: List of SAP directories

DB01: It gives idea about exclusive wait situations using the Database Lock Monitor.
We can see number of deadlock along with table name

DB02: Check database growth, freespace in tablespaces, critical objects, extents of tables and indexes

We can get current size of tablespaces by clicking “current size”

DB12: Check backup/restore situation

DB16: On Oracle check for search for messages with the "SEVERITY" type "E" (error) that occurred in the past 4 weeks.

DB24: Check administration tasks such as backup/recovery, archive frequency, administration tasks

Report /SDF/MON: The tool allows for the collection of data on CPU Utilization,Memory Management, Database Performance, Work Process Utilization, Workload, STAD, RFC etc. The information linked with each of the above areas is stored in the database for further usage. The data can be collected for predefined periods of time and for a set frequency of seconds STAD: Used to check response time of programs/transactions and provides various levels of detail which can be tailored.

ST14: The ST14 application monitor is mainly used during SAP GoingLive session. Analysis batch jobs collect performance-relevant key figures such as document statistics and customizing settings, the analysis results can be viewed as a tree and downloaded to a service session. See SAP Note 69455.

ST05: ST05 traces every action of a user on a server. SQL trace needs to be switched off and the ST05 writes trace files into the local filesystem and overwrites them circularly.

ST12: ST12 combines ABAP and performance (SQL) trace into one transaction, with major functional enhancements especially for the ABAP trace part. In a joint switch on/off with the performance trace, ST12 allows to activate the ABAP trace for another user. See Note 755977. The ST12 can also be used for tracing workprocess, program/transaction or a user. At a click of a button you can view the SQL and ABAP trace information.

Other useful transactions that can be used depending on circumstances: SM58 SM59 SMQ1 SMQ2 SMGW SDCCN SM37 SM51 SM50 RZ04 RZ10 RZ20 SE16 SE12 TU02 DB03 SMQS DB21 SMQR SM13

Discuss with your developers/programmers if performance improvements are possible. For performance problems caused by customer programs SAP offers SAP Customer Program Optimization (http://service.sap.com/cpo) by eliminating costly performance bottlenecks by tuning critical customer programs.
Also ensure you have setup Earlywatch Alert as per SAP Note 207223. A good starting point for performance documentation is:
http://service.sap.com/performance
http://service.sap.com/earlywatch
http://service.sap.com/goinglivecheck
http://service.sap.com/safeguarding -
Source: http://www.saptechies.org

Applying license to Java systems (SAP Portals)

noreply@blogger.com (Anonymous) — Sat, 02 Nov 2013 22:25:00 +0000

Go to the path: /usr/sap/<SID>/JC*/j2ee/admin

Go to admin directory.
Set environment variable DISPLAY by below command to start visual display with user friendly environment
setenv DISPLAY <IP address>:x.0 (x is variable)

After setting environment,we can verify graphics setting by command (1) xclock (2) xlogo

Now run the go script in admin directory to start Visual admin by following command-:
./go

In visual admin click on CONNECT
Now enter user ID and Password

Now we can see the system settings here.
Select the server

Go to Services –> Licensing Adapter.
Now we can see the license details and hardware key details.
Click on installed Licenses Tab to check expired license details.
Go to General Tab again.
Now click on “Install License from file” button

We can browse the license file (.txt) from the path where we have kept .

After selecting (.txt) file, we will get below message that “License is successfully installed”.

We can go again to Installed Licenses tab in above screenshot to verify our new successfully installed license.

If we want to logout from the visual admin then point mouse to connect button then it will show we logout and exit option.
If we click logout then you will get disconnected from the server but still you will be in visual admin .
If we click exit then you will come out of visual admin there will be no visual admin screen . After that simply you give the command exit on putty.
We will come out of the system.

Netweaver license key

noreply@blogger.com (Anonymous) — Fri, 01 Nov 2013 04:37:00 +0000

To operate SAP NetWeaver or individual components, you need one or more of the following SAP NetWeaver license keys:
● License type Standard (ABAP license key for components SAP BW, SAP KW, and SAP Web AS)
● License type J2EE Engine (license key for standalone SAP J2EE Engine)
After you have installed the components, the system is equipped with a temporary license, which is valid for four weeks. During this time, you have to apply for a permanent license from SAP and install it.
In SAP NetWeaver 7.0 and higher, there is a new type license key in addition to the old type. This new license key is based on a digital signature. Both types of license key are installed and administered with SLICENSE, as previously, and are available as temporary and permanent license keys. The functions for the new license keys can be found by choosing the New Licenses button and are described in the procedure the same as the existing functions are.
To allow a seamless transition, both types of license keys initially function in parallel after the upgrade. If license keys of the old type were already installed, you can continue to use these. However, we recommend that you also import license keys of the new type, since the license keys of the old type will be deactivated in the future. For this reason, only keys of the new type are assigned for new installations.
Requesting an SAP License Key
Information about requesting the license key from SAP is available on the SAP Service Marketplace at http://service.sap.com/licensekey and in SAP Note 94998
Source: help.sap.com
Process to generate netweaver license key:

Login to Java portal home page

Click on “SAP NetWeaver Administrator”

It will prompt for valid ID and password.
After successful providing credentials, below screen will appear.

Now go to configuration management tab

Click infrastructure

Now click on License button

It will lead to a screen where we can see currently installed license and its validity.

To apply license just click Install from file and browse the license file and install.

Few notes on SAP License:

Note Number	Topic (Short Text)
94998	Request license key for systems / delete systems
767123	NetWeaver 04 License Key
765620	SAP NetWeaver Developer Studio
566263	SAP license in upgrade to Release 6.x (or higher)
628630	Core dump in SlicShmInit
174911	Formation of the hardware key (customer key)
612645	Performance problems accessing table LICENSE
432308	SAPLICENSE 6.10: new field SYSTEM-NR
355536	Importing the SAP license from a file
538081	High availability SAPLICENSE
576136	License expiry date is not displayed correctly
428966	Transaction SLICENSE: installation is not working
485233	Table MLICHECK in wrong table space on Oracle
742024	Downloading the license key
181543	License key for high availability environment
198140	Reassigning systems

Changing page format in SAP Printer via SPAD

noreply@blogger.com (Anonymous) — Wed, 30 Oct 2013 18:25:00 +0000

You can print any size of output from SAP, it all depends on what page format is defined and configured in your SAP system. Most of the standard page format are already defined in SAP but often you come across the situation where the required output doesn’t even come close to any of these predefined page format. Printing cheques and receipts are some common example. Defining and configuring Page format is multi-step process and often is printer specific. In short its very easy to get your setting wrong and situation is worse when printer is physically away from you.
Its very important to understand how this page format works in SAP. The process starts with defining the Page Format, but you need few more setting to actually print this page size on printer. Page format just define the size of page for sap script (this size info defined in page format is not passed to printer), next step is to define Format type which defines 'Type of format' and what orientation are allowed with this page format. It is important to note that Page Format and Format type should have same name. Well, you can argue why do we need to define Format Type. To find out that, which you may find bit confusing refer sap note 2374. Still you can not print with this page size on printer. To allow printer to use this new page format you need to add this page format to device type of printer. This step will enable you to print the output but correct page size information will not be passed to printer. You need to actually put printer specific code to set desire page size on printer.

Now let us go through each step with screen shot. You need to have access to transaction SPAD and changes to the repository and cross-client customizing should be permitted in the client where you will create/change page format.

Execute transaction SPAD. By default transaction will not show all the tabs, you need to click on 'Full administration' to get the desire tab.

Now click on Page format

You must be in change mode

Enter the desired page format

Then save

Creating S-user ID in SAP Marketplace

noreply@blogger.com (Anonymous) — Thu, 10 Oct 2013 19:42:00 +0000

What is S-User ID?
S-User ID is just a unique user ID with which you can access SAP portal link. We call it as SAP Service Marketplace.

We can request new S user accounts for project team by clicking the Request New Users link in SAP Marketplace. Once SAP receives the user account request, a new account is created and the login information (S user account and password) is available online. The Basis administrator can then provide this to the appropriate project team user. Once the user account is created by SAP, the necessary authorizations can be performed by the Basis administrator online. Several other options are available for administering the online user accounts, including a few mass maintenance options.

Login to service.sap.com page and go to “Data Administration” tab and the go to “User Data”

In User Data, click “Request New User” button.

There we will get a New user request form with some necessary details like Title, Surname, First Name, Language, Telephone No etc.
Fill details and click “Authorization” button.

Fill all details

Here in authorization page select the relevant authorizations which we need for particular user or we can copy another person’s authorization to new user.

To copy from a particular user Click on “User Id”

We will get option to type user name of the person from whom we are going to copy.

After entering the user ID click “Search” and we will get search result.

Click on user name.
And then click copy

You will get list of all authorization which selected user has got.
Now select done

You will again be redirected to initial screen.
Now save it.

Now we will get message “Your request has been saved and will be processed”

Go to display requested user tab.

The new requested user’s name will be shown here in “In Progress” status.

After 2 hours you will get below screen with status “Successful”

Send the user ID and initial password listed in this page to the user.
Inactive Users
When a user no longer works for your company or does not need access to SAP Service Marketplace any more, the Super Administrator is responsible for deleting it to prevent unauthorized access.
Users deleted in the last six months can be viewed and reactivated using Display Deleted Users. Users that have not logged on to SAP Service Marketplace for 12 months are automatically deleted if they are not actively kept through the Clean up Inactive Users function.

Developer Key and its requirement (DEVACCESS table)

noreply@blogger.com (Anonymous) — Sun, 06 Oct 2013 09:44:00 +0000

What is Developer Key?

The developer key is a combination of your installation number, license key (that we get from marketplace http://service.sap.com/licensekey) and the user name. We need this for each person that will make changes (Dictionary or programs) in the system.

Why Developer Key is required?

SAP developers require two things before they can actually do development work in SAP - right authorizations and a developer access key. As with everything else in SAP, when a developer tries to execute a transaction, he will need the required authorizations in her profiles. In addition, he needs to be assigned a developer access key. The authorizations can be checked in the user master records while the developer access key can be checked using table DEVACCESS. Table DEVACCESS will show the user ID and the developer key assigned to the user ID. You should only expect to see name of developers in this table.

What happens when the entry for a developer is deleted in the DEVACCESS table but the developer continues to use the same user ID?

The developer can still use the old developer access key.
The reason: Developer access key is nothing but an algorithm based on system number and SID and some other system values (SAP does not reveal the information). The developer access key is validated by SAP using a Kernel level C system program ''CHECK_DEVELOPER_KEY'. So, even if the developer access key has been deleted for a user ID in the DEVACCESS table, he can still use the same developer access key.

Which Table is the Developer Key Stored In?

If we would like to look up at your developer key and save it and have it available for the next system refresh.
The table name is DEVACCESS and can be viewed with SE16 and SE11.
For new ABAP developer, we will be prompt for the developer if we are trying to create a program using the standard SAP naming convention.
Customer own created program should all start with a "Y" or "Z".

How to register developer in marketplace?

Login into sap marketplace and go to below mentioned tabs as shown in screen.

Click on “Register Developer”

Insert the SAP User ID and select relevant installation number.

Then click “register” button.
Then developer key will generate and appear at the bottom of the screen.

Steps to perform Kernel Upgrade

noreply@blogger.com (Anonymous) — Sat, 05 Oct 2013 07:10:00 +0000

SAP Kernel is the core of the application. Like all other applications the Kernel contains the executable files (.EXE files for stating various processes in SAP. It contains those files which are used to run every event in SAP. ex: starting database, shutdowns of database, starting sap, shutdown of sap, saposcol, to uncar the sap files etc. It contains more than 120 exe files.
That’s the reason why when a Kernel upgrade is done it means new versions of the various EXE files replace the older versions.

The steps to do kernel upgrade are listed below:

1. Check existing kernel Level from server (system=>status=>other kernel info OR disp+work –v | more)

2. Download the latest kernel patch from SMP
http://service.sap.com/swdc
There are 2 files to be downloaded from SMP:
a) Database Independent Files
This is of the nomenclature SAPEXE_<Patch level>-<release date>.SAR
b) Database Dependent files
This is of the nomenclature SAPEXEDB_<Patch level>-<release date>.SAR

3. Make temp directory in sap server (temp) and upload sar file into it.(ftp)

4. Take backup of existing run directory to run_old. (copy and rename)
Copy the present kernel folder safely. This is important because the activity is completely reversible and switching over to the old kernel will be possible.

5. Extract sar files (SAPCAR –xvf *.SAR)
Uncar the files using the SAPCAR utility and store it in a directory. SAPCAR is a program executable located in the KERNEL folder itself. If SAPCAR is not working, then copy the executable from the kernel folder to the location where the .SAR files are located.
SAPCAR -xvf <filename.SAR>

6. stop sap server (stopsap all)

7. stop saposcol (saposcol –k)
SAPOSCOL service should be stopped because it also will get overwritten by the new file.

8. stop lisner (orasid user – lsnrctl stop)

9. check all service running in os level (ps –ef |grep sap, ora, dw)

10. Release shared memory (cleanipc instance no –remove, slib remove)

11. Replace all uncar file to run directory (cp –R * /usr/sap/SID/SYS/exe/run)

12. Some *.o files are not replace existing files then move that file from existing run directory to other directory and again execute step no 11.

13. Switch user to root and go to /usr/sap/SID/SYS/exe/run directory execute command ./saproot.sh SID to set permission.
Check the permissions of the files in the kernel directory
chown [-R] newowner filenames
chmod <1>permissions filename

14. Start saposcol (./saposcol –l) by only root user

15. Start listner (lsnrctl start )by orasid user

16. startsap all by sidadm

17. Check service are started or not.(ps –ef |grep dw)

18. Check sap kernel patch level.
Execute the command disp+work -v to get the new kernel level

Do we need to shutdown database also during kernel upgrade (SAP Recommendation)?

IDocs Deletion

noreply@blogger.com (Anonymous) — Thu, 03 Oct 2013 15:26:00 +0000

Deletion of idocs- PH4
(1) Go to BD87 and Idoc number

(2) Press F8 or execute to search for Idoc.Following screen will appear containing idoc information-:

(3) Click on Idoc status-: for example ‘51’ in below case-:

(4)Goto Edit-> Restrict and Process

(5)Below screen will appear

In this screen, UNCHECK Bkgd processing and click on execute .

(6) Below screen will appear displaying status record-:

Click on delete flag-:

Below screen will appear, click yes.

Following confirmation will appear-:

Click on back button on appearing screen-:
Below screen will appear with changed status of Idoc-:

Changing instance profile parameter to increase/decrease the number of UPD/DIA/BTC workprocess

noreply@blogger.com (Anonymous) — Sat, 28 Sep 2013 21:01:00 +0000

Changing instance profile parameter to increase/decrease the number of UPD/DIA/BTC workprocess.
Here we are reducing the UPD wp and increasing DIA wp.

Login as <sid>adm and go to profile path by cdpro command.
There we will find a file with naming convention *DVEBMGS*<instance_number>

Edit the values of this file by vi editor command.

Initially update (vp) value was 3 and 2 respectively. It has been reduced to 2 and 1 resp.

DIA has been increased from 12 to 14.

Initial (before restart)

Restart: stopsap all and startsap all

After restart (DIA wp increased)

We can see that number of dialogue(DIA) wp has increased.