How to use STAD to show historical data

What is STAD

The Business Transaction Analysis (Transaction STAD) delivers workload statistics across business transactions (that is, a user's transaction that starts when a transaction is called [/n....] and that ends with an update call or when the user leaves the transaction) and jobs.

 

STAD Alternative Way

 

My attempt to show you to view historical data which are taken from the STAD transaction for a long time.

The default time period is 48hrs for STAD transaction. We only can analyze data for this time frame. The alternative way to save earlier STAD reports will be discuss here. I think this will be helpful for the administrators to analyse varies issues in their systems.

 

Method

Run STAD in Background with scheduled  in periodically.

The STAD program is RSSTAT26 which is run in background when we run the STAD transaction.

 

 

Step By Step Guide

 

• Transaction SE38 and provide the program name RSSTAT26 as in screen. Then execute

    

 

• Then select Program -> Execute in Background

 

      

 

       

 

 

• Then Select the data time and finally click on periodic values.

 

 

• Then Select the period.

 

 

• Then click on save button on above screen to save the background job.
• you can see the message for successful background job.

 

 

Now creating background job is completed. ++++++++++++++++++++++++

 

Next step is to check the report which the background job is created.

 

Then Goto SM37 for background jobs.

 

 

Then click on pool icon show on the image.

 

Click on the icon mentioned under type column.

 

 

 

Then you can see the report for given period.

 

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

 

The report can be customized for user, transaction and more parameter fields. Then the report can be create for specific requirements and historical statistic data.

How to create Trust/Trusted RFC relationship

1.Create a RFC destination to the system you want to trust(for example Y57->Y58)

 

 

2. Create a trusted system in Y57 using the RFC destination you just created.

 

3. Go to SMT2, you will see trusting system is here.

 

4. Create a RFC destination without user and password but using "Trust Relationshiop" and "Current user" instaed.

Now you can use this RFC destination logon to Y57 without enter user and password

How to find SQL Traces in ST05

When i was working with Performance issues on BEx queries we face so many issues.

While coming  we created BEx reports for dashboard requirement and always users want run the dash board they want immediately.

We made aggregates on cube but again some performance issue came. How do you which object is using frequently then we trace the Dash board BEx queries.

How to find the SQL Trace

1.enter the T- code- STO5

Below screen appear then check the SQL Trace and RFC Trace then select the activate trace with filter – give user name -> USER1.

Select continue

Now see trace activated.

2.Enter the T-code- RSRT

Run the query and it took 8 minutes time

Go to again T-code- ST05

Deactivate the Trace now trace are switched off

Then select the display trace

Then next screen will appear

Filter the object name was Info cube E face table

Double click on the SQL select statement

Below screen will appear

In SELECT statement how many object are using we find easily (for information i am erasing the using all info object) then we made aggregates based on the SQL script.

After making aggregates on cube our dash board report came within 2 minutes.

ABAP Short Dump ASSIGN_TYPE_CONFLICT & SYNTAX_ERROR during DTP Load & Transports

This article is based on SAP BI 7.30 version with support package 5.

Sometimes we would encounter ABAP short dumps during transports or during data load through DTP's for new developments or for changes in the existing developments.

These errors occur when the Infocube & DSO are changed & without recollecting the related transformations.  There are 2 possibilities which would occur

1. ) Your transport might fail with RC12  throwing error “Uncaught_Exception” with an exception as “CX_RS_PROGRAM_ERROR” and the program which is terminated as “CL_RSO_TLOGO_PERSISTENCY======CP”.
2. ) Your transport is successful and data load through DTP fails with the error “Assign_Type_Conflict”.

The reasons for these are that

1. ) when the Infocube or DSO is changed, the program(new metadata) which is generated get’s updated with the time & date and the logic. The generated program in source is different to the one in target. So when you transport these changes of only the data target’s without the transformations(these transformations does not include the changes done to the Infocube), the program gets updated in the target system. But the transformations in the target system are still pointing to the old generated program (this is orphaned metadata). This is when you would get a data load error “Assign_Type_Conflict” through DTP load.

During Data Load:

During Transports:

The way to rectify this is using the SAP Note 1627236 which I have given below in a simpler format.

In a gist:

1. ) Delete the inconsistencies in the transformations using function module in the source system.
2. ) Re-Collect the transformations in a new transport.
3. ) Delete the inconsistencies in the transformations using function module in the target system.
4. ) Transport the newly collected objects to the target system.

In detail:

1. ) Run the function module “RSTRAN_ROUT_RSFO_CHECK” using SE38 in the source system. 
2. ) Copy the technical ID of the transformation which is causing error and paste it in the function module. 
3. ) Run the program for the the transformation  with both “M” & “A” object versions with the option “Simulate” selected.
4. ) If there is no error then you would get a message  as  else it will display the error message.
5. ) Once running the program with “Simulate” option is complete, run it with “Repair_W” option checked for both “A” & “M” options. Choose option “Yes”. If it asks for a transport then collect it else after this step is done, collect the transports again in a new transport.
6. Note: The steps given above have to be done exactly the same way in target system before doing the transports
7. If there are multiple transformations, it’s good to collect each of them in a separate transport along with their DTP's. This helps in identifying the transformation which is throwing error(if in case you get the error again).
8. Once the above steps are complete in the target system, transport the requests from source to target system.
9. So as to cross check, when you re-do the steps above you would get the msg .

Related SAP Notes: 1627236, 18013091913191.