Transaction code SM62 is used to create SAP events and as well as for events administration.

Events are used to trigger the jobs in SAP and it is used to manage the dependency across multiple jobs without using process chains. An event by itself doesnt do anything. Normally background job needs to be defined & configured to wait for the event. So, create background job through SM36, specify the new event name as the Start Condition. New background job always can be defined as a periodic job. This allows you to trigger the job in the future as opposed to one time only.

Scenario example: You have job X that needs to be triggered after the completion of job X1. In that case, you can raise an event (E1) at the successful completion of job X1 and use the event (E1) as a start condition for job X. If you have multiple jobs, for e.g job X needs to be triggered after the successful completion of job X1, X2 & X3. In order to model this scenario you need to raise individual events after the completion of X1 (E1), X2 (E2) & X3 (E3). Use an event collector to raise another event (E4) when E1, E2 & E3 are raised. Use event E4 as a start condition for job X. You can resemble event collector with AND process type in a process chain.

SAP Background Processing

 SAP background processing is a method for automating routine tasks and for optimizing the use of your organizations SAP computing resources. In background processing, you instruct the R/3 System to run programs for you. You can use background processing to execute long-running or resource intensive programs at off peak times. You can use it to assign the system the task to execute reports and programs. There is no strain on your dialog resources and reports running in the background are not subject to the runtime restrictions of dialog processing (termination of the program after a runtime of ten minutes). The segregation of background processing to special work processes gives you an additional dimension for separating background processing and interactive work. Normally, background processing and interactive work in the system take place at different times. For example, the system is used interactively during the day and background processing takes place at night. You can use background work processes to separate background processing and interactive work also by servers because background jobs are only executed on servers that offer background processing. The end user can usually schedule the program to be started in the background as a job from the application transaction. The job then waits for the planned execution time in the job scheduling table. If the time has come and free background work processes are available, the job is distributed to a background work process by the background scheduler and then executed. Additional note: To display your own jobs, use transaction code SMX. The system administration and the work preparation have access to a tool for scheduling different types of background takes with transaction SM36. The system-wide monitoring of

jobs takes place with transaction SM37. For cross-system scheduling and monitoring of background tasks, you can use SAP Central Process Scheduling (SAP CPS) and other licensed partner products.

SM28: SAP Initial Inconsistency Check

Transaction code SM28 is to perform check the SAP system installation does not contain errors during the process of installation, which if any needs to be attended. This is one time activity after the installation only.

Note: Transaction code SM28 is same with the transaction code SICK.

SAP: Reset SPAM Queue Status

1. In the SPAM status, you found the SPAM status is in Error stop. You may need to reset the queue to reschedule back the queue.

2. Go to Extras > Reset status > Queue.

3. Click Yes to continue. The status of the queue may now reset which mean that when you import the queue again, the SPAM will start at the first step.

Tags: reset spam queue status

Compare SAP Jobs in SM37

Posted by itsiti on November 8, 2011 in SAP Basis 0 Comment

You can do the comparison between 2 or more jobs that are available in the SAP system. To do this, go to transaction code SM37. On the initial screen, list out the jobs that you wanted to compare (based on day/time). Tick on the selected jobs and go to Job > Compare jobs. You will get this comparison pop up display job tree. The comparison is consists of general job information, job steps and job start condition.

Tags: compare jobs, sap jobs comparison

Install & Configure FTP Server in Windows Server 2003

This step-by-step article describes how to install and configure a File Transfer Protocol (FTP) server for anonymous access.

Install Internet Information Services and the FTP Service

In Windows Server 2003, the FTP Service is not installed by default when you install IIS. If you already installed IIS on the computer, you must use the Add or Remove Programs tool in Control Panel to install the FTP Service. Because FTP depends on Microsoft Internet Information Services (IIS), IIS and the FTP Service must be installed on the computer. To install IIS and the FTP Service, follow these steps. 1. Click Start, point to Control Panel, and then click Add or Remove Programs. Click Add/Remove Windows Components. In the Components list, click Application Server, click Internet Information Services (IIS) (but do not select or clear the check box), and then click Details.

2. Click to select the following check boxes (if they are not already selected): Common Files File Transfer Protocol (FTP) Service Internet Information Services Manager

3. Click to select the check boxes next to any other IIS-related service or subcomponent that you want to install, and then click OK. Click Next and when you are prompted, insert the Windows Server 2003 CD-ROM into the computers CD-ROM or DVD-ROM drive or provide a path to the location of the files, and then click OK. 4. Click Finish. IIS and the FTP service are now installed. You must configure the FTP Service before you can use it.

Configure The FTP Service

To configure the FTP Service to allow only anonymous connections, follow these steps: 1. Start Internet Information Services Manager or open the IIS snap-in. 2. Expand Server_name, where Server_name is the name of the server. 3. Expand FTP Sites 4. Right-click Default FTP Site, and then click Properties. 5. Click the Security Accounts tab. 6. Click to select the Allow Anonymous Connections check box (if it is not already selected), and then click to select the Allow only anonymous connections check box.

When you click to select the Allow only anonymous connections check box, you configure the FTP Service to allow only anonymous connections. Users cannot log on by using user names and passwords. 7. Click the Home Directory tab. 8. Click to select the Read and Log visits check boxes (if they are not already selected), and then click to clear the Write check box (if it is not already cleared). 9. Click OK. 10. Quit Internet Information Services Manager or close the IIS snap-in. The FTP server is now configured to accept incoming FTP requests. Copy or move the files that you want to make available to the FTP publishing folder for access. The default folder is drive:\Inetpub\Ftproot, where drive is the drive on which IIS is installed.

EWZ5: EMU Conversion Lock & Unlock SAP Users

Transaction code EWZ5 is EMU Conversion which used to lock and unlock users. You can select which user to lock and unlock.

Execute OS Commands from SAP GUI

1. Execute SE38 and put RSBDCOS0 in the program field. Click on execute.

2. In this example, i run command to ping www.google.com. As you can see, the result is the same like when you are running on operating system level. You can try to run other commands. Just make sure to check current operating system running so that you are executing the right command.

SGEN: Generate the Objects of a Transport Request

You can use this generation task to regenerate the ABAP load for all objects in a transport request that can be generated. This task does not, however, take ABAP loads into consideration that were invalidated by modified Dictionary objects. To include these loads, choose Regenerate Existing Loads > Generate Objects with Invalidated Load Only. After choosing this task, a screen appears that allows you to search for the name of the transport request using the selection button, or to specify it directly. 1. Execute transaction code SGEN, choose Generate the objects of a transport request.

2. Put the name of request (transport number).

3. Select the server for parallel generation. For a quicker execution, the load generator bases itself on a parallel processed procedure which incorporates available servers as much as possible. The default selection corresponds to the server used for this transaction and to the computers with the same type (MT: machine type). When you change the server selection, the servers you select must have the same machine type.

4. The SAP load generator will running and you can always look the job status and progress to monitor the process.

AL15: SAPOSCOL Destination

Transaction code AL15 is used to manage logical destinations that call up rfcoscol in the SAP system. You need to specify a logical destination and then save it as a saposcol destination using Add Destination. This logical destination can then be used under saposcol remote. The field Database Server specifies whether this destination leads to the SAP Systems database server. The remote saposcol can be used for both dedicated database servers and other non-SAP System servers.

SCC4: Clients Overview

Transaction code SCC4 is used for to define the client. This is a cross-client transaction; any changes made will affect all the clients in the SAP system. This is a controlled transaction which is to be authorized user only.

1. A client has various characteristics that are maintained considering for which purpose the client is used.

2. You can view the details of each client by highlighting the client and click on Display.

Additional note: Client - The transactions that are carried in this client is only accessible for users assigned to this client Logical system Is a value which has dependency in the transactions as it gets tagged with the transaction data, if any change is done then the relevant data will be lost even though exists in the system. Hence making a change of the logical system once defined is not to be done in Production system. Client role Defines for which purpose the client is used for, it can be SAP reference client, Test client, Customizing client, Demo client or Production client.

SAP R/3 History & Release

SAP R/3 is the former name of the main enterprise resource planning software produced by SAP AG. It is an enterprise-wide information system designed to coordinate all the resources,

information, and activities needed to complete business processes such as order fulfillment or billing. History of SAP R/3 The first version of SAPs flagship enterprise software was a financial Accounting system named R/1 called as YSR. This was replaced by R/2 at the end of the 1970s. SAP R/2 was in a mainframe based business application software suite that was very successful in the 1980s and early 1990s. It was particularly popular with large multinational European companies who required soft-real-time business applications, with multi-currency and multi-language capabilities built in. With the advent of distributed clientserver computing SAP AG brought out a clientserver version of the software called SAP R/3 (The R was for Real-time data processing and 3 was for 3-tier). This new architecture is compatible with multiple platforms and operating systems, such as Microsoft Windows or UNIX. This opened up SAP to a whole new customer base. SAP R/3 was officially launched on 6 July 1992. It was renamed SAP ERP and later again renamed ECC (ERP Central Component). SAP came to dominate the large business applications market over the next 10 years. SAP ECC 5.0 ERP is the successor of SAP R/3 4.70. The newest version of the suite is SAP ERP 6.0 Releases SAP R/3 Release 1.0A Release Date 6 July 1992 SAP R/3 Release 4.0B Release Date June 1998 SAP R/3 Release 4.5B Release Date March 1999 SAP R/3 Release 4.6A Release Date 1999 SAP R/3 Release 4.6B Release Date Dec 1999 SAP R/3 Release 4.6C Release Date April 2001 SAP R/3 Enterprise Release 4.70 Release Date March- Dec 2003 SAP R/3 Enterprise Edition 4.7 SAP R/3 Enterprise Central Component 5.0 SAP R/3 Enterprise Central Component 6.0 Organization SAP R/3 was arranged into distinct functional modules, covering the typical functions in place in an organization. The most widely used modules were Financial and Controlling (FICO), Human Resources (HR), Materials Management (MM), Sales & Distribution (SD), and Production Planning (PP). Each module handled specific business tasks on its own, but was linked to the others where applicable. For instance, an invoice from the billing transaction of Sales & Distribution would pass through to accounting, where it will appear in accounts receivable and cost of goods sold. SAP typically focused on best practice methodologies for driving its software processes, but more recently expanded into vertical markets. In these situations, SAP produced specialized modules (referred to as IS or Industry Specific) geared toward a particular market segment, such as utilities or retail.

SM51: SAP Server Overview

Transaction code SM51 is to display list of active application servers that have registered in the SAP message server. Further, you can manage & display the status, users, work process in all application servers belonging to the SAP System.

Processes: Display & control work process. [SM50] User: Display & manage user sessions. [SM04] SNC Status: Display SNC status. Release Notes: Display detailed release information for an application server. 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. [SM21]

AL08: List of All Users Logged On

Transaction code AL08 shows the list of all the users who are logged on to the system globally or for all the instances in the system which are active.

Active instance Shows the Active instance. Active users Displays the active users logged on to the active instance. Interactive users Displays the Dialog users logged on to the active instance. RFC users Display the users that are connected via RFC on the active instance. Mand Client number. User User name of users logged on. Terminal From which Terminal/machine user has logged on. T-code Last executed transaction code. Time The time when a user last initiated a dialog step by entering data. External Sessions Number of External sessions the user has opened. It use SAP memory to share data between external sessions and it based on per main window. An external session is started when starting a program and when ever the use of CALL TRANSACTION. Each user

can open maximum 6 SAP system windows in a single SAPGUI session. Each of these windows corresponds to a session on the application server with its own area of shared memory. The session can be created by System -> Create Session. Internal Sessions Number of Internal sessions the user has opened. A session that with in external session. There can be many internal sessions in an external session. ABAP MEMORY is used to exchange the data between internal sessions. When calling a program using SUBMIT or CALL Transaction, it will be loaded in a new internal session.

SE06: Processing after Installation of CTO

Transaction code SE06 has to be executed once in every newly installed R/3 System. This applies to an R/3 standard installation as well as the installation of a copy of an existing R/3 system. SE06 provides the following functions for processing after installation: Generating basic settings of the Change & Transport Organizer. Closing other requests & tasks. Setting the system change option.

Standard installation

The system was installed from the SAP CD using R3setup. It is assumed that the system is running on a correct, delivered version of the R/3 System. No adjustments based on corrections or repairs have been made.

Database copy / database migration

The system was created on the basis of a copy. R3setup provides utilities to do this. The system needs to be assigned a new and independent role within the SAP system group or outside of it.

Read more: http://itsiti.com/se06-processing-after-installation-of-cto#ixzz1fKAKDOWI

Start & Stop SAPOSCOL in SAP

Run T-Code ST06 -> Operating System Collector.

To stop

To start

Check status

Tags: saposcol

Read more: http://itsiti.com/start-stop-saposcol-in-sap#ixzz1fKAjudJO

SAP: Lock & Unlock User From CUA

1. To lock or unlock a user from CUA, you need to login to the CUA system and execute transaction code SU01. Click on the LOCK icon.

2. From the prompted box, you can choose to lock or unlock the system globally or in local only.

SUGR: Maintain User Groups

Transaction code SUGR is used to create and maintain user groups in SAP system. The user groups commonly used to to categorize user into a common denominator, sort users into logical groups and allow segregation of user maintenance, this is especially useful in a large organization. User groups can categorized as two types, Authorization user group : In conjunction with S_USER_GROUP authorization object. It allows to create security management authorization by user group. e.g. you can have a local security administrator only able to manage users in his groups, Help-Desk to reset password for all users except users in some group. General user group : In conjunction with SUIM and SU10, to select all the users in a specific group. User can only be member of one authorization user group but several general user group.

SE73: SAPscript Font Maintenance

In SE73 tansaction, there are 6 menus to manage fonts: Font families - You may create a font family either by using this menu, or by installing a TrueType font. - List of fonts are shown in 2 colors, Blue: represent non-TrueType fonts and Yellow: represent TrueType fonts. The font family description also have 4 last characters equal to regular expression [_N][_B][_I][_X] which indicates what styles are installed, where: N = normal, B = bold, I = italic, X = bold + italic. For example Arial N_I_ means that the family font is a true type font with normal and italic, but there is neither bold nor bold + italic. Arial NBIX contains all styles. System fonts - Font conversion: for the selected system font, and for each device type, SAP determines and displays the printer font that will be used for printing.

 Printer fonts - List of device types - Generate Font: you must select one device type, all fonts are checked - Check Print Controls: you must select one device type, SAP displays values of printer controls used for each printer font defined for this device type - Font size: it indicates the size in decipoints (120 means 12 points). It must be 0 if you define a proportional font. System Bar Codes Printer Bar Codes Install a TrueType font - Creates a font family based on a TTF file. The same may also be achieved using RSTXSF01 program (exactly the same as the SE73 option) and RSTXPDF2 program by selecting options Read and save font file and Install global softfont.

SM12: Lock Concept

The SAP System is equipped with a special lock mechanism that synchronizes access to data on the database. The purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneously. Lock entries are usually set and deleted automatically when user programs access a data object & release it again. The lock mechanism is closely related to the Update Mechanism. 1. You can use SM12 to check and delete lock entries.

2. In SM12, check any lock entry older > 2 days. If any outdated entry found, check the corresponding user is user online/offline in AL08. Get the user contact from SU01 and inform about the lock else if the user is offline, release the table from lock by deleting the lock.

Additional note: Important profile parameters for the lock concept: enque/table_size Size of the lock table managed by the enqueue server in the main memory. The lock table contains information on which locks are currently held by whom. You can check whether the update server is functioning correctly, since the lock table can grow very fast if the update function stops. If no update problems exist, you can use this parameter to increase the size of the lock table. Default value: 4096Kb rdisp/wp_no_enq Number of enqueue work processes that are to run on this instance. rdisp/enqname Name of the application server that provides the enqueue service. The lock mode: Shared Lock (S) Several users can access locked data at the same time in display mode. Requests from further shared locks are accepted, even if they are from different users. An exclusive lock set on an object that already has a shared lock will be rejected. Exclusive (E) An exclusive lock protects the locked object against all types of locks from other transactions. Only the same lock owner can reset the lock .

Define & Setup SAP Logical System

You perform this cross-client procedure only in one SAP System and transport this table to all other SAP Systems connected to the CUA. Alternatively, you can define the logical systems for each SAP System by performing the following procedure in every SAP System for the logical systems there. 1. Run transaction code BD54. Click on pencil icon to covert from display to change view. Then, click on New Entries.

2. Use the following naming convention for the logical system names, <System ID>CLNT<Client>. Save your entries, which are included in a transport request. Create the logical system name for the central system in all child systems.

SE41: Menu Painter

The transaction code SE41: Menu Painter is a tool with which you design user interfaces for your ABAP programs. ABAP programs contain a wide variety of functions, which fall into different categories within the user interface. It is important for users to be able to differentiate between these categories, and to choose the right function easily. In the SAP System, you can arrange functions using the Menu Painter.

AL11: SAP Directories

Posted by itsiti on January 23, 2011 in SAP Basis 1 Comment Updated on Aug 16, 2011

1. Transaction code AL11 is used to display all the SAP Directories. We can access the different file systems that have been defined and attached to a Parameter. In this transaction we can view a file, find files under a directory. Few important directory parameters are DIR_CT_RUN, DIR_DB2_HOME, DIR_DATA, DIR_EXECUTABLE, DIR_TRANS.

2. When you double click on a directory, you will see all the files in the directory. Using the directory parameters in the profile or in program, we can call a file from the OS level in SAPGUI on the user PC/Laptop.

SM13: Update Request

Transaction code SM13 is a update management transaction which is used for: Display update requests Analyze problems pertaining to the update Test and debug canceled update requests Display and reset the status of update requests Delete update requests Display statistics on updates

Disable Transport All in STMS

1. Logon to Transport Domain controller and run transaction STMS. Go to Overview -> Systems. Choose the system to be disable import all.

2. Under Transport Tool tab, add/create Parameter NO_IMPORT_ALL set its value to 1.

3. The BIG LORRY or Transport All option will not be listed.

Tags: stms, transport all disable

Read more: http://itsiti.com/disable-transport-all-in-stms#ixzz1fKEFbrsc

Reset SAP TMSADM User

Posted by itsiti on June 30, 2011 in SAP Basis 0 Comment

If you want to reset user TMSADM to the default, or if the configuration of this user was damaged, then: 1. Log on to the SAP system where you want to reset the TMSADM user. Call transaction STMS. Choose Overview > Systems. The system overview appears. Choose Extras > Reset User TMSADM. The system user TMSADM is regenerated with the default authorizations.

SM62: Event Creation & Administration

Transaction code SM62 is used to create SAP events and as well as for events administration. Events are used to trigger the jobs in SAP and it is used to manage the dependency across multiple jobs without using process chains. An event by itself doesnt do anything. Normally background job needs to be defined & configured to wait for the event. So, create background job through SM36, specify the new event name as the Start Condition. New background job always can be defined as a periodic job. This allows you to trigger the job in the future as opposed to one time only.

Scenario example: You have job X that needs to be triggered after the completion of job X1. In that case, you can raise an event (E1) at the successful completion of job X1 and use the event (E1) as a start condition for job X. If you have multiple jobs, for e.g job X needs to be triggered after the successful completion of job X1, X2 & X3. In order to model this scenario you need to raise individual events after the completion of X1 (E1), X2 (E2) & X3 (E3). Use an event collector to raise another event (E4) when E1, E2 & E3 are raised. Use event E4 as a start condition for job X. You can resemble event collector with AND process type in a process chain. Source: http://forums.sdn.sap.com/thread.jspa?threadID=377630

SDMO: Search SAP Transaction Codes

1. Execute transaction code SDMO. For an example, you want to search for backup transaction code. So, type backup on the search field and execute.

2. From the search result, you can see the list of transaction code that related to backup. So, from here, you can pickup any transaction code!

SMMS: SAP Message Server Monitor

You can use the message server monitor to closely monitor the functioning of the message server. The initial screen is identical to the SAP Application Server Overview (SM51). All SAP

servers that have logged on to the message server are displayed. To monitor the message server, you can use the Message Server Monitor (transaction SMMS) in the SAP System. You can check and change all the important settings, create and view traces, read statistics, and so on.

Prerequisites
You are logged onto the SAP system, and the message server is running.

Features
The menu option Goto contains all of the functions of the message server monitor.

Display Details
To view detailed information about the client on which the cursor is positioned, choose Goto > Display details.

Information about the Release

To view detailed information about the release of the message server, choose Goto > Release Notes. The release notes provide information on the version of the SAP Message Server, and on the release and Support Package level of the SAP kernel. Kernel information tells you the release of the SAP kernel. Besides kernel release and compile information, this screen provides the following information: Update level specifies with which kernel releases the kernel can run in an SAP System. If different application servers are to run with different kernel patch levels in one system, they must all have the same update level. Patch number specifies the last Support Package level that is relevant for the component

message server. Source ID indicates the actual kernel patch level (the number after the full stop).

Hardware Key
You can display the hardware key of your SAP system, which you need to install the SAP license, by choosing Goto > Hardware Keys.

Parameters
You can view all the parameters associated with the Message server by choosing Goto > Parameters > Display. Some of these parameters can be changed dynamically while the system is running; to do this, choose Goto > Parameter > Change. You can display the RZ11 documentation for every parameter. To do this, place your cursor on the parameter name and choose Documentation.

Statistics
You can activate, display, deactivate, or reset Message server statistics. To do this, choose Goto > Statistics. The statistics include information on, among other things, the number of logins, requests received, bytes written and read.

Trace
You can access the following functions of the message server trace by choosing Goto > Trace: Display trace file (dev_ms) Reset trace file Increase or decrease trace level

Services
To display the open ports on the message server choose Goto > Services. On these ports you can access the message server, if you want to Monitor the Message Server from the Browser.

Logon Data
You can display the logon data for the individual SAP application servers that are currently logged on to the message server. To do so, select a server and choose Goto > Logon data > Display. The number of dialog work processes (in the dialog mode) that the message server needs for load distribution is displayed under Additional data. The relevant dispatcher sends this data to the message server when the server is started.

Expert Functions
These functions are required for analysis performed by SAP, and are not described further here. Exceptions to this are the server functions Shut Down Server (Hard), Shut Down Server (Soft,) Terminate connection, Deactivate and Activate. These functions control the state of the application server.