Tuesday, 18 February 2014

List of SAP products

This presents a partial list of products of the enterprise software company SAP AG
 
 Business Solutions
 
Industry Solutions
 
Solutions for Small and Midsize Enterprises
 
 Platforms and frameworks
 
Legacy Platform   
R/1 called as NTR 1973
 
R/2 at the end of the 1970s. SAP R/2 was in a mainframe based business application software suite that was very successful in the 1980s and early 1990s.
 
SAP R/3 was officially launched on 6 July 1992 (The "R" was for "Real-time data processing" and 3 was for 3-tier). 
  • SAP R/3 Enterprise Release 2.0 / 2.1 Released 1993
  • SAP R/3 Enterprise Release 3.0 / 3.1 Released 1995
  • SAP R/3 Enterprise Release 4.0B Release Date June 1998
  • SAP R/3 Enterprise Release 4.5B Release Date March 1999
  • SAP R/3 Enterprise Release 4.6A Release Date 1999
  • SAP R/3 Enterprise Release 4.6C Release Date April 2001
  • SAP R/3 Enterprise Release  Date March-December 2003
  • SAP R/3 Enterprise Release 4.70 Release Date March 2004
  • SAP R/3 Enterprise Central Component 5.0 Release Date August 2005
  • SAP R/3 Enterprise Central Component 6.0 Release Date June 2006
  • SAP ERP 6.0 - Enhancement Packages (1,2,3,4,5,6) /2007/
  • SAP R/3 Enterprise Umer(EVKUE) Component 7.0 Release Date 2007
  • SAP HANA (High Performance Analytics Appliance) Release Date October 2010
 
Posted by at No comments:

Friday, 14 February 2014

RZ10 How to change SAP parameters ?

go to RZ10


You can  either search the parameter or create the parameter and then set the value to the desired and save the same


Set the parameter value in the text box provided and click copy button to copy the same and then press back button and press copy again in the next screen. After that press the back arrow


Click on Save button to save and activate the profile.

Press no to goto the next screen


Press yes, to activate the profile.


The parameter will take effect after restart of the application server

Posted by at No comments:

How to add or extend datafiles in sap system based on oracle database ?

What is BRTOOLS?

BRTOOLS is the database administration tool supported by SAP for oracle database.

How to access BRTOOLS ?

BRTOOLS can be accessed by logging into database host as ora<sid> user and calling brtools at the command prompt.

How to add or extend datafiles in sap system based on oracle database?

Once brtools is called at command prompt, following menu will be displayed

BR*Tools main menu

1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
======================================
Select option 2 - Space management from the above query and press c to continue.

It displays another screen as below :

Database space management

1 = Extend tablespace
2 - Create tablespace
3 - Drop tablespace
4 - Alter tablespace
5 - Alter data file
6 - Move data file
7 - Additional space functions
8 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help
=============================================
Select Option 1- Extend tablespace and press continue.

In the next screen, you will be prompted to enter tablespace name, size/location of new datafile to be added, initial filesize, maximum filesize, autoextend (yes/no). Please provide all the relevant details and you can see an SQL query is being built based on the inputs given by you.

Once all the inputs are provided, press continue to execute the command and the datafile will be added.
Posted by at No comments:

SM13

        SM13

Reasons for update deactivation :

Update will get deactivated in cases of serious database problems.

Some of the examples of update deactivation and solutions for those are given below :

 1) Update will get deactivated when oraarch is full

Solution : Trigger archivelog backup and ensure sufficient space is left in oraarch and then activate the update manually

 2) When some critical tablespaces are 100% full and database is not able to perform some operations

Solution : Monitor the database and findout the tablespaces which are 100% full.  Add necessary datafiles and ensure there is enough free space left out in them. Then activate the update manually


 How to activate or deactivate an update in sap ?

Use transaction SM14 and goto update tab. There update status can be viewed with a push button. If it is in deactivated status, click it to activate  and viceversa.

How to switch off automatic update deactivation ?

In RZ10, set the parameter rdisp/vb_stop_active to 1 and activate the profile to switch off automatic update deactivation incase of database problems.


How to troubleshoot, if update got deactivated ?

Please perform the following steps if udpate got deactivated :

  •  Check all the tablespaces and ensure figureout if any tablespace is 100% full. If so, add necessary space and activate the update as mentioned above

  • Check if oraarch is full. Trigger archivelog backup and ensure there is enough space and activate the update again

  • Check SM21 log and ST22 dumps

  • Check workprocess trace for any other issues


  
What happens for the updates that are in progress, if update got deactivated ?

If update got deactivated all the updates that are in progress or waiting to get executed, won't be cancelled. They will be assigned either init or auto status. Once the database issue got fixed and update is activated again, all these updates which are in init or auto status will resume again

          
                                              Update work process (V)
A. It is used to update the database by reading from the temporary tables. It can’t    communicate with user
     directly

B. There are 2 types of update work process. They are v1 and v2
    V1 update is used for critical jobs and V2 update is used for non critical jobs

C. We need at least one update work process per sap system and we have more than per dispatcher

D. The update profile parameter name is rdisp\wp_no_vb, rdisp\wp_no_vb2

E. Update monitoring is – SM13
    Here we can check critical and non critical updates. We can specify date and time

F. Update program administration – SM14
    This transaction code is used for active to deactivate & deactivates to activate update request and you  
    configure the update servers, update groups and display & monitoring update parameters.

G. Update temporary table is VB*
    Vbmod – update function module
    Vbdata – update data
    Vberror – update error information
    Vbhdr – update header
    Vbwrk – work list for mass processing at a time have update

H. Update status are
    Init – the status will be initial.
    Run – update is started in main database.
    Error – update is thrown into error.
   Auto – update is thrown into error due to problem in database space.

 I. Update tables are stored in TBLOD

J. SAPMV45A: which update work process is going on?

K. Update types are 3: they are
     1.Local update: Dialog work processes update the directly in Database that is called local update.
     2.Synchronous: Dialog work processes update goes to the temporary table that is called synchronous.
     3.Asynchronous: temporary table goes to database that is called asynchronous

L. Update statistics are 4:  they are
    Read, Write, Execute and Delete

M. Update parameters
      1.rdisp\vb_stop_active: Set to “0” so that update can be deactivated. If the value is set to be “1” update
      can be activated.
      2.rdisp\vbdelete: This parameter is used to delete the old update requests based on the no. of days. It
      will delete default 50 days.
      3.rdisp\vbmail: It is used to send an email. It update thrown an error which can be viewed in “SBWP”
      (“sap business workplace”) based on your user (set to “0” or “1”).
      4.rdisp\vbname : Name of the server running where update are processed
      5.rdisp\vbreorg: It is used to delete the incomplete update request.
     1=delete, 0=no, we can also schedule a background job “RSM13002” but it will delete the update  
      request which are in completed it will be deleted after restarting.
      6.rdisp\vb_delete_after_execution: It is used to delete the update request soon after the execute of  
      the update. Set it to”1” to delete the record (or) “2” to the record will not be deleted. If it is set to “1”
      the background job “RSM13002” is not required. If not schedule periodically daily during off peak
      hours.
Posted by at No comments:

Thursday, 13 February 2014

Difference between SM50,SM51,SM66

SM50 will display the work Process Overview of the current application server.

 SM51 will display the SAP servers and u can select the particular server and check the work process running on that application server on clicking on any work process it will take u to that application server.

 SM66 Global work Process Overview
Posted by at No comments:

Monday, 10 February 2014

How to find out long running jobs in SAP ?

Goto SM37 and select the active job status between any 2 given date/time and list them.




Double click on the job


How to troubleshoot a background job running for long duration in sap?


1) First of all identify the job that is long running and identify details like job class, workprocess that is executing the job

How to identify long running background jobs

2) Click on the job to view the display job screen. In the screen, click on job log to understand what is being performed by the job currently. This may give details like job is currently extracting some data packages or processing data packages etc

3) Identify the executing server and process id of the job from the step 1 and goto transaction SM50 of the respective executing server to view more details about the background job running.

Figure out the status of the job like On Hold or running from the process overview. If the job is On Hold, find out the reason for On Hold by examing the "Reason" column of SM50 transaction. Reason for On Hold could be due to CPIC/RFC/DEBUG/ENQ/PRIV/UPD etc.

Double click on the reason column for detailed information on the same and troubleshoot accordingly. If reason is RFC, check out which RFC it is referring to and cross check whether destination system is up or not and any other problems with that system.
  • If it is ENQ, check out any lock issues like lock overflow etc
  • If it is PRIV, check out for memory bottlenecks
  • If it is UPD, check out whether any update issues
  • If it is CPIC, check out for any network , gateway, message server and other communication problems

4) After performing step3, if you figure out job is not on Hold and it is in running state, then examine report column to identify what report/program is being executed by the job. Once you got the report/program details, figure whether it sap program or custom program and take actions accordingly.

5) Also examine Action and table columns in SM50 transaction of respective executing server to identify what is the action( roll in/roll out /Sequential read/Physical read/insert/update/delete etc)  being carried out by the job currently and what is the table on which action is being carried out.

If it is sequential read, figure out the cost of that sequential etc and consider for indexing etc. If it is physical read, check out whether there are too many swaps and consider resizing buffers accordingly. If you observed delay is due to high roll in/roll out, identify reasons for the same and tune buffer/memory parameters accordingly.

6) Once you get the table details on which action is being carried out, figure out        

  •     How many records are existing in the table ?
  •     Is this taking long time due to volume of records ?
  •     Are there proper indexes on the table ?(If no proper index, consider index creation  by taking help of DBA )
  •     Is the table having upto date statistics ? (If statistics are out of date,
              consider updating statistics of that table)


7) Consider debugging the process in SM50 ( Program/Session -> Program ->   Debugging ) to figureout the issue

8) Using ST05 or ST12, a trace can be taken for background job to figure out where exactly time is being consumed and to identify various cpu/memory bottlenecks or any buffer issues.

9) STAT/STAD transcation can be used to figure out what is the reason for high response time and actions can be taken accordingly

10) By taking help of ABAP er, even ABAP run time analysis can be done using SE30 transaction

By following the above steps, you can pin point the issue and take actions accordingly to minimize runtime of long running background jobs.

Posted by at No comments:

SAP support pack schedule?

In SMP, 
Go to “Software Downloads” tab  -> “SAP Software Download Center” -> “SAP Support package stacks” -> SP Stacks maintenance schedule



Posted by at No comments:

SM21 system log

In case of issues like update failure, lock table overflow, spool overflow, operating system issues, network issues, table space full issues and other database issues system log will get updated with the error message and the relevant time stamp. By using this timestamp and error message, basis administrator can identify the cause for the issue and can fix the issue.
 Based on the issue and the time stamp in system log, in many cases, you can find out relevant ABAP runtime dumps in ST22 (which provides much more detail about the issue) and the issue can be tackled accordingly.
go to->SM21

click “Reread system log”


As shown in the above screen, in the system log you can view following information:
1. Time Stamp
2. Type of work process
3.  System Number
4.  Client Number
5.  User id (who executed the transaction)
6.  Tcode  executed
7.  Priority
8.  Text related to the issue

Based on al l the above details, basis administrator can figure out the issue. In most cases, if additional details are required related to dumps, they can check in ST22 transaction.

check All remote system logs?
go to -> SM21

click on Reread system log




Posted by at No comments:

ST11: Display Trace Files

ST11 is used to display the trace files in the work directory. 
Using this transaction we can view the trace files for all the work processes that happen at the OS level with start of SAP and operational status of SAP work process.
If you want to save a file locally,choose System -> List -> Save -> Local file.


1. Double-click on a file to display the log / trace.

Posted by at No comments:
Subscribe to: Posts (Atom)