The "Saved Lists" in SQ01 can only be accessed from SQ01. There is no standard tool or report for displaying it. That means if you create a Z transaction code to run this query, you cannot access the "Saved Lists" from your Z Tcode.

If you want do create a customer report to display the "Saved Lists", you can use the following functions/reports:

- function RSAQ_REPORT_NAME to get the report name for a specific query
- function RSAQHLI_HANDLE_LIST_ID to choose a specific saved list for a query report
- report RSAQQLIS to display this list

*** UPDATE 20th Oct 2014 : Please look at:http://scn.sap.com/docs/DOC-54097 and OSS note 886102 for the automation and improvement updated by SAP ***

It is not uncommon that once BW QA gets refreshed or system copy from BW Prod, the source system connectivity to ERP system breaks. This document shows the step-by-step to restore BW QA to ERP QA.

ERP System:               ERP Quality System (QAS) client 100

BW QA System:          BW Quality System (Q11) client 100

Scenario:                    Source Systems QASCLNT100 is broken in txn RSA1 in BW QA (Q11) after it is refreshed from BW Production. This is a need to restore the connection for transport migration to work successfully.

Pre-requisite:

1. Open clients via txn SCC4, SE06 in ERP QA (QAS) and BW QA (Q11). If not, you will encounter dump DYNPRO_SEND_IN_BACKGROUND when trying to recreate the Source Systems in x11’s txn RSA1. (This step requires Basis authorization and should be done by Basis)

• Logon to ERP QA (QAS) , run txn SCC4 and open client for changes. Repeat for BW QA (Q11).

• In ERP QA (QAS) Run txn SE06, open namespaces so that there is no error when running FM RSAP_BIW_DISCONNECT later on. Repeat for BW QA (Q11).

2. In BW QA (Q11), go to txn WE20, check for ERP QA (QASCLNT100). If it does not exist, create it.If it exists, select the ERP QA's Partner Profile QASCLNT100 and delete RSRQST from outbound and RSINFO and RSSEND from inbound. Save your partner profile. It should look like the screen below.

3. Obtain ALE user-id passwords for to logon to QAS client 100 (ERP) and Q11 client 100 (BW) later on.

Step-by-Step Restore Procedure:

1. In BW QA (Q11), run txn SE11, table RSBASIDOC, narrow the results by putting in your ERP system id only e.g. QAS*

Result

2. In BW QA (Q11), run txn SE37, enter function module RSAP_BIW_DISCONNECT and client Test/Execute button.

This step deletes obsolete BW connections. Repeat this step for all entries in table RSBASIDOC.

Enter the values accordingly and click Generate button.

I_BIW_LOGSYS = BW QA system (Q11)

I_OLTP_LOGSYS = ERP QA system (QAS)

I_FORCE_DELETE = X

Caution: DO NOT enter a value in the field "RFC target sys". This would cause the function module to run in the system specified there!

Result

3. In BW QA (Q11), run txn RSA1 and Create Source System QASCLNT100.

With existing RFC destination and passwords, enter the fields like below:

You will be prompt to logon to QAS client 100. Click Continue button will do.

Click Use button if you are confident that the RFC destination works perfectly. If not, you could click Check button to confirm.

You might encounter a pop up message like this below. Click Delete will do. If this happens, after delete, repeat step 3 again.

4. With existing RFC destination and passwords, you should be able to create the Source System for ERP QA (QASCLNT100) without problem.

Problems that I encountered along the way……..

Problem 1:  DYNPRO_SEND_IN_BACKGROUND when trying to generate Source System QASCLNTxxx in txn RSA1

Solution:     Open clients in txn SE06 and SCC4 in both ERP QA and BW QA systems

Problem 2:  Entry in inbound table already exists

Solution:     

1. Go to WE20 and check whether Partner profile QASCLNT100 exist in LS type,if not just add Parnter profile with same and save.
   Partner profile Name: QASCLNT100
   TYPE: LS
   Give:
   Ty: US
   User: User Name
   Lang: EN
   and Save.
2. Again re-click on Partner Profile: QASCLNT100
   you will see ,there will be some entries in Inbound & out Bound Tabs.
   Delete the following from outbound:
   1.RSRQST
   Delete the following from inbound.
   1.RSINFO
   2.RSSEND
   and save your partner profile.
3. Now execute txn RSA1, it will ask to active Workbench, activate it and it should work.

Lastly, this document is only possible from the two reference below and many other related threads that I had also come cross so I would also like to give credits to them.

References:

OSS Note 886102 – System Landscape Copy for SAP Netweaver BW (Phase 6)

Transfer Structure Prefix error - http://scn.sap.com/thread/170753

SAP ST-PI and ST-A/PI patch update

Summary :-

This document will show you how to update the ST-/PI and ST-A/PI in SAP with help of service preparation check RTCCTOOL .

Author: Brindavan Mookaiah

Designation: SAP BASIS Consultant

Tabls of content

1. 1) EWA report
2. 2) Run RTCCTOOL
3. 3) Implement the ST-A/PI and ST-PI

Step 1)

Check the EWA report about the ST-PI and ST-A/PI patch to update.SAP will recommend upgrading the new version based on SAP Application.

Steps 2)

Once if you able to see that the ST-A/PI & ST-PI  need to update and SAP recommeded. Then login into SAP and go to T-code SE38 and then execute program  'RTCCTOOL '.

Download the latest ST-PI and ST-A/PI from service market place http://www.service.sap.com

Once you downloaded  the required file(ST-PI& ST-A/PI) from market place and copy the file into the server. Mostly this file will be SAR file.

Login in to OS level with SIDadm and extract the file using SAPCAR.

,After  the files are extracted, place the files into directory "/usr/sap/trans/EPS/in".

Then login into SAP level and go-t-code SAINT --> click Installation package --> load package --> from appliaction server

click go back to the pervius menu and select the  ST-A/PI --> click start

Click No

SPAU adjustmnet can be done later. You inform to ABAP team to fix if any SPAU adjustment is there.

Once the ST-AP conmpleted successfully, then upadte the ST-PI.

ST-PI need to update in T-code SPAM

Login into SAP and go-t-code 'SPAM'

Then click Display/define--> select the compent ST-PI

and start implement once you select the complenet ST-PI and click--> support package ---> import queue

it will take 15 to 20 mintues to complete.

  once the ST-PI completed, Click--> support package--> confim the queue

Note: ST-A/PI need  to update in T-code SAINT and ST_PI need to update in t-code SPAM.

SAP Portal Issue Analyzing using Http-Watch Tool

Summary:-

This document contains how to analyses the issue in SAP portal issue when the system is up and running using third-party tool Http watch log. You can able to  find the issue in portal like sso, third party system connection failed or any other issue.  Even you able check the performance issue as well. this tool is IE pug-in

Created: Brindavan Mookaiah

Designation: SAP BASIS Consultant

Created: Brindavan Mookaiah

Designation: SAP BASIS Consultant

Table of content  :-

1. 1)      Download the Httpwatch log tool…………………………………………………………….
2. 2)      Install and check………………………………………………………………………………………..

Step 1

Downlaod the Httpwatch log from the following URL HttpWatch 9.4: HTTP Sniffer for IE, Firefox, iPhone and iPad .

Step2

once you downloaded the httpwatch tool  then install the same by clicking--> "httpwatch"

once you install the httpwatch you can able to see the httpwatch plug-in in IE

Click httpwatch

once you clicked the httpwatch tool, you can able to see the like above  in IE.

Then enter the portal URL and then click "record".

Record everthing upto the issues which you faced.

then Click stop.

Then you can save the file as CSv,XML or HWL file.

save the file into your local desktop.

click the Portal log file which you saved in your local desktop.

Now you can able to analyze the log where exacting causing issue.

By default after an installation of a system, SAP GUI will begin with the client 001.

Logon screen SAPGUI

For change this configuration, we will modify the next parameter:  Login/system_client

This parameter is not dynamically switchable, so, if you change his value, you need restart the system to take effect the changes. For check if a parameter is or not dynamically switchable, you can go to transaction RZ11, put the name of the parameter and see if the option “Dynamically Switchable” is selected:

Transaction RZ11

Now, for modify the value of this parameter, you must be use the transaction RZ10:

1. Select the instance profile.
2. Select the edition mode: “Extended maintenance”
3. Press the button: “Change”

Transaction RZ10

You will see a list with the parameters in the instance profile. For add a new parameter, press in the button “Create” located in superior menu:

Superior Menu of Transaction RZ10

Follow the next steps:

1.     Put the parameter name: login/system_client
2.     Put the client number you will use default when the SAPGUI logon screen start.
3.     Press the button "Copy"

Transacction RZ10 - Create Parameter

Come back and save the changes:

Transacction RZ10 - Save Changes

When you come back to the initial screen of RZ10 transacction, you can see the instance profile with the status "Not Saved":

Initial Screen - Transacction RZ10

For save and activate the changes, follow the next steps:

     1. In the superior menu, select the "Save" option:

     2. Select "Yes" for activate the new instance profile:

     3. You can see a message with confirmation for the changes:

     4. The next message tells you about restart the system for the changes take effect:

     5. Again in the initial screen of RZ10 transaction, you can see the new version of instance profile:

Finally, when you start the logon screen of SAPGUI, you can see the new client number set in the login/system_client parameter, in this case, the client number is 100:

SAPGUI Logon screen

It's a simple thing, but is so helpful when you do it your first installation

Best regards from Chile

@Fepezoabarca

                          SAP NWBC for HTML and Desktop configuration steps

Summary :-

     This dcoumnenst conatin the information about requirement , hardware , configuration steps and Comparison of NWBC for Desktop and NWBC for HTML.

Created by  : Brindavan Mookaiah

Designation : SAP BASIS Consultant

Table of content:-

1)  Hardware and software requirement.................................................................................................

2)  Differences Between NWBC for Desktop and NWBC for HTML.......................................................

3)  Configuration steps...........................................................................................................................

4) Insatllation NBC for Desktop and HTML............................................................................................

NWBC is shipped in two variants:

1. NWBC for Desktop is a MS Windows/.NET-based application that needs a local installation. It uses SAP GUI for Windows under the hood to run Dynpro-based transactions and integrates Web
applications using the Internet Explorer control in its shell.

2. NWBC for HTML is a browser based version using HTTP/s for connecting to a SAP NetWeaver Application Server ABAP backend. SAP GUI transactions are rendered using the SAP GUI for HTML.

  you prefer based on your client requirmenet.

Step 1

   Hardware and software requirement

Step 2

Differences Between NWBC for Desktop and NWBC for HTML

Step 3

Configuration steps

Step 4

4.1 Download NWBC forDesktop client installation from SAP(service Market place)

4.2 Install the NWBC for Desktop 4.0

4.3 Activate the NWBC on ABAP system in T-code SICF "/default_host/sap/bc/nwbc

4.4 you will get the URL link like https://<servername>:portno/sap/bc/nwbc?sap-client=000

4.5 Cliec the NWBC and mentione the URL like bleow

4.6 then click on log on

After enter the log on user name and password you will able to see the belwo screen.

NWBC for HTML

Once you activated the services , the URL will genarted and able to access SAP from HTML page.

Note : Both scenarios the user-ID must exist in ABAP system & proper authorization.

Purpose

The purpose of this document is help in searching for specific content (relating to an error log) in the SAP Netweaver Application Server ABAP workprocess (or any other R/3 related service/process) traces. This can be a very tedious affair if many workprocesses are configured and this document explains how to do this from the SAP server end, rather than logging to the operating system to search in the actual trace file.

Example Scenario

Lets say the configured Single Sign On (SSO) setup between SAP Portal and the R/3 system fails with issues similar to:

Usually in such cases, the BASIS admin analyzes the J2EE and ABAP server logs. Now from the J2EE end, more details can be seen from the diagtool trace ( see http://service.sap.com/sap/support/notes/1045019 for SAP NW 6.40 and 7.00 servers and http://service.sap.com/sap/support/notes/1332726 for SAP NW 7.1+ servers), but when it comes to the ABAP server, the request can be handled by any one of the R/3 dialog workprocesses (usually one productive ABAP instance has 20 or more dialog workprocesses). Now searching all the dev_w0 files can be a cumbersome affair particularly if many ABAP instances are involved.


Solution

Use the ABAP server search function (TCode: /nSM51).

Type in the search text entry. There are some recurring error entries like “note 1055856” , “cannot create SAP logon ticket”, “TWPSSO2ACL”, “ticket issuer not trusted” etc. when there is an SSO issue. Or just use the user ID with which the issue was reproduced (or time or any other valid parameter).

The next screen shows you the exact trace file which has the error:

Navigate to the trace file (using /nAL11 or /nST11) and voila, you get more information:

Now, check the note and help documents to solve this. The only caveat is that this search is instance specific; if you have more than one ABAP server, this needs to be done individually on each instance.

NOTE: http://service.sap.com/sap/support/notes/1769367 :  Issuer of SSO ticket is not authorized also provides important information on troubleshooting such issues.

For a similar guide on checking application logs on an Application server JAVA, check:

http://scn.sap.com/community/netweaver-administrator/blog/2014/11/17/how-to-check-logs-for-particular-j2ee-application-issue

You may encounter issue when downloading file via webgui. You are requested to send the java console trace. Below is the procedure.

1.   Go to Control Panels and choose Java.

2.   In the Java control panel go to "Advanced" tab.

3.   In "Java console" section select "Show console" option.

4.   Start Webgui and reproduce the problem.

5.   After below Java Console is launched, press 5 (depends on what SAP consultant requests) to set the trace level to 5.

6.   Save the trace in .txt format and attach to the incident.

Below are the Source and Target Details during the ECC 6.0 EhP7 Upgrade for our System upgrade

    Source: ECC 6.0 EhP5

    Target: ECC 6.0 EhP7

    OS: Linux RHEL 6

    DB: ORACLE 11.2.0.3

Prerequisites

Checking the Hardware Requirements

Checking the Software Requirements

Checking the Source Release of the SAP System

Meeting the Operating System-Specific Requirements

Upgrade of the Operating System and Database System if required

Checking the Software Update Manager Version, Please try and ensure that we have latest Tool SUM 1.0 SP10

Checking the Software Delivery Manager Version

Checking the Structural Requirements for ABAP

Setting the Operation Mode for the Update

Checking the Number of Background Processes

Making Preparations in the Monitoring Area

Checking the Requirements for the Modification Adjustment

• Update SPAM/SAINT to latest version and in the EPS we have SPAM/SAINT 51 so do it in advance
• OS level user: SIDADM and ORASID, SAP level user DDIC password in all the clients should be known prior to start and in 000 ,System user password is required for DB .
• 1639578,1547947 and 1622837 notes should be referred to setup the new DB connection before the issue arises( - Secure connection of AS ABAP to Oracle via SSFS for removal of OPS$ mechanism)
• Cleanup profile directory and only active and relevant profiles should be there , all the backup profiles etc. should not be present and removed from the location, See SAP note 1649026 .
• In case you are upgrading the second system in the landscape Import TR for SAP notes 001680583,0001678047,1609895,1861585 and can be imported before the upgrade and hence you can skip this step during the SUM checks, else you need to implement the above mentioned notes in DEV system and then generate a TR for the same. \
• Cleanup Inbound/Outbound(SMQ1/SMQ2) queues
• Perform Kernel upgrade on source if required
• Archive log mode off if required at any stage
• Generate XML from Solution manager system
• Download software packages
• Get the number of Dialog and Background WP's increased and hence you can use the NZDM option
• Double the sessions and processes in Oracle from existing setup
• SAP note 1387739 for ACT_UPG phase please refer options used during the upgrade.
• Implement the new authentication technique as mentioned in SAP notes 1639578,1547947 and 1622837, so that you do not run into any issues and your production operation is not affected.
• You need to ensure that your present SAP kernel level should meet the criteria to use ssf authentication.
• Increase Memory as per client infrastructure capacity.
• Increase CPU as per client infrastructure capacity.
• Use NZDM option so that you use maximum resources and most of the activities are taken care during uptime only.

1.      Increase R3load processes and use 10 parallel phases
2.  Do not run SGEN during preprocessing phase. Run SGEN manually after upgrade to save time during preprocessing.
3.  Update SPAM/SAINT Latest Version in advance

• Create RFC destinations: FINBTR@<sysid>CLNT<(><<)>client> before hand for each client except 000,066
• Take the backup of /sapmnt/<SID>, /usr/sap/trans, /usr/sap/<SID>adm and /usr/sap/<SID>
• If there are operation modes set in the system, please adjust those as per WP distributon for upgrade
• Determining the Host for the Preparations(If separate host for shadow etc.. )
• Create New Table space with brtools named PSAPSR3740 of size 140 GB in advance

Use of NZDM (Configuration)

• NZDM option used for reduced downtime
• Increased the CPU Count as per infrastructure if running on same host.
• Increased memory as per infrastructure if running on same host.
• PSAPTEMP table space increased upto 20% of total DB size so as to avoid out of space in TEMP.
• Increase Sessions and Oracle Processes (Formula Sessions =2* Processes)
• Create PSAPSR3740 Tablespace of 140 GB size in advance (Applicable to ECC systems only)
• If your installation is of type HA then please make sure that XML file generated from solution manager contains the hostname of ASCS instance, else you will get an error while SUM is trying to recognize the instance .
• If Installation of SAP system is heterogeneous then please make sure that ASCS and CI kernels are upgraded independently, SUM tool even will ask you for DB host OS incase of HA/Distributed installation.

Challenges/Learnings

• Update statistics manually before the Upgrade starts.
• Increase the PSAPTEMP table space up to 20% of used DB size and then again reduce as per original allocation
• Create Table space PSAPSR3740 in Advance.
• Update SPAM/SAINT version to latest available
• Setup of SSF authentication mechanism for WP’s, before upgrade. As you need to complete the preprocessing with ssf mechanism in place and system needs to be restarted and environment parameters need to be implemented manually
• Change in SAP Kernel path and hence you need to update /usr/sap/<SID>/SYS/exe/dbg link to reflect to new path.Ensure that new kernel path is updated in <sid>adm and ora<sid> users for all the systems , including App servers. If App servers are there then prefer to reinstall app servers with latest SWPM.
• Reinstall App servers
• Check Host agent version
• Increase the shared memory parameters on Linux Kernel as below in the file /etc/sysctl.conf and activate :

1. kernel.shmmax=68719476736
2. kernel.shmall=41943040

Simple Steps to enable PDF printing for Web Dynpro

Prerequisites-

1) SAP Net weaver 7.3 As Java System (ADS should be installed), is not the please deploy ADOBE DOCUMENT SERVICES 7.31 SP07.

2) SAP Business Suite 7 System

3)Profile Parameter SAPFQDN should be set in both As Java and As ABAP system.

The general ADS setup should be completed first between the AS Java system where the ADS component is installed and ABAP system where PDF printing should be configured.

Basic configurations steps can be checked in below link.

ADS Configuration in Netweaver 7.3

After successfull completion of steps shown in above document we need to do further steps for enabling ADS functionality in Web Dynpro.

Prerequisites after basic setup is completed:

Make sure following USAGE TYPES are fully configured in AS JAVA System where ADS is configured and running.

• AS JAVA
• Adobe Document services
• PDF Export

Note: Missing Components need to be verified and deployed ( Please be careful to check the Software components which are missing and then try to implement first in sandbox or dev system first)

Observation : You will see 2 r 3 components related to BI Base Components missing from  Usage Type PDF Export

Once the SC are deployed if needed , we need to create a TCP/IP RFC in AS ABAP system where we want to enable ADS for web Dynpro.

Following steps using :1413938 - WD ABAP ALV - creating print version

Steps:

Navigate to this path in AS ABAP System  using tcode SPRO -

SAP Customizing Implementation Guide

    + SAP NetWeaver

      + Application Server

        + SAP List Viewer (ALV)

          +Click on Create RFC Destination in AS ABAP ( Read the help document before setting up RFC since the setup changes according to the way we want to generate PDF document  and also the AS JAVA release )

This Document steps shows for following scenario:

1) Generating PDF Document using ADS

2) Java release is 7.31

If the above 2 points matches then follow the steps below:

RFC creation:

Now Create JCo RFC in AS JAVA System where ADS in installed.

Save.

Once saved start the program ID and check the status if its running, once confirmed please check the RFC created in AS ABAP system if the test connection works.

Note: ADS_AGENT user should have all the roles required and also need “s_rfc” role to be assigned.

Now check the results in Web Dynpro by doing a print preview in some reports and should get the ADS Format result.

If there is a performance issue on an ABAP system, BASIS Admin must think about the increasing basis tables in my opinion.

And ADMIN can do the following proactive and reactive operations.

As for the proactive operations Standart Jobs must be checked. Sap Note "16083 - Standard jobs, reorganization jobs" gives detail about reorganization and deletion jobs. Let me take the list of standart jobs also here. You can see details in the note.

For reactive operations admin can do the followings;

• Take the list of largest tables. Depending on the database type the list can be taken as below;

• Then apply the available solutions depending on the table types listed in the SAP Note 706478 - Preventing Basis tables from increasing considerably

Here is an example of an ERP system cleanup process.

DB type is MS SQL Server.

• There were some missing standart reorganize or delete jobs. They were resscheduled according to the note mentioned above.

• The list of largest tables was like below. We dealt with only these tables. This list can differ according to the system or project.

• According to the tables the following actions are done;
  • For tables EDI40, EDIDS, EDIDC
    • The item in the note says: "2. Archive old entries as described in Note 40088."
    • We had meeting with business consultants and data owner. After an aggreement data was archived with IDOC archive object. Only last 3 months data is left. After first archive some data could not be deleted because of the statuses. Then business consultants changed the statuses of the data for archiving and deletion. Second archiving and deletion is done. On each run TAANA is run tor table analysis.

• For tables BALDAT, BALHDR
  • The item in the note says: "1. Delete old entries as described in Note 195157."
  • According to the note with the discussion of data owner SBAL_DELETE job was scheduled weekly. Last 3 months data is left.

• For tables TST03
  • The item in the note says: "11. See Note 48400, which describes the options for reorganizing TemSe and spool. See also Note 666290."
  • The following standart jobs were controlled and some variants has been changed for short retention periods. 

SAP_REORG_SPOOL (RSPO1041) 

SAP_REORG_JOBS

SAP_REORG_BATCHINPUT

SAP_SPOOL_CONSISTENCY_CHECK

SAP_REORG_ORPHANED_JOBLOGS

SAP_REORG_ORPHANED_TEMSE_FILES

• For tables ARFCSDATA, ARFCSSTATE, TRFCQOUT
  • The item in the note says: "7. Check the proposals from Note 375566."
  • After aggreement with business consultants and data owner RSTRFCQDS job was scheduled. Variants were created for each qrfc queue names.

• For tables SWWLOGHIST, SWW_CONT
  • The item in the note says: "4. Archive entries that are no longer required as described in Note 49545."
  • We discussed the issue with business consultants and decided to delete data older than 3 months. For cleaning RSWWWIDE and RSWWHIDE jobs were scheduled weekly with a variant older than 3 months. 

     You can also use WORKITEM archive object to archive the workitem data depending on the business need.

• For table SNAP
  • The item in the note says: "13. See Note 11838 for further information."
  • Reorganization is done in ST22 transaciton. RSSNAPDL program is scheduled daily basis.

• For tables IDOCREL, SRRELROLES
  • The item in the note says: "3. See Note 505608 and regularly schedule RSRLDREL."
  • After aggreement with business consultants and data owner RSRLDREL job was scheduled. Variants were created according to eh link types. Note can be checked for details.

• For tables BDCP, BDCPS
  • The item in the note says: "5. See Note 513454 and regularly schedule report RBDCPCLR to delete change pointers that are no longer required."
  • After aggreement with business consultants and data owner RBDCPCLR job was scheduled.

• For tables Z* tables
  • Business Consultants and data owner has decided about the customer tables data. They built up programs for cleaning. We scheduled those programs for regular intervals.

• Out of this list of action since the DB was MS SQL Server we also applied the note "1744217 - MSSQL: Improving the database performance"

In addition to the main note for basis tables you can also use Data Management Guide that contains detailed information about avoiding and reducing data. Use below address.

http://service.sap.com/ilm

-> Data Archiving   -> Media Library   -> Literature and Brochures   -> Data Management Guide

SAP CEN configuration for CCMS Alerts

(Kernel 7.21 and above for satellite system)

Summary:-

This document contain the step by step how to configure the CEN configuration for CCMS alerts in kernel 7.21 and above of satellite systems.

Created by: Brindavan Mookaiah

Designation: SAP BASIS Consultant

Table of Contents

SMTP Configuration .....................................................................................................

Configure CEN (Central Monitoring System)...................................................................

Create the CSMREG User.............................................................................................

Activating Background and Central System Dispatching ..................................................

Step-by-Step ................................................................................................................

Activate central system dispatching in CEN ...................................................................

Registering a CCMS Agent SAPCCM4X for ABAP-System ...............................................

Creating Central Z Method for Alerting ..............................................................................

Auto Reactions for E-Mail Alerting in SBWP.......................................................................

Assigning Z method to MTE classes .................................................................................

Testing method assignment and mail alert .........................................................................

SMTP Configuration

Go to TR:”SCOT” double click on “SMTP”

Provide the SMTP connection information.

Provide the Default Name as “your FQDN”

Schedule the send job

Configure CEN (Central Monitoring System)

Create the CSMREG User

Note: You must create this user in CEN and all monitored ABAP systems.

Goto T-code RZ21 ->Technical Infrastructure -> Configure Central System -> Create CSMREG User

Specify any password for this user. You require it during the installation and registration of the CCMS agents

and when creating RFC destinations in monitored systems, among other things.

Activating Background and Central System Dispatching

For all data collection methods in the monitoring architecture to be correctly started, background dispatching

needs to be activated. It starts all data collection methods that are executed periodically in the background

process (as jobs). To execute an auto-reaction in CEN for alerts from remote systems, central system

dispatching needs to be activated.

Note: Activate background dispatching in CEN and in all monitored ABAP systems in client 000.

•Call transaction RZ21. The Monitoring: Properties and Methods screen appears.

•Choose Technical Infrastructure Method Execution Background Dispatching

Background dispatching is performed by the job SAP_CCMS_MONI_BATCH_DP, which runs once an hour.

Note that not only this job, but also the data collection methods started by this job, run under your user

name. You should therefore ensure that your user has the authorizations required for this.

Activate central system dispatching in CEN

Step-by-Step

•Call transaction RZ21. The Monitoring: Properties and Methods screen appears.

•Choose Technical Infrastructure Central System Central System Dispatching.

Central system dispatching is performed by the job SAP_CCMS_CENSYS_DISPATCHER.

Registering a CCMS Agent SAPCCM4X for ABAP-System

If the connecting systems are more than kernel version is 7.21.

Note : Please be aware, that in this release

there is already an integrated sapccm4x agent always started in

sapstartsrv by default, and you are not allowed to use both types of

the agents simultaneously, it will lead to inconsistencies.

If you do not have a special reason to use classical RFC sapccm4x

agents, then please unregister these agents from CEN, please move the

content of the agent working directory (DIR_LOGGING/sapccm4x on each

instance) to another place and restart sapstartsrv with (sapcontrol -nr 02 -function RestartService SID)

  Kindly follow the below steps to install sapccm4x gent

1) Please move the content of the agent working directory (DIR_LOGGING/sapccm4x on each instance)

    to another place.

2) please restart sapstartsrv with “sapcontrol -nr 02 -function RestartService

3) Login into SOLAM system and got to T-code RZ21 and then click

The screen will appear like below to select the system type and the press enter.

4) Fill the required system information in the below screen

Once the system is registered then goto T-code RZ21 and click Agent for remote systems-->Display

Note: If the system CI and DB install in different host. Please install the sapccmsr agent on DB-host

to get the alerts from database host system.

Creating Central Z Method for Alerting

In Transaction RZ21 Click on Topology -> Method -> Display Overview

Copy “CCMS_OnAlert_Email_V2” to “Z:central_CCMS_OnAlert_Email ”

Change option to “Only in Central System, Triggered by CCMD agents”

Maintain Below parameters

Note: make sure that the SENDER user id is mentioned in the upper case letters below and it is present in the client 000

      of Solution Manager system.

Check “Auto –Reaction Method”

Auto Reactions for E-Mail Alerting in SBWP

Crating Distribution list for E-mail alerting --> Goto TR:SBWP

Create Folder “z” folder under shared

Title=<something>

Select the second field of „Entry in DL‟ to „External Address‟

Then click on Create button

You need to specify a folder by clicking on F4 button.

If there are no folders create a folder, say, ZBASIS etc..

Click on „Create Folder‟

Mention the folder which you created if not please created the folder.

To see the distribution list from SBWP transaction, click on „Shared Folders‟ on the left,

To add list of email ids to the group double click on „BASISEMAILGRP‟ on the right.

Select “Z” folder and click on “Distribution Lists” and create “BASISEMAILGRP”

Mention your E-mail address

Assigning Z method to MTE classes

Select TBI and click on „MTE Classes from System‟ button to refresh MTEs from TBI system

Then select the MTEs you want from the middle section and then select central auto reaction method from

right.

Click on „Assign Central Auto-Reaction‟ button,

Select the first checkbox below and then click OK.

Note: Similarly assign the central auto reaction method to as many MTEs as you wish.

You can go to satellite system and check if the auto reaction method assigned.

Testing method assignment and mail alert

Goto T-Code: RZ20 and click the MTE class which you have already assigned the Zmethod

Example: I have assigned for “Abortedjobs”

Click on “YES”

Now we can alert see alert in INBOX with Subject and body

Note : For SOLMAN7.1 you can go-forward to install SMD agent installation.

For more details : Please find the following link about the SMD.

http://wiki.scn.sap.com/wiki/display/SMSETUP/Installation+of+SMD+Agent+With+SWPM+SP04

Home - SAP Solution Manager Setup - SCN Wiki

Step by step how to Install Diagnostics Agent and connect the agent to adaptive computing

When the 720 kernel is used the default syslog record length will be 320 bytes. When the 720 kernel is used on a ABAP system for which still the central system log daemons rslgsend and rslgcoll are needed, the instance profile parameter rslg/new_layout value must be set to 9 (notes: #1517379, #1118986, #1633731, #1453912 and #1636252).

  If a system is upgraded and there are still old records with the old length in the syslog files on disk, the administrator should delete all the old syslog files before the upgraded system is started again. When the users still complains about corrupted syslog entries after the upgrade and after deleting the old existing syslog files, the administrator needs to set the instance profile parameter rslg/new_layout value to 9, stop the system and delete all the old syslog files again for each instance and restart the system again.

Always be sure that you did delete the old syslog files in the correct way.

At first in the beginning the EWA report only reported the standard CPU data for the physical server and the data for this is directly collected by SAPOSCOL in a 24 hour buffer in which for each hour 4 times 60 measurements are stored because SAPOSCOL collects the data every 15 seconds by default.

After this SAP decided to create new monitor structures for the OS virtualization but the monitoring data for the CPU_Virtualization_Power

is not stored in the 24 hour SAPOSCOL buffer anymore. Actually the data is still collected by SAPOSCOL but only as a snapshot and we do need the

CCMS monitoring segment to store the data for a longer period. This can be done by using an ABAP report which reads the SAPOSCOL snapshot

data and stores the data in the CCMS monitor segment but this report only can be started each 5 minutes or this can be done by using a SAPCCM4X

agent and the agent can read the SAPOSCOL snapshot data every 60 seconds and sometimes even a little bit faster than this.

Now, if you do not use the SAPCCM4X agent then the difference between the old EWA report and the new one is 240 measurements or 12 measurement each hour.

If you are using the SAPCCM4X agent the number of measurements each hour will be at least 60. I know that this is still not the 240

measurements which we had before but at least it is much better then the 12 measurements.

Perhaps, in the further SAP can try to change something in the agent and collect the last 4 SAPOSCOL snapshots (if available) and in this way we also will get 240 measurements in the CCMS monitor segment each hour again.

-How to use SAP transaction ST06 for SAP performance analysis

http://www.sap-perf.ca/sap-st06-for-performance-analysis/

To lock, unlock client, use transaction se37
For this operation use functional modules:

1. SCCR_LOCK_CLIENT (to lock the client)
2. SCCR_UNLOCK_CLIENT (to unlock the client)

This function is used to lock \ unlock client from logins. When you lock a client, all users try to log on A client will show message "A client currently blocked from entering." A client will be available for entry only available to users SAP * and DDIC.

To unlock:

1. Run tr. SE37
2. Enter the name of the module SCCR_UNLOCK_CLIENT
3. Press F8 to activate
4. Enter the number of client and press (F8).

To lock the procedure is the same, only with the module SCCR_LOCK_CLIENT

1. each 300 seconds started by the so-called Auto ABAP. The exact point of time depends on the time when the instance was started.
2. at each fifth logon at the instance.

RZ20 for CPU_Virtualization_Power

- the CPU_Virtualization_Power subtree is in responsibility of the agent

- all other CPU_Virtualization_* nodes are in responsibility of saposcol

This means:

1) agent creates CPU_Virtualization_Power and is responsible for the content
2) fortunately - the data presented in the subnode are gained from saposcol and are reachable in other CPU_Virtualization_*   subtrees
3) agent does some kind of renaming in the nodes, e.g.  "Entitlement" could be found as "Guaranteed Capacity" in CPU_Virtualization_Virtual_System subtree

Summary - the values present in CPU_Virtualization_Power are collected by agent from other CPU_Virtualization_* subtrees, which are maintained by saposcol. It's kind of duplicity. The saposcol is always the originator of the data. There are no additional data in the _Power node which are not present in other virtualization subtrees.

This means that you can say that in the old EWA reports the OS CPU operating statistics are based on 4x60 is 240 measurements each hour.

After this SAP decided to create new monitor structures for the OS virtualization but the monitoring data for the CPU_Virtualization_Power
is not stored in the 24 hour SAPOSCOL buffer anymore. Actually the data is still collected by SAPOSCOL but only as a snapshot and we do need

the CCMS monitoring segment to store the data for a longer period. This can be done by using an ABAP report which reads the SAPOSCOL

snapshot data and stores the data in the CCMS monitor segment but this report only can be started each 5 minutes or this can be done by using a

SAPCCM4X agent and the agent can read the SAPOSCOL snapshot data every 60 seconds and sometimes even a little bit faster than this.

Annual SAP Security audit has always been a tough ask for administrators.

to extract the Combination of critical authorization & monitor the same is a time taking exercise but it can be extracted on a simple click with SAP Critical Authorization Reports all you have to do is maintain the critical Authorizations.

to maintain the critical authorizations execute the transaction SU_VCUSRVAR_CHANGE

1)  Double Click Critical Authorizations

2)  Click on New Entry you can also Copy it from Standard depending upon your requirement.

     Select the Color based on criticality

3) after adding your entries select the newly created Authorization ID and Double click the Authorization Data on Left Pane

Under Object mention the Authorization objects field Name enter the Field name For e.g

Save the entries

4) Double Click Variants for critical Authorization

and maintain the Variant by Clicking New Entries Save the New Entry

and then Select the newly created entry & double click the Critical Authorization

and add the critical authorization which we created in Step 2

now execute the transaction S_BCE_68002111

select the created variant and execute the report

What is SAPS

SAPS is the standard SAP Benchmark of performance measurement ( i.e. measurement of CPU power). SAPS is an acroynm word for - SAP Application Performance Standard (SAPS).

It is hardware-independent unit of measurement that describes the performance of a system operation in the SAP environment. It is derived from the Sales and Distribution (SD) benchmark.

Hardware vendors do a benchmark on their hardware for SAP as per their methodology to see how many SD users can be supported. Each module has a weightage. The number of users in each module is converted to number of Normalized SD (NSD) and SAPS value can be obtained.

QuickSizer

Standard SAP sizing tool is available in SAP Marketplace called Quicksizer. However, SAP standard tool is for estimate only and is not accurate. It does not benefit to customers to get the exact sizing solution.

Sizing solution in QuickSizer tool is based on number of concurrent users in each module, approximate number of objects created in each module and approximate number of line items created in every hour.

However, practically, only business functionality who are familiar with business transactions may provide information regarding estimate number of objects created per hour in each module-wise and estimate number of  line items  created or processed in every hour. Basis or System Administration or technical consultants  are not sure what  data to be entered in order to fill up the sizing in Quicksizer tool.

The question is whether it is mandatory to fill up the standard SAP Quicksizng tool?. The answer is No.

SAP stongly advises customers to contact various Hardware vendors and obtain sizing Questionnaires form from each vendor. Filled-up Questionnaires form will be sent back to their hardware vendors. There is no need to enter number of objects  and / or  line number of items created or processed in every hour. Hadrware vendors have their own default values. They recommend configurations with sufficient headroom to avoid resource bottlenecks.

Basis consultants from implementation partner can assist customer to filled-up quationanaires form and also choose the correct hardware configuration.

Hardware vendors cannot help you estimate the impact of workload and infrastructure changes ind eployed environments.

Limitation in using SAPQuick Sizing Tools

Sizing calculation is not an accurate. It is an estimate. SAP advises customers to contact Hardware supplier to provide sizing solution based on the customer's requirement. Every Hardware supplier has its own sizing methodology.

Quicksizer estimates are based on assumptions - SAP  assumtions about resource requirements based on transaction volumes generated by the user and the hardware vendor's assumption about how deployed application will use system resources.

Quicksizer cannot help you estimate the impact of workload and infrastructure changes in deployed environments. When the CIO asks, "What will it take to support another five hundred users?" or "Can we do multiple application and infrastructure configurations?"

Inaccurate : No consideration of workload and infrastructure changes while sizing capacity and performance. Accuracy has been estimated at 20%. Hence it would be difficult to obtain the exact accuracy of SAPS value.

The following lists are not taken into account in SAP Quicksizer calculation.

• Unicode

• Custom Objects

• Workload (batch processing, print)

• Interface

SAPS Sizing Methodology

In this document, SAPS calculation is taken on the basis of only number of users and workload. SAPS calculation is taken into account only for SAPECC 6.0 with EHP and SAP Netweaver 7.0 and higher. Also this document is valid for  medium to large sized companies i.e. upto 3000 users and database size upto 2TB. This document is not valid for users beyond 3000 and database size  above 2TB.

Classification of SAP users:

Based on the working hours, SAP users are classified into Low, Medium and High users.

Low users:          Users that spend less than two hours working in SAP (Top Management levels such as Executives, CFO, CIO, Vice-President, General Managers, etc)

Medium users:    Users that spend around four hours in SAP (Middle executives level such as Manager, Dy. Manager, Sr. Engineer, Account Officer etc)

High users:          Users that spend more than four hours in SAP (Clerk, Supervisors, Junior Engineer, Junior Accounts officer, etc)

Based on my  experience in various Implementation and Upgrade projects , the SAPS value is not influenced by the above-mentioned type of users. Hence SAPS value does not vary between High, Medium and Low users.

Normalized  SD users:

Different modules have their own weightage. There are many various modules in SAP R/3 or ECC systems.

These are

PP          Production Planning

MM         Materials Management

SD          Sales and Distribution

FICO       Finance and Controlling

HCM       Human Capital Management

QM         Quality Management

Classify the users  who are involved in business transactions in each module. For example, if the number of users involved in Production Planning (PP) is 10, convert number of PP users to SD users. Thus one PP user is equivalent to 1.3SD user because  in the PP module, the number of Line items created per one PP transaction is more than the number of line items created in one SD transaction. Therefore for ten PP users, number of SD users will be 1.3*10 = 13SD users.

Similarly, one Human resources (HR) user equals 0.4SD user becasue in HR module there is less number of line items created per one HR transactions than in one SD transaction. One Plant Maintenance (PM) user is equivalent to 1.1SD user .

Hardware vendors do a benchmark on their hardware for SAP as per their methodology to see how many SD users can be supported. The number of users in each module are converted into number of Normalized SD user (NSD) and SAPS value can be obtained.

SAP QuickSizer tool: To Obtain SAPS for number of named users

The tool is available in SAP MarketPlace website. This requires S-userid and password. CLick the following website link

http://service.sap.com/quicksizing

(A)     Sample result for SAPS value is  shown in the figure

SAPS value based on Workloads

After obtaining SAPS for given users from SAP QuickSizer tool, additionally, the following lists must be taken in to account for calculating SAPS value.

These are

• Custom Objects

• Interfaces

• Batch Loads

• Unicode

(B)     Rule of Thumb for Custom Objects:

Nearly all the SAP customers have large number of custom objects. Objects can be programs, tables, function modules etc. Custom programs consume much more SAP extended memory and high CPU utilization takes place because  of inefficient coding or expensive sql coding. Hence SAPS value for custom objects is also to be considered.

Based on EWA reports from various customers, it is recommended that for custom objects with reporting required SAPS  to be increased by 30% as a user executes most of the custom objects in a Dialog workprocesses. Thus taking custom objects into account

New SAPS for Custom objects = 30% of SAPS obtained from SAPQuickSizer tool

(C)     Rule of Thumb for Interfaces

Additionally 15 % more for standard SAP BI interface with SAP ECC system is taken into account (since SAP Business Intelligence i.e. BI 7.0 extracts data from ECC 6.0, hence heavy processing takes place in ECC 6.0 system (see the tx code sm50 with user "Aleremote" )  thus drastically lowering the performance . Hence required SAPS value is increased by 15%).

Furthermore, Non-SAP interface with ECC system is to be taken into account i.e. ECC system send / receive data from Non-SAP using IDOC. Hence required SAPS value is increased by 5%.Thus for SAP Bi and  Non-SAP interafce with ECC system = 15+5 = 20% . Therefore

New SAPS value for Interface = 20% of SAPS obtained from SAP Quick Sizing tool.

(D)     Rule of Thumb for Batch Loads

Experience showed that batch load depends on the number of application servers including primary instance.  Number of dialog instances required depends on the number of users executing batch loads.

For example, assume for 1000 named users. one Primary instance and one Dialog Instance  installed.  In this scenario, batch loads for two servers will be extremely high where large number of  batch jobs processing takes place becasue batch jobs are distributed in only twos servers only.

However, if there are three Dialog instance servers installed in addition to Primary instance server, batch jobs are distributed in four servers . Hence load in each server can be medium to high for same number of users.

If there are more than five Dialog instance servers  installed in addition to Primary instance server, batch jobs are distributed in six servers or more. Thus load in each server can be low to medium.

Note that, experience shows that for more number of batch jobs running in parallel in all application servers installed, high IO utilization will take place on database server.  This will  slows  down overall Production system performance i.e. there will be high intensive read / write operation on Disk / filesystems storage in  database server.

Thus it is advisable to schedule the jobs  after office hours. Also It is advisable not to increase number of background work processes beyond 3  during office hours i.e. should not be > 3 background workprocesses in each application servers including primary instance server. This will improve  IO  performance and enable end users to work in SAP production system comfortably.

It is recommended that 25% extra be taken account for  upto 3000 named users

Thus new SAPS value for Batch load = 25% of SAPS obtained from SAP QuickSizer tool

(E)     Thumb rule for Unicode System loads

Unicode systems use between 1 and 5 bytes of space to store single characters. As a result, the resources of the system could be doubled.

Practically, the load on the CPU caused by the applications, increased by about 25-35%. The load on the RAM, again caused by application programs / transactions  increased by about 50%.

It is advisable that 25% extra be taken so the required SAPS  is increased by 25%  for the databse size upto 2.5TB and irrespective of the number of users.

Thus SAPS for uniocde system = 25% of SAPS obtained from SAP Quicksizer tool.

(F) Final SAPS result for Production system

Total SAPS value (F)  = SAPS value obtained from SAP quick sizer tool (A) + SAPS value obtained from Custom Load (B) + SAPS value obtained from Interfaces (C) + SAPS value obtained from Batch load (D) + SAPS obtained from uniocde (E) .

Sample example is shown in the figure below.

Accuracy has been estimated at  55% becaue  we have taken estimate value for custom loads, interfaces, uniocde  and batch loads. Also other processes such as data Archiving, Monthly/Quarterly/yearly closing account , full offline/online backup etc are not taken into account.

SAPS for Non-Production systems

SAPS for Development server

Only business configuration data is created in the development system. There will be no master and applications data . Custom objects are created in development server and also unit testing takes place in this server.

Thus only few developers will be used in the development server.

Thumb Rule: 35% of  Final SAPS taken in Production system  (F) will be used  for Development server.

SAPS  for Quality Server

In Quality system, data such as Master, Applications, User, Business configuration will be present in the Quality server. Periodically, data in the quality system is refreshed with full Production data.  Customizing data and / or custom objects imported into Quality system by means of transport requests that were created and released in the development system. After transport requests imported into the quality server, business consultants test business transactions or reports to ensure no error occured in the quality system.

Thus there will be some workprocesses (Dialog / background) running in the quality server during testing the transactions or reports.

Thumb Rule: 65% of  Final SAPS taken in porduction system (F) will be used for Quality server.

FAQ

Usually similar questions arises from various SAP customers

1)           What SAPS value are required for database server and SAPS value for Central Instance Server ?

Though SAP recommends 30% of Final SAPS value for database server and 70% of Final SAPS value for Central Instance server.

I do not agree with SAP recommendation as the performance issue is mostly due to high database server load becasue more number of workprocesses status in "running" (as in tx code sm50 or sm66) connected to database server for data fetch  ( you can see in tx code sm50 or sm66 "Sequential database read" or commit data i.e. saving records or line items to the database server ((high intensive Read and Write operations on the Disk storage  in the database server causes extremely high IO load).

Hence it is strongly advisable to have higher SAPS value for Database server.

2)     How many Application servers are required i.e. required number of Dialog Instance servers ?

Total number of workprocesses  depends on the number of CPU or cores installed in the server. One core (  for CPU speed less than 3GHz) can handle two  workprocesses. For CPU speed is 3GHz or higher, one  core can handle five  workprocesses. So for example if Central Instance has 6 cores and its CPU speed is 3.2Ghz then maximum number of workprocesses permissible is 30.  To increase beyond workprocesses, you need additional application server (i.e. Dialog Instance Server).

3) What about SAPS value after version upgrade ?

For version upgrade from SAP R/3 4.6C or below to SAP ECC 6.0 with EHP 4 or higher  or SAP WEB AS 620 and below upgrade to SAP Netweaver 7.3 and higher  without unicode   existing SAPS to be increased by 40% or by 60%  with unicode. 

For version upgrade from SAP ECC 5.0 to SAP ECC 6.0 with EHP 4 or higher or SAPWEB AS 640 and higher upgrade to NW 7.3 and higher. existing SAPS to be increased by 20% for non-unicode and 30% for uniocde

SAPS is not relevant for for EHP upgrade or SP stack upgrade,  However, for additional number of users, SAPS calculation is to be taken in to account.

Related Content

http://www.sap.com/solutions/benchmark/index.epx

http://service.sap.com/quicksizer   - For Sizing exercises,  QuickSizer tool from SAP MarketPlace

http://www.sap.com/solutions/benchmark/pdf/IBM_NewsJuly2010.pdf

See SAP note1833501 for the latest Diagnostics Agent Installation & Setup Guide.

Detailed Information available via SCN Wiki Article http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Maintenance+Procedures