eBOM project files with the extension ‘ebpx’ are really ‘XML’ files which can be edited with any text or xml editor. The data structure is hierarchal and needs to be translated into a structure more equivalent to a table with fields for reporting in Crystal Report. This is achieved using one or more xsl transformation files. When a Crystal report is opened in eBOM any xsl files found in the same folder as the report are processed against the current project before the report data is refreshed with the resulting output saved to the same folder in a file named after the xsl file with the xml extension.

In the example we make a file named ItemMaster.xsl which contains the xsl for selecting ItemMaster elements and their corresponding TypeName, PartNumber and Description from a project file and use it to make a new xml file named ItemMaster.xml. We then make a compatible schema file ItemMaster.xsd and in a new Crystal report use these two files to make a new data source using the Native XML driver.

A copy of the files resulting from this walkthrough can be downloaded by following this link:

http://www.beaumontsoftware.com/transfer/Crystal Walk Through Files.zip

Step 1 – Make a new xsl transformation file

Make a new folder for the report ‘…\My Documents\eBOM 2009\Reports\Demo’

In the new folder make a new text document and rename it ItemMaster.xsl

With Notepad edit ItemMaster.xsl and paste in the following text:

<?xml version=’1.0′ encoding=’utf-8′ ?>

<xsl:stylesheet xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” version=”1.0″><xsl:output method=”xml”/>

<xsl:template match=”/”>

<xsl:element name=”ItemMasters”>

<xsl:for-each select=”Project/ItemMasters/*” >

<xsl:element name=’ItemMaster’>

<xsl:element name=’TypeName’>

<xsl:value-of select=”./TypeName”/>

</xsl:element>

<xsl:element name=’PartNumber’>

<xsl:value-of select=”./PartNumber”/>

</xsl:element>

<xsl:element name=’Description’>

<xsl:value-of select=”./Description”/>

</xsl:element>

</xsl:element>

</xsl:for-each>

</xsl:element>

</xsl:template>

</xsl:stylesheet>

Step 2 – Export sample data

Open the Demo Project in eBOM 2009

On the Project Explorer select the project node

From the File menu choose Export

On the Export dialogue:

Set the XSLT location to the path of the xsl file made in step 1

Set the destination to the same path with the file name ‘ItemMaster.xml’

Click export

Step 3 – Make a Schema file

In the same report folder make a new text document and rename it ItemMaster.xsd

With Notepad edit ItemMaster.xsd and paste in the following text:

<?xml version=”1.0″ encoding=”utf-16″?>

<xs:schema attributeFormDefault=”unqualified” elementFormDefault=”qualified” xmlns:xs=”http://www.w3.org/2001/XMLSchema”>

<xs:element name=”ItemMasters”>

<xs:complexType>

<xs:sequence>

<xs:element maxOccurs=”unbounded” name=”ItemMaster”>

<xs:complexType>

<xs:sequence>

<xs:element name=”TypeName” type=”xs:string” />

<xs:element name=”PartNumber” type=”xs:string” />

<xs:element name=”Description” type=”xs:string” />

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:schema>

Step 4 – Make a new report

Open Crystal Reports and make a new blank report

Save it in the new folder alongside the ItemMaster.xsl, ItemMaster.xml and ItemMaster.xsd files

e.g. ‘…\My Documents\eBOM 2009\Reports\Example\Sample Report.rpt’

Step 5 – Set the data source

From the Crystal Reports Menu select Database – Database Expert…

On the Database Expert in the tree view of available data sources expand ‘Make New Connection’ and then the ‘XML’ node.

On the resulting XML dialogue set the Local XML File to ItemMaster.xml made in Step 2 – Export Sample Data

Make sure ‘Specify Schema File’ is checked and click ‘Next’

Set the ‘Local Schema file’ to ItemMaster.xsd set in Step 3 – Make a Schema file

Click End

Expand the ItemMasters node on the resulting new connection

Use the ‘>’ button to add ItemMasters/ItemMaster to the report

Click OK to close the Database Expert

Step 6 – Design Report

Use the Field Explorer to add the PartNumber and Description fields to the detail section of the report

Click preview to see the list of ItemMasters in the sample data.

Step 7 – Make the Report Portable

From the Database menu select ‘Set DataSource Location’

In the ‘Current Data Source’ window expand the ‘Properties’ node for the new connection.

Right click on ‘Local XML File’ and choose ‘Same as Report’

Repeat for ‘Local Schema File’

Close the ‘Set Datasource Location’ dialogue

Save and close the report

Step 8 – Test the report in eBOM 2009

Start eBOM 2009 and make a new project

Make a new component

Open the new report

2. Click the Report Preview button

3. The following window will show (or something similar). Type in an ID, range of IDs or a Working List Name (depending on which report you’ve opened)

4. You will then be questioned to log into the database using the biotics_report user password:

Search Methods:
Why are IDs better than names?

· Not case sensitive

· Quicker

Why are names better than IDs?

· Simple to remember

· No need to look names up

Working List Name – This report accepts a working list name as the search parameter. Use this report if you want to dump all of the records in a particular working list. The working list name is showed on the Biotics main window when a working list is active. Be advised that the working list name for a given subject area is not necessarily unique. If duplicate working list names are found in your database, the contents of all like-named working lists may be retrieved when using this report.

Working List ID – This report accepts a working list ID as the search parameter. Use this report if you want to dump all of the records in a particular working list. Working list IDs are always unique. Unfortunately, the working list ID is not showed on the Biotics main window when a working list is active. In order to see a list of the working list IDs for each working list name, run the following query in the Biotics Tracker Query Builder (substitute the appropriate working list type from the list below):

Subject Area Working List Type

Contact CON

Element ELE

Element Occurrence ELO

Managed Area MGA

Reference REF

Site SIT

SELECT * FROM WORKING_LIST WHERE WORKING_LIST_TYPE=’ELO’

ID – This report accepts either a single record ID or a range of record IDs for a given subject area. Use this report in order to dump one or more records by their unique record ID (without having to first make a working list.)

Note: All NatureServe Reports are configured to use the following ODBC Data Source configuration. If you choose to use a different configuration, you may have to enter your database password repeatedly for each subreport.

1. Click START menu –> Settings –> Control Panel –> Administrative tools –> Data Sources (ODBC) (Note: Windows NT/XP Configuration may be slightly different).

1. Select the System DSN tab from the ODBC Data Source Administrator. System DSN will make the ODBC connection for anyone who logs in to the computer, and User DSN will make an ODBC connection just for the current Windows user. Click the Add button.

1. Select the Oracle ODBC Driver (or Oracle in OraHome92 for Oracle 9i or Oracle in OraDb10g_home… for Oracle 10g) from the driver list. Note: NEVER use the Microsoft ODBC for Oracle driver. …unless you like poor results and poorer performance.
   

1. Click End.

1. The Oracle ODBC Driver Configuration window is showed. Fill in the following fields. Your TNS Service Name may vary depending – for a standard installation, this will be ORACLE_SERVER.

Data Source Name: BIOTICS_REPORT

Description: Reporting Connection

Service Name: ORACLE_SERVER

1. Click Test Connection – this is only available in newer versions, therefore skip to step 8 if you do not have this button.

1. In the Oracle ODBC Driver Connect window, enter the ‘biotics_report’ username if necessary and password (biotics_report) and select OK. As long as you have the right user name and password, the connection should be successful.
   

8. Click OK in the ODBC Data Source Administrator window.

An other way is to make use of DataDefinition files. They are just ASCII files which contains the fields and their properties that are to be used in the report. Using such a file means that there is no direct connection with the database. In Visual Basic the query is executed and the result – together with de DataDefinition file – will produce the report.

To make it work you have to take three steps:

1 making the DataDefinition file

2 making the report

3 merge them in VB and show the result

The Biblio.mdb will be used in this example.

Step 1: making the DataDefinition file

The report needs to be a view to be of all present authors with their titles and year of publication. The fields Author.Author, Titles.Tiltle and Titles.Year Published must be shown on the report. Due the keys the table Title Authors is used. The SQL to get the result is:

SELECT Authors.Author, Titles.Title, Titles.[Year Published]

FROM Titles INNER JOIN (Authors INNER JOIN [Title Author] ON Authors.Au_ID = [Title Author].Au_ID) ON Titles.ISBN = [Title Author].ISBN;

Making the DataDefinition file can be done in Crystal Reports but also in any ordinary editor like notepad. The format is fixed:

Fieldname

Fieldtype

Fieldsize

Description

All on one line separated by a TAB.

Author String 255 name

Title String 255 Title

YearPublished String 4 year

Don’t forget to save the file with the name: AuthorTitles.ttx Crystal Reports needs that to be able to define a report on this file.

Step 2: making the report

Start Crystal Report; choose for New, Standard report. On the tab Data select Active Data. On the next screen the choice is Data definition. Select with Browse the file you have made in step 1. Click on End. On the tab Fields select Add all and then Preview Report.

The report will be shown. As values the given descriptions will be shown. With Design you can change what you want on the report. Just save the report (standard extension .rpt). For quick merging in VB use the same name for the report as for the DataDefinition file: AuthorTitles.rpt

Step 3: merge them in VB and show the result

Open a new project in VB (name = prjDDCR). Place on the default form (name = frmDDCR) a commandbutton (name = cmdShowReport; caption = Show report). Don’t forget to add the reference for DAO (Microsoft DAO Object Library ) and for Crystal Reports (Crystal Reports Engine Object Library).

Add the next code to the general section of the form. (It’s just an example so all values are hard-coded.)

Option Explicit

Private db As DAO.Database

Private CDOSet As Object

Private RepApp As Object

Private CrystRep As CRPEAuto.Report

Private RepDb As CRPEAuto.Database

Private RepTables As CRPEAuto.DatabaseTables

Private RepTable As CRPEAuto.DatabaseTable

Private LabelRows() As Variant

On the Form_Load event add the next code. Don’t forget the code in the Form_Unload event! Change the path to the right location of your local Biblio.mdb

Private Sub Form_Load()

Set db = OpenDatabase(App.Path & “\biblio.mdb”)

End Sub

Private Sub Form_Unload(Cancel As Integer)

db.Close

End

End Sub

Under the cmdShowReport_Click event is the code which merge the result of the executed SQL with the DataDefinition file and the actual report.

Private Sub cmdShowReport_Click()

Dim strSQL As String

Dim rs As DAO.Recordset

Dim intFN As Integer

Dim strFN As String

Dim strLine As String

Dim intX As Integer

Dim intC As Integer

Dim intLabelCount As Integer

‘

Set RepApp = CreateObject(“Crystal.CRPE.Application”)

Set CrystRep = RepApp.OpenReport(App.Path & “\AuthorTitles.rpt”)

Set CDOSet = CreateObject(“CrystalDataObject.CrystalComObject”)

‘

intLabelCount = 0

intFN = FreeFile

strFN = App.Path & “\AuthorTitles.ttx”

Open strFN For Input As intFN

Do While Not EOF(intFN)

Line Input #intFN, strLine

If Len(strLine) <> 0 And Right(strLine, 2) <> “%%” Then

CDOSet.AddField Split(strLine, vbTab)(0), vbString

intLabelCount = intLabelCount + 1

End If

Loop

‘

strSQL = “SELECT Authors.Author, Titles.Title, Titles.[Year Published]” + _

” FROM Titles INNER JOIN (Authors INNER JOIN [Title Author] ON ” + _

” Authors.Au_ID = [Title Author].Au_ID) ON Titles.ISBN = [Title Author].ISBN;”

Set rs = db.OpenRecordset(strSQL)

With rs

If Not (.EOF And .BOF) Then

.MoveLast

ReDim LabelRows(.RecordCount – 1, intLabelCount – 1)

.MoveFirst

For intX = LBound(LabelRows) To UBound(LabelRows)

For intC = 0 To .Fields.Count – 1

LabelRows(intX, intC) = CStr(“” & .Fields(intC).Value)

Next ‘intC

.MoveNext

Next ‘intX

‘

CDOSet.AddRows LabelRows

Set RepDb = CrystRep.Database

Set RepTables = RepDb.Tables

Set RepTable = RepTables(1)

Call RepTable.SetPrivateData(3, CDOSet)

CrystRep.Preview “AuthorTitles.rpt”

Else

‘

End If

End With

‘

Set rs = Nothing

Set RepApp = Nothing

Set CrystRep = Nothing

Set CDOSet = Nothing

End Sub

Compile the project. Just hit the commandbutton. Crystal Reports will open a separate window to show the result of the executed query in the report. You can open as much reports as you wish.

The advantage of using a DataDefinition file is that no hard solutions has to be made on the database side. You don’t have to make views available to the users. You don’t have to make a special user with only access to those tables you want. Adding a new report does not mean to be forced to compile a new executable. If you save the SQL and the DataDefinition files in the database you only have to update the relevant tables. You can save the reports also in the database but it’s better to have them located outside the database. Showing all available reports form a certain location is just simple to do. Merging the three files together is just a simple extension on the example project.

Download Now —>

What is the use of profile paramater ztta/roll_area?

The value specifies the size of the roll area in bytes.  The roll area is one of several memory areas, which satisfies the user requests of user programs.  For technical reasons, but, the first 250 KB or so of a user context are always stored in the roll area, further data
- up to the roll area limit ztta/roll_first,
- in the extended memory, up to the limit ztta/roll_extension or if extended memory is exhausted, then
- again in the roll area, until the roll area is full, then
- in the local process area, up to the limit abap/heap_area_dia or abap/heap_area_total or until the address space or the
  swap space is exhausted.

Followed by termination with errors like STORAGE_PARAMETERS_WRONG_SET an error code, that points to memory bottleneck Minimum data transfer with context change; but, the increase helps to avoid problems (address space, swap space, operating system paging).        *– Anupam Sharma

What is R/3? and  what is basis version?

SAP Basis:
- Provides the runtime environment for all SAP applications
- Optimally embeds the application in the system environment
- Defines a stable architecture framework for system enhancements
- Contains the tools for administering the entire system
- Allows the distribution of resources and system components
- Provides interfaces for decentralized system parts and external products.

An R/3 instance is a group of R/3 services that are started and stopped as a unit (by an R/3 dispatcher) and have a common instance profile. The name of an R/3 instance is composed of letters standing for the relevant services, and an instance number which is unique for each computer. The services may be D, V, E, B, M, G, or S, which respectively stand for dialogue, update, enqueue, background, message, gateway, and spool services. 

Tips by : Suresh Babu

I want to know the version or name of SAP that is implemented in real time?

This is a very generic question and really depends on what you are implementing (modules).

The history of the “R/3″ is

3.0D Basis 300
3.0E Basis 300
3.0F Basis 300
3.1H Basis 310
3.1I Basis 310
4.0B Basis 400
4.5B Basis 450
4.6C Basis 460
4.71 Basis 6.20
4.72 Basis 6.20
5.00 Basis 6.40 (ECC 5.0 – Enterprise Core components)
6.00 Basis 7.00 (ECC 6.0) – really in RampUp

All of those have increased business functionality and interfaces to other systems (CRM, BW etc.)

What is mysap?

It’s a term for all the systems that in a contract (e. g. a MySAP business suite consist of ERP2005, CRM2005, SRM2005).

What is the systems configuration required to implement SAP.. i.e for production,development and QAS servers the hard disk space, RAM, Processor

This also depends on what your are implementing, how many users will work on the system, how many records in what area are made etc.

We need a HUGE database system and an even larger application server for ~ 900 users and 12 languages.

What is ASAP?

It’s an ancient term for an implementation strategy. Blueprint -> prototype -> goLive (if you want to say it in one sentence).

How should I set priority for Printing say like user, teamlead, project manager?

There’s nothing like “priority” settings for spool processes. Just define more (profile parameter rdisp/wp_no_spool) processes so people don’t need to wait.

Using Tc SGEN I have generated 74% job and later I have terminated the job.  I wish to start generating from where it stopped I have refreshed but to no chance nothing was done.  How should I further proceed so as to complete the remaining job..

Start SGEN again and select the same you have selected before. It will popup and question if you want to start from scratch or generate the just the remaining.

Private mode is a mode where the heap data is getting exclusively allocated by the user and is no more shared across the system. This happens when your extended memory is exhausted.

What is osp$ mean? What if user is given with this authorisation?

OPS$ is the mechanism the <SID>adm users uses to connect to the database .

Why do you use DDIC user  not SAP* for Support Packs and SPam?

Do _NOT_ use neither DDIC nor SAP* for applying support packages. Copy DDIC to a separate user and use that user to apply them.

Can you kill a Job?

Yes – SM37 – select – kill

If you have a long running Job,  how do you analyse?

Use transaction SE30.

How to uncar car/sar files in a single shot?

on Unix: 
$ for i in *.SAR; do SAPCAR -xvf $i; done

When we should use Transactional RFC ?

A “transactional RFC” means, that either both parties agree that the data was correctly transfered – or not. There is no “half data transfer”.

What is the use of Trusted system. I know that there is no need of UID and PWD to communicate with partner system. In what situation it is excellent to go for Trusted system ?

E. g. if you have an R/3 system and a BW system and don’t want to maintain passwords. Same goes for CRM and a lot of other systems/applications.

Let me know if my understanding below is right:
1) By default the RFC destination is synchronous
2) Asynchronous RFC is used incase if the system initiated the RFC call no need to wait for the response before it proceeds to something else.

Yes – that’s right.

But keep in mind, that it’s not only a technical issue whether to switch to asynchronous. The application must also be able to handle that correctly.

Which table contains the details related to Q defined in SPAM? Is there a way to revert back the Q defined? If yes, How?

There is a “delete” button when you define the queue. If you already started the import it’s no more possible since the system will become inconsistent.

What is a developer key? and how to generate a developer key?

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

What is XI3.0 ? CLARIFY XI = Exchange Infrastructure – Part of Netweaver 2004.

SAP Exchange Infrastructure (SAP XI) is SAP’s enterprise application integration (EAI) software, a component of the NetWeaver product group used to facilitate the exchange of information among a company’s internal software and systems and those of external parties. Like other NetWeaver components, SAP XI is compatible with software products of other
companies. 

SAP calls XI an integration broker because it mediates between entities with varying requirements in terms of connectivity, format, and protocols. According to SAP, XI reduces integration costs by providing a common repository for interfaces. The central component of SAP XI is the SAP Integration Server, which facilitates interaction between diverse operating systems and applications across internal and external networked computer systems. 

How to see when were the optimizer stats last time run? We are using win2k, oracle 9, sapr346c.

Assumed DB=Oracle

Select any table lets take MARA here but you should do the same for MSEG and few others to see whether the dates match or not.Run the following command on the command prompt:-

  select last_analyzed from dba_tables where table_name like ‘%MARA%’;

This gives you a straight answer .Else you can always fish around in DB14 for seeing when the optimzer stats were updated.

What are the APO Basis transaction code which is required for monitoring of the APO System?

Answer:

You can check Transactions under menu path of SCM Basis:

Some of vital transactions are:

/SAPAPO/AMON1 – Alert Monitor 
/SAPAPO/AMON3 – Alert Overview by Objects 
/SAPAPO/AMONMSG_SEND – Send Alerts 
/SAPAPO/AMONMSG_SEND – Send Alerts 

/SCMB/ANOT_PROF – Make/Change Alert Notification Profile (User) 
/SCMB/ANOT_PROF – Make/Change Alert Notification Profile (User) 
/SCMB/ANOTMP – Make/Change Message Profile 

/SCMB/ANOTMP – Make/Change Message Profile 

/SCMB/ANOTMP – Make/Change Message Profile 
/SAPAPO/PE_LOG_DISP – Show PSM Application Log 
/SAPAPO/PE_SEL – Define Selections 
/SAPAPO/PE_SEL – Define Selections 
/SCMB/TDL_BO_COPY – Define Service Profile for Copying Time Series 

CCMS Related:

RZ20 – CCMS Monitor Sets 
RZ23N – Central Performance History (CPH) 
RZ03 – Control Panel 
SM66 – Global Process Overview 
SM49 – Do External Commands 

Performance related Tcode:

ST03N – Aggregated Statistics Records – Local 
ST03G – Aggregated Statistics Records – Global 
STAD – Individual Statistics Records (ABAP Only) 
STATTRACE – Individual Statistics Records (All) and Traces 
ST07 – User Distribution 

ST02 – Buffers 
ST10 – Table Accesses 
TU02 – Parameter Changes 
OS06 – Activity 
OS04 – System Configuration 
OS03 – Parameter Changes 
OS07 – Activity 
OS05 – System Configuration 
OS03 – Parameter Changes 
OS01 – LAN Check with PING 
AL15 – SAPOSCOL Destination 

Database:

ST04N – Activity 
DB01 – Exclusive Locks 
DB02 – Tables/Indexes 
DB03 – Parameter Changes 
SM21 – System Log 
ST22 – ABAP Runtime Errors 
AL11 – SAP Directories 

SM50 – Process Overview 
SM66 – Global Process Overview 
SM51 – SAP Instances 
SM04 – Local Users 
AL08 – Global Users 

RZ10 – System Profile 
SMLG – Logon Groups 
SM69 – Show/Change External Commands 

DB Admin:

DB12 – Backup Logs 
DB13 – Local 
DB13C – Central 
DB14 – Operations Monitor 

DB20 – Make Statistics 
DB21 – Configuration 

Print related:

SP01 – Output Controller 
SPAD – Spool Administration 
SE73 – Font Maintenance 
SP11 – TemSe Contents 
SP12 – TemSe Administration 

Background Processing:

SM37 – Jobs – Overview and Administration 
RZ01 – Job Scheduling Monitor 

Although there might be many SOX critical transactions, here are a handy list of some most critical ones.

TCODES Critical Risk Description

F.80      Mass Reversal of Documents
FI12      Change House Banks/Bank Accounts
F.34      Credit Limit Mass Changes 
CA87    Mass Replace Work Center
CL04    Delete Class 
CAT6   Human Resources
IP30     Run Date Monitoring
LN08    Number range maint.: LVS_LENUM
PA20    Show HR Master Data
PA70    Quick Entry
PA30    Maintain HR Master Data
PFCG   Role Maintenance – System integrity, stability at risk
MMPV Close Periods
MMRV Allow Posting to previous Period
RZ04    Maintain SAP Instances
SU01    User Maintenance – Should be restricted to User Admins only
SA38   ABAP Reporting -Can run programs not protected appropriately
SCC1  Client Copy – Special Selections
SCC4  Client Admin. – System stability & integrity at risk
SCC5  Delete Client – System stability at risk
SCC6  Client Import – System stability & integrity at risk at risk
SCCL  Local Client Copy – System stability & integrity at risk
SE01   Transport Organizer – System stability & integrity at risk
SE11   Data Dictionary Maint. – System stabiltiy & integrity at ris
SE13   Maintain tech tables settings – System stabilitiy at risk.
SE16   Data Browser – Exposure to confidential information
SE37   Function Builder
SE38   ABAP Editor – System stabiltiy & integrity at risk
SM01  Lock Transactions – System stabiltiy at risk
SM02  System Messages – Should be restricted to System Admins only
SM30  Table Maintenance – System integrity & stability at risk 
SM49  Do OS commands – System stability at risk
SU02   Profile Maintenance – System stability and integrity at risk

You check the work processe and even cancel it if some work proccesses which are unwanted or taking too long time which are causing your system to work properly.
Some times due to too many processes the system become slow.

Now if you want to delete then select the procees go to menu PROCESS?

Under process there are two option one is cancel with core and other is cancel without core.

Try to cancel the processes using cancel without core option because if you cancel with core then the other dependent processes are also get canceled.

WEDI – ALE IDoc Administration 
WE21 – Ports in Idoc processing 
WE60 – IDoc documentation 
SARA – IDoc archiving (Object type IDOC) 
WE47 – IDoc status maintenance 
WE07 – IDoc statistics 

BALE – ALE Distribution Administration 
WE05 – IDoc overview 
BD87 – Inbound IDoc reprocessing 
BD88 – Outbound IDoc reprocessing 
BDM2 – IDoc Trace 
BDM7 – IDoc Audit Analysis 
BD21 – Make IDocs from change pointers 
SM58 – Schedule RFC Failures 

Basic config for Distributed data:
BD64: Maintain a Distributed Model 
BD82: Generate Partner Profile 
BD64: Distribute the distribution Model 

Programs:
RBDMIDOC – Making IDoc Type from Change Pointers 
RSEOUT00 – Process all selected IDocs (EDI) 
RBDAPP01 – Inbound Processing of IDocs Ready for Transfer 
RSARFCEX – Do Calls Not Yet Executed 
RBDMOIND – Status Conversion with Successful tRFC Execution 
RBDMANIN – Start error handling for non-posted IDocs 
RBDSTATE – Send Audit Confirmations 
For testing you can use WE19

This is the transaction code for the Dynamic Menu.

Based on your search string, you can get all related transaction codes for all the SAP application modules.

For e.g. the Search text for ADMIN returns the following results:

———————————————————-
|Tcode|Transaktionstext                                 
———————————————————-
|ADOK |AM: System Administration Guide                  
|BALE |Area Menu for Administration                     
|BDMO |ALE CCMS Group Administration              

CATSX|Time Sheet Admin.: Initial Screen                
|CICY |CTI Administration                               
|CJV6 |Maintenance: Version administration              
|CN84 |PS: Archiving project – admin.                   
|COA4 |PP: Archiving order – administration             
|CSADM|Content Server Administration                    
|FC_BW|Administrator Workbench                          
|FDTA |TemSe/REGUT Data Administration                  
|FDTT |Treasury Data Medium Administration              
|FO86 |Change active admin.contract fees                
|FO8E |Make admin.contract event                      
|FO8F |Change admin.contract event                     
|FO8G |Show admin.contract event                     
|FO8H |Admin.costs acct sttlmnt simulation              
|FOART|REsearch: Administration Web-User                
|HRCMP|Compensation Administration                      
|HRCMP|Budget Administration: Show                   
|HRCMP|Budget Administration: Change                  

|IM_AR|Admin. of App. Request Archives                  
|KA18 |Archive admin: assess., distr., …              
|KE72 |Archive Administration: Line Items               
|KE73 |Archive Administration: Totals Recs              
|KPRO |KPRO Administration                              
|OAAD |ArchiveLink Administration Documents             
|OG00 |Personnel Administration Customizing             
|OG01 |Personnel Administration Customizing             
|OMSM |CS MM Set Up Administrative Data                 
OOCM_|Compensation Administration Settings             
|OOML |Room Administration Mail Connection              
|OOPC |Administration: Personnel No. Check              
|OY22 |Make subadministrator  Customizing             
|OYEA |IDoc administration                              
|PA97 |Compensation administration – matrix             
|PA98 |Compensation Administration                      
|PA99 |Compensation Admin. – Release Report             
|PACA |PF administration                                
|PAT1 |Personnel Administration infosystem              
|PC00_|CBS survey salary administrations                
|PC00_|Tax Certificates – Administration 16             
|PP26 |Plot Scenario Administration                     
|PP2D |Administer Payroll Results                       
|PSO5 |PD: Administration Tools                         
|PUCA |PC administration for PF                         
|PVSEA|Administer Search Engine                         
|QD25 |Archiving Notifications: Admin.                  
|S002 |Menu Administration                              
|SA02 |Academic title (cent. addr. admin.)             
|SA04 |Name prefixes (centr. addr. admin.)              
|SA05 |Name suffix (centr. addr. admin.)                
|SA07 |Address groups (centr. addr. admin.)             
|SA08 |Person groups (centr. addr. admin.)              
|SA09 |Internat. versions address admin.                
|SA10 |Address admin. communication type                
|SARA |Archive Administration                           
|SBPT |Administration Process Technology                
|SCC4 |Client Administration                            
|SCON |SAPconnect – Administration                      
|SCOT |SAPconnect – Administration                      
|SCUA |Central User Administration                      
|SCUM |Central User Administration                     
|SE78 |SAPscript: Graphics administration           
|SECST|Administration of Secure Memory            
|SENG |Administration of External Indexes            
|SENGE|Explorer Index Administration                   
|SIAC1|Web Object Administration                        
|SLICE|Administer SAP Licenses                          
|SLWA |Translation Environment Administratn          
|SM14 |Update Program Administration                    
|SP12 |TemSe Administration                             
|SPAD |Spool Administration                             
|SPAT |Spool Administration (Test)                   

SPHA |Telephony administration                         
|SPHB |SAPphone: System Administration                  
|SSAA |System Administration Assistant                  
|SSCA |Appointment Calendar: Administration             
|SSCA1|Appointment calendar: Administration            
|SSO2 |Workplace Single Sign-On Admin.                 
|SSO2_|Workplace Administration SSO2 Ticket             
|STMA |Proposal Pool Administration                    

|SURAD|Survey Administration                            
|SURL_|Personalization for URL Gen. Admin.              
|SUUMD|Show User Administration                      
|SWDC |Workflow Definition: Administration              
|SWEAD|Event Queue Administration                       
|SWEQA|Event Queue Administration

|SWEQA|Queue Administrator Maintenance             
|SWIA |Selection rep. for work items(admin)             
|SWRK |Administrtation using work areas                 
|SWUF |Administration of Runtime System                 
|SWUL |Customizing: Process Administrator               
|SWUX |SAPforms Administration                          
|SYSAD|System Administration: Task List                 
|S_ALR|IMG Activity: CIC_V_CCMCTIADMIN                  
|S_ALR|IMG Activity: SIMG_EURO_ADMINUSER                
|S_BCE|IMG-Aktivität: BCDIGSI_ADMIN                  
|S_PH0|InfoSet Query: Administration                    
|S_PH0|InfoSet Query: Administration                    
|S_PH0|InfoSet Query: Administration                    
|S_PH0|InfoSet Query: Administration                    
|S_PH0|InfoSet Query: Administration                    
|TBD0 |Datafeed: Adminster Archives                     
|TBD3 |Datafeed: Market data administration         
|TBD6 |Datafeed: Log file administration                
|WE46 |IDoc administration                              
|WORKI|Administrtation using work areas                 

This is the transaction code for the Dynamic Menu.

Based on your search string, you can get all related transaction codes for all the SAP application modules.

For e.g. the Search text for ADMIN returns the following results:

----------------------------------------------------------
|Tcode|Transaktionstext                                  |
----------------------------------------------------------
|ADOK |AM: System Administration Guide                   |
|BALE |Area Menu for Administration                      |
|BDMO |ALE CCMS Group Administration                     |
|CATSX|Time Sheet Admin.: Initial Screen                 |
|CICY |CTI Administration                                |
|CJV6 |Maintenance: Version administration               |
|CN84 |PS: Archiving project - admin.                    |
|COA4 |PP: Archiving order - administration              |
|CSADM|Content Server Administration                     |
|FC_BW|Administrator Workbench                           |
|FDTA |TemSe/REGUT Data Administration                   |
|FDTT |Treasury Data Medium Administration               |
|FO86 |Change active admin.contract fees                 |
|FO8E |Make admin.contract event                       |
|FO8F |Change admin.contract event                       |
|FO8G |Show admin.contract event                      |
|FO8H |Admin.costs acct sttlmnt simulation               |
|FOART|REsearch: Administration Web-User                 |
|HRCMP|Compensation Administration                       |
|HRCMP|Budget Administration: Show                    |
|HRCMP|Budget Administration: Change                     |
|IM_AR|Admin. of App. Request Archives                   |
|KA18 |Archive admin: assess., distr., ...               |
|KE72 |Archive Administration: Line Items                |
|KE73 |Archive Administration: Totals Recs               |
|KPRO |KPRO Administration                               |
|OAAD |ArchiveLink Administration Documents              |
|OG00 |Personnel Administration Customizing              |
|OG01 |Personnel Administration Customizing              |
|OMSM |CS MM Set Up Administrative Data                  |
|OOCM_|Compensation Administration Settings              |
|OOML |Room Administration Mail Connection               |
|OOPC |Administration: Personnel No. Check               |
|OY22 |Make subadministrator  Customizing              |
|OYEA |IDoc administration                               |
|PA97 |Compensation administration - matrix              |
|PA98 |Compensation Administration                       |
|PA99 |Compensation Admin. - Release Report              |
|PACA |PF administration                                 |
|PAT1 |Personnel Administration infosystem               |
|PC00_|CBS survey salary administrations                 |
|PC00_|Tax Certificates - Administration 16              |
|PP26 |Plot Scenario Administration                      |
|PP2D |Administer Payroll Results                        |
|PSO5 |PD: Administration Tools                          |
|PUCA |PC administration for PF                          |
|PVSEA|Administer Search Engine                          |
|QD25 |Archiving Notifications: Admin.                   |
|S002 |Menu Administration                               |
|SA02 |Academic title (cent. addr. admin.)               |
|SA04 |Name prefixes (centr. addr. admin.)               |
|SA05 |Name suffix (centr. addr. admin.)                 |
|SA07 |Address groups (centr. addr. admin.)              |
|SA08 |Person groups (centr. addr. admin.)               |
|SA09 |Internat. versions address admin.                 |
|SA10 |Address admin. communication type                 |
|SARA |Archive Administration                            |
|SBPT |Administration Process Technology                 |
|SCC4 |Client Administration                             |
|SCON |SAPconnect - Administration                       |
|SCOT |SAPconnect - Administration                       |
|SCUA |Central User Administration                       |
|SCUM |Central User Administration                       |
|SE78 |SAPscript: Graphics administration                |
|SECST|Administration of Secure Memory                   |
|SENG |Administration of External Indexes                |
|SENGE|Explorer Index Administration                     |
|SIAC1|Web Object Administration                         |
|SLICE|Administer SAP Licenses                           |
|SLWA |Translation Environment Administratn              |
|SM14 |Update Program Administration                     |
|SP12 |TemSe Administration                              |
|SPAD |Spool Administration                              |
|SPAT |Spool Administration (Test)                       |
|SPHA |Telephony administration                          |
|SPHB |SAPphone: System Administration                   |
|SSAA |System Administration Assistant                   |
|SSCA |Appointment Calendar: Administration              |
|SSCA1|Appointment calendar: Administration              |
|SSO2 |Workplace Single Sign-On Admin.                   |
|SSO2_|Workplace Administration SSO2 Ticket              |
|STMA |Proposal Pool Administration                      |
|SURAD|Survey Administration                             |
|SURL_|Personalization for URL Gen. Admin.               |
|SUUMD|Show User Administration                       |
|SWDC |Workflow Definition: Administration               |
|SWEAD|Event Queue Administration                        |
|SWEQA|Event Queue Administration                        |
|SWEQA|Queue Administrator Maintenance                   |
|SWIA |Selection rep. for work items(admin)              |
|SWRK |Administrtation using work areas                  |
|SWUF |Administration of Runtime System                  |
|SWUL |Customizing: Process Administrator                |
|SWUX |SAPforms Administration                           |
|SYSAD|System Administration: Task List                  |
|S_ALR|IMG Activity: CIC_V_CCMCTIADMIN                   |
|S_ALR|IMG Activity: SIMG_EURO_ADMINUSER                 |
|S_BCE|IMG-Aktivität: BCDIGSI_ADMIN                      |
|S_PH0|InfoSet Query: Administration                     |
|S_PH0|InfoSet Query: Administration                     |
|S_PH0|InfoSet Query: Administration                     |
|S_PH0|InfoSet Query: Administration                     |
|S_PH0|InfoSet Query: Administration                     |
|TBD0 |Datafeed: Adminster Archives                      |
|TBD3 |Datafeed: Market data administration              |
|TBD6 |Datafeed: Log file administration                 |
|WE46 |IDoc administration                               |
|WORKI|Administrtation using work areas                  |
----------------------------------------------------------

What the difference between tcode SE09 & SE10?

SE09 transaction is for workbench transport request wherein the developers can track their changes or modifications to the workbench objects . 

Whereas SE10 is a customising transport request transaction.this is used for showing customising requests. Sometimes this may be restricted to business analysts.

The steps to change the Title of any SAP transaction code are as follows:

First, goto tcode SE63

On the top left Menu of the screen – Click Translation – Small texts – Transactions

For example, assuming you want to change the title of the tcode FB01 from Post Document to Post Document for G/L.  On the first screen, fill in the following information:

Transaction code – FB01

Source Language – English
Target Languate – English

To change the Title, click the Edit button

On the second line, type in the Title (For e.g. Post Document for G/L) you want for the transaction code

Click the Save button

Now, called up the transaction code /nFB01 again and you should be able to view the new Title.

Please note that it works for most of the Transaction code except for those new Delight in transaction code in 4.6x.

Now days there’s so many choices. Start at http://www.sap.com/services/education/index.epx, pick your country and select Certification Program. 

If you’ve got enough years of experience I don’t reckon certification would make much difference to a full time job. 

But if you’re a contractor, I could see it highly worthwhile. Upgrades / Migrations have to have certified Basis Consultant.

Do you require training to attend certification?

I have done certification in the month of FEB 2003. I took training also. 

If you question me the question – Do you require training to attend certification? I will question you following questions- 

1. Do you have time to attend the course in the first place? 
2. Do you want to inform outside world that you want to prove yourself? Coz, World listen you when you are certified. No matter how terrible your skills are. 
3. Do not want to take chances? 
4. Invest money? Remember I am using word invest money? Investment is always linked with expectations of future higher returns? 
5. Can keep job and other onhand tasks away for the training time? In otherwords have difficulty to free yourself and so the best choice is making yourself free by attending course would help? 
6. Want to know in and out of SAP? Coz course would try to give you the behind picture in depth (practically may not be possible but may be right to some extent) 
7. Conceptually weak in many of the aspects of basis? 

If your answer is “YES” then better take course before writing exam? 

Esp. in IT, you learn quicker when someone guide you rather than you do self study. Of course with Basis certification you need both as time is limited. Also you may have to fight for best tutor (remember). 

There are pros and cons. You are the better judge. If you can give more valid reasons for the choice you made. Go ahead. Sure you will win. Most vital is committment. 

Caution: more than one answer may be right.
Please mark ALL right answers.

Question:
When making a logon group for Logon Load Balancing, which of the following CANNOT be specified?

A.  Maximum allowable response time. 
B.  Maximum number of users who may be logged on to the instance.
C.  Name of the instance defined for the logon group. 
D.  Maximum number of sessions per user.
E.  Name of the logon group

Question:
Which R/3 System user is used for starting external programs using SAP background jobs?

A.  DDIC
B.  SAP*
C.  SAPR3
D.  SAPCPIC
E.  <sid>adm

Question:
Name the R/3 System transaction used for mointoring a spool requests.

A.  SM50
B.  SM51
C.  SPAD
D.  SP01
E.   SM37

Question:
Which of the following is authorized to maintain R/3 user id parameters?

A.  Only the R/3 system administrator. 
B.  All R/3 users having an account in the same R/3 client.
C.  Only the user himself.
D.  Only the R/3 system administrator and the user.

Question:
Given a LAN with an R/3 Central Instance with database (Node: host1, Instance Name:DVEBMGS01, SAPSID:C11), and R/3 Dialog Instance (Node: host2), and several R/3 Frontend PC’s what is the name of the profile where the SAPDBHOST parameter is defined?

A.  C11_DVEBMGS00_host1
B.  The SAPDBHOST parameter is defined in the database startup profile.
C.  TEMU.PFL
D.  DEFAULT.PFL
E.  START_DVEBMGS01_host1

Question:
Given and R/3 Central Instance with all services installed, using Instance ID01, and having the SAP ID of C11.  What is the name of the directory where the work process trace files are written (for Windows NT replace the “/” with “\”)?

A.  /usr/sap/C11/DVEBMGS01/data
B.  /usr/sap/C11/DVEBMGS01/log
C.  /usr/sap/C11/DVEBMGS01/work
D.  The trace files are written in internal database tables.
E.  The trace files are written in the home directory of the database.

Question:
Which of the following functions is NOT possible using the SAP Online Service System (OSS)?

A.  Do online searches for R/3 Notes.
B.  Register problems with the SAP Hotline.
C.  Lookup SAP training dates and course offerings.
D.  Register changes to SAP objects.
E.  Apply for official Internet address from SAP.

Detailed Analysis of Monitoring Process

Standard System Checks

C

1.1 Check that All Application Servers are up and Work Process Analysis – SM51

Transaction SM51 allows you to look at all the servers in your system (for example, the PRD database server and all of its application servers). You do not have to log into each server individually.

§ If one of your dialog application servers is not up, the users who normally log on to that application server will not have a server to log on to.

§ If the batch application server is down, batch jobs that are specified to run on that server will not run.

1. In the Command field, enter transaction SM51 and choose Enter (or choose ToolsàAdministration, then MonitoràSystem monitoringàServers).

2. Review the list of instances under Server name. Verify that all your instances are listed. If it is listed, it is up and running.

2

Process overview transactions allow users to view the status of work processes and monitor for problems. Transaction SM51 is a central transaction from which you can select the instance to monitor. SM51 starts transaction SM50 for each application server. Transaction SM50 is used for a system without application servers.

Transaction SM51 is one place to look for jobs or programs that may be “hung,” which would be indicated by long run times. If batch jobs are not running, transaction SM50 may provide a hint of the problem, if all the batch work processes are in use.

1. In the Command field, enter transaction SM51 and choose Enter (or choose ToolsàAdministration, then MonitoràSystem monitoringàServers).

2. Select the instance you want to view.

3. Choose Processes.

4. This is the Process Overview transaction (SM50) for that instance.

2

Some of the column definitions are:

Column Text Definitions

No Work process number

Ty Type of work process

PID OS PID (Process ID) number

Status Current status of the work process

Err Number of detected errors in the work process

CPU Cumulative CPU time that the current process is taking

Time Cumulative “wall” time that the current process is taking

Program Name of the ABAP program

Clie Client number

User User ID that is using the work process

Table Table that the action is being performed on

1.2 SM04 (USER OVERVIEW)

Menu Path:

Tools/Admin/Monitoring/System/Users

Note: Unfamiliar user id’s, addresses unresolved to names, what clients are logged in to, unusual number of sessions open and ensure the tracing is turned off.

1.3 SM66 (Global Process Monitor)

Menu Path:

Tools/Administration/Computing Center/Management System/Control/All work Processes

Provides overview of work process activity in the system. Helps to identify long running programs as well as the reason for slow performance.

Vital Statistics:

Block work processes (Time>5Sec)

Long Database Operations (Ex: SAPLGLIV, SAPLNRIV) running for long time.

Many Load Operations

Work processes in PRIV mode

Work processes with high number of restarts

1.4 ST07 (Application Monitor)

It is the responsibility of the BASIS administrator to monitor the number of users on a particular application server, based on this we can configure logon groups (SMLG).

1.5 Locks, Transaction SM12

A “lock” is a mechanism that prevents other users from changing the record on which you are working. There may be “ancient” locks still in place from transactions that did not release, or from when the user was cut off from the network. Unless cleared, these locks prevent access or change to the record until the system is cycled. The simplest way to locate them is to look for locks from prior days.

Vital: The profile parameter rdisp/gui_auto_logout should be set. This parameter defines an automatic logout of the user if there is no activity for the set number of minutes.

1. In the Command field, enter transaction SM12 and choose Enter (or choose ToolsàAdministration, then MonitoràLock entries).

2. Enter * in Client.

3. Clear the User name field.

4. Choose Enter.

5. Look for locks from previous days in the Time column.

The presence of a lock from a previous day could mean that the user was “disconnected” from the network and the R/3 System.

To clear a lock, complete these steps on the system’s application and the database servers:

1. Check that the user is not logged on any of the servers with transaction SM04 (no application servers) or AL08 (with application servers).

If the user is not on the system, but transaction SM04 shows them on the system, delete their sessions. This step, by itself, may clear the lock.

2. Check that there are no processes running under the user ID using transaction SM50 or SM51.

3. Check that there are no batch jobs running under the user ID using transaction SM37.

4. Check that there are no updates in process for that user ID using transaction SM13.

5. Once you know that there is no activity using the user’s ID, select the lock entry for deletion.

6. Choose Lock entriesàDelete.

1.6 Failed Updates, Transaction SM13

A failed update or an “update terminate” is an update to the database that failed. These failed updates occur when a user entry or transaction is not entered or updated in the database.

You should check the system for failed updates several times a day.

The longer you wait after the update terminate has occurred, the more hard it is for users to remember what they did when the update terminate occurred.

1. In the Command field, enter transaction SM13 and choose Enter (or choose ToolsàAdministration, then MonitoràUpdate).

2. Enter * in Client.

3. Enter * in User.

4. Under Status, select All.

5. Change the date to a year ago in From date.

6. Look for entries with an Err in the Status column.

These entries are failed updates or update terminates. You may also see other entries listed without the Err status. If you have no failed updates, you may stop here. If you do have failed updates, continue.

7. Double-click on the entry with an Err status.

8. Choose ABAP small dump.

§ If a small dump exists, it will appear.

§ Some problems that can occur with an update terminate include:

¨ No small dump

In this case, the only clues you have are the:

Ø User ID

Ø Date

Ø Time

Ø Transaction

¨ Difficulty reading the small dump

The ability to read a small dump comes with experience and practice. Only some of a small dump’s content is useful to the developer.

¨ Small dump with small usable information

¨ Update terminate occurring “downstream” from the actual transaction

The data in the small dump may be of small value in finding the root source of the update terminate (for example, if the terminate occurred in the FI posting of an SD transaction, you do not know which SD transaction document caused the problem).

¨ Update terminate occuring in a batch job

There is no indication of which batch job (by job name) caused the update terminate.

9. The users need to be contacted. They should check for the missing entry and reprocess the missing transaction. Do not attempt to reapply the failed update.

1.7 System Log, Transaction SM21

The system log is the R/3 System’s log of events, errors, problems, and other system

messages.

1. In the Command field, enter transaction SM21 and choose Enter (or choose ToolsàAdministration, then MonitoringàSystem log).

2. Enter the beginning date and time that you want to review from the log in from date/time. (You can also enter an end date and time if you want to view a specific time period.)

3. Choose Reread system log. (If you want to see the log from all application servers, goto System logàChooseàCentral system log, then choose Reread system log.)

These options allow you to view the system log in the following priority layers:

§ Problems

§ Problems and warnings

§ All messages

2

3 What to look for:

§ Unusual entries

Before you can recognize the unusual entries, you will need to become familiar with which entries are in the log under normal conditions (for your installation for a specific system).

§ Column C for the error status

Errors are the red Ks and warnings are the yellow Ws. These entries can also be examined with the Alert Monitor (RZ20).

§ Double click on any entry in the log to gain additional information.

1.8 Batch Input Jobs, In-Error or To Be Processed, Transaction SM35

This transaction shows jobs that need to be processed or started, and jobs with errors that

need to be resolved.

This transaction is vital because it alerts you to batch input jobs that:

§ Need to be processed

These are jobs that are waiting to be processed. If not processed, the data will not post to the system.

§ Are in error

These are jobs that have failed due to an error. The danger is that only a part of the job may have posted to the system. This increases the potential for data corruption of a different sort, as only part of the data is in the system.

1. In the Command field, enter transaction SM35 and choose Enter (or choose SystemàServicesàBatch inputàEdit).

2. Enter a start date of at least a week ago (or even further back if needed) in Creation date from.

3. Under Session status, select both:

· To be processed

· Incorrect

These selections show only the batch jobs that need to be processed and those with errors that need to be resolved.

4. Choose Enter.

5. Contact the responsible user to say them or determine why these jobs are in:

a. Sessions still to be processed

b. Errors in sessions

1.9 Background Jobs, Transaction SM37

Background jobs are batch jobs scheduled to run at specific times during the day.

If you are running critical jobs, you need to know if the job failed because there may be

other processes, activities, or tasks that are dependent on these jobs.

You should have a list of all the critical jobs scheduled to run. For each of these jobs, you

should have a list that shows:

§ When they are scheduled to run

§ The expected run time

§ Emergency contact (names and phone numbers) if a job fails or has problems

§ Restart or problem procedure for the job

1. In the Command field, enter transaction SM37 and choose Enter (or choose SystemàService, then JobsàJob overview).

2. Enter * to get all jobs in Job name.

3. Enter either * (for all users) or the user ID that the batch jobs run under (to limit the show to those scheduled under a specific user ID in User name).

4. Enter a start date in From.

5. Enter an end date in To.

6. Under Only jobs with status, select:

· Active

· Finished

· Terminated

7. Choose Enter.

8. Check for failed or cancelled jobs.

Analyze why jobs failed or were cancelled and make the necessary corrections.

9. Check critical jobs.

You need to know the job name that they run under to do this.

To check a job log:

10. Select the job.

11. Then choose Job log.

Check job performance and record run times. A deviation from the usual run time on a job may indicate a problem and should be investigated.

811

10

1.10 Transaction DB02

This task involves monitoring the growth of the database and projecting future growth to

Determine when to plot to expand the database.

1. In the Command field, enter transaction DB02 and choose Enter (or choose ToolsàCCMS, then Control/MonitoringàPerformance Menu, and then DatabaseàTable/Indexes).

2. Choose Space statistics under Database system

3. Check %-Used

Drill down on Tablespaces or Tables and indexes if issues are learned.

A

1.11 Check the Spool, Transaction SP01

The spool is the R/3 System’s output manager. Data sent to the printer is sent to the R/3

spool and then sent to the operating system to print.

There may be problems with the printer at the operating system level. These problems need to be resolved immediately for time-critical print jobs. Check for active spool jobs that have been running for over an hour. These long-running jobs could indicate a problem with the operating system spool or the printer.

1. In the Command field, enter transaction SP01 and choose Enter (or choose SystemàServicesàOutput controller).

2. Clear User name.

3. Set the From date to a week ago.

4. Clear Client.

5. Choose Enter.

6. Look for jobs with an error in the Output Status column.

1.12 Printing / Spool System, Transaction SPAD

The spool administration screen can be used to identify problems and errors with printing processes.

1. In the Command field, enter transaction SPAD and choose Enter (or choose ToolsàCCMSàSpoolàSpool administration).

2. At the bottom of the screen, choose Print request overview.

3. Check the number of Total print requests

· This number should never be more than 99,000

When the spool is this large, performance issues start to develop

1.13 ABAP Dump Analysis, Transaction ST22

An ABAP dump (also known as a small dump) is generated when a report or transaction terminates as the result of a serious error. The system records the error in the system log (transaction SM21) and writes a snapshot (dump) of the program termination to a special table.

You use an ABAP dump to analyze and determine why the error occurred, and take

Corrective action.

1. In the Command field, enter transaction ST22

There are two selection methods to show the list of dumps.

§ For simple selection; today or yesterday (go to step 2)

§ For free selection (go to step 5)

2. Under No. of small dumps, if there is a value other than zero (0) in Today or Yesterday, dumps have occurred that need to be examined.

3. Select Today.

4. Choose Show list to get a list of small dumps for the day. Go to step 8.

5. Choose Selection.

6. Enter your selection criteria in the ABAP Dump Analysis screen.

7. Choose Execute.

8. Double-click on the dump you want to analyze.

9. This screen shows the “small dump.”

Performance Checks

2.1 CCMS Central Alert Monitor, Transaction RZ20

Transaction RZ20 is a centralized alert monitor and is new with Release 4.0. With this transaction, you can monitor the servers in your landscape, such as development, QA, testing, production, and so on. You no longer have to individually log into each system to search for alerts

§ An alert indicates a potentially serious problem that should be quickly resolved. If not contained, these problems could degenerate into a disaster.

1. In the Command field, enter transaction RZ20 and choose Enter (or choose ToolsàCCMS, then Control/MonitoringàAlert Monitor 4.0).

2. Click the node next to the server to expand the server options.

3. Double-click on the monitor.

4. Look for any alerts, which are indicated in red.

5. Click the node next to the <sid> to drill down for additional details.

6. Select the alert

7. Choose Show alerts.

To get detail for the alert:

8. Select the alert item.

9. Choose Choose detail (magnifying glass icon).

10. Review the details.

11. Choose Back

To “acknowledge” the alert:

12. Select the alert item(s).

§ Alert (red)

§ Warning (yellow)

13. Choose Complete alerts.

§ You still have to perform a task based upon the alert.

§ “Acknowledging” the alert only means you received the alert notification, nothing else.

14. When all alerts and warnings are acknowledged, the alert will change to green.

To get more details on the alert, you can start the analysis tool.

From the previous screen:

1. Select the alert (for example, Page_Out)

2. Choose Start Analysis tool.

2.2 Transaction ST02

The buffer tune summary transaction displays the R/3 buffer performance statistics. It is used to tune buffer parameters of R/3 and, to a lesser degree, the R/3 database and operating system.

The buffer is vital because significant buffer swapping reduces performance. Look under Swaps for red entries.

1. In the Command field, enter transaction ST02 and choose Enter The two vital things to review are:

§ Hit Ratio, for which the target value is 95 percent and higher

Soon after starting the system, this value is typically low, because certain buffers are empty. The hit ratio will increase as the system is used and the buffers are loaded. It usually takes a day to load the buffers that are normally used.

§ Swaps, for which the target value is less than 1,000

Swaps occur when the necessary data is not in the buffer. The system has to retrieve the data from the database. The swap value is reset to zero (0) when the system is restarted.

· Buffer swaps may be due to:

¨ Buffer too small, out of space

¨ Out of buffer directory entries

¨ Fragmentation in buffer, particularly the program buffer

Ø If program buffer exceeds 10,000, it should be investigated

¨ Generic table buffer

Ø Sometimes very large buffered objects should be unbuffered (over 2MB)

2.3 Workload Analysis of the System, Transaction ST03

Workload analysis is used to determine system performance.

Statistics should be checked, and trends should be recorded to get a “feel” for the system’s behavior and performance. Understanding the system when it is running well will help determine what changes need to be made when it is not.

1. In the Command field, enter transaction ST03 and choose Enter (or choose ToolsàAdministration, then MonitoràPerformance, then WorkloadàAnalysis).

2. To check Response times

A. Choose Detailed analysis menu from toolbar.

B. Choose One recent period from Performance history, Global.

C. Choose a time period.

Ø Today

Ø Previous days

Ø This week

Ø Previous weeks

Ø This month

Ø Previous months

D. Select date.

E. Choose Dialog at the bottom of the screen

F. Choose Transaction profile from the toolbar

Ø Main menu dialog step average time should be very small

§ If it is not, this could indicate a dialog instance bottleneck

Ø Key dialog transaction step time components

§ Wait time should be very small

§ DB time should be much less than CPU time

3. To compare servers

A. Choose Detailed analysis menu from toolbar

B. Choose Compare all servers from Performance history, Global.

Ø This indicates average performance across all instances

Ø If there is a performance problem specific to an instance, Avg wait time and CPU time will be the best indicators.

2.4 DB Performance Analysis, Transaction ST04

The database error log is the record of database-level errors.

Database error logs may indicate a database problem that is not reported in other locations.

1. In the Command field, enter transaction ST04

A. Choose Goto →Database log.

B. In the Database Messages window, select Only alerts.

Ø This selection reduces the amount of text to look through in the first pass.

Ø During a second pass through this transaction, select All messages.

C. Choose Display.

D. Scroll down the log to check for error messages.

2. Check the database statistics

A. Oracle data buffer checks

Ø If there are more than a few million reads, the buffer quality should be > 98%

§ < 98% could indicate buffer too small or expensive SQL statements

Ø Buffer waits should be < 5% of reads

§ > 5% could indicate I/O bottleneck

B. Oracle “call statistics” checks

Ø Reads per user call should be < 40

§ > 40 could indicate expensive SQL

Ø User calls / recursive calls should be > 5

§ < 5 could indicate that the Shared Pool may be too small

C. Oracle “shared Pool statistics” checks

Ø DD cache quality should be > 90%

§ < 90% could indicate that the Shared Pool is too small

Ø SQL Area getratio, pinratio should be > 90%

§ < 90% could indicate that the Shared Pool is too small

3. Check database SQL

A. Go to Detailed analysis menu on tool bar, then to Resource consumption by, SQL request, sort by “Buffer Gets”

B. Look for statements with:

Ø More than 1,000-10,000 budgets / record (most optimization potential)

Ø Buffer gets / total reads since start in more than 5% of the total

Ø More than a few executions

Ø Larger fraction of reads from disk than other statements

Ø Double click on line to get more information

§ Once showed, the “Clarify” option can be selected for further analysis

2.5 Local OS Monitor, Transaction ST06

The local OS monitor receives information from the OS collector.

1. In the Command field, enter transaction ST06 and choose Enter (or choose ToolsàCCMS, then Control/MonitoringàPerformance Menu, then Operating systemàLocalàActivity).

2. Check the following areas

¨ CPU utilization and system load

Ø Check idle %

Ø Check load average

§ Load average should be > 1.5

¨ Physical and virtual memory

¨ Swap statistics

¨ Slowest disk

¨ LAN statistics

File System Checks

3.1 Check SAP R/3

This process will remove ancient data from the /usr/sap/<SID>/DXX/work directory

1. Remove ancient dev_w# files

· Logon each application server through transaction SM51

¨ Highlight one application server

¨ Select Processes button

· Follow path ProcessàTraceàReset files

2. Remove ancient dev_rd# files

· Logon each application server through transaction SM51

¨ Highlight one application server

¨ Select Processes button

· Run transaction /nSMLG

· Follow path GotoàTraceàGatewayàReset File

3. Remove ancient dev_rfc files

· Run transaction SM59

· Follow path RFCàDelete Trace

Download Now –>

Download Now —>

Download Now –>