How to run a report in SAP?

This article answers the following queries:

 How to run a report or program in SAP?
 What is the need of RSBTCDEL program?
 How to delete old background or batch jobs in SAP?
 How to run a report in background in SAP ?
-------------------------------------------------------------------------------------
---
In SAP environment, there will be frequent requirement by ABAPers
/functional/technical team to run various reports. This can be done through
SE38 transaction code.

Go to transaction SE38 as shown below and provide the program/report

name which you would like to run.

In the below example, am running a report / program RSBTCDEL which is

used to delete old background jobs

Click on execute button to run the report. Depending on the program/report,

you will be prompted to enter the input parameters(variants) so that system
can action the same.

In the below report, am selecting to delete all batch jobs that are with
username BASIS , older than 30 days and which are finished or canceled.
Click on execute button, once you have provided the inputs. Then the
program will run in dialog mode and the status similar to below screen will
appear on the status bar.

How to run a report or program in background mode in SAP?

In case you would like to run the program in background, please follow
these steps:
Navigate to Program -> Execute in Background as shown below
Once you execute as shown above, program will run in the background.
 How to create an Oss message
This article answers following queries :

 How to create an Oss message in SAP?

 What are the different priorities of tickets/message that can be created ?
 In what cases Very high priority message to be raised?
-----------------------------------------------------------------------------

In real time scenarios, there might be situations, where local basis administrators could not resolve the issue. In
those cases, a message can be raised to SAP so that SAP consultants can resolve the issue based on priority of the
ticket.

Please follow below steps to raise an Oss message:

Step1: Goto Service Market Place. Navigate to Help & Support -> Report a Product Error

As shown in the above screen, there will be 4 steps to raise an Oss message.

They are

i) Choose system (Select system on which issue to be reported )

ii) Prepare Solution Search (Solution search can be performed here by using
keywords of the issue)

iii) Find Solution (System displays some notes which are relevant to the issue.
If any of the notes suits your requirement, they can be reviewed and
applied and message creation can be deferred.

iv) Enter message ( If note of the listed notes are applicable, you can go ahead
and create an Oss message)
Step 2 : Please refer below screen. Please provide SID of the system regarding which you would like to report an
issue and click on search button. It displays the system details.

Click on SID, which opens up the following screen.

Step 3: In the above screen, provide the keyword of the issue and conduct a search.

System displays all the notes that are relevant to this issue as shown below

Step 4: Please review the notes listed and try if you can apply any of these to resolve your issue. If none of the
notes suits, you can proceed further to create a message to SAP.
As shown in the above screen, select the Language, Component and Priority of the message.

By default English language will be selected. If you would like to change, you can do the same by selecting from
the dropdown.

Afterwards, the relevant component of the SAP system for which you would like to report needs to be selected. A
click on component button, opens up screen as below from which component of the SAP system can be
selected. Please note this is very important to raise a ticket in correct component for faster resolution of issue.
Otherwise, it delays because an SAP consultant will have to go through the issue and he has to in turn forward this
message to correct component(In other words, to correct team – As each component will be supported by a
separate expert team)
Next, priority of the message to be selected.

There are 4 types of priorities

 Very high
 High
 Medium
 Low
Depending on the priority of the issue this is to be selected. SAP responds to you based on the priority selected.

In case you have selected very high priority to create an Oss message, you will need to provide some extra details
to SAP like Business Impact, Revenue Loss, Number of users impacted etc. In these cases, an SAP consultant will
call you within 15mins to understand the issue and lowers the priority if it does not suit to Very high priority call. If
they consider it as very high priority call, they start working on the issue immediately, requesting further details in
case of any required.

Hence, Please note, In case you are selecting very high priority, please make sure you have valid business reason
for the same like production system is down and lots of users are unable to work and huge amount of revenue loss
to the company.

Next as shown in below screen enter problem details like short text (subject of the issue) and long text (description
of the issue)
Below this, any attachments related to the issue like screenshots, dump files etc can be uploaded in the
Attachments section

In Contacts & Notifications section name , email id, contact number of the reporter to be provided so that SAP can
contact you in case of emergencies related to this issue.

Once all these details are provided, please click on save message push button to save the Oss message. It provides
an Oss message number. Please note the same. After that, please click on send message push button which
actually sends the message to SAP.

Generated Oss number can be used for further correspondence with SAP.
 How to view OSS messages based on their various criteria?
This article answers the following queries:

a) How can we check OSS messages owned by us?

b) How to check OSS messages of other users ?

c) How to spool a report on the oss messages created between any 2 intervals?

d) How to view all Oss messages based on their status for any given period?

e) How to export Oss messages list to an excel?

------------------------------------------------------------------------------------

How to check Oss messages owned by us

Login to Service Market Place and navigate to “ my Inbox” as shown below :

It displays all the customer messages that are owned by you.

(However in the example above there are no messages displayed, as I haven’t created any)

How to check Oss messages owned by others

Please select Customer Messages from the drop down of Search for (highlighted in the above screen) and click on
Go button , to proceed to the following screen
As shown in the basic search of above screen, Oss messages can be filtered and viewed based on:

 Customer Number

 Installation Number (based on particular system)

 Reporter Name ( User who has created the message)

 Status ( based on status of message)

 Create date ( based on create date interval)

 Changed within last days (based on last change)

 Priority

 Component

 Message Number

How to spool a report on the OSS messages created between any 2 intervals

Advanced search tab will have much more options than basis search as shown below
For example : If I have to view all Oss messages, which are in Status “In Processing by SAP” and “Customer
Action” and whose priority is Very high/High/Low and messages which were created between 15.09.2011 to
22.09.2011, I can select as shown in the above screen.

After selecting all these, click on Search push button which displays all the Oss messages which meets these
criteria as shown below:

Click on Down All pushbutton (highlighted) in the above screen, to download these oss messages into an excel
sheet for further processing/reporting
How to check transactional RFC(tRFC) related errors?
This article answers the following queries :

 How to check transactional RFC (tRFC) related errors?

 How to find out status of transactional RFCs(tRFC) in SAP?
 What is the transaction used to perform transactional RFC checks?
 How to re-process failed or stuck LUW related to transactional RFC?
 How to delete a transactional RFC related LUW from sap system?
 How to reprocess all the transactional RFCs or LUWs that are stuck in SAP system at a time?

-------------------------------------------------------------------------

Transactional RFC related checks and maintenance can be done using SM58 transaction code

Sometimes, in real time scenario you can face following issues :

 Process chain related performance issues in BIW system due to transactional RFCs stuck in R3
system.
 Idocs flow not happening from R/3 to XI system

In these scenarios, SM58 transaction code will be useful to find out stuck tRFCs and action them accordingly.

Please login into SAP system and use SM58 as shown below :

Using SM58, we can select TRFCs based on

 Any 2 dates

 User id

 Function of TRFC
  TRFC Destination

 TRFC Status

If you would like to list all, then use * as input in these fields

In the following screen, you can see the list of TRFCs that are waiting to be processed or stuck
tRFCs as shown below

We can delete or re-process these LUWs based on the scenario. This can be done by navigating to
Edit menu as shown below

You can reprocess an tRFC LUW, by selecting the same and by navigating to Edit -> Execute
LUW. This can also be done by pressing F6 button.

An LUW can also be debugged by navigating to Edit -> Debug LUW option
In case large number of tRFCs are stuck, all of them can be processed at a time by selecting
Edit -> Execute LUWs option as shown in the above screen.

You can also directly goto QRFC administration and QOUT scheduler from SM58 transaction as
shown in the below screen.
How to create an RFC Connection in SAP ?
This article answers the following queries :

 How to create an RFC connection ?

 How to test RFC connection ?
 How to delete an RFC ?

How to create an RFC destination ?

Go to SM59 transaction :
 Click on create icon in the above screen, which leads to below screen

Specify RFC Destination name and description and connection Type in the
above screen

Please note respective connection type to be selected from dropdown based

on the connection required. Usually 3 is for ABAP system. (Pls find
screenshot below)
In the below screen, please select load balancing radio button based on your
system setup (i.e if there is load balancing configured for your system,
specify it as yes otherwise no)

Please provide Target host details like hostname or ipaddress and system
number as below:
As shown below, Proceed to Logon & security tab and provide following
details :

Select trusted system as no, in case you would like to connect to a system
with a user id and password.

If you don’t want to get authenticated by credentials specify the system as

trusted system which won’t prompt to enter user id/pwd credentials in the
below screen.

Please provide Language details like EN (for English), Client details, User id
and password for the system you would like to create a connection.

Please leave default values in other tabs (i.e MDMP & Unicode, Special
options, Administration) and then click on Save to complete the RFC
creation.

How to Test RFC connection ?

If it functioning well it should show output similar to below screen :

If this is fine, come back to earlier screen and execute Unicode test by
clicking the button. Output similar to below screen, should be displayed if
connection is OK
Also you need to perform authorization test to make sure user id / password
credentials provided are correct.

Please navigate as below and perform the test :

Navigate to Utilities -> Test -> Authorisation test and click the same to
execute.
If the RFC configuration is fine, screen shot similar above will appear.
Otherwise an error will be displayed based on which you need to
troubleshoot to fix the issue.

How to delete an RFC ?

Goto SM59 and select the RFC that is to be deleted as shown below :

And click on delete icon

Click yes to confirm deletion, which deletes the RFC.

Click on Connection test tab to check the connection for the RFC

How to schedule Basis standard jobs ?

This article answers the following queries :

 How to schedule Basis standard jobs ?

 What is the need of scheduling basis standard jobs ?
 What are the Standard jobs that should run in an SAP system & their
significance?
-------------------------------------------------------------------------------------
---

How to schedule Basis standard jobs ?

Goto transaction SM36 and click on "standard jobs" pushbutton. This inturn
displays standard jobs screen. Here select all the jobs and click on "default
scheduling" push button to schedule all of them as per their default
schedule.
Incase you would like to change the default schedule for each job, it can also
be done by selecting each job and defining its start date/time and periodicity
in the same screen.

What is the need of scheduling basis standard jobs ?

Standard jobs are the jobs that should run regularly in the SAP system.
These jobs will perform housekeeping like deleting old spool requests (thus
avoiding spool overflow), deleting old background jobs/logs/updates/batch
input sessions/ABAP short dumps, collecting operating system/database
level statistics (used for workload reporting) etc

What are the Standard jobs that should run in an SAP system & their
significance ?

SAP_CCMS_MONI_BATCH_DP : Internally this job runs

RSAL_BATCH_TOOL_DISPATCHING report. This job dispatches monitoring
architecture methods

SAP_COLLECTOR_FOR_JOBSTATISTIC : Internally this job runs RSBPCOLL

report. This job generates run time statistics for background jobs

SAP_COLLECTOR_FOR_PERFMONITOR : Internally this job runs RSCOLL00

report. This job collects data for the performance monitor

SAP_COLLECTOR_FOR_NONE_R3_STAT : Internally this job runs

RSN3_STAT_COLLECTOR report. This job will collect non-abap statistic data
(Distributed Statistic Records - DSR)
 SAP_REORG_ABAP_DUMPS : Internally this job runs RSSNAPDL report. This
job cleans up old abap short dumps

SAP_REORG_BATCH_INPUT : Internally this job runs RSBDCREO report. This

job cleans up old batch input sessions

SAP_REORG_JOBS : Internally this job runs RSBTCDEL report. This job

cleans up old background jobs

SAP_REORG_JOBSTATIC : Internally this job runs RSBPSTDE report. This

job cleans up old data from the run time statistics of the jobs

SAP_REORG_ORPHANED_JOBLOGS : Internally this job runs RSTS0024

report. This job cleans up orphaned job logs. The logs that cannot be deleted
by RSBTCDEL report (i.e SAP_REORG_JOBS), remains as orphans which will
be deleted by this job.

SAP_REORG_SPOOL : This job internally runs RSPO0041 report. This

job deletes old spool data

SAP_REORG_XMILOG : This job internally runs RSXMILOGREORG. This job

deletes XMI logs

SAP_SOAP_RUNTIME_MANAGEMENT : This job internally runs

RSWSMANAGEMENT report. This job does the SOAP runtime monitoring

SAP_REORG_UPDATERECORDS : This job internally runs RSM13002 report

and this deletes old update records