SAP BASIS OS Level (UNIX) Commands?

Commands	Description
dpmon d	Dispatcher queue monitor
Sapdba (up to SAP R/3 -4.7)/ brtools	database administration
PS	Running work process
ps -eaf|grep dw	process overview
ps -eaf|grep ora	check oracle service is running
Ps –eaf | grep dw kill -9	Kill work process
msmon pf=profile path name=sid	to check the message server status
gwmon pf=profile path nr=num	to check the gateway status
Ps –eaf | grep lsnrctl	Listener status
Rslgview pf =-r –ft | pg	System logs
Disp + work –v	to check the version of r3 kernel
R3trans –d ,tnsping	Checking the connection with database
Df –k	File system monitor
Du –k	Display all directories and size of current directory
Sqlplus “/as sysdba” (new versions)	SQL prompt and database connection
Saplicence  -get	to get hardware key
saplicense -install	to install license
sappfpar all pf=profile path	display all profile parameters
sappfpar check path=profile path	checks the required space for memory
memlimits	to check the available space for heap and swap memory
telnet	Remote system login
telnet <ipaddress><dispatcherportnum>	to check the remote sap system is up and running
ftp	file transfer protocol
rcp	remote copy of files
Start/stop sap	Start / stop Sap instance
ping	check destination host reachable
niping	check connection between server and a client by transferring packets
systeminfo	check the configuration of system
Ps -eaf	Processes status
lsps -a	Swap space
topas	Memory

Solution Manager 7.1 Monitoring

1. Summary

This document contains a checklist to be performed before the go live of a system to be presumed as system monitoring enabled.

2. Table of Contents

Section 3 is to check if the data is coming into solution manager without which, the data would not be available at the solution manager end. This section contains checks on solution manager getting system component data of managed system to the LMDB, the background jobs setup to collect the data from system monitoring perspective.

Section 4 is to check if the LMDB is updated with the proper data automatically, the necessary components marked for “Diagnostics” so that the extractors for these components are enabled.

Section 5 is to check the status of managed system configuration, the RFCs, the system parameters and the most critical part of “Configure Automatically”.

Section 6 is to check the status of “System Monitoring” in the system.

3. Pre-requisites Check in Solution Manager

3.1 The System Preparation and Basic Configuration

3.2 Check Users

3.3 Check Central Correction Note

3.4 LMDB – SLD Synchronization

3.5 Wily Introscope Enterprise Manager

3.6 Solution Manager Extractor Job

4. LMDB and Technical System

4.1 Definition of Technical System

4.2 Diagnostics Relevant

4.3 Product System

4.4 FQDN for Hosts

4.5 RFC Destination (For ABAP System Only)

5. Managed System Configuration

5.1 Check Status of Managed System Configuration

5.2 Check RFC Destinations

5.3 Diagnostics Agent and Host Agent

5.4 System Parameters

5.5 Configuration Users

5.6 Configure Automatically

5.7 Logical Components

5.8 Extractors

6. System Monitoring

6.1 Configure Infrastructure

6.2 Define Scope

6.3 Setup Monitoring

6.4 Reporting

3. Pre-requisites Check in Solution Manager

3.1 The System Preparation and Basic Configuration

Run transaction SOLMAN_SETUP

Ensure update needed should be blank, that is all the updates necessary must be performed. The most common update is updating the central correction note and unlocking of the critical users.

3.2 Check Users 

Check the following users and ensure it is unlocked.

SOLMAN_ADMIN

SMD_ADMIN

SM_EXTERN_WS

SM_INTERN_WS

SOLMAN_BTC

3.3 Check Central Correction Note 

Check if the latest version of the central correction note is implemented. Once implemented, proceed to section 3 of “System Preparation” in SOLMAN_SETUP, execute “Post Processing” manually.

3.4 LMDB – SLD Synchronization 

Ensure the following two jobs run in solution manager successfully at a frequency of 10 minutes.

SAP_LMDB_LDB_0000000001

SAP_LMDB_NOTIFY_LDB_0000000001

3.5 Wily Introscope Enterprise Manager 

Ensure that Wily Introscope Enterprise Manager is always available. To check the availability, proceed to path SM_WORKCENTER --> Solution Manager Administration --> Infrastructure --> Expert Mode.

The status of Manageable and Status should be green.

3.6 Solution Manager Extractor Job 

The most critical job in solution manager is the extractor job, this job runs every minute once. The job name is EFWK_RESOURCE_MGR. Check the status of the jobs and the job log. There should be no line indicating that the resource cap has exceeded.

4. LMDB and Technical System

4.1 Definition of Technical System

The data supplier should be automatic that is it should be from the SLD; the system should be marked as installed.

4.2 Diagnostics Relevant

Both Application Server ABAP and Process Integration (Functional component, system taken as an example) should be marked installed and the Diagnostics relevant flag marked (in this case it is not done). The Product system should be created and assigned as shown.

4.3 Product System

The Product system should be created and should be assigned to the technical system. The Verification must be completed and should be in status “Green”. To execute this, the pre-requisite is that the SMD Agents and the Host agent must be installed in all the hosts in prior.

4.4 FQDN for Hosts

Ideally, all the hosts should have FQDN filled in.

4.5 RFC Destination (For ABAP System Only)

The RFC destinations must be created and maintained (can be done during managed system configuration as well.

5. Managed System Configuration

5.1 Check Status of Managed System Configuration

Ideally, all the statuses should be in “Green”. Update needed should not mark.

5.2 Check RFC Destinations

On choosing “Test”, for the client, the output should be as shown below.

5.3 Diagnostics Agent and Host Agent

SMD Agent should be in status green and on clicking “Check Host Agents” the result in the log also should be green as shown below.

System Parameters

5.4 System Parameters

Load balancer host and port should be reached successfully

On “Check URL…” the return code should be 200.

The user provided should have sufficient roles and authorizations. Ensure it is provided and updated.

DB Parameter’s must be filled and the system marked for “Setup DBACockpit / DB extractors”.

5.5 Configuration Users

Configuration users must be created and must be working. The test of SMDAGENT_CSQ user must pass through.

5.6 Configure Automatically

Configure automatically must be in status green.

5.7 Logical Components

A logical component must be created and the system assigned to the logical component.

The logical component should be assigned to the solution. To do this, proceed to transaction SMSY --> Solution Landscape --> Choose the solution and in edit mode, add the logical component to the solution.

5.8 Extractors

Ideally all the extractors created must be in green status. Path to access Extractor: SM_WORKCENTER --> Solution Manager Administration --> Landscape --> System --> Extractor Framework

6. System Monitoring

6.1 Configure Infrastructure

All the steps of “Configure Infrastructure” must be in “Green” status.

6.2 Define Scope

The status of Auto Configure, Monitoring and Reporting should be green.

6.3 Setup Monitoring

The templates must be active and applied. The “Assignment Status” must not be yellow – which indicates it has to be re-applied again.

6.4 Reporting

Reporting should be in status green.

IDOC Status Codes and Reprocess reports

After the process of inbound function module and outbound function module the state of status will be recorded in the status record of IDOC. We can view the status by using transaction codes WE02, WE05 and WE07.Here is the list of main IDOC stats codes for Outbound and Inbound IDOC.

Outbound IDOC status codes with status description.

01: IDoc generated

02: Error passing data to port (It’s an error status)

03: Data passed to port OK

04: Error within control information of EDI subsystem

05: Error in translation

06: Translation successful.

07: Error on syntax check (It’s an error status)

08: Syntax check successful

09: Error on interchange handling (It’s an error status)

10: Interchange handling successful

11: Error on dispatch (It’s an error status)

12: IDOC Dispatch successful

13: Retransmission successful

14: Interchange Acknowledgement positive

15: Interchange Acknowledgement negative (It’s an error status)

16: Functional Acknowledgement positive

17: Functional Acknowledgement negative (It’s a warning error status)

18: Triggering EDI subsystem successful

19: Data transfer for test successful

20: Error on triggering EDI subsystem (It’s an error status)

21: Error on passing data for test (It’s an error status)

22: Dispatch successful, acknowledgement still due

23: Error on retransmission (It’s an error status)

24: Control information of EDI subsystem successful

25: Processing despite syntax error (It’s a warning error)

26: Error during syntax check of IDoc (It’s an error status)

27: Error in ALE dispatch level (It’s an error status)

29: Error in ALE service (It’s an error status)

30: IDoc is ready for dispatch in ALE service

31: IDOC is marked for deletion.

32: IDoc was edited

33: Original of an IDoc which was edited

34: Error in control record of IDoc (It’s an error status)

35: IDoc reloaded from archive

36: Timeout error on Electronic signature not performed (It’s an error status)

37: IDoc added incorrectly (It’s an error status)

38: IDoc archived

39: Arrival of IDOC in target system confirmed

40: Application document not created in target system (It’s an error status)

41: Application document created in target system

Inbound IDOC status codes with status description.

42: IDoc was created by test transaction

50: IDoc added

51: Application document not posted (It’s an error status)

52: Application document partially posted (It’s an error status)

53: Application document posted successfully.

54: Error during formal application check (It’s an error status)

55: Formal application check successful

56: IDoc with errors added (It’s an error status)

57: Test IDoc: Error during application check (It’s an error status)

60: Syntax error on IDOC (It’s an error status)

61: Processing despite syntax error (It’s a warning error status)

62: IDoc passed to application

63: Error passing IDoc to application (It’s an error status)

64: IDoc ready to be transferred to application

65: Error in ALE service (It’s an error status)

66: IDoc is waiting for predecessor IDoc in serialization process

68: IDOC is marked for deletion.

69: IDoc was edited

70: Original of an IDoc which was edited

71: IDoc reloaded from archive

73: IDoc archived

74: IDoc was created by test transaction

Using the standard report RC1_IDOC_SET_STATUS we can change the status of an IDOC if we require for that. We can reprocess IDoc if we are getting errors.

We can reprocess IDoc if we are getting errors. Several standard reports are available for this reprocessing. Here are some standard reports for reprocessing of IDOC.

Report RBDMANI2

We can execute this program for manual reprocess of IDOC. It can be used when we get the status 51 or status 63 errors for an inbound IDOC.

Report RBDMANIN

It used for Posting of inbound IDocs with Status 51.

Report RBDMOIND

It checks whether the communication with tRFC was successfully completed. If successfully completed, the status of the IDoc is changed. This reprocess program can be used for outbound IDOC with status codes from 03 to 12.

Report RSEOUT00

For reprocessing outbound IDOC with status 30

Report RBDAPP01

For reprocessing inbound IDOC with status 64

Report RBDAGAIN

It for reprocessing of incorrect outbound IDOC with statuses 02, 04, 05, 25 and 29

Report RBDAGAI2

It for reprocessing of IDOCs after ALE input error with statuses 56, 61, 63 and 65

Report RBDAGAIE

It for reprocessing of Edited IDOCs with status 32 and 69

Changing an IDoc's status:

Idoc’s current status.. you wish to change.

SE38 – ABAP editor

Pgm RC1_IDOC_SET_STATUS

click on execute

IDOC entry and status change screen:

Selection entered.

click on execute

and remove the test check if you want it to process. .. the check will run a report with the number effected.. if you want to process.

and the report below is displayed

ALL ‘orders’ status ‘51’ idocs have been changed to ‘68’

NOTE: leave the message type BLANK if you want to use the IDOC number for selection