Leanin Tree Health Check document

1) Check the app server(s) & work process – SM50/SM51/SM66

2) Check for any lock issues – SM12

3) Check for update failures – SM13

4) Check for the spool consistency and spool numbers –SP01/SP12

5) Check for system logs – SM21

6) Check for any short dumps – ST22

7) Check the background jobs – SM37

8) Check for outbound emails – SOST

9) Check for the queue – SMQ1 / SMQ2

10) Check the IDocs – BD87

11) Check the Buffer –ST02

12) BW system RSPCM

13) CRM system SMWO1

1) SAP ECC Application server status available at SM51

LT has six application servers. We can see the status of all servers in Active state.

Choose any one of the application servers and doable click on it. We can see the process oversee.

As aforesaid, we must check all application server process oversee.

Global work process oversee SM66.

If we see any errors or time more than 3 hours we need to intimate the same to LT team .

2) Check for any lock issues – SM12

Go to Txn SM12, input ‘*’ in the User name field and click the button “LIST”.

The processes are displayed as shown below.

If we see any entry showing time more than 3 hours, other than background jobs, we can escalate to LT.

3) Check for update failures – Txn SM13

Input ‘*’ in the USER field. Input previous days date in the “From Date” field.

If we see any issues, we can escalate to LT

4) Check for the spool consistency and spool numbers – Txn SP01/SP12

In the “Spool requests” tab, input “*” in the “Created By” field and leave the “Date Created” field blank.

In the “Output requests” tab, input “*” in the “Created By” field and leave the “Date Created” field blank.

If you find any spool request / output requests errors or issues, we can escalate to LT.

Txn - SP12

In the following screen, go to the path “Temse Data Storage Concistency check”.

The below shown is the resultant screen. Any errors in the following screen can be escalated to LT.

5) Check for system logs Txn - SM21

In the following screen, go to the path “system log chose All remote systems logs”.

Enter the previous days date in the “From Date/Time” field and execute.

6) Check for any short dumps Txn - ST22

If we find any short dumps corresponding to “Today” or “Yesterday”, we can escalate the same to LT.

7) Check the background jobs Txn - SM37

Input ‘*’ in the User name field. Input previous days date in the “From” field.

If we find any errors or any canceled jobs, we escalate the same to LT.

8) Check for outbound emails Txn – SOST

We can see the following screen as we enter into the Transaction SOST.

9) Check for the queue – SMQ1 / SMQ2

- SMQ1Input “*” in the “Queue Name” and “Queue Destination” and execute.

The following is the output screen and if we find any errors in the output, we can escalate to LT.

Txn - SMQ2

Input “*” in the “Queue Name” and “Queue Destination” and execute.

The following is the output screen and if we find any errors in the output, we can escalate to LT.

10) Check the IDocs Txn - BD87

Input previous days date in the “Changed On” field and execute.

The following is the output screen and if we find any failure messages, we can escalate the same to LT.

11) Check the Buffer Txn - ST02

We can see the following screen as we enter into the Transaction ST02.

Any “Swaps” in the above shown screen need to be escalated to LT.

BW SYSTEM

The following are the steps & processes to be performed in the BW system.

Please note that all the aforesaid steps from the document need to be performed in the BW System and also the following ones.

Txn - RSPCM

We can see the following screen as we enter into the Transaction RSPCM.

CRM SYSTEM

The following are the steps & processes to be performed in the CRM system.

Please note that all the aforesaid steps from the document need to be performed in the CRM System and also the following ones.

Txn - SMW01

From the following scree, click on the “Variants” button.

As shown below, select the variant “CHECK_ERRORS”.

Once we select the variant, the screen will be input with the values from the variant for the respective fields.

Execute the transaction for the output.

The following is the output for the transaction. If we see any errors in the following screen, the same can be escalated to LT.