|
Share this post:
|
|
Applying Hot Packages Using OSS --> http://www.zshare.net/download/108784843d8fce82/
|
Share this post:
|
|
Using the paging mechanism lazy page out (removing the pages that are not in the address area of an active process), Windows NT creates permanently free working memory (see Special Features under Windows NT). Therefore, Transaction ST06 displays a very high value for Physical mem free in comparison to Physical mem avail (see the following graphic). Due to a faulty interpretation, the number of work processes is often increased ("There is still unused working memory available").
Instead of using Transaction ST06, you can also use the menu path:
Tools ® CCMS ® Control/Monitoring ® Performance Menu ® Operating System ® Local ® Activity
Compare the chapter Operating System Monitor: Overview from the CCMS documentation.
A higher Physical mem free-value has no bearing on the memory use of the system (no. 9 in the following graphic). Physical mem free in relation to Physical mem avail is by definition very large (see Windows NT: Paging Mechanism Lazy Page Out).
|
Share this post:
|
|
Follow the steps to print SAP R/3 documents using printer attached on Linux PC:-
SAPGUI for Java should be installed on my Linux. We can’t use Frontend Printing (F acces method) since there was no SAPLPD program on it.
The SAPLPD package on SAPGUI for Windows is duplicate Linux’s LPD flow. It is using same architecture and working method. Since Linux already had it LPD (and CUPS), it doesn’t need SAPLPD anymore. You can use LPD (and CUPS) to replace SAPLPD function.
SAPGUI for Java on Linux can use U : Print Using Berkeley Protocol acces method. Fill the Host printer column with name of your printer defined on your Linux PC. Use simple name and no space. On Destination host, fill with IP address of your Linux PC where your printer attached.
After that, open your inetd.conf file and add this at the end of lines.
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpdand you need to restart your inetd daemon or reboot your PC.
If you are using xinetd.conf, please add this at the end of lines.
service printer { socket_type = stream protocol = tcp wait = no user = lp server = /usr/lib/cups/daemon/cups-lpd }Restart your xinetd daemon.
Before you print your SAP R/3 documents, please make sure your LPD (and/or CUPS ) daemon is running well.
|
Share this post:
|
|
Prerequisites
Particular functions of AIX (late swap allocation, disclaim) enable an alternative implementation of the Extended Memory with a size of several GB as of R/3 Release 3.1G kernel. A single user context can still only use approximately 1 GB of Extended Memory, but the sum of usable Extended Memory for all user contexts combined can be much higher.
Since a lot of Extended Memory is provided, you can set a high limit for the shared memory consumption. It is also no longer necessary to assign mainly heap memory in background processes to keep the usage of the Extended Memory low. Heap is particularly small on AIX.
You can also minimize roll memory, which accelerates the context switch (roll-in/out) and the dialog and background processing, for example, with synchronous updating.
Procedure
Recommended parameters in the instance profile:
Parameter | Recommendation | Meaning |
ES/TABLE | SHM_SEGS | Switches to the alternative implementation of the Extended Memory (EM) |
em/max_size_MB | 4096 | Enables maximum 4 GB of Extended Memory; can be larger if needed |
ztta/roll_extension | 500000000 | Limit of approximately 500 MB (2 shared segments) of Extended Memory per user context |
ztta/roll_area | 3000000 | Reduces consumption of roll memory in background processes |
ztta/roll_first | 1 | Reduces consumption of roll memory in dialog processes |
abap/heap_area_nondia | 20000000 (20 MB) | Can be set relatively low, so that a heap bottle neck is avoided in the data segment |
The following parameters should only be changed after consulting with SAP.
Parameter | Default | Meaning |
es/shm_proc_seg_count | 3 | Specifies the number of shared memory segments that are used as shared and privately. |
es/shm_max_priv_segs | 2 | This parameter must be lower by 1 than es/shm_proc_seg_count. (=>2*256 MB is usable) |
es/shm_user_count | 1024 | This describes the maximum number of users in all open sessions. |
es/shm_user_count | This specifies the maximum number of AIX system segments that ESSHM uses. |
|
Share this post:
|
|
You can use Transaction ST02 to check if the buffers from the roll and paging areas are the same size as the paging files. By comparing the values under Max. use, you can check if the buffer size is large enough.
You can determine from the row Extended Memory that the R/3 Extended Memory is sufficiently large. The value Max. use is, in this example, noticeably smaller than the created memory area (In memory). If both values are identical, you must increase the extended memory (profile parameter: em/initial_size_MB).
|
Share this post:
|
|
Keyword: BASIS
Title : Mass user creation using SCAT
|
Share this post:
|
|
Keyword: BASIS
Title : SAP MaxDB - Using Third-Party Backup Tools
|
Share this post:
|
|
Note
You can display documents from any list or statistic (such as Applicants by name and Applications) in which individual applicants are listed.
Procedure
If you want to use applicant lists to display documents stored for an applicant, proceed as follows.
This accesses the Report Tree: Initial Screen.
This takes you to the Display Report Tree
You can also save the Recruitment sub-tree as your initial screen. To do this, place the cursor on Recruitment and choose Edit ® Set focus. Then choose Settings ® Define initial position. The next time you access the report tree for Personnel Management, the Recruitment sub-tree is displayed immediately.
This takes you to the initial screen of the chosen report.
The system displays a list of applicants who meet the selection criteria.
The system displays a list of all documents stored for the applicant.
Result
The system displays the documents for the applicant you selected.
|
Share this post:
|
|
Use
You want to find an applicant number. In this case, you call up the input help in the Applicant number field and execute the appropriate search help. This finds the desired applicant number in the system.
Procedure
The system displays the maintainable fields for the selected search help. Make entries in these fields.
Note that you do not have to make entries in all the fields in the selected search help. You also have the option of making generic (e.g. M*) or masked (e.g. M++er) entries.
Note that for most search helps, you also have the option of restricting the number of values suggested by the system. The system suggests a default value, which you can overwrite.
The system displays a list of values that are assigned to the selected search path.
The system then writes this applicant’s applicant number to the Applicant number field.
Result
You have displayed a value list using search help and have selected the desired applicant. The system has written this applicant number to the Applicant number field.
|
Share this post:
|
|
Use
The search help for applicant numbers allows you to access applicant numbers if you do not know the actual numbers you are looking for. Several search helps are available in the Applicant number field if you use the input help. You choose the desired search help (e.g. Personal data) and enter the relevant data as prompted by the search help. The system selects the relevant data and outputs it in list form. You select the desired applicant from this list. The system then writes this applicant’s applicant number to the Applicant number field.
Prerequisites
Search helps are available via the standard settings. You can use these search helps, or you can customize them to suit the needs of your enterprise.
To find out more about search helps, choose menu path Basic Settings ® Maintain Search Helps in Customizing.
Features
The following search helps are set up for applicant numbers in Recruitment in the standard system:
For more information on matchcodes, see the Basis documentation under Search Helps.
|
Share this post:
|
|
Keyword: SAP HR
Title : Linking Employee Photos using SAP Archive Link
