Use

You can display a list of application servers that have registered themselves with the SAP message server by executing Transaction SM51, or by choosing Monitor ® System monitoring ® Servers. Only these application servers are active in an SAP System.

Further, you can also manage, and display the status, of the users and work process in all application servers belonging to the SAP System.

Integration

The function for managing users and work processes corresponds to the user- and process-tools. For more information, see Displaying and Controlling Work Processes and Displaying and Managing User Sessions.

Features

The application server display includes the following information:

· Server Name: name of the individual application server.

The name usually consists of the host name, the SAP System name, and the SAP System number.

· Host: host name of the individual server

· Type: SAP Work Process type(s) for which an application server has been configured

As well as the familiar work process types Dialog, update (Update and Upd2), Enqueue, Batch and Spool, there is also the entry ICM. This means that on the application server in question an Internet Communication Manager (ICM) is configured that can accept or send requests from the Internet (HTTP and other protocols). For more information see Internet Communication Manager (ICM).

· Status: The possible statuses of an application server (initial, starting, active, passive, shutdown and stop) are described in Statuses of an SAP Application Server.

You can make changes to statuses in the Message Server Monitor (transaction SMMS). The possible functions are described below:

The following functions are available as pushbuttons or in the menu:

You can use your cursor to select an application server by clicking on the relevant line (except for the Refresh function). The function that is executed then refers to this server.

Function	Meaning
Refresh	Refreshes the display
Processes (or double-click)	Displaying and Controlling Work Processes
User	Display and Manage User Sessions
SNC Status	SNC status
Release Notes	Display detailed release information for an application server (R/3 Kernel, database, operating system)
Remote logon	Log on by any server in the system; you can see the server where you are logged on in the status bar in the second entry from the left.
System log	System logs
General list functions	Choose detail, filter, sort in ascending and descending order, etc.

There are additional functions that you can only use via the menu:

Goto ® SAP directories

The SAP directories of the server on which the cursor is currently positioned are displayed. The environment variables are displayed on the left and the path to the physical directory on the right. To display the contents of a directory, double-click that directory, or click the Display button. You can also display the individual files here. For more detailed information, see the CCMS documentation.

Goto ® OS Monitor

The OS Monitor provides you with statistics about the host platform, on which an SAP instance is running (for more information, see Operating System Monitor in the CCMS guide).

Goto ® Gateway Monitor

You can also access the Gateway Monitor using transaction SMGW. It is described in Using the Gateway Monitor in the SAP System.

Goto ® ICM Monitor

You can also access the ICM monitor in transaction SMICM. It is described in Monitoring the ICM with the ICM Monitor.

Goto ® Server information

The following functions are covered:

Function	Meaning
Environment	This displays the environment variables for the selected server.
Communication table	The communication table for the relevant application server is displayed. All the CPI-C connections for the selected server are displayed (seeBC - SAP Communication: CPI-C Programming and BC - SAP Communication: Configuration.) The connections are displayed where the local dispatcher of the client is located and those connections where the server is located. This means, the connections to the server that were made externally.
Queue Info	For more information, see Queue Info
Release notes	Same information as with the pushbutton Release notes (see above)
WP-CA blocks	Internal information for troubleshooting
APPC-CA blocks
Logon data	Logon data pertaining to the selected server.
Test connection	Tests the connection to the server on which the cursor is position. If the server is active, the message Server is active is issued in the status bar. The alternative message is Server is deactivated.
Trace Search	You can specify a character string in accordance to which all dev_* trace files are searched. This provides an initial overview of the error search.

Host Name Buffer ® Reset ®

This option lets you make the changes made in the OS hosts and services tables in a running SAP System take effect by making the desired changes at the operating system level and then, instead of restarting, resetting the host name buffer for the following components. (See also SAP Note 25917.)

· Selected application server

· Message server

· Internet Communication Manager (ICM)

· Entire system (all host name buffers)

There are the following application server states.

Application Server State	Meaning
initial	The application server has logged on to the message server. When the server is in this state, it cannot be accessed.
starting	The application server starts the work process and initializes all required services. Requests cannot be processed in this phase.
active	This is the "normal" state of the application server. It receives and processes requests, and creates and sends requests to other servers.
passive	In this state, the application server can continue to process received requests or create requests itself. However, no new requests should be sent to the server. The purpose of this state is to "logically" remove from the system a server that has to be stopped during productive operation. The server finishes processing its existing requests, but does not accept any new requests and can be terminated without having to interrupt any relevant requests such as updates or batch jobs. This state can be changed to the "active" state.
shutdown	The application server is in the shutdown phase, that is, it will be terminated. This state is similar to the "passive" state, but cannot be changed to the "active" state. This state or phase ends with the termination of the server.
stop	The application server has terminated the connection to the message server and can no longer be accessed.

For a description of the functions for manipulating the state of an application server,.

Definition

The communication table contains all of the CPI-C connections for the server on which the cursor was positioned .

The connections are displayed where the local dispatcher of the client is located and those connections where the server is located. This means, the connections to the server that were made externally.

Use

The communication table helps you keep track of the CPI-C connections when monitoring the system or analyzing problems.

Structure

Destination	Conv-Id	User	Type	Status	Client	Req	Wp	Time
GTADIR_SERVER	61004034	KUNZ	CLIENT	ALLOCATED	.	.	1	09:16:44
.	60788713	RFC_CORR_REQ	SERVER	ALLOCATED	R/3	CMRCV	0	09:18:22
EU_SCRP_WN32	60230342	KUNZ	CLIENT	ALLOCATED	.	.	1	09:05:18
.	02602553	HINZ	SERVER	ALLOCATED	R/3	.	0	09:51:07
.	88959741	SCHMITT	SERVER	ALLOCATED	R/3	CMSEND(SAP)	1	17:51:27
.	86810585	MAIER	SERVER	ALLOCATED	R/3	CMSEND(SAP)	0	12:41:09

The entries in the table have the following meaning:

Field	Meaning
Destination	Communication partner If the computer where you are currently logged on is the server of a CPI-C connection (see Type column), the destination column will be empty. If the local host is the CPI-C client, the remote destination, which is the server for this connection, is displayed in this field. You can display and maintain RFC destinations using Transaction SM59 or by clicking display and maintain Destination .
Conv-Id	Conversation ID
User	User
Type	Client that requested a service and therefore the connection, or server that fulfills the client’s request
Status	Current connection status; the following entries are possible:
	INITIALIZED	Connection is being made
	ALLOCATED	Connection is made
	DEAL NOW	Connection is being terminated
	DEALLOCATED	Connection has been terminated
	CLEAR SNC	When using SNC: Encrypted data is still being supplied before the connection can be terminated.
Client	If Type = SERVER , information about the client. Is the client also an R/3 System or an external program?
Req	Last call or request (on the CPI-C level)
Wp	Last work process, used for processing
Time	Time of the last request that dealt with the connection

You can display information on the SNC connections of the server here.

The table contains the following fields:

Field	Meaning	Profile parameter
Server name		rdisp/myname
SNC active	Green light: yes / no light: no	snc/enable
Appl. PName		snc/enable snc/identity_as
GUI logon	Lock open: insecure connections are accepted Lock closed: insecure connections are not accepted	snc/accept_insecure_gui
RFC logon		snc/accept_insecure_rfc
Internal RFC logon		snc/accept_insecure_r3int_rfc
CPIC logon		snc/accept_insecure_snc
External programs		snc/permit_insecure_start
GSSAPI library	Path to GSS library	snc/gssapi_lib

The profile parameters are explained in the RZ11 of the parameter documentation.

The following documents are also relevant for SNC:

• SNC User's Guide, Technical Document.

SAPNet: http://sapnet.sap.com/systemmanagement -> Security -> Secure Network Communications

• SAP Complementary Software Program

SAPNet: http://www.sap.com/csp

SNC, see: http://www.sap.com/products/compsoft/scenarios/bc/bcsnc.htm

The following table contains the trace components of the SAP kernel together with their one-character abbreviation. You see these letters in each line of the trace file and you need them if you want to determine using parameter rdisp/TRACE_COMPS which components are to write traces.

More information: rdisp/TRACE* Parameters

Component Abbreviation in Trace File	Component (Selection using SM50 or SM04)
M	Task handler
A	ABAP Processor
Y	Screen Processor
X	Extended memory
E	Lock management (enqueue)
I	IPC (inter process communication)
S	Print (spool)
N	Secure Network Communication, (SNC)
T	Debug system
L	Background
B	Database
C	Database (DBSL)
P	Paging
R	Rolling
D	Diag processor

You can use the rdisp/TRACE* profile parameters to set the level of detail and the components that write traces.

You can change the parameters dynamically with the exception of rdisp/TRACE_COMPS, thus changing the trace behavior in productive operation.

Features

The following table lists the parameters and their meanings.

Trace Parameters

Parameter	Meaning	Value Range, Example
rdisp/TRACE	You use this parameter to set the trace level for the dev_* developer trace. The following values are permitted: Caution Trace level 2 or higher affects the performance of the system and should only be set for an error analysis. The trace files also grow very quickly when trace logging is activated. Check that there is enough space on the hard drive where the SAP directory is located. You can use the rdisp/TRACE_LOGGING parameter to prevent the trace files from getting too big. End of the caution.	Whole number between 0 and 3: 0: No trace. 1: Error messages are written to the trace file. 2: Full trace. The trace entries are dependent on the SAP program traced. 3: Like 2 but data blocks are also traced.
rdisp/TRACE_COMPS	Each SAP component has an abbreviation (see Trace Components). This parameter controls the status of the components as follows. Component X Is inactive if the code letter is not in the string (no trace at all) Writes the trace only to level 1 (error) if the component is contained in the string only as a lowercase letter Writes the trace with a higher level if the component is contained in the string as an uppercase letter (and rdisp/TRACE is set accordingly)	Character string consisting of letters for the trace components and the strings All or all. Example You want all components to write the trace up to level 1. Thereafter, you only want the task handler components to write the trace. Set the string to Mdyabcirplesxn. To avoid long strings, you can start the string with ALL (all letters uppercase) or all (all letters lowercase) and then list possible exceptions. rdisp/TRACE_COMPS =all, M Meaning: All components to level 1, thereafter only task handler components. This is also the default setting. rdisp/TRACE_COMPS =All, ads Meaning: All components up to the highest level, but not diag, ABAP, or spool. End of the example. Caution If the parameter does not work as intended, formulate the string so that it begins with all or All. End of the caution.
rdisp/TRACE_LOGGING	This parameter activates trace logging.	The parameter values must have the following syntax: Syntax rdisp/TRACE_LOGGING = on, [k m] [global=on off] off End of the code. The first part specifies that logging is active. The value here can be either on or off. If logging is active, you can specify the file size in the second part.
rdisp/TRACE_PATTERN_0 rdisp/TRACE_PATTERN_1 rdisp/TRACE_PATTERN_2	rdisp/TRACE_PATTERN_ (=0,1,2) defines a search pattern to automatically switch off the SAP trace. This parameter only has an effect if trace logging is activated using rdisp/TRACE_LOGGINGrdisp/TRACE_LOGGING. In this case, the trace files are searched for the search pattern before being automatically reset. If the pattern is found, trace logging is deactivated and the trace level is reset to 1. The following trace files are included in the search: All dev_w* work process trace files dev_disp dispatcher trace files dev_rd gateway trace files dev_icm ICM trace file (if available) dev_ms message server trace file (if available) The search pattern can contain the special character * for any character string and ? for any character. Use the backslash (\) to ensure that special characters are treated as ordinary characters.	Character string that can contain the special characters * or ?. Caution For the sake of readability, the search patterns in the following examples are enclosed in inverted commas. When specifying your own search terms in RZ11 or in the profiles, however, enter them without inverted commas. End of the caution. Example Pattern "word1 * word?" is found in line "one example with word1 and word2" but not in line "one example with word1 and word" Pattern "10 \* 10 =" is found in line "Multiplication: 10 * 10 = 100" but not in line "Addition: 10 + 10 = 20" End of the example.
rdisp/TRACE_SEARCH_LIST	You can use this parameter to specify a list of trace file types to be included in the automatic trace search. More information: Trace Logging	Special character string. As a value for this parameter, you can enter a list with the following elements (use a comma or a semicolon to separate elements): ALL, DISP, WP, GWRD, MS, ICMAN Example rdisp/TRACE_SEARCH_LIST = WP, ICMAN Meaning: All work process trace files and the ICM trace file are included in the search. End of the example.
rdisp/TRACE_RESOLUTION	You can use this parameter to control the frequency of the timestamp in the trace files. It specifies how often per second a timestamp is to be written. The default value for this parameter is 1, which means that (at least) one second must separate the timestamps. 0 deactivates the writing of timestamps. With a parameter value > 0, the milliseconds of the timestamp are displayed in the following format: "Fri Sep 3 14:47:54:433 2004"	Whole number (between 0 and 10) Example 0: No timestamp is written 1: A maximum of one timestamp is written per second (old behavior) 5: A maximum of five timestamps are written per second (at least 200ms separate the timestamps) 10: A maximum of ten timestamps are written per second (at least 100ms separate the timestamps)

Use

You can use the trace functions to follow the process of various operations in your SAP system. This allows you to monitor the system and to isolate problems that occur.

Features

You can use the trace functions to monitor the following operations in your system:

· SQL database accesses

For more information, refer to the SQL trace documentation in the BC - ABAP Workbench: Tools guide.

· ABAP programs

For more information, refer to the ABAP runtime documentation in the BC - ABAP Workbench: Tools guide.

· Internal operations in the SAP system and authorization check

You can use transaction ST01 for this (see System Trace).

· Traces generated by SAP processes (developer traces).

These are the trace files that are written by the individual SAP system processes.These trace files contain detailed technical information for use in the event of problems in your System.For more information about this, see Developer Traces. To display the trace files you can use transaction ST11.

Activities

To access the trace facility, choose Tools ® Administration ® System Administration ® Monitor ® Traces.

Use

You can use this function if you want to activate trace level 2 or 3 for a long period, but want to ensure that the trace file does not become too large. This is useful if you are trying to locate a sporadic error. If you are “waiting” for a particular trace output, you can specify that the trace file should be saved after the pattern you are searching for is found, and that the trace level should then be reset to 1.

In this way, you can easily control the size of the trace files. You can also search the trace file for a particular character string without running the risk of filling up your hard disk if a high trace level is active.

Features

Set Size Limit for Trace Files

To activate trace logging, you have to set the parameter rdisp/TRACE_LOGGING. Here, you also specify the maximum size of the trace file.

If the trace file reaches that size, the content is written to a log file with the name of the trace file and the extension .old. The current trace file is then reset. The parameter rdisp/autothtime is used to define how often the trace file should be checked and, if necessary, reset. The default is 60 seconds.

Trace logging is active for the following trace files:

· Work process traces dev_w*

· Dispatcher trace dev_disp

· Gateway trace dev_rd

· ICM trace dev_icm

· Message server trace dev_ms

Specify Trace Components

The parameter rdisp/TRACE_SEARCH_LIST is used to specify a list of trace components that you want taken into account in the automatic trace search.

As a value for this parameter, you can enter a list with the following elements (use a comma or a semicolon to separate elements):

· ALL: all trace files are searched (default)

· WP: all work process trace files are searched

· DISP: the dispatcher trace file is searched

· GWRD: the gateway trace file is searched

· ICMAN: the ICM trace file is searched (if available)

· MS: the message server trace file is searched (if available)

rdisp/TRACE_SEARCH_LIST = WP, ICMAN means: all work process trace files and the ICM trace file are searched.

Search Trace Files for a Pattern

The parameter rdisp/TRACE_PATTERN_ is used to search the trace files for a specific pattern. The file is searched for the pattern, once the size specified in rdisp/TRACE_LOGGING has been exceeded. If the pattern is found, the trace level is reset to 1 for all active components.

You can also use wildcards (* for any character string, ? for a single character) in the pattern. Use the backslash (\) to ensure that special characters are treated as ordinary characters.

Note that wildcards reduce system performance, especially if they are in the middle of a pattern.

For the sake of readability, the search patterns in the following examples are enclosed in inverted commas. When specifying your own search terms in RZ11 or in the profiles, however, enter them without inverted commas.

The pattern "word1 * word?" is found in the line "one example with word1 and word2", but not in the line "one example with word1 and word".

The pattern "10 \* 10 =" is found in the line "multiplication: 10 * 10 = 100", but not in the line "addition: 10 + 10 = 20".

You cannot join several search patterns logically, for example, you cannot search for pattern 1 and pattern 2.

System-Wide Trace Logging

If you want to search for a pattern on all the servers of a system and when this is found end the trace logging on all the servers (that is, reset the trace level to 1), you use the addition global=on. If global=off or is not set at all, the logging is only switched off on the server where the pattern was found.

Standalone Message Server.

The message server itself searches only for the string in dev_ms, if parameter ms/standalone = 1 is set. Otherwise the search is performed by a work process of the same instance as that with which the message server was started.

If the message server does the search itself, the search is started in a separate thread, which means that if the file is large, the normal processing of requests is not hindered.

Activities

Proceed as follows.

...1.Activate trace logging by setting the parameter rdisp/TRACE_LOGGING to ON. Also specify the size at which, once reached, the trace file is logged and the trace level is reset to 1.

You can dynamically change this parameter in transaction RZ11.

The parameter values have the following syntax:

rdisp/TRACE_LOGGING = on, [k | m] , [global=on | off] | off

The first part specifies that logging is active. The value here can be either ON or OFF. If logging is active, you can specify the file size in the second part. The addition global=on or global=off is effective only if the parameter rdisp/TRACE_PATTERN_0 for the pattern search has been set. (compare with system-wide trace logging).

· rdisp/TRACE_LOGGING = off : no trace logging

· rdisp/TRACE_LOGGING = on, 1000: trace is logged if the trace file contains more than 1000 bytes

· rdisp/TRACE_LOGGING = on, 20 k: trace is logged if the trace file contains more than 20 KB

· rdisp/TRACE_LOGGING = on, 30 m, global=on activates trace logging, if the trace file is larger than 30 megabytes. If the pattern searched for has been found in a trace file, trace logging is deactivated on all the servers.2. Use the parameter rdisp/TRACE_PATTERN_0 to specify a trace pattern for automatically switching off the SAP trace. This parameter has effect only if trace logging is activated using rdisp/TRACE_LOGGING.In this case, the trace files are searched for the search pattern before being automatically reset. If the pattern is found, trace logging is deactivated and the trace level is reset to 1. The following trace files are included in the search:

· Work process traces dev_w*

· Dispatcher trace dev_disp

· Gateway trace dev_rd

· ICM trace dev_icm

· Message server trace dev_ms

The search pattern can contain the special character * for any character string, and ? for any character. The parameters rdisp/TRACE_PATTERN_1 and rdisp/TRACE_PATTERN_2 can be used to define other search patterns. All search patterns use the or operator; in other words, if one of the patterns is found, the trace level is reset.

Sometimes, internal user or customer might request you to change the Title of the SAP Transaction code to a more meaningful one and SAP allows this to be done painlessly.

The steps to change the Title of any SAP transaction code are as follows:

First, goto tcode SE63

On the top left Menu of the screen - Click Translation - Short texts - Transactions

For example, assuming you want to change the title of the tcode FB01 from Post Document to Post Document for G/L. On the first screen, fill in the following information:

Transaction code - FB01

Source Language - English
Target Languate - English

To change the Title, click the Edit button

On the second line, type in the Title (For e.g. Post Document for G/L) you want for the transaction code

Click the Save button

Now, called up the transaction code /nFB01 again and you should be able to view the new Title.

Please note that it works for most of the Transaction code except for those new Enjoy transaction code in 4.6x.

You can access all the transaction codes by using the transaction code 'SDMO'.

This is the transaction code for the Dynamic Menu.

Based on your search string, you can get all related transaction codes for all the SAP application modules.

For e.g. the Search text for ADMIN returns the following results:

----------------------------------------------------------
|Tcode|Transaktionstext |
----------------------------------------------------------
|ADOK |AM: System Administration Guide |
|BALE |Area Menu for Administration |
|BDMO |ALE CCMS Group Administration |
|CATSX|Time Sheet Admin.: Initial Screen |
|CICY |CTI Administration |
|CJV6 |Maintenance: Version administration |
|CN84 |PS: Archiving project - admin. |
|COA4 |PP: Archiving order - administration |
|CSADM|Content Server Administration |
|FC_BW|Administrator Workbench |
|FDTA |TemSe/REGUT Data Administration |
|FDTT |Treasury Data Medium Administration |
|FO86 |Change active admin.contract fees |
|FO8E |Create admin.contract event |
|FO8F |Change admin.contract event |
|FO8G |Display admin.contract event |
|FO8H |Admin.costs acct sttlmnt simulation |
|FOART|REsearch: Administration Web-User |
|HRCMP|Compensation Administration |
|HRCMP|Budget Administration: Display |
|HRCMP|Budget Administration: Change |
|IM_AR|Admin. of App. Request Archives |
|KA18 |Archive admin: assess., distr., ... |
|KE72 |Archive Administration: Line Items |
|KE73 |Archive Administration: Totals Recs |
|KPRO |KPRO Administration |
|OAAD |ArchiveLink Administration Documents |
|OG00 |Personnel Administration Customizing |
|OG01 |Personnel Administration Customizing |
|OMSM |CS MM Set Up Administrative Data |
|OOCM_|Compensation Administration Settings |
|OOML |Room Administration Mail Connection |
|OOPC |Administration: Personnel No. Check |
|OY22 |Create subadministrator Customizing |
|OYEA |IDoc administration |
|PA97 |Compensation administration - matrix |
|PA98 |Compensation Administration |
|PA99 |Compensation Admin. - Release Report |
|PACA |PF administration |
|PAT1 |Personnel Administration infosystem |
|PC00_|CBS survey salary administrations |
|PC00_|Tax Certificates - Administration 16 |
|PP26 |Plan Scenario Administration |
|PP2D |Administer Payroll Results |
|PSO5 |PD: Administration Tools |
|PUCA |PC administration for PF |
|PVSEA|Administer Search Engine |
|QD25 |Archiving Notifications: Admin. |
|S002 |Menu Administration |
|SA02 |Academic title (cent. addr. admin.) |
|SA04 |Name prefixes (centr. addr. admin.) |
|SA05 |Name suffix (centr. addr. admin.) |
|SA07 |Address groups (centr. addr. admin.) |
|SA08 |Person groups (centr. addr. admin.) |
|SA09 |Internat. versions address admin. |
|SA10 |Address admin. communication type |
|SARA |Archive Administration |
|SBPT |Administration Process Technology |
|SCC4 |Client Administration |
|SCON |SAPconnect - Administration |
|SCOT |SAPconnect - Administration |
|SCUA |Central User Administration |
|SCUM |Central User Administration |
|SE78 |SAPscript: Graphics administration |
|SECST|Administration of Secure Memory |
|SENG |Administration of External Indexes |
|SENGE|Explorer Index Administration |
|SIAC1|Web Object Administration |
|SLICE|Administer SAP Licenses |
|SLWA |Translation Environment Administratn |
|SM14 |Update Program Administration |
|SP12 |TemSe Administration |
|SPAD |Spool Administration |
|SPAT |Spool Administration (Test) |
|SPHA |Telephony administration |
|SPHB |SAPphone: System Administration |
|SSAA |System Administration Assistant |
|SSCA |Appointment Calendar: Administration |
|SSCA1|Appointment calendar: Administration |
|SSO2 |Workplace Single Sign-On Admin. |
|SSO2_|Workplace Administration SSO2 Ticket |
|STMA |Proposal Pool Administration |
|SURAD|Survey Administration |
|SURL_|Personalization for URL Gen. Admin. |
|SUUMD|Display User Administration |
|SWDC |Workflow Definition: Administration |
|SWEAD|Event Queue Administration |
|SWEQA|Event Queue Administration |
|SWEQA|Queue Administrator Maintenance |
|SWIA |Selection rep. for work items(admin) |
|SWRK |Administrtation using work areas |
|SWUF |Administration of Runtime System |
|SWUL |Customizing: Process Administrator |
|SWUX |SAPforms Administration |
|SYSAD|System Administration: Task List |
|S_ALR|IMG Activity: CIC_V_CCMCTIADMIN |
|S_ALR|IMG Activity: SIMG_EURO_ADMINUSER |
|S_BCE|IMG-Aktivität: BCDIGSI_ADMIN |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|TBD0 |Datafeed: Adminster Archives |
|TBD3 |Datafeed: Market data administration |
|TBD6 |Datafeed: Log file administration |
|WE46 |IDoc administration |
|WORKI|Administrtation using work areas |
----------------------------------------------------------

In Transaction MM01, I want to block the material type "Non-Stock Material (ie)NLAG." What are the ways to do it?
You can add an authorization group to the material type. An authorization can be added to the material type via transaction OMS2. Users who do not have authorization for M_MATE_MAR for the authorization group on that material type will not be able to maintain it in MM01.

1. What is a transaction?

- A transaction is dialog program that change data objects in a consistant way.

2. What are the requirements a dialog program must fulfill?

A dialog program must fulfil the following requirements

- A user friendly user interface.

- Format and consistancey checks for the data entered by the user.

- Easy correction of input errors.

- Access to data by storing it in the data bases.

3. What are the basic components of dialog program?

- Screens (Dynpros)

- Each dialog in an SAP system is controlled by dynpros.A dynpros consists of a screen

And its flow logic and controls exactly one dialog step.

- ABAP/4 module Pool.

Each dynpro refers to exactly one ABAP/4 dialog program .Such a dialog program is also called a module pool ,since it consists of interactive modules.

4.What is PBO and PAI events?

PBO- Process Before Output-It determines the flow logic before displaying the screen.

PAI-Process After Input-It determines the flowlogic after the display of the screen and after receiving inputs from the User.

5. What is dynpro?What are its components ?

- A dynpro (Dynamic Program) consists of a screen and its flow logic and controls exactly one dialog steps.

- The different components of the dynpro are :

Flow Logic: calls of the ABAP/4 modules for a screen .

Screen layout: Positions of the text, fields, pushbuttons and so on for a screen

Screen Attributes: Number of the screen, number of the subsequent screen, and others

Fields attributes: Definition of the attributes of the individual fields on a screen.

6. What is a ABAP/4 module pool?

-Each dynpro refers to exactly one ABAP/4 dialog program.Such a dialog program is also called

a module pool ,since it consists on interactive modules.

7..Can we use WRITE statements in screen fields?if not how is data transferred from field data to screen fields?

-We cannot write field data to the screen using the WRITE statement.The system instead transfers data by comparing screen fields names with ABAP/4 variable names.If both names are the same,it

transfers screen fields values to ABAP/4 programs fields and Vice Versa.This happens immediately after displaying the screen.

8.Can we use flow logic control key words in ABAP/4 and vice-versa?

- The flow control of a dynpro consists os a few statements that syntactically ressemble ABAP/4 statements .However ,we cannot use flow control keywords in ABAP/4 and vice-versa.

9.What is GUI status? How to create /Edit GUI status?

-A GUI status is a subset of the interface elements used for a certain screen.The status comprises

those elements that are currently needed by the transaction .The GUI status for a transaction may be composed of the following elements:

-Title bar.

-Mneu bar.

-Application tool bar

-Push buttons.

To create and edit GUI status and GUI title,we use the Menu Painter.

10. How does the interection between the Dynpro and the ABAP/4 Modules takes place?

-A transaction is a collection os screens and ABAP/4 routines, controlled and executed by a Dialog processor. The Dialog processor processes screen after the screen, thereby triggering the appropriate

ABAP/4 processing of each screen .For each screen,the system executes the flow logic that contains the corresponding ABAP/4 processing.The controls passes from screen flow logic to ABAP/4 code and back.

11. How does the Dialog handle user requests?

- when an action is performed ,the system triggers the PROCESS AFTER INPUT event.The data passed includes field screen data data entered by the user and a function code. A functioncode is a technical name that has been allocated in a screen Painter or Menu Painter to a meny entry,a push button,the ENTER key or a function Key of a screen.An internal work field(ok-code)in the PAI module evaluates the function code,and the appropriate action is taken.

12. What is to be defined for a push button fields in the screen attributes?

- A function code has to be defined in the screen attributes for the push buttons in a screen.

13. How are the function code handles in Flow Logic?

- When the User selects a function in a transaction ,the system copies the function code into a specially designated work field called OK_CODE.This field is Global in ABAP/4 Module Pool.The OK_CODE can then be evaluated in the corresponding PAI module. The function code is always passed in Exactly the same way , regardless of Whether it comes from a screen’s pushbutton,a menu option ,function key or other GUI element.

14.What controls the screen flow?

- The SET SCREEN and LEAVE SCREEN statements controls screen flow.

14. The Function code currently active is ascertained by what Variable?

- The function code currently active in a Program can be ascertained from the SY-UCOMM Variable.

15. The function code currently active is ascertained by what variable ?

- By SY-UCOMM Variable.

16. What are the “field” and “chain” Statements?

- The FIELD and CHAIN flow logic statements let you Program Your own checks.FIELD and CHAIN tell the system Which fields you are checking and Whether the System should Perform Checks in the flow logic or call an ABAP/4 Module.

17. What is an “on input filed” statements?

- ON INPUT

The ABAP/4 module is called only if a field contains the Value other than the initial Value.This initial Value is determined by the filed’s Dta Type: blanks for character Fields

,Zeroes for numerics. If the user changes the Fields Value back t o its initial value,ON INPUT does not trigger a call.

18. What is an “on request Field” statement?

- ON REQUEST

The ABAP/4 Module is called only if the user has entered the value in the field value since the last screen display .The Value counts as changed Even if the User simply types in the value that was already there .In general ,the ON REQUEST condition is triggered through any

Form of” MANUAL INPUT’.

19. What is an on”*-input filed” statement?

ON *-INPUT

- The ABAP/4 module is called if the user has entered the “*” in the first character of the field, and the field has the attribute *-entry in the screen Painter.You can use this option in Exceptional cases where you want to check only fields with certain Kinds of Input.

20. What are conditional chain statement?

ON CHAIN-INPUT similar to ON INPUT.

The ABAP/4 module is called if any one of the fields in the chain contains a value other than its initial value(blank or nulls).

ON CHAIN-REQUEST

This condition functions just like ON REQUEST, but the ABAP/4 module is called if any one of the fields in the chain changes value.

21. What is “at exit-command:?

The flowlogic Keyword at EXIT-COMMAND is a special addition to the MODULE statement in the Flow Logic .AT EXIT-COMMAND lets you call a module before the system executes the automatic fields checks.

22. Which Function type has to be used for using “at exit-command” ?

- To Use AT EXIT – COMMAND ,We must assign a function Type “E” to the relevant function in the MENU Painter OR Screen Painter .

23. What are the different message types available in the ABAP/4 ?

- There are 5 types of message types available.

- E: ERROR

- W-WARNING

- I –INFORMATION

- A-ABNORMAL TERMINATION.

- S-SUCCESS

24. Of the two “ next screen “ attributes the attributes that has more priority is -------------------.

Dynamic.

25. Navigation to a subsequent screen can be specified statically/dynamically. (TRUE/FALSE).

TRUE.

26. Dynamic screen sequence for a screen can be set using ------------- and ----------------- commands

Set Screen, Call screen.

27. The commands through Which an ABAP/4 Module can “branch to “ or “call” the next screen are



1.------------,2--------------,3---------------,4------------.



- Set screen,Call screen ,Leave screen, Leave to screen .

28. What is difference between SET SCREEN and CALL SCREEN ?



- With SET SCREEN the current screen simply specifies the next screen in the chain , control branches to this next screen as sonn as th e current screen has been processed .Return from next screen to current screen is not automatic .It does not interrupt processing of the current screen.If we want to branch to the next screen without finishing the current one ,use LEAVE SCREEN.



- With CALL SCREEN , the current (calling) chain is suspended , and a next screen (screen chain) is called .The called can then return to the suspended chain with the statement LEAVE SCREEN TO SCREEN 0 .Sometime we might want to let an user call a pop up screen from the main application screen to let him enter secondary information.After they have completed their enteries, the users should be able to close the popup and return directly to the place where they left off in the main screen.Here comes CALL SCREEN into picture .This statement lets us insert such a sequence intp the current one.

29. Can we specify the next screen number with a variable (*Yes/No)?



- Yes



30. The field SY-DYNR refers to--------------



Number of the current screen.



31. What is dialog Module?

- A dialog Module is a callable sequence of screens that does not belong to a particular transaction.Dialog modules have their module pools , and can be called by any transaction.



32. The Syntex used to call a screen as dialog box (pop up)is---------



CALL SCREEN

STARTING AT

ENDING AT



33. What is “call mode”?

- In the ABAP/4 WORLD each stackable sequence of screens is a “call mode”, This is IMP because of the way u return from the given sequence .To terminate a call mode and return to a suspended chain set the “next screen” to 0 and leave to it:

LEAVE TO SCREEN 0 or (SET SCREEN 0 and LEAVE SCREEN) .When u return to the suspended chain execution resumes with the statement directly following the original CALL SCREEN statement.The original sequence of screens in a transaction (that is , without having stacked any additional call modes),you returned from the transaction altogether.





34. The max number of calling modes stacked at one time is?

- NINE



35. What is LUW or Data base Transaction ?



- A “LUW”(logical unit of work) is the span of time during which any database updates must be performed in an “all or nothing” manner .Either they are all performed (committed),or they are all thrown away (rolled back).In the ABAP/4 world , LUWs and

- Transactions can have several meanings:



LUW (or “database LUW” or “database transaction”)



This is the set of updates terminated by a database commit. A LUW lasts, at most, from one screen change to the next (because the SAP system triggers database commits automatically at every screen change).



36. What is SAP LUW or Update Transaction?

Update transaction (or “SAP LUW”)

This is a set of updates terminated by an ABAP/4 commit. A SAP LUW may last much longer than a database LUW, since most update processing extends over multiple transaction screens. The programmer terminates an update transaction by issuing a COMMIT WORK statement.



37. What happens if only one of the commands SET SCREEN and LEAVE SCREEN is used without using the other?

If we use SET SCREEN without LEAVE SCREEN, the program finishes processing for the current screen before branching to . If we use LEAVE SCREEN without a SET SCREEN before it, the current screen process will be terminated and branch directly to the screen specified as the default next-screen in the screen attributes.



38. What is the significance of the screen number ‘0’?

In “calling mode”, the special screen number 0 (LEAVE TO SCREEN 0) causes the system to jump back to the previous call level. That is, if you have called a screen sequence with CALL SCREEN leaving to screen 0 terminates the sequence and returns to the calling screen. If you have not called a screen sequence, LEAVE TO SCREEN 0 terminates the transaction.



39. What does the ‘SUPPRESS DIALOG’ do?

Suppressing of entire screens is possible with this command. This command allows us to perform screen processing “in the background”. Suppresing screens is useful when we are branching to list-mode from a transaction dialog step.



40. What is the significance of the memory table ‘SCREEN’?

At runtime, attributes for each screen field are stored in the memory table called ‘SCREEN’. We need not declare this table in our program. The system maintains the table for us internally and updates it with every screen change.



41. What are the fields in the memory table ‘SCREEN’?

Name Length Description



NAME 30 Name of the screen field

GROUP1 3 Field belongs to field group 1

GROUP2 3 Field belongs to field group 2

GROUP3 3 Field belongs to field group 3

GROUP4 3 Field belongs to field group4

ACTIVE 1 Field is visible and ready for input.

REQUIRED 1 Field input is mandatory.

INPUT 1 Field is ready for input.

OUTPUT 1 Field is display only.

INTENSIFIED 1 Field is highlighted

INVISIBLE 1 Field is suppressed.

LENGTH 1 Field output length is reduced.

DISPLAY_3D 1 Field is displayed with 3D frames.

VALUE_HELP 1 Field is displayed with value help.



42. Why grouping of fields is required? What is the max no of modification groups for each field?

If the same attribute need to be changed for several fields at the same time these fields can be grouped together. We can specify up to four modification groups for each field.



43. What are the attributes of a field that can be activated or deactivated during runtime?

Input, Output, Mandatory, Active, Highlighted, Invisible.



44. What is a screen group? How it is useful?

Screen group is a field in the Screen Attributes of a screen. Here we can define a string of up to four characters which is available at the screen runtime in the SY-DNGR field. Rather than maintaining field selection separately for each screen of a program, we can combine logically associated screens together in a screen group.



45. What is a Subscreen? How can we use a Subscreen?

A subscreen is an independent screen that is displayed in a n area of another (“main”) screen. To use a subscreen we must call it in the flow logic (both PBO and PAI) of the main screen. The CALL SUBSCREEN stratement tells the system to execute the PBO and PAI events for the subscreen as part of the PBO or PAI events of the main screen. The flow logic of your main program should look as follows:

PROCESS BEFORE OUTPUT.

CALL SUBSCREEN INCLUDING ‘’ ’’.

PROCESS AFTER INPUT.

CALL SUBSCREEN .

Area is the name of the subscreen area you defined in your main screen. This name can have up to ten characters. Program is the name of the program to which the subscreen belongs and screen is the subscreen’s number.



46. What are the restrictions on Subscreens?

Subscreens have several restrictions. They cannot:

· Set their own GUI status

· Have a named OK code

· Call another screen

· Contain an AT EXIT-COMMAND module

· Support positioning of the cursor.



47. How can we use / display table in a screen?

ABAP/4 offers two mechanisms for displaying and using table data in a screen. These mechanisms are TABLE CONTROLS and STEP LOOPS.



48. What are the differences between TABLE CONTROLS and STEP LOOPS?

TABLE CONTROLS are simply enhanced STEP LOOPS that display with the look and feel of a table widget in a desktop application. But from a programming standpoint, TABLE CONTROLS and STEP LOOPS are almost exactly the same. One major difference between STEP LOOPS and TABLE CONTROLS is in STEP LOOPS their table rows can span more than one time on the screen. By contrast the rows in a TABLE CONTROLS are always single lines, but can be very long. (Table control rows are scrollable). The structure of table control is different from step loops. A step loop, as a screen object, is simply a series of field rows that appear as a repeating block. A table control, as a screen object consists of: I) table fields (displayed in the screen ) ii) a control structure that governs the table display and what the user can do with it.



49. What are the dynapro keywords?

FIELD, MODULE, SELECT, VALUES and CHAIN are the dynapro keywords.



50. Why do we need to code a LOOP statement in both the PBO and PAI events for each table in the screen?

We need to code a LOOP statement in both PBO and PAI events for each table in the screen. This is because the LOOP statement causes the screen fields to be copied back and forth between the ABAP/4 program and the screen field. For this reason, at least an empty LOOP….ENDLOOP must be there.



51. The field SY-STEPL refers to the index of the screen table row that is currently being processed. The system variable SY-stepl only has a meaning within the confines of LOOP….ENDLOOP processing. Outside the loop, it has no valid value.



52. How can we declare a table control in the ABAP/4 program?



Using the syntax controls

type tableview using screen .



53. Differentiate between static and dynamic step loops.

Step loops fall into two classes: Static and Dynamic. Static step loops have a fixed size that cannot be changed at runtime. Dynamic step loops are variable in size. If the user re-sizes the window the system automatically increases or decreases the number of step loop blocks displayed. In any given screen you can define any number of static step loops but only a single dynamic one.



54. What are the two ways of producing a list within a transaction?

By submitting a separate report.

By using leave to list-processing.



55. What is the use of the statement Leave to List-processing?

Leave to List-processing statement is used to produce a list from a module pool. Leave to list processing statement allows to switch from dialog-mode to list-mode within a dialog program.



56. When will the current screen processing terminates?

A current screen processing terminates when control reaches either a Leave-screen or the end of PAI.



57. How is the command Suppress-Dialog useful?

Suppressing entire screens is possible using this command. This command allows us to perform screen processing “in the background”. The system carries out all PBO and PAI logic, but does not display the screen to the user. Suppressing screens is useful when we are branching to list-mode from a transaction dialog step.



58. What happens if we use Leave to list-processing without using Suppress-Dialog?

If we don’t use Suppress-Dialog to next screen will be displayed but as empty, when the user presses ENTER, the standard list output is displayed.



59. How the transaction that are programmed by the user can be protected?

By implementing an authority check.



60. What are the modes in which any update tasks work?

Synchronous and Asynchronous.



61. What is the difference between Synchronous and Asynchronous updates?

A program asks the system to perform a certain task, and then either waits or doesn’t wait for the task to finish. In synchronous processing, the program waits: control returns to the program only when the task has been completed. In asynchronous processing, the program does not wait: the system returns control after merely logging the request for execution.



62. SAP system configuration incluedes Dialog tasks and Update tasks.

63. Dialog-task updates are Synchronous updates.

64. Update –task updates are Asynchronous updates.

65. What is the difference between Commit-work and Rollback-Work tasks?

Commit-Work statement “performs” many functions relevant to synchronized execution of tasks. Rollback-work statement “cancels: all reuests relevant to synchronized execution of tasks.



66. What are the different database integrities?

· Semantic Integrity.

· Relational Integrity.

· Primary Key Integrity.

· Value Set Integrity.

· Foreign Key integrity and

· Operational integrity.



67. All SAP Databases are Relational Databases.

68. What is SAP locking?

It is a mechanism for defining and applying logical locks to database objects.



69. What does a lock object involve?

The tables.

The lock argument.



70. What are the different kinds of lock modes?

Shared lock

Exclusive lock.

Extended exclusive list.



71. How can a lock object be called in the transaction?

By calling Enqueue and Dequeue in the transaction.



72. What are the events by which we can program “help texts” and display “possible value lists”?

-PROCESS ON HELP-REQUEST (POH).

-PROCESS ON VALUE-REQUEST (POV).



73. What is a matchcode?

A matchcode is an aid to finding records stored in the system whenever an object key is required in an input field but the user only knows other (non-key) information about the object.



74. In what ways we can get the context sensitive F1 help on a field?

- Data element documentation.

- Data element additional text in screen painter.

- Using the process on help request event.



75. What is roll area?

A roll area contains the program’s runtime context. In addition to the runtime stack and other structures, all local variables and any data known to the program are stored here.



76. How does the system handle roll areas for external program components?

- Transactions run in their own roll areas.

- Reports run in their own roll areas.

- Dialog modules run in their own roll areas

- Function modules run in the roll area of their callers.



77. Does the external program run in the same SAP LUW as the caller, or in a separate one?

- Transactions run with a separate SAP LUW

- Reports run with a separate SAP LUW.

- Dialog modules run in the same SAP LUW as the caller

- Function modules run in the same SAP LUW as the caller.

The only exceptions to the above rules are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND TASK (ALE applications). These always run in their own (separate) update transactions.



78. What are function modules?

Function modules are general-purpose library routines that are available system-wide.



79. What are the types of parameters in the function modules?

In general, function module can have four types of parameters:

- EXPORTING: for passing data to the called function.

- IMPORTING: for receiving data returned from the function module.

- TABLES: for passing internal tables only, by reference (that is, by address).

- CHANGING: for passing parameters to and from the function.



80. What is the difference between Leave Transaction and Call Transaction?

In contrast to LEAVE TO TRANSACTION, the CALL TRANSACTION statement causes the system to start a new SAP LUW. This second SAP LUW runs parallel to the SAP LUW for the calling transaction.



81. How can we pass selection and parameter data to a report?

There are three options for passing selection and parameter data to the report.

- Using SUBMIT…WITH

- Using a report variant.

- Using a range table.



82. How to send a report to the printer instead of displaying it on the screen?

We can send a report to the printer instead of diplaying it on the screen. To do this, use the keywords TO SAP-SPOOL:

SUBMIT RSFLFIND…TO SAP-SPOOL DESTINATION ‘LT50’.



83. How can we send data to external programs?

Using SPA/GPA parameters(SAP memory).

Using EXPORT/IMPORT data (ABAP/4 memory)



84. What are SPA/GPA parameters (SAP memory)

SPA/GPA parameters are field values saved globally in memory. There are two ways to use SPA/GPA parmeters:

By setting field attributes in the Screen Painter.

By using the SET PARAMETER or GET PARAMETER statements.