ERP Software Corner
Tips and Tricks (22)
/n Skip to the next record if you are processing one batch input session
/bend Cancel a batch input foreground process
/nend Close all R/3 sessions and logoff with a dialog prompt
/nxxxx Call the transaction xxxx in the same session
/o Generate a session list
/oxxxx Call the transaction xxxx in an additional session
/i Delete the current session
/h Turn the debug mode on
/Nex Close all R/3 sessions and logoff without a dialog prompt
Special copy and paste
Click on the area and press CTRL+Y. It allows you to copy many lines at once and paste them afterwards.
I may be missing the boat here and simply telling you what you already know but 3 people in my office all experienced the same issue when installed Mercury QC and noone knew what was going on..... Our WINLOGON.INI file was wiped out in the C:\WINDOWS directory.
Well it turns out when you turn off UAC (Windows Vista User Access Control) it takes you to a different place giving you the "opportunity" to create a new SAPLOGON.INI file!!! If you turn UAC back on your old INI file magically reappears. If you want UAC off, because it's a major PAIN and some programs don't work well with it on (Mercury Quality Center is one), then make a copy, turn UAC off and then copy the INI file to the C:\WINDOWS directory and you are good to go.
Can't wait until they sunset Vista !!!
If you are interested in the Where-used list of SAP objects, you need the report SAPRSEUB. This one is able to create the "where used list" for all SAP objects as well.
Normally, the "where used list" for SAP objects is only very limited filled. So, it is typically, that only about 20% of the data is filled. Therefore, the results are not very helpful.
When you want to have a complete overview on cross refereces of the SAP tables and ABAPs, you need to run SAPRSEUB. You should keep in mind, that this needs about 10 GB space in the DB and takes about 2 days to complete.
But then, you really have a perfect tool in order to understand the SAP sources in detail ;-))More information on report SAPRSEUB is available in note 28022.
This SAP Tip courtesy of Raju at help-sap.blogspot
All of us know that R/3 system architecture consists of Presentation Server, Application Server and Database Server. Here I would like to share some details of Application Server.
Application Server basically consists of a DISPATCHER and multiple WORK PROCESSES.
A work process is where individual dialog steps are actually processed and the work is done. Each work process handles one type of request.
Functions of dispatcher:
- Equal distribution of transaction load to the work processes
- Management of buffer areas in main memory
- Integration of the presentation levels
- Organization of communication activities
All requests that come in from presentation servers are directed first to the dispatcher. The dispatcher writes them first to the dispatcher QUEUE. The dispatcher pulls the requests from the queue on a first-in, first-out basis. Each request is then allocated to the first available work process. A work process handles one request at a time.
In order to do any processing for a user's request, work process needs two special memory areas: viz. User Context and Program Roll Area.
User Context is memory area that contains information about the USER.
Program Roll Area is memory area that contains information about the PROGRAMS execution
User Context holds the following information of the User needed by R/3:
- The user's current settings
- The user's authorizations
- The names of the programs the user is currently running
When a user logs on, a User Context is allocated for that logon. When they log off, it is freed.
Roll Area holds the following information of the program:
- The values of the variables
- The dynamic memory allocations
- The current program pointer
Every time a user starts a program, a roll area is created for that instance of the program. If three users run the same program at the same time, three roll areas will exist-one for each user. The roll area is freed when the program ends.
An ABAP/4 program occupies only one work process for one dialog step. At the beginning of the dialog step, the Roll Area and User Context are rolled in to the work process. At the end of the dialog step, they are rolled out.
During the roll-in, pointers to the roll area and user context are populated in the work process. This enables the work process to access the data in those areas and so perform processing for that user and that program. Processing continues until the program sends a screen to the user. At that time, both areas are rolled out. Roll-out invalidates the pointers and disassociates these areas from the work process. That work process is now free to perform processing for other requests. The program is now only occupying memory, and not consuming any CPU. The user is looking at the screen that was sent, and will soon send another request.
When the next request is sent from the user to continue processing, the dispatcher allocates that request to the first available work process. It can be the same or a different work process. The user context and roll area for that program are again rolled in to the work process, and processing resumes from the point at which it was left off. Processing continues until the next screen is shown, or until the program terminates. If another screen is sent, the areas are again rolled out.
When the program terminates, the Roll Area is freed.
The User Context remains allocated until the user logs off.
In a system with many users running many programs, only a few of those programs will be active in work processes at any one time. When they are not occupying a work process, they are rolled out to extended memory and only occupy RAM. This conserves CPU and enables the R/3 system to achieve high transaction throughput.
Components of Work Process:
Each work process has the following components:
All requests pass through the task handler, which then distributes the request to the appropriate part of the work process.
The interpreters interpret the ABAP/4 code. There are two interpreters: the ABAP/4 interpreter and the Screen interpreter. ABAP/4 Interpreter is data processing language and Screen Interpreter is very specialized screen processing language. Each is processed by its own interpreter.
The database interface handles the job of communicating with the database.
Type of Work Processes:
There are seven types of work processes. Each handles specific type of request.
Dialog requests (processes only one request at a time)
V (Update) (Primary and Secondary)
Requests to update data in the database
Background jobs (Starts at a specified time)
Print spool requests (generated online or during back ground processing for printing)
Logical lock requests
Routes messages between application servers within an R/3 system
Funnels messages into and out of the R/3 system
An update request can be divided into one primary (V1) and several Secondary update components (V2). Time-critical operations are placed in V1 component and those whose timing are less critical are placed in V2 components. If a V1 update fails, V2 components will not be processed.
Spool requests are generated during dialog or background processing and placed in the spool database with information about the printer and print format. The actual data is placed in the Tem Se (Temporary Sequential objects).
- If there are three R/3 systems in your current system landscape, then there will be three databases.
- If an R/3 system has two application servers, then it will have three instances. Two for the Application Servers and one for Database server
- A new roll area is allocated whenever a program is executed, and it is de-allocated when the program terminates. The roll area contains the values of the variables for that program and the current program pointer.
- A user context is allocated each time a user logs on, and de-allocated when he or she logs off. It contains information about the user, such as authorizations, profile settings, and TCP/IP address.
- The roll-out occurs at the end of a dialog step. It frees the work process to ready it for other requests, so that the program will not use CPU while waiting for user input.
- BEARBEITEN "Work on",
- ERMITTELN "determine",
- PRUEFEN "examine or check",
- AUFBAUEN "CONSTRUCT",
- LESEN "Vintages",
- GELESEN means "read"
FI T880 Company
T001 Company code
CO TKA01 Controlling area
LO T001W Plant / sales organization
SD TVKO Sales organization / company code
TVTW Distribution channel
TVBUR Sales office
TVKBT Sales office text
TVKGR Sales group
TVGRT Sales group text
T171T Sales district text
MM T001L Storage locations
T024E Purchasing organization
T3001 Warehouse number
TVST Shipping point
TVLA Loading point
CO TKA02 Assign company code to controlling area
LO T001K Assign plant (valuation area) to company code
SD TVKO Sales organization / company code
TVKOV Distribution channel / sales organization
TVKOS Division to sales organization
TVTA Sales aria
TVKBZ Sales office to sales area
TVBVK Sales group to sales office
TVKWZ Plants to sales organization
MM T024E Purchasing organization / company code
T024W Plant to Purchase organization
T001K Link plant ( = valuation area) / company code
TVSWZ Shipping point to plant
T320 Assignment MM Storage Location to WM Warehouse
OneAccess-UserManager also helps you manage the complex documenting, testing, process control, and sign-off requirements mandated by Sarbanes-Oxley sections 302, 404, and 409
Vice President- SAP Practice
OneAccess-UserManager for SAP
SAP Certified-Powered by Netweaver
Phone: 1 877 717 5487
Automate and Meditate
You can add additional menu transaction in the SAP main menu without affecting the original SAP default area menu S000.
For example, you have created a transaction code called ( z123 - ABC Own Report ) and you want to insert it under Logistics. The specific user will be able to access ABC Own Report by clicking Logistics -> ABC Own Report.