Paid SAP Basis Consulting Services

Hi guys,

I am offering Remote SAP Basis Support and Service to your company. No matter your company have dedicated SAP Basis or not, we can help you. Your company could hire me as Remote SAP Basis.

You can check here for futher information.

Paid Support : Cheap SAP Print Management using Linux Client

My deepest regret that I have to do this in order to support me maintaining this blog since I have to maintain my internet connection. I need to charge to you if you want to get this simple information.

I am offering paid support to Basis who want to implement Linux Migration on workstation so that by using SAPGUI for Java on Linux can print smoothly as well as Windows-based SAPGUI client. On SAPGUI for Windows, you can easily print SAP documents. But you can’t do that when you’re using SAPGUI for Java on Linux.

If you are interested in this solution, please call me on YM : devratt.

Print SAP documents using Linux

A lot of people keep asking me how to print SAP R/3 documents using printer attached on Linux PC.

SAPGUI for Java is already installed on my Linux PC but I was unable to print any SAP documents ? We can’t use Frontend Printing (F acces method) since there was no SAPLPD program on it. Tell me how ??

Installation and Configuration of SAPGUI for Java on Linux

Based on many questions in my email inbox, asking how to install and configure SAPGUI for Java on Linux, here I’ll explain it briefly.

Prepare these stuffs before you can proceed to installation :

1. You have to make sure that your Linux system has been installed with JRE (Java Runtime Environment) from SUN Microsystem (http://java.sun.com). If you don;t have it, just download it from here. Some of linux distros such as Fedora, Ubuntu, OpenSuSE etc using JRE from GNU called GIJ (GNU for Java). We can’t use this JRE. We need to replaced it. I’ll show you how to changed it later.

DB2 Optimized for SAP – Set it and forget it

You may have read that the last release of DB2 (8.2.2) was specifically Optimized for SAP. What exactly does that mean? Well in this and the next few postings I’ll describe exactly what new features were in 8.2.2 and how, if you are using SAP (and even if you are not), you can take advantage of these new features.

The first is what I like to call the One SAP Knob.
If you administer an SAP database then you likely know that there are a number of settings SAP strongly recommends that you set. This is not a big issue when you initially get started but as new versions of DB2 and/or SAP come out it can be a burden to read through all the release notes to find out what new registry variables should be set and/or what changes to existing registry variables should be made. Well if you are on 8.2.2 your life has just gotten easier. You can turn the SAP Knob to the ON position and forget about it. What do I mean? Well there is a new registry variable in DB2 8.2.2 called DB2_WORKLOAD. If you run

db2set DB2_WORKLOAD=SAP

this will automatically set a number of registry variables based on what IBM and SAP have determined to be the optimal settings. Think of this as a parent setting which takes care of all the children registry variables underneath it. If a future fixpack of DB2 or release of SAP has new or more optimal (if that’s even correct grammar) registry settings, DB2 will automatically adjust them as long as the DB2_WORKLOAD setting is set to SAP. If you want to see what registry variables are controlled by the DB2_WORKLOAD variable, you can run

db2set -gd DB2_WORKLOAD=SAP

and you will see a list of 17 registry variables and their settings, specifically designed in cooperation with SAP to tune DB2 optimally for an SAP workload.

How can we calculate archivelog size each day?

How can we calculate archivelog size each day/hour?
This is not a difficult idea for someone who work as DBA, I just wish more idea for discussion and sharing . Some Idea using V$LOG.BYTES and V$ARCHIVED_LOG.*
but I believe V$ARCHIVED_LOG view be able to help:
Archivelog size each day:

SQL> select trunc(COMPLETION_TIME) TIME, SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB from V$ARCHIVED_LOG group by trunc (COMPLETION_TIME) order by 1;

TIME SIZE_MB
———- ———-
2011-02-12 71797.87
2011-02-13 75880.52
2011-02-14 73569.37
2011-02-15 76776.81
2011-02-16 73959.86
2011-02-17 69969.71
2011-02-18 74677.10
2011-02-19 75474.95
2011-02-20 77967.07
2011-02-21 67802.70

Archivelog size each hour:

SQL> alter session set nls_date_format = ‘YYYY-MM-DD HH24′;

Session altered.

SQL> select trunc(COMPLETION_TIME,’HH24′) TIME, SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB from V$ARCHIVED_LOG group by trunc (COMPLETION_TIME,’HH24′) order by 1;

TIME SIZE_MB
————- ———-
2011-02-21 00 6396.65
2011-02-21 01 2797.31
2011-02-21 02 2010.45
2011-02-21 03 1871.77
2011-02-21 04 1481.5
2011-02-21 05 2868.20
2011-02-21 06 2363.89
2011-02-21 07 4269.26
2011-02-21 08 2469.08
2011-02-21 09 3007.06
2011-02-21 10 3561.97
2011-02-21 11 2530.57
2011-02-21 12 3509.08
2011-02-21 13 3022.5
2011-02-21 14 3514.97
2011-02-21 15 4057.45
2011-02-21 16 3021.27
2011-02-21 17 4014.31
2011-02-21 18 4011.66
2011-02-21 19 4008.10
2011-02-21 20 3015.46

That is just my samples ^^
How about archive log size each of day/hour on RAC?- Using GV$ARCHIVED_LOG ???
SQL> select INST_ID, RECID, NAME, to_char(COMPLETION_TIME,’YYYY-MM-DD HH24:MI:SS’), ARCHIVAL_THREAD# , blocks * block_size from GV$ARCHIVED_LOG order by COMPLETION_TIME;
INST_ID RECID NAME TO_CHAR(COMPLETION_ ARCHIVAL_THREAD#
———- ———- ————————————————– ——————- —————-
4 258572 +ARCH/DB/4_73214_617849235.dbf 2011-02-21 20:29:52 4
2 258572 +ARCH/DB/4_73214_617849235.dbf 2011-02-21 20:29:52 4
1 258572 +ARCH/DB/4_73214_617849235.dbf 2011-02-21 20:29:52 4
3 258572 +ARCH/DB/4_73214_617849235.dbf 2011-02-21 20:29:52 4
1 258573 +ARCH/DB/1_55739_617849235.dbf 2011-02-21 20:44:22 1
3 258573 +ARCH/DB/1_55739_617849235.dbf 2011-02-21 20:44:22 1
4 258573 +ARCH/DB/1_55739_617849235.dbf 2011-02-21 20:44:22 1
2 258573 +ARCH/DB/1_55739_617849235.dbf 2011-02-21 20:44:22 1

NO!!! – What do we see? – When we want to calculate archivelog size on RAC, we just use V$ARCHIVED_LOG view. So, on RAC:
Archivelog size each day:

SQL> select trunc(COMPLETION_TIME) TIME, SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB from V$ARCHIVED_LOG group by trunc (COMPLETION_TIME) order by 1;

TIME SIZE_MB
———- ———-
2011-02-12 71797.87
2011-02-13 75880.52
2011-02-14 73569.37
2011-02-15 76776.81
2011-02-16 73959.86
2011-02-17 69969.71
2011-02-18 74677.10
2011-02-19 75474.95
2011-02-20 77967.07
2011-02-21 67802.70

Archivelog size each hour:

SQL> alter session set nls_date_format = ‘YYYY-MM-DD HH24′;

Session altered.

SQL> select trunc(COMPLETION_TIME,’HH24′) TIME, SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB from V$ARCHIVED_LOG group by trunc (COMPLETION_TIME,’HH24′) order by 1;

TIME SIZE_MB
————- ———-
2011-02-21 00 6396.65
2011-02-21 01 2797.31
2011-02-21 02 2010.45
2011-02-21 03 1871.77
2011-02-21 04 1481.5
2011-02-21 05 2868.20
2011-02-21 06 2363.89
2011-02-21 07 4269.26
2011-02-21 08 2469.08
2011-02-21 09 3007.06
2011-02-21 10 3561.97
2011-02-21 11 2530.57
2011-02-21 12 3509.08
2011-02-21 13 3022.5
2011-02-21 14 3514.97
2011-02-21 15 4057.45
2011-02-21 16 3021.27
2011-02-21 17 4014.31
2011-02-21 18 4011.66
2011-02-21 19 4008.10
2011-02-21 20 3015.46

How about your idea?

Error “LIST_TOO_MANY_LPROS” when using SAPGUI for Java

Lately, I am facing some error “LIST_TOO_MANY_LPROS” when using SAPGUI for Java 7.20 rev 9 to access SAP ERP 6.0 EHp 5 with Basis release 702 SP 12 (KB70212). Then I search this on service.sap.com and found this useful SAP Notes  17447011.

Summary

Symptom

Accessing Implementation Guide through SPRO in HTML & JAVA GUI results in Runtime error as LIST_TOO_MANY_LPROS

Other terms

SPRO,LIST_TOO_MANY_LPROS

Reason and Prerequisites

While accessing IMG through SPRO in HTML & JAVA GUI, it results into run time error as LIST_TOO_MANY_LPROS.
This is because of some method calls are failing to be implimented in JAVA and HTML GUI.

Solution
Manual Steps to be followed:
1. Enter T-Code ‘SPRO’.
2. Click on ‘Settings’..’User-Specific Settings’..’General’
3. Uncheck all the check boxes.
4. Restart the t-code ‘SPRO’.

By this, some of the Control features cannot be accessed,
but the IMG navigation is possible.
Now, I am able to access SPRO smoothly again.

How to do remote client copy ( SCC8 ) & How to do client transport( SCC9 )

Hi,
Hope the below information helps.
HOW to do remote client copy ( SCC8 )
1. create the new client in the target system via tcode SCC4
2. log on to the traget client of the traget system with the user SAP* and password PASS
3. for the planned copy run, you must define the RFC connection between the R3 systems as the source client, if this has not already been
done.
4. you should also protect the source client of the source system against changes during the copy. To do this, log on to the source system and
lock the source client : In scc4 (
change mode ), choose the option ” Currently locked Due to client Copy “
5. you can start the copy in the target system. Execute tcode SCC9
6. using the profile, choose the data to be copied
7. choose the RFC connection. The source system and client are chosen automatically for the RFC connection
8. before the actual copy, test the RFC connection using the RFC system check. In addition to testing the connection, the R3 system releases
are checked.
9. start the copy in background ( in test mode )
10. check the status of the copy procedure from the target system. You can do this at any time by choosing Client Administration..tcode SCC3
11. start the copy in background ( in final mode )
12. check the status of the copy procedure…SCC3
NOTE : with a remote client copy, only the table data is moved, not the table definitions. If user-specific, client-dependent tables were created in
the source client, they are not automatically copied to the target client, and an error may be caused. It is the responsibility of the user to create
the necessary tables in the target client manually via SE11.
HOW to do client transport : ( SCC9 )
prerequisites : the source and target system must have the same R3 release. The R3 system can not checked the R3 release since there is no
connection between the
systems established.
1. create the target client in the target system via tcode SCC4
2. log on the source client in the source system with a user with transport authorization ( Not SAP* or DDIC )
3. using the client maintenance tool ( SCC4 ), lock the source client against changes
4. go to the client transport menu by choosing Tools > Administration > Administration > Client Transport > Client Export or transaction SCC9.
When you confirm your
selection, you are notified of which transport requests were created for this task.
KO – Client-independent
KT – client-dependent
KX – texts
5. check the logs created for the copy run via SCC3
To import the transports created into another R3 system :
1. copy the required files to the corresponding subdirectory of the local transport directory of the target system
2. on the operating system level, from the subdirectory bin of the local transport directory of the target system, execute the commands :
tp addtobuffer <request> <target system> client=<client>
tp import <request> <target system> client=<client>
3. the remaining file with the text elements requires different procedure. Log on to the target client of the target system and access the client
administration tool by selecting
Tools > Administration > Client Administration > Client Admin. Choose client Transport > Post-process Import. Select the request
<SID>KT<number of the request> and
execute it online or in background. This procedure copies and generates the client-dependent text elements.

STMS Status of Importing Queue (Request Does Not Match Component Version)

With Version SAP_BASIS 702 a new feature was added to the TMS system, tp was checking the component version of the transport which was released and the component version of the system where the transport was going to be imported. If there was a difference, this difference was highlighted in the import queue (transaction stms_import) and if you tried to import the transport, the import would stop with a warning message about the difference in the SAPCOMPONENT versions.
You have error import status “Request does not match component version”.

Solution:
Set STMS  profile parameter : SP_TRANS_SYNC = OFF
This can be added via transaction STMS of the domain controller.
Call transaction STMS
Goto ‘Systems Overview’
Double click you wish to add the parameter to
Goto ‘Transport Tool’ tab
Goto ‘change mode’
Add SP_TRANS_SYNC to parameter column and OFF to value column
Save, activate and distribute

Related SAP Notes
1581638 SAP component checks no longer working in TMS
1577714 Transport requests in Check requirements phase

Bypass Maintenance Optimizer on SAP Solution Manager

We had to confirm each packages through Maintenance Optimizer. I’ve found the way to bypass maintenance optimizer:

go at http://service.sap.com/patches and add all patches you want to download basket

you can go into SE37
choose function module /TMWFLOW/MO_UI_BASKET_AUTHORIZ
choose SINGLE TEST
click on EXECUTE
choose packages and click on CONFIRM

there ya go, you can download using SAP download manager… and avoid Maintenance Optimizer.