Académique Documents
Professionnel Documents
Culture Documents
4 Changing the default password for sap* user .......................................................................................6 Mass Maintenance of Users Profiles ....................................................................................................7 How can I create multiple User Id at Random .....................................................................................7 How to delete expired roles? ................................................................................................................8 What are user groups and how can we use them? .............................................................................10 Hide the User Menu ...........................................................................................................................10 Function and Role of User Types and DDIC User .............................................................................11 Transports and Upgrade..........................................................................................12 Meaning behind those unconditional tp command mode ...................................................................12 Transport guide Tips for Different SAP Objects ................................................................................13 Transport Request within same Server Different Clients ...................................................................15 Upgrade SAP or Installation of SAP R/3 and ECC ............................................................................17 SAP Message : TP_CANNOT_CONNECT_SYSTEM .....................................................................19 Restrict The Transport Access In Production .....................................................................................21 Basis - Changing Parameters for the Transport Control Program ......................................................22 Find transports imported into system by search criteria .....................................................................23 Transporting a Request From OS .......................................................................................................23 Find Your SAP Transport Request Number Even If You Forgot ......................................................24 Comparing SAP Objects .....................................................................................................................24 Comparing two SAP clients ...............................................................................................................24 Information on how the OPS$ Users Work ........................................................................................25 How To Do the TMS Configuration? .................................................................................................27 Where To Find Deleted Transport Request Logs ...............................................................................28 Statistics...................................................................................................................29 Statistics of SAP Application Modules ..............................................................................................29 Statistical Logs for all the R/3 System ...............................................................................................30 Finding the SAP Statistics for transactions and programs .................................................................31 List of Inactive Users Logs .................................................................................................................31 Incorrect SAP login logs ....................................................................................................................32 How to Find How Much Allocated Memory .....................................................................................32 What is the Maximum Memory a good Program Should Request .....................................................33 Archiving.....................................................................................................................34 Archiving and Reorganization are totally different issues .................................................................34 Archiving the Material Master ...........................................................................................................35 Deletion of Vendor Consignment Records .........................................................................................36 Reasons For Archiving Financial Accounting Data ...........................................................................37 System Audit....................................................................................................................38 The Step required to Audit at the User Level......................................................................................38 Audit of SAP multiple logons ............................................................................................................39 SAP Security and Authorization Concepts .........................................................................................39 SAP Performance Tuning.........................................................................................42 SAP Load Balancing and Work Processes Troubleshoot ...................................................................42 Tuning Summary In Transaction ST02 ..............................................................................................44 Troubleshooting SAP Performance Issues .........................................................................................44 Administration..........................................................................................................45 SAP Administrator Daily Activities ...................................................................................................45
Tcodes used for Daily System Monitoring .........................................................................................46 Monitor and Administrate 4 SAP Systems .........................................................................................47 Brief Description About SAP Basis Implementation .........................................................................48 Message......................................................................................................................48 Basis - Message Class - System Message ..........................................................................................48 Solution Manager......................................................................................................49 What Is The Use of Solution Manager ...............................................................................................49 Email.................................................................................................................................50 How to test the sending of documents from R/3 applications via fax, paging or Internet mail? .......50 Creating a SAP mail distribution lists ................................................................................................53 Configuring eMail in Case of Alert ....................................................................................................54 e-Mail The Back Ground Jobs ............................................................................................................55 Unicode....................................................................................................................56 Whether a System is Unicode or non-Unicode ..................................................................................56 Network..................................................................................................................57 Bandwidth requirement of ISP to connect to SAP server through VPN ............................................57 See from which network IP address and host name a user has logged on .........................................58 No System name and transaction code in SM04 ................................................................................58 Jobs............................................................................................................................59 Suspend/UnSuspend Released ABAP Jobs ........................................................................................59 What Is The Job Name EU_REORG Meant? ....................................................................................59 Tables..........................................................................................................................60 Reorganization of Single Object ........................................................................................................60 How to activate the IMG Change Log? ..............................................................................................60 Basis - Edit, create, delete or adjust your database table ....................................................................62 Finding any of the SAP tables that have been changed ......................................................................62 Transport Tables between Clients ......................................................................................................62 Copying table entries from client 000 ................................................................................................63 SAP Transaction Table .......................................................................................................................63 SAP Tablespace sizes in large databases ............................................................................................63 Authorization Objects.....................................................................................................66 Printing and Fax......................................................................................................70 Mass Lock All Printers with SPAD ....................................................................................................70 Print to an USB printer from SAP .....................................................................................................71 Parallel printing to all the SAP device printers ..................................................................................71 How can I print A3 format in SAP .....................................................................................................72 Delete multiple spool request .............................................................................................................74 Auto convert SAP spool output to PDF file .......................................................................................74 Printing ABAP Report over LAN and WAN .....................................................................................75 Sending faxes from SAP ....................................................................................................................76 OSS.............................................................................................................................76 Apply OSS Notes On My SAP R/3 System .......................................................................................76 Manually Applying OSS note on SAP Standard Program .................................................................78 SPAU and SPDD ................................................................................................................................79 SAP Transaction code to pre-compile all system program ................................................................80 Transaction Codes...................................................................................................80 Changing the Title of SAP Transaction ..............................................................................................80 Basis Frequently Asked Question...................................................................................81 Interview Questions for SAP Basis ....................................................................................................81
SAP Administration Questions Answers ............................................................................................83 Basis Administration Questions Answers ..........................................................................................85
I want to lock all the users in SAP during MTP. I know using SU10 we can do it. Any other alternative ways to lock the users. Is there a way in SAP to unlock a locked user for a limited time, then automatically after x time set the user back to lock status? You can fill in "valid from" and "valid until", but you cannot say from Monday to Friday from 8 12:00 for part time workers. Can we schedule to lock all users? If users get locked, from SU01 you can unlock them. Use SU10 to mass lock/unlock the users. Use address data or authorisation data to get a list of users - select the ones you want and click transfer. Once this is done click on lock or unlock. You can also use transaction code EWZ5 to mass lock/unlock the users or Execute program EWULKUSR in SE38 or Set a profile parameter (login/failed_user_auto_unlock) to unlock at midnight the locked users. or Here's an ABAP code, short and simple, isn't it? REPORT zreusrlock.
DATA: time_limit TYPE sy-datum. DATA: days TYPE i VALUE 40. time_limit = sy-datum - days. UPDATE usr02 SET uflag = 64 WHERE trdat < time_limit. If you don't want to specify the time in the program, you can use SE38 to schedule it as a daily background job with the date and time. or Probably the easiest way would be to write a sqlplus SQL script that sets all the UFLAG fields in table USR02 to 64 EXCEPT for the BNAMEs you don't want locked. When you are done, you can do the same again but change the UFLAG field to 0. The SQL statement would look like: update SAPR3.USR02 set UFLAG = 64 where MANDT = <client number> and BNAME != <don't lock user 1> AND BNAME != <don't lock user 2>; You can replace != with <> if you want. To run this from an OS command line, you would type: Unix/Oracle 8---> sqlplus internal @<SQLpath+SQLname> NT/Oracle 8.0---> plus80 internal @<SQLpath+SQLname> NT/Oracle 8.1---> sqlplus internal @s<SQLpath+SQLname> Unix/Oracle 9:--> sqlplus /nolog @<SQLpath+SQLname> NT/Oracle 9-----> sqlplus /nolog @<SQLpath+SQLname> In UNIX you can cron the script to schedule it. In NT you can schedule it as a task. or This is another method to UNLOCK ALL users. Start Oracle Server manager (I assume you are on Oracle) connect internal update sapr3.usr02 set uflag='0' where mandt='399'; When users are locked, the uflag is set to 64. Finish, just query to check. select bname, uflag from sapr3.usr02 where mandt='399'; Please note that unlocking users from low level (like Oracle sqlplus) should be used as last resort. Frequent use of low level access may tempt you to use on other things. Highly dangerous and your IS auditors will not be too happy.
Is there a way to set a list of users that cannot be locked, even if we try to lock them manually, and even if they fail connection ( wrong password )? Increase this parameter in SAP Instance profile: login/fails_to_user_lock = 6 (max is 99 wrong attempts, i.e, value 99). Currently you have a value of 3. login/failed_user_auto_unlock (for your midnight unlocking). Ask users to remember passwords!! If someone is deliberately login-in with different username/password (thereby blocking legitimate access of that user), check hostname from SM21.
There is also a profile parameter which can override the use of SAP* with PASS to close this security hole in SAP (login/no_automatic_user_sapstar). When this parameter is defined either in your DEFAULT.PFL profile or the instance-specific profile and is set to a value of '1', then the automatic use of SAP* is deactivated. The only way to reactivate the kernel-defined SAP* userid at this point would be to stop SAP, change this parameter to a value of 0 (zero), and then restart SAP. The default password for SAP* is 06071992. (DDIC has 19920706)
Note - I noticed you said the profiles are all the same. Then this is much easier...no need to enter the roles/profiles, just duplicate this ID and change the name, dept and password only. Okay..first stage has finished. Then double click the Object to begin inserting parameters. Then you will see an object for each fields that you run from SU01. Choose the right field example user id (BNAME) and choose button 'Insert Import Parameter (F6)' and you may click Next Screen to 'watch' what have been recorded and proceed to choose several other objects like password field (PASSWORD1, PASSWORD2), roles field (AGR_NAME), group field etc. If you happen to choose the wrong object, then you can reset back (Edit -> Reset Parameterization). You may see so many junk fields captured and this is because SCAT records every steps/dialogs. Once done, choose Back and save this case. Then you need to click 'Goto -> Variant -> Export' and save it. After that use Ms Excel to open it and begin inserting all other user ids. Save and close. Remember to close this file because SCAT will use it. Then last one, get back to SCAT and click button execute, processing mode chose Background, choose external file 'the one you created with Excel' and execute. At this moment don't use tcode SU01 bcoz you may interrupt the simulation. Wait for the logs. If you see reds then error was happening.
6. Now highlight the user. 7. Click on the pencil button. 8. Click on the Activity Groups tab. 9. Enter the profile name (PM_NOTIFICATION_PROCESSOR). 10. Enter the valid from and valid to dates (04/08/2002). 11. Change the radio buttons to remove user from both the Activity Group and Profile Tabs. 12. Click on the trash can. In another customer message the following was provided by developement: We don't have a regular functionality for mass deletion of roles. But if you want to avoid the deletion by hand or with an own created report, I would suggest the following: The attached note 324962 includes the report ZDELETE_RY_T_AGRS which could delete all roles with names like 'T_....' or 'RY....'. The report gives you a list of all these roles and deletes then the selected ones. You can modify the report to get all your roles in the selection list. Therefore you have to change the following: SELECT * FROM AGR_FLAGS INTO TABLE L_AGR_FLAGS WHERE FLAG_TYPE = 'COLL_AGR' AND FLAG_VALUE = 'X'. SORT L_AGR_FLAGS BY AGR_NAME. LOOP AT SINGLE_ACTGROUPS WHERE AGR_NAME+11 <> SPACE AND <<< delete ( AGR_NAME(2) = 'T_' OR AGR_NAME(2) = 'RY' ). <<< delete LOOP AT SINGLE_ACTGROUPS WHERE AGR_NAME+11 <> SPACE. <<< insert READ TABLE L_AGR_FLAGS WITH KEY AGR_NAME = SINGLE_ACTGROUPSAGR_NAME BINARY SEARCH. Text from an additional customer message as further help: - go on role tab - select remove from user - enter ZR.PRD.GENERIC and date : 06/04/2002 12/31/9999 - go to profile tab - select remove from user - save - do the same for ZR:HR:ESS from 01/01/2002 to 12/31/9999 and worked from date for testid was 01/01/2002 and testid2 02/01/2002 and the 2 assignement were deleted And the roles were removed from the 2 UMR. So it works as designed.
To put it simple, when the user logs on to the system he should have only the SAP Standard Menu. You have two ways to control this : 1. Default hide for all the SAP users. Goto SM30 and edit the table SSM_CUST and set ALL_USER_MENUS_OFF = YES and transport the same in production server. or 2. Hide based on individual SAP users. You can also try SM30 and maintain table USERS_SSM for individual users.
Users are allowed to change password through some software in middle tier. Usage: - These are used for login to system through external systems like web application 4. Service For this kind of users:GUI login is possible. Initial password and expiration of password are not checked. Multiple logins are allowed. Users are not allowed to change the password. Only admin can change the password Usage:- These are used for anonymous users. This type of users should be given minimum authorization. 5. Reference For this kind of users:GUI login is not able. Initial password and expiration of password are not checked. Usage:- These are special kind of users which are used to give authorization to other users. Tips by : Rajeev Sharma What are the functions of DDIC user in Production system? There are many functions of DDIC user. For E.g.. When you configure TMS you won't be able to configure it using sap*. For this you need a user who has access to Data dictionary and ABAP repository Object like DDIC user or user with sap_all and sap_new permission. 2) When we install R/3 in Landscape then we need to configure TMS. With the help of default user DDIC we can configure s_trnsprt and s_cts_admin. We cannot create new user for our client( Client of Company ) as creating new user gets charged.
tp import transportrequest <sid> clientxxx U126 tp import transportrequest <sid> clientxxx U148 The u stands for unconditional force ( how hard you want to force the request into the system - do you want to overwrite without warnings, or softly try to load the objects). 0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location. 1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again. 2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals. 3: When used with tp import, it overwrites the system-dependant objects. 5: During the import to the consolidation system it permits the source systems other than the integration system. 6: When used in import phase, it helps to overwrite objects in unconfirmed repairs. 8: During import phase it ignores the limitations caused by the table classification. 9: During import it ignores that the system is locked for this kind of transport. u128 is combination of 128 OF THE above points.
1.1 Export/import This method gives you the opportunity to select the subprojects or objects you want to transfer. Hence you don't transfer the object a colleague might have created and that should stay in development system. LSMW -> Extras -> Export project 1.2 Transport request With this method, you can transport a LSMW project in full (you can not select the objects you want). With this method, the project will be transported as any other SAP object in a transport order. LSMW -> Extras -> Create change request
2 Program variants If you have several program variants in a development system that you want to transport, use the following method to transport them: Execute program RSTRANSP (via se38) and inform the program and/or variant names (you can transport variant of several programs in one shot). 3 Layout In some transactions, one can save layout of the screen (sort, filter, ... criteria). These layouts can be transported: In the required transaction, when your layouts have been saved, go to Settings -> Layout -> Layout Management. Select the desired layouts and go to Layout -> Transport There you can add your layouts in existing TO or create a new one. DB data In some unusual cases, you might have to transport data of a SAP table. Go to transaction SE16, select your entries and go to Table entry -> Transport entries. It's only possible for some tables... If you cannot do it that way, you have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list. Go in modification mode and add a new line with: PgmID = R3TR Obj = TABU Object name = Name of your table Double-click on the created line and, depending on your need, put '*' in the key field or double-click on it and select the key you need to transport. 4 Queries Queries, datasets and user groups can be exported/imported between the systems thanks to the program RSAQR3TR. 5 Standard texts Standard texts used in SAPScript (created with transaction SO10) can be included in transport orders. You have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list. Go in modification mode and add a new line with: PgmID = R3TR Obj = TEXT Object name = TEXT,,ST, Example : R3TR / TEXT / TEXT,YMM_MEDRUCK_MAIN_16_EC,ST,F You can also copy a Sapscript object (like standard text) with the program RSTXCPFS. How to transfer a executable report from dev server to prd server? And that report contains one user defined view. I want to transfer *the report and the view* from dev to prd.
At the time of creating the report itself it will ask you to select the PACKAGE. Here you should select the package instead of $TMP package, which for transporting the objects and create a new request and save it. If you want to give a TCode for the program that you have created just give SE93 in the GUI Window and give the TCode name there and enter the Create button. there you should give the name of the object or program that you have created and save it. After completing this go to SE09 TCode and select the MODIFIABLE Check box and press DISPLAY Button. In the next screen you have to select the Request that you have created and click the check syntax icon. If no errors are there then you can press the Release Directy icon to transport the request to the Quality system. From there it has to be transported to the Production System.
In other words, when you release a change request in DEV Client 0XX it will not only automatically be added to the Import Queue for QAS but also 0X1, 0X2, of DEV. To set this up requires the steps below: 1) Open the file TP_DOMAIN_DEV.PFL (located on your transport domain controller such as the DEV box. The file will be in usrsaptrans/bin) Edit with notepad for each parameter on each system: DEV/CTC = 0 Change to =1 2) Next you need to create Target Group before creating the transport route. Create a Target Group: Access the initial screen of the graphical or the hierarchical editor in change mode. STMS > Overview > Transport Routes (the default editor will appear, either Hierarchical or Graphical, to change the default editor : STMS > Extras > Settings > Transport Routes. You can also switch to one or the other from Goto > Graphical Editor.) > Configuration > Display Change > (or change icon or F5) Edit > Transport Target Groups > Create In the dialog box, Create Target Group: Enter a name for the target group /GR_QA/ (The name must begin and end with a forward slash /) ...and a description Targets for Consolidation route Choose "Insert line" Enter the required target system/client combinations Use a separate line for each client. Example: Target System Target Client Client Name DEV 0X1 Sandbox DEV 0X2 Testing
QAS 0XX Quality Assurance System The idea is that we want to include the clients that will get an addition to their import queue when we release a change request from DEV. Choose Transfer Now you have to change the transport route to include the Target Group you created. STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Delete Now create a Transport Route with Extented Transport Control: STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Create > Extended Transport Control icon at lower left of dialog box. > Consolidation route, enter integration system and transport layer. In Target system/client enter the SID of either an R/3 System and a client or an existing Target Group. Each System must be specified by System and Client. The Target Group can be used for the consolidation system. Distribute and activate the changes as usual by choosing Configuration > Distribute and activate NOTE: After you set up Extended Transport Control there might be requests in an import queue that will show a red status in the CTL column. This is because these change requests need a client specified before they can be imported. These are old requests that were already in the queue. From Import Queue Screen Mark the change request Choose Request > Target Client > Set Enter the Target Client ID and choose Enter. To change a target client before starting an import: Import Queue Screen > mark Change request > target client > change > enter target client id and choose enter.
installation. Upgrade to 4.7 Have you gone through an upgrade to 4.7? What are the difference or changes associated with 4.7. If you are currently on 4.6C and are inching forward to upgrading to 4.7 then this information might be useful to you. There is very little difference between 4.6 and 4.7, the only "steps" you should need are steps in SU25 ( skip step 1) Then go through all your role and perform a merge old new to bring in the new authorization objects Just to forewarn you of a potential problem which have been encounter at the point of writing. After updating/ modifying roles in step 2C, when going back into 2C to make sure all roles are now green, 70% have gone back to red! The maintenance done is ok, but there seems to be a problem while trying to go back into the roles again to re-generate. SAP recognizes them as needing "adjustment", so you cannot pick them up in mass generate in PFCG as they do not come in, even though the authorizations tab is red. This problem is currently with SAP and it is confirmed that nothing have been done wrongly. Generally, the work is quite manageable in the upgrade, but don't be surprised at how big the upgrade is when compared to upgrading from 46b to 46c. If we have full software of 46c and 47E is it possible to upgrade 46c to 47E or there is a seperate 47E upgrade software need to be requested from SAP? Where I can get the document with upgrade steps on the service market place? It is of course possible and supported: http://service.sap.com/inguides --> SAP Components --> SAP R/3 Enterprise --> (choose your version) at the bottom there is an "Upgrade guide" for Windows and Unix. For Upgrades it is recommended to read ALL the notes mentioned in the upgrade guide and to make sure one is using
- the correct version of the "tp" program - the correct version of the "R3trans" program - the correct version of the "R3up" program All that is explained in the upgrade guide and in the corresponding notes. If this is your first upgrade you should take a person, that has some experience on doing that for the first time. Installation of SAP R/3 Currently we are going to install SAP on a new IBM server from the existing COMPAQ server. Where can I get the steps for that. Configuration is : OS - windows 2003 server DB - Oracle 9i SAP 4.7 http://service.sap.com/instguides --> SAP Components --> SAP R/3 Enterprise --> SAP R/3 Enterprise Core 4.70 / Ext. Set 2.00 (SR1) --> Inst. Guide - R/3 Enterprise 4.7 x 2.00 SR1 on Win: Oracle The above url is the SAP Service Marketplace with all the information you need to install, configure and run system. You need to be a valid licensed customer with a user ID and PASSWORD to use that. Without access you won't be able to successfully run any SAP systems because it has notes, patches etc.
I get this message in QAS:"SAP system is waiting for the inclus. in transport domain" When trying to update the config from DEV client 000, I get this message:System DEV is unknown in the Transport Management System Diagnosis An error occurred in the TMS communication layer. System: QAS.DOMAIN_DEV(000) Function: TMS_CI_CHECK_ACCESSTOKEN Error: UNKNOWN_SYSTEM (DEV) System Response The function terminates. Procedure Log this system on to the Transport Management System. If this error occurs in the function TMS_CI_CHECK_ACCESSTOKEN, then the TMS configuration was deleted in the R/3 System QAS.DOMAIN_DEV(000). Configure the TMS in this R/3 System again. You need to: 1. logon to the transport domain controller with admin user in client 000. 2. Run STMS 3. System overview 4. select QAS 5. Menu line option "SAP system" --> "Approve" 6. Distribute configuration When you are logged on the transport domain server and run STMS --> System Overview. Is QAS listed? If so, select it and perform the checks under "SAP Systems" in menu line. If they are not successful you might want to try the following to configure the TMS on QAS from scratch. First delete QAS from system overview on the domain server. Then do the following steps... In your QAS system in client 000. Run tcode SE06 --> Database copy or Database migration --> Perform post-installation actions. Then confirm that you want to delete all old CTS/TMS config and type in QAS as source system for the database copy.
Then run STMS again and type in the correct data for the transport domain controller. Logon to the transport domain controller in client 000. Run STMS. Open system overview. Choose the SID of the QAS system and click on "SAP System" in the menu and choose Approve. This will add the QAS system to your TMS config again. Perform the checks from menu line "SAP Systems" again.
What is Role Transportation from development server to Production server. I have also create New role, but how to bring out the role to production server. We have installed IDES 4.7 Server. In Development: Run TCD PFCG - Enter the Role to be transported in the text box. - Click on truck symbol left corner of options bar - then series of screens will appear. - In one of the screen don't select user assignment. It will also ask you the change request no. After that go to TCD SE10 and release the request. NOW go to stms and select Quality system and import the request into it. After testing you can import the request in PRD system
To change a global parameter to a local parameter, you must delete the global parameter and enter the new local parameter. The operating system is only displayed if values exist for this field. Finally to remove the import all request (big truck) button from STMS
click the Insert Line (button) Tick Global Fill in Parameter = NO_IMPORT_ALL, Value = 1.
Save your entries. If you enter a parameter unknown to the transport control program, or a value that is not permitted, the transport control program ignores this entry in the transport profile.
Version(s) in the version database: X 00002 X 00001 S 46X X 46X ABCD123456 01.08.9999 15:52:43 SAP 00.00.0000 00:00:00
To compare objects, start the Customizing Cross-System Viewer in the logon client (client of the system in which you are logged on) and then logon in the compare client (client to be compared). The Customizing Cross-System Viewer compares Customizing objects by the following criteria: - Project IMG This option shows changes in your project. - Application components This option compares Customizing objects in specified application areas. - Business Configuration Sets This option concentrates on Customizing settings which are of particular importance for the processes in your company. - Transport requests This option shows the objects which would be overwritten by a transport. - Manual selection In this option, you specify which objects are compared. The compare client security level must be: 0 (unrestricted), or 1 (no overwriting) You can set this in the client maintenance SCC4. You must also create a Remote Function Call link in SM59.
Hope this could help you. Also refer to the following sapnotes: 1. 400241 : Problem withe ops$ or sapr3 connect to oracle 2. 134592 : Importing the SAPDBA role (sapdba_role.sql) 3. 361641 : Creating OPS$ users on UNIX 4. 50088 : Creating OPS$ users on Windows NT/Oracle 5. 437648 : DB13: External program terminated with exit code 1/2 ---------select owner from dba_tables where table_name='SAPUSER'; ## If owner is not the sid you require, then drop the table SAPUSER Drop table "<owner>".SAPUSER; #or# Drop table "domain\OPS$SIDadm".SAPUSER; ## IF THE ANSWER IS 0 ROWS SELECTED THEN CREATE THE TABLE SAPUSER # Check whether OPS$<SID>adm user exist, if no then create it create user OPS$SIDadm default tablespace psapuser1d temporary tablespace psaptemp identified externally; # if exist then drop it; DROP USER OPS$SIDADM; # Grant connect & resource roll to OPS$<SID>ADM; grant connect, resource to OPS$SIDADM; # Creat table SAPUSER create table "OPS$SIDADM".SAPUSER ( USERID VARCHAR2(256), PASSWD VARCHAR2 (256)); # update "OPS$<SID>ADM.SAPUSER with the follwoing command insert into "OPS$SIDADM".SAPUSER values ('SAPR3', 'sap'); #sap = <password> # Under NT it is required that user sapservice<sid> can also access the SAPUSER table. In order to avoid problems with the data consistency, it does not make sense to create an additional
SAPUSER table having the same contents. You should rather define a synonym. Check if a suitable synonym exists by using the following call: SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER'; # IF NOT THEN CREAT IT create public synonym sapuser for OPS$SIDADM.SAPSUER; # if synonym already exists drop the existing synonym by the following command drop public synonym sapuser; #If another name <name> is returned as first value: DROP SYNONYM "<name>".SAPUSER; # AND CREAT it again with above command # To allow access to the synonym (or the associated table), a grant needs to be executed. The authorization for this has only the ops$ user who is the owner of the actual table - that is ops$<sid>adm. Therefore, you need to log on with the corresponding operating system user (<sid>adm) and execute the following commands: CONNECT / GRANT SELECT, UPDATE ON SAPUSER TO "OPS$SAPSERVICE<sid>"; # Now you can recreate the synonym (not PUBLIC, if possible): CREATE SYNONYM "OPS$SAPSERVICESID".SAPUSER FOR "OPS$SIDADM".SAPUSER; CREATE SYNONYM OPS$SAPSERVICESID.SAPUSER for OPS$SIDADM.SAPUSER; # COMMIT AFTER COMPLETION of the activity & restart the DB
The SID is XY1 - Development & Quality XY6 - Production Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems? How can I make thro it? First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure -----------------1. Login to the system with sap* in client 000 2. Goto SE06. 3. Click Post installation activities 4. Goto STMS 5. It will ask for Domain controller name. 6. Enter DOMAIN_<SID> as domain controller name and enter the description. 7. Click Save button Steps to add the other system with Domain controller ---------------------------------------------------1. Login to system with sap* in client 000 2. Goto SE06 3. Click Post installation activities 4. Goto STMS 5. It will ask for Domain controller name. 6. Enter System ID of the Domain controller 7. Enter DOMAIN_<SID> as domain controller name and enter the description. 8. Click Save button 9. Login to Domain controller system 10. Approve the added system.
If you have simply deleted the the requests from import queue through "Extras-> Delete imported requests" in transaction STMS_IMPORT and have not deleted the logs at OS level, then you can check in "Goto-> Import History" in the same transaction to view the requests. Just double click on the request you want and you enter the "Display Object List" screen for the particular request. Here you can click on the secong "Spectacles" icon to display the transport steps of the request in each of your SAP system. Just double click on a step, e.g. 'Import', 'Check Version','Export' etc. to display the log for that particular step. You can also view the logs from operating system in the directory <TRANSDIR>/log. The logs are named in the format: <Source SID><Step ID><Request no>.<Target SID>, where step ID is a single alphabet denoting a particular transport action.
Statistics
Performance database Select instance Select desired period Choose Transaction profile
To find the Frequently Used Programs or Transactions in 4.6x :ST03 ---> Detail analysis Button --> Under Global - One recent period then select day or week or month ---> Transaction profile Button In 4.6x, you can also try the new Workload Analysis tcode 'ST03N'. The SAP standard retention period is 3 months. You can change the Standard Statistics via clicking :Goto -> Parameters -> Perfomance Database To analyze the Statistics by users for transactions and programs use transaction STAT STAT looks at the STAT file created by each SAP Instance. It is by default 100 MB. Every hour there is a COLLECTOR_FOR_PERFORMANCE job RSCOLL00 aggregating this data into MONI table. It will truncate STAT file once the specified limit is reached. So, you can see details for however many days in this 100 MB using STAT, or ST03 to see the MONI aggregated data. To change the 100 MB limit, ST03 -> Goto -> Parameters -> Performance Database.
in the address space that your program can use for its own data. I won't get into a sad chat about all this bat thats hared memory. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An IMODE is an internal mode. An example may be best, log onto a SAP system, create a new session and leave one at the main menu and with the other go to ST02. In ST02 near the bottom of the screen double click on the extended memory line. In the next screen click on the Mode List button. You will see you have the ST02 session marked with an X for being attached and another session in IMODE 0. With the other session got to SM36 then swap back to ST02, press enter and you will see the session has an IMODE 0 and an IMODE 1 use. Now from the SM36 screen click on the button Job Selection and jump back to St02 and press enter, you will see the session has an imode 0 1 and 2 active. Imode 0 is not really an IMOde but the main mode that all your information relevant in any transaction is available. As you call transactions inside transactions you need new memory and the old stuff needs to be save for when you green arrow back. This is why you have imodes so that when you green arrow back from the job selection screen above (I mode2) it is no longer the active mode and imode 1 is reactivated.
applications you are running, how many systems are connected (BW, CRM, APO etc.) and so on. Start with note 88416, there is explained in depth what it is and how it works. For Windows you also should look in note 129813 which will describe the rebasing process since M$ has the start addresses of their DLLs loaded into the PXA. This is one reason why we switched to a non M$ operating system because after each IE patch (in fact after each patch) you need to check if the new DLLs will fragment your PXA/shared memory. Note 546361 can also be helpfull. If you have "hangs" in the system read note 530871 which will describe the problem (and finally recommend upgrading to Windows 2003). What is Zero Administration Memory Management? The zero administration memory management on Windows requires no manual settings and adapts itself dynamically to the memory requirements of the users. Even hardware changes (for example memory enhancement) are detected and the parameters set correspondingly. The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. An "infinitely" large memory resource is made available with this method. The extended memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended memory extends itself in steps of "[PM] / 2" up to the set limit of the profile parameter em/max_size_MB or until the address space in the Windows pagefile is used up. By setting the standard value for em/max_size_MB to 20000 MB (100000 MB for 64 bit), it is the size of the Windows pagefile that finally represents the actual limit for the extension of the extended memory. The profile parameter PHYS_MEMSIZE determines how much of the entire main memory is to be used by SAP. The parameter is entered during installation in accordance with the entry. The standard valuefor PHYS_MEMSIZE is the size of the main memory [HS]. Even with zero administration management, the Windows system should be configured in such a way that it keeps the file cache to a minimum size. Therefore, make sure that indicator "Maximize Throughput for Network Application" is activated under 'Control Panel' -> 'Network' -> 'Services' -> 'Server' -> 'Properties'.
Archiving
Archiving and Reorganization are totally different issues
Archiving is a process when you archive old master/transactional records which are not in use any more from long time. You archive those records keep on some backup device. These records can be displayed, and only Display, can never be reloaded in tables again physically.
This will free up the space in tables from those records which are not in use any more but exist in tables physically. Reorganization basically removes deleted data from tables. During different transactions you delete some records, which are deleted virtually but not physically. Even Archive process delete those records virtually. So you run Reorganization to free up the space consumed by deleted records. This make the difference between the two clear. Now about reorganization. It depends on which OS and DB you are using. If Oracle, SAPDBA is best tool to reorganise. In addition to above, you can reorganise the whole database, but it takes time depending upon your database. Some times it can be more than a day or you can reorganise a table suggested in Early Watch system. It all depends on you.
Use in routing Use in sales and distribution Use in bill of material Delivery exists Costing data exists Info record exists Purchase order exists
The Archiving steps :Archiving object MM_MATNR for archiving material master records. You can display the archived data, but not reload it. To archive the material master, first goto transaction MM71. Type in a variant name and click Maintain. (Tick the Test Mode for archive simulation). Save the variant. Maintain the Start date and Spool parameters and click execute. Click Goto Job Overview to check the archive status. To do a permanent delete, goto transaction SARA and click Delete button. Maintain the Archive Selection, Start date and Spool parameters. Click Test Session for testing or click execute to start the deletion program. Click Goto Job Overview to check the delete status. Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
g) Select the 'Spool Parameter' button and save entries. Eventually enter a valid printer to have the result outputted. h) You are ready now to start the process. Press the 'Start' button and monitor the success with the 'Job Overview' button You can also go the 'fast path' by using transaction SE38, program MMREO002 for selecting the data to archive. For large data archiving, use the background jobs and run those during off-peak times. Create Archive File: Consignment Record: Archiving process: a) Select Action: Archive and enter a new Variant, for example: Z_CONS_ARCH_01, press 'Maintain' b) On selection screen, select the 'Sequential Dataset' if you selected data as described in the Data Selection step, otherwise enter the material number and plant for the deletion of a single record. c) Select the fields 'Consignment' and 'Special Stock' and Test mode, if you want to try out first. ** This applies for SAP systems prior to release 3.1H: Select also the flag called 'BATCHES'. The SAP program MMREO020 has a bug which can be worked around with this selection. Without selecting 'BATCHES', the archived records cannot be deleted. For systems with applied Hotpackages for 3.1H this workaround is not necessary d) Press the green back-arrow and enter the description of this new variantt on the screen which follows. e) Save the variantt which brings you again to the selection screen. Press green back arrow again. f) To start archiving process (batch-job), press the 'Start Date' button and select the time when you want to start this process. Select 'Immediate' for instant processing and press the 'Save' button on the bottom of the 'Start Time' window. g) Select the 'Spool Parameter' button and save entries. Eventually enter a valid printer to have the result outputted. h) You are ready now to start the process. Press the 'Start' button and monitor the success with the 'Job Overview' button You can also go the 'fast path' by using transaction SE38, program MMREO020 for selecting the data to archive. For large data archiving, use the background jobs and run those during off-peak times. If you run the program online, you will see a confirmation on the status bar telling 'New Archive file created:....' Delete Archived Records: Info Record a) Follow the menu path: Tools - Administration - Administration - Archiving b) Select the Object Name MM_SPSTOCK for consignment / Special Stock c) Select the menu button 'Delete' d) Select the menu button: 'Archive Selection' e) Click the archive created in previous step f) Select Start Date for process and Spool Parameters for output g) Submit selection. h) Check status by pressing the Job Overview button
There are both technical and legal reasons for archiving Financial Accounting data. Archiving: 1) Reduces storage and runtime problems caused by the constant growth of transaction data. 2) Makes master data easier to manage and to keep up to date. 3) Enables data to be accessed at a later date. You can archive data no longer required in the online system using certain standard functions. This data is then stored in archive files and deleted from the online system. For legal and commercial reasons, it is important that you are able to access archived data files online again, and the reloading function allows you to do this. Data must meet certain conditions before it can be archived. Some of these controls are already defined in the system, for instance the fact that you cannot archive documents that contain open items. Certain other controls are user-defined. Every archiving function can be accessed from archive management (SARA). To reach archive management, choose: Tools --> Administration --> Archiving or from the Accounting --> Financial Accounting --> General Ledger, Accounts Receivable, Accounts Payable or Banks menus --> Periodic processing Archiving <Archiving object> . When you access archive management from these menus, the archiving object is defaulted by the system in the field Object name. Otherwise you must enter the name of the archiving object manually.
System Audit
The Step required to Audit at the User Level
The followings will help you to Understand how to Audit at the Users level: Creating a User Audit Profile 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SM19. 3. From the top-most menu bar on the Security Audit: Administer Audit Profile screen, click Profile -> Create. 4. On the Create new profile popup, type in a new Profile name and click the green Enter picture-icon. 5. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen, click the BOX to the left of Filter active to place a TICK in the box. In the Selection criteria section, select the Clients and User names to be traced. In the Audit classes section, click "on" all the auditing functions you need for this profile. In the Events section, click the radio button to the left of the level of auditing you need. Once you have entered all your trace information, click the Save picture-icon. You will receive an Audit profile saved in the status bar at the bottom of the screen.
6. Please note that while the user trace profile has been saved, it is not yet active. To activate the user trace, see the next section Activating a User Audit Profile. 7. You may now leave the SM19 transaction. Activating a User Audit Profile 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SM19. 3. On the Security Audit: Administer Audit Profile screen, select the audit profile to be activated from the Profile dropdown. Click the lit match picture-icon to activate it. You will receive an Audit profile activated for next system start in the status bar at the bottom of the screen. The audit will not begin until after the SAP instance has been recycled. 4. You may now leave the SM19 transaction. Viewing the Audit Analysis Report 1. Log on to any client in the appropriate SAP system. 2. Go to transaction SM20. 3. In the Selection, Audit classes, and Events to select sections of the Security Audit Log: Local Analysis screen, provide your information to filter the audit information. If you need to trace the activities of a specific user, be sure to include that user's ID. Click the Re-read audit log button. 4. The resulting list is displayed. This list can be printed using the usual methods. 5. You may now leave the SM20 transaction.
Review the following :* System security file parameters (TU02) (e.g. password length/format, forced password sessions, user failures to end session etc.) have been set to ensure confidentiality and integrity of password. Security-Parameter-Settings-Documentation * Setup and modification of user master records follows a specific procedure and is properly approved by management. * Setup and modification of authorizations and profiles follows a specific procedure and is performed by someone independent of the person responsible for user master record maintenance. * An appropriate naming convention for profiles, authorizations and authorization objects has been developed to help security maintenance and to comply with required SAP R/3 naming conventions. * A user master record is created for each user defining a user ID and password. Each user is assigned to a user group, in the user master record, commensurate with their job responsibilities. * Check objects (SU24) have been assigned to key transactions) to restrict access to those transaction. * Authorization objects and authorizations have been assigned to users based on their job responsibilities. * Authorization objects and authorizations have been assigned to users ensuring segregation of duties. * Users can maintain only system tables commensurate with their job responsibilities. * Validity periods are set for user master records assigned to temporary staff. * All in-house developed programs contain authority check statements to ensure that access to the programs are properly secure. Select a sample of :* Changes to user master records, profiles and authorizations and ensure the changes were properly approved. (The changes can be viewed with transaction (SECR). * Ensure that security administration is properly segregated. At a minimum there should be separate administrators responsible for: - User master maintenance. (This process can be further segregated by user group.)
- User profile development and profile activation. (These processes can be further segregated.) * Verify that a naming convention has been developed for profiles, authorizations and in-house developed authorization objects to ensure: - They can be easily managed. - They will not be overwritten by a subsequent release upgrade (for Release 2.2 should begin with Y_ or Z_ and for Release 3.0 by Z_ only.) * Assess through audit information system (SECR) or through a review of table USR02, whether user master records have been properly established and in particular: - The SAP_ALL profile is not assigned to any user master records. - The SAP_NEW profile is not signed to any user master records. Verify that procedures exist for assigning new authorization objects from this profile to users following installation of new SAP releases. * Assess and review of the use of the authorization object S_TABU_DIS and review of table authorization classes (TDDAT) whether :- All system tables are assigned an appropriate authorization class. - Users are assigned system table maintenance access (Through S_TABU_DIS) based on authorization classes commensurate with their job responsibilities. * Assess and review of the use of the authorization objects S_Program and S_Editor and the review of program classes (TRDIR) whether: - All programs are assigned the appropriate program class. - Users are assigned program classes commensurate with their job responsibilities. * Ensure through a review of a sample of :- In-house developed programs that the program, code either: - Contains an Authority-Check statement referring to an appropriate authorization object and valid set of values; or
- Contains a program Include statement, where the referred program contains an Authority-Check statement referring to an appropriate authorization object and valid set of values. I think an auditor would want to know what methods you are using to approve who gets what profile and what method you are using to document it so that if you review your documentation you could compare it with what authorization the user currently has and determine if the user has more authorizations (roles) than he has been approved for by the approval system in place.
Are all the work processes (dia,btc,enq,upd,up2,spo) running or just all the dialog work processes? If all the work processes are running, then you may want to look at SM12 (or is SM13?) and see if updates are disabled. If they are, look at the alert log (if it's an Oracle database) and see if you have any space related errors (e.g. ORA-01653 or ORA-01654). If you do, add a datafile or raw device file to the applicable tablespace and then, re-enable updates in SM12. If only all the dialog work processes are running, there are several possible causes. First, look to see if there's a number in the Semaphore column in SM50 or dpmon. If there is, click once on one of the numbers in the Semaphore column to select it and then, press F1 (help) to get a list of Semaphores. Then, search OSS notes and, hopefully, you'll find a note that will tell you how to fix the problem. If it's not a semaphore (or sometimes if it is), use vmstat on UNIX or task manager on Windows to see if the operating system is running short on memory which would cause it to swap. In vmstat, the free column (which is in 4k pages on most UNIX derivatives) will be consistently 5MB or so and the pi and/or po columns will have a non- zero value. The %idle column in the cpu or proc section will be 0 or a very low single digit while the sys column will be a very high double-digit number because the operating system is having to swap programs out to disk and in from disk before it can execute them. In task manager, look at free memory in the physical memory section under the performance tab. If it's 10MB or 15MB (I think), then the operating system will be swapping. Usually, when all the dialog work processes are running, you won't be able to log in via SAPgui and will need to execute the dpmon utility at the commandline level. The procedure is basically the same on UNIX and Windows. On UNIX: telnet to server and login as sidadm user. cd to /sapmnt/SID/profile directory execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_hercules_DVEGMS00) select option "m" and then, option "l" On Windows: Click on START, then RUN Type "cmd" and press enter change to drive where profile directory resides (e.g. f:) cd to \sapmnt\SID\profile execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_zeus_DVEGMS00) select option "m" and then, option "l" On both operating systems, you'll see a screen that looks like what you see in SM50. Depending on what you see here, will depend on what you do next, but checking the developer trace files (e.g. dev_disp) in the work directory (e.g. /usr/sap/SID/DVEGMS00/work) is never a bad idea.
- Different Operating System The same goes for operating systems, a standard Windows 2000 (or 2003) isnt configured for optimal throughput, there is a LOT to tune, e. g. enable "background process priorities", stop non-needed services, network configurations (TCP window sizes) etc. Also the connection between application and database servers can be an issue - SAP Itself Almost for each and every long running program there are optimizations, be it on ABAP layer or on selection layer. Out of my experience, most self developed programs (Z*-programs) are the main issue, because developers program "quick-and-dirty" doing "select *" and other things. For e.g.: If CPU is 100% Busy, what action should be taken to keep CPU idle? This can't be answered generally. One need to check what process is using so much CPU - then one can start digging deeper. To add info regarding this issue, you may use: st06->details analysis menu->snapshot analysis->top CPU from there, start to narrow down. As you see there is not a quick button to press on and everything will be well. A good start can be the book "SAP Performance Optimization Guide".
Administration
SAP Administrator Daily Activities
SAP DAILY ACTIVITIES 1] Check that all the application servers are up: sm51 SAP Servers sm04/al08 Logon Users 2] Check that daily backup are executed without errors db12 Backup logs: overview 3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs. sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.
4] Operating system Monitoring st06 5] Extents monitoring db02 Database monitoring--Check for max-extents reached 6] Check work-processes(started from sm51) sm50 Process overview-- All work processes with a running or waiting status. 7] Check system log sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events. 8] Review workload statistics st03 Workload analysis of <sid> sto2 tune summary instance 9] Look for any failed updates sm13 update records 10] check for old locks sm12 lock entry list 11] Check for spool problems sp01 spool request screen-- check for spool that are in request for over an hour. 12] Review and resolve dumps st22 ABAP Dump analysis 13] Checking .trc file in SAP trace directory for block corruption on daily basis. C:\ORacle\sid\saptrace 14] Archive backup brarchive -f force -cds -c Insert the archive backup tape 15] Review NT system logs for problem -> NT system log- look 4 errors or failures -> NT security log- failed logon 2 sap servers -> NT Application log -look 4 errors or failures
In sm21 try to check for errors. In sp01 try to see if any spool jobs have failed. In st02 look if any swaps are happening, swaps are not good for performance. In st04 look for Database alert logs and Performance. In st03 look for ratio hits. In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system In db13 look if the jobs have run successfully. In sm37 look for any cancelled scheduled job and take action appropriately. In sm12 look for any pending locks from the previous days. In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.
Message
Basis - Message Class - System Message
Configure System Messages
For example, when a user blocks himself out and receives a message : "User blocked. Contact system administrator" You can open a repair and change the message in Message class 00. This can be done in transaction SE91 - Message Maintenance. Messages allow you to communicate with the users from your programs. They are mainly used when the user has made an invalid entry on a screen. To send messages from a program, you must link it to a message class. Each message class has an ID, and usually contains a whole set of message. Each message has a single line of text, and may contain placeholders for variables (e.g. & & & - three variables). All messages are stored in table T100. Once you have created a message, you can use it in the MESSAGE statement in a program.
Solution Manager
What Is The Use of Solution Manager
What is the use of solution manager, and what we can do with solution manager? Now a days solution manager is mandatory. 1. it is used for generating keys and downloading support packages 2. it is used to document user requirments and preparing senarios what needs to to be adopted using solution manager, where the blue print is the part of solution manager 3. it is used for reporting, solution desk,to manage the change requests and use to monitor entire landcape Central message processing in the SAP Solution Manager: - Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA) - Assign processor - Send messages to the creator and other processors - Forward message to other processors or support units - Create documents and URLs - Attach documents - Status assignment and monitoring - Create a worklist with selection conditions *-- Shankar
I have a requirement to install SAP Solution Manager Solution Support Enablement Package (SEP) in our solution manager 4.0. This SEP contains, RBE, TDMS, ...etc., I checked for the software download at market place but couldn't find the software package, can anyone help me to download this SEP for windows/oracle. Look at following: http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> Installations and Upgrades -> SAP Technology Components -> SAP Support Enablement Package >SAP Support Enabl. Package 1.0 How to configure the service desk on Solution Manger 4.0. I want to cofigure Solution Manger only for service desk I have install Solution Manger 4.0. What is the Step please explain. Check: http://service.sap.com/rkt-solman There are tutors, PDFs and powerpoints to guide you through the configuration process. Markus *--
If you have 3 or 4 client systems, must you install SAP solution manager for each one of these systems and manage them independently -or- 2. Can you install One Solution manager, that will manage all 3 these systems in one solution manager -or- 3. Do you install 3 Solution managers for each of the systems, then another one linked to the 3 individual solution managers, which then in turn manages the 3 systems in one. In any System landscape only one solution manager is installated in one system and it will communicate with the other system using the RFC and collect the report from each and every system through (SDCCN).
Email
How to test the sending of documents from R/3 applications via fax, paging or Internet mail?
What are the system requirements? What do you have to configure? The sending of documents via external communications services like fax, paging (radio call services, SMS), Internet mail, X.400, and so on is carried out with the components SAPoffice and SAPconnect. For an 'actual' sending via the corresponding communications services you still need R/3-external additional components ("SAPconnect node") which are delivered either by SAP (for example SAP
Internet Mail Gateway or SAP Exchange Connector) or by external manufacturers (for example, fax servers).
. . . . . . . . . . . . . . . . . . . . . ................ . R/3 . . +----------------------+ . ! Application ! . +----------------------+ . | . | <------- Business Communication Interface v . +----------------------+ . ! SAPoffice ! . +----------------------+ . | . | <------- SAPoffice/SAPconnect send queue v . +----------------------+ . ! SAPconnect ! . +----------------------+ . | . . . . . . . .|. . . . . . . . . | | <------- RFC Interface BC-CON v +----------------------+ ! Communication system ! ! ="SAPconnect node" ! +----------------------+ | v Data transfer network
You can check the correct sending of documents from applications with two different tests: 1. 'Actual' test Documents are actually transferred via the communications services. Precondition is the installation of an external communication system and its connection to the data transfer networks (telephone line, Intra/Internet...). This way, the documents can be transferred to any participant of the corresponding communications service (fax machines, mailboxes...). 2. 'Loop-back' test The documents are returned here to the own R/3 System which functions like a SAPconnect node and are stored in the SAPoffice inbox of an R/3 user. The operation of an external communications system is nonrequired in this case. In general, all points relevant for application can be checked during this test: Contents and structure of the documents, entry of sender and receiver addresses, format of the documents for transmission, handling of status confirmations and so on
. . . . . ................ . +-------------+ ! Application ! +-------------+
. . .
. . . . . . . . . . . .
For both tests, proceed as follows: 1. 'Actual' test Contact the R/3 System administration to set up the R/3-external infrastructure necessary for the required communication service and to carry out the R/3 internal configuration. 2. 'Loop-back' test a) Address management All R/3 users who want to send documents via a communication service need an address of the respective communication service type which is used as a sender specification. All users also need an address of this type to receive documents in the R/3 System via a communications service and under which they are attainable as receivers. If documents are to be sent to the own R/3 user during the loop-back test, a single address of the corresponding communication service suffices for this user. This is then used both as sender and as receiver specification. Create addresses The address maintenance of R/3 users is carried out either via the R/3 User Maintenance (Transaction SU01) or the Private office settings (Transaction SO12): Address --> Other communication... Selection of the required communication service. Enter address. Copy or save. b) Configuration of SAPconnect (Transaction SCOT) Set communication method 4.0 + 4.5: Goto --> Customizing --> Communication methods as of 4.6: Settings --> Communication methods Set the method of the required communication service to the value 'SAPCONNECT' and save the setting. Create node View --> Nodes, node --> Create Nodes = for example system name/client "ALR003" For example, Description = "ALR client R/3 System 003" RFC destination = 'NONE' Address type = Selection of the required communication service. Address area = for example '*' Format = 'PDF' for fax, 'RAW' for paging and Internet mail Device type = 'POST2' for fax, 'ASCIPRI' for paging and Internet mail Restrict send time = do not flag
Country = 'DE' (only for fax) Flag Node-specific fax number changes... = (only for fax) Enter two entries in the table: (only for fax) Begin. no Substitute Comment ----------------------------------00 + foreign country 0 +49 home country Set further address type = 'no' Maximum waiting time... = enter nothing Node can resolve path references = do not flag Node is to be monitored by the alert monitor = do not flag Node in use = mark Schedule send process View --> Jobs, job --> Dispatch Job name = for example 'SAPconnect' --> place cursor on variant SAP&CONNECTALL Schedule job (F6) Schedule periodically, for example 5 minutes. After sending a document from an R/3 application this is displayed in the outbox of the sender (if requested SAPoffice interface). After the next SAPconnect transmission process (according to the period chosen when scheduling the job) the document is displayed in the inbox of the receiver
Indexing : Tick Specify the 'Retention period of a document in this folder (days)'. Choose the 'Folder access authorization'. Finish, click the Enter button. Click the tabstrips 'Distri. list content' to type in your mailing list. Save your entries. Finally, test it by sending a mail via the distribution list ZXXXX.
When you set the job up you can specify an external email in the spool list recipient section. It should look something like the below. There will be some mail side setup required depending on your environment and what is possible.
One the job process is completed, the email will be send out to the recipient.
Unicode
Whether a System is Unicode or non-Unicode
How to Verifying whether a system is Unicode or non-Unicode? disp+work should show you the whether the system is Unicode or Non-Unicode. log in to server and then command prompt type disp+work -V | more you can find your system use Unicode or non. or else login SAP and goto System--> status. Logon to SAP, click on System/Status. See the Unicode system column.
Network
Bandwidth requirement of ISP to connect to SAP server through VPN
We are in the process of implementing SAP for our overseas sales offices. However, the Server will be situated at our country. We want our overseas sales office to connect to our SAP Server through VPN. What should be the optimum internet bandwidth that they should use at their place to connect to our SAP server? Does SAP recommend any standard bandwidth for this process? From our experience, there is no general rule that one can follow, as several factors will affect the connectivity 1. No of hops between your ISP and that of the remote site, the more hops the poorer the performance, even having large bandwidth may not improve the performance by much if there are numerous hops in between. 2. Is the Internet connectivity solely used for your VPN or other purposes such as web surfing, email etc, other traffic can consume large amount of traffic thus causing your SAP performance to be poorer 3. ISP's bandwidth to the public internet - If the ISP is heavily over subscribed, and has limited bandwidth connecting to the international network, you will find that you will not be able to get the
international throughput you subscribed for as such, performance may be poor even you have paid for a line with a large bandwidth 4. No of users at your remote office using the VPN - In general the lines we use are 64kbps for sites with approx 3-5 users, we are also using ADSL lines with 512kbps connectivity and they enjoy close to local Lan performance for SAP.
See from which network IP address and host name a user has logged on
To see the network IP address from which a user has logged on, perform the following steps: Call transaction OS01, click "Presentation Server" button, "Change View" button. If you are using Citrix, you will not be able to view the user individual IP address as it will be the same Citrix IP address. To check the speed and quality of the user's network connection, select the desired presentation server and click "10 X Ping" button.
So the user name will show up more than once in AL08. Under the application server they are logged into, each instance of that user name on that application server represents a session open. For instance if you run AL08, you will have your name show up at least twice on the application server you are logged into. One will show AL08 and the other will not have a transaction next to it. Then you will notice your user name showing up on all other application servers with no transaction. This is because you are using AL08.
Jobs
Suspend/UnSuspend Released ABAP Jobs
BTCTRNS1 - Suspend all Released Jobs Released Jobs will have the status Released/Susp. in transaction SM37. BTCTRNS2 - Reverse Suspend for all Released Jobs
Starting in Release 2.1, this index is automatically updated online. The job can be repeated at any time. After a termination, the job is automatically scheduled for the next day; it then starts at the point oftermination. (EU_INIT can therefore be terminated deliberately, if it disturbsother activities in the system.) EU_REORG: As mentioned above, the indices are automatically updated online by the tools. To keep the effort for updating these indices as low as possible, only the changes are logged, which means a reorganization of the complete index for each program is required from time to time. To avoid having this reorganization interfere with online work, job EU_REORG runs every night and performs this task. If job EU_REORG did not run one night, this simply means that thereorganization takes place more often online.
Tables
Reorganization of Single Object
You have ARCHIVED the BSIS table (because of old data etc) and now this BSIS table has "holes" in physical structure and it's quite a large table. Here are the steps to reorg. a single object: 1. Take a backup of your Oracle database. 2. Shutdown SAP 3. Start Oracle Database with Rollback Segment PSAPROLLBIG (all other smaller segments not started). Remember, the size of PSAPROLLBIG should be equal or larger than your BSIS table. 4. Ensure sapreorg directory has enough space for taking BSIS Oracle Export dump. The Oracle Export utility compresses the file to some extent. 5. Fire your SAPDBA from Unix level. 6. Go into SAPDBA "reorganisation" menu. 7. Select "Reorganize Single Table / Index" 8. Give BSIS as table name. 9. Start. 10. Don't Forget, first upgrade your SAPDBA tools first from OSS/SAPNet. These include: 1. sapdba 2. brtools 3. brarchive 4. brbackup 5. brrestore 6. brconnect.
If your table change log is not active, it will gives you a message that :...table logging is switched off... This particular setting can be changed in the following path :IMG--> Basis Components --> System Administration --> Tables changes recording You can log changes made to the following tables: - Control tables (system logic control) - Customizing tables What is recorded is always in the form of complete "before" images, that is, all entries as they appear before the changes. The recorded data is compressed without buffering, and this is not an appropriate method for recording and managing large amounts of data. Activating logging impacts on performance as it entails twice as many database updates as would otherwise be the case, and the database storage load is also increased substantially. It is recommend that you use logging for your production clients and Customizing clients so that you can see exactly where Customizing tables have been changed. Other than the reasons above, it is not recommended that you use this tool for application tables. Two conditions have to be met for a table to be logged: 1. The table has to be selected for logging in the Dictionary (see Dictionary -> Table maintenance -> Technical configuration). 2. Logging also has to be set in the system profile Set the rec/client (note the use of lowercase characters) profile parameter to one of the following values :- OFF: no logging at all (effectively a central system switch) - nnn: logs client-specific tables in client nnn only - mmm,nnn,ppp,...: logs client-specific tables in the named clients - ALL: logs all client-specific tables in all clients. Caution: Only in exceptional circumstances is it appropriate to use the 'ALL' setting. If, for example, the profile parameter is set to 'ALL' when you upgrade all test clients (including 000, the SAP client), these changes are recorded in the system log file. This reduces performance and requires a lot of database space. The default setting is OFF (no changes are logged). If logging is set in the ABAP Dictionary, changes to client-indepedent tables are always logged unless rec/client is set to 'OFF' Use the ABAP programs RSTBHIST or RSVTPROT to analyze table changes. RSVTPROT allows you to analyze change logs both at table level and with reference to Customizing objects. To access the program, select an executable Customizing activity in IMG and choose Goto -> Change log.
impossible, so we saw and let extents grow. In fact, by the time we went live, we had 2 objects over 450, 5 objects over 300, about 50 objects (tables and indices) that were over 100 extents, and we had hundreds of objects over 10 extents. I agree to doing both planning for growth and monitoring growth. And the earlier in your SAP implementation you do this the better - which is something we did not do until after we created our productive instance. We were very concerned about this situation and spoke to 3 or 4 different SAP consultants. We got the same answer from each - objects in high extents will have little or no performance impact. Like Sanjay mentioned, the consultants had no specific reason for this. I do not believe you will find an SAP employed person who will say you should keep extents below a specific value. Also, I cannot definitively give that advice either. Over the months we have all our objects below 100 extents. We have not seen a significant change in database response time. Our goal is to have all objects below 20 extents - which is a corporate standard. But we will not ask for extra down time to reach this goal. Good luck trying to keep objects below 10 extents. While data is "pumped" into the system during the weeks before going live, whatch the extents, they will take off. This also occurs after performing a SAP version upgrade. Mark A. Kochanski -----Reply Message----Subject: Re: BASIS: Tablespace sizes in large databases -Reply [3] From: "Robert A. Simard" Gentleman, Why not do both? Planning for growth is critical. Monitoring daily can be automated via CCMS can it not? With proper alert thresholds, a system freeze can be thwarted long before extents reach 300 (max extents in my version of Oracle). My question to you both is, how many extents are to many? I have heard from consultants that SAP says that, for performance reasons 10 is the limit. I do not understand the logic in this. Unless There is alot of fragmentation throughout the tables, why not 50 or 100? I just completed a Client Copy and have 4 tables in the BTABD tablespace that are over 17 extents. Is this to many? and should I lose the uptime for a reorg for 17 versus 10 extents? I guess what I am asking is, since both of you seem to have put some thought into this, is there a hardand fast number when in comes to an acceptable amount of extents? SAP seems to be overly conservative most of the time - was wondering if anyone has good numbers? Thanks and have a great day. ~Bob
---------------------------------------------------------------------------Robert A Simard SAP-Basis Support, NT Sys. Admin. "Whoever is first in the field and awaits the coming of the enemy, will be fresh for the fight; whoever is second in the field and has to hasten to battle will arrive exhausted." Sun Tzu - The Art of War --------------------------------------------------------------------------------Reply Message----Subject: Re: BASIS: Tablespace sizes in large databases -Reply [3] -Reply From: Sanjay Shastri Good suggestion and well received ;-) Now to try and answer your question, looking at just Oracle ( or any DB ), you would think that too many extents would cause problems with your performance ( and that is quite true in most cases ). However, I believe I read on this list that SAP ignores the extent growth ( no explanation provided ) and that it 'really does not matter how large the number gets'..... We have several tables that are over 150 extents and don't see too much of a performance glitch ( on an overall level ) but in practice, I do not let any table go beyond 100 extents in an SAP environment. Letting indices grow too much seems to have a much greater impact. Any comments / insights? - Sanjay -----Reply Message----Subject: BASIS: Tablespace sizes in large databases -Reply -Reply From: Sanjay Shastri <SShastri@bdm.com> Mark, would you be willing to risk a system freeze, even if it happens once? I happen to believe in the saying 'prevention is better than cure' ! You are correct that keeping up with extent growth and increasing the size of the next extent via SAPDBA controls the extent problem but, resizing the tables offers one advantage in that you plan better for growth and you are not bogged down by too much of an maintenance effort. System availability IS critical and minimizing downtime doesn't hurt... ;-) - Sanjay -----Reply Message----Subject: BASIS: Tablespace sizes in large databases -Reply -Reply From: Mark Kochanski Sanjay, Tablespaces will grow and you can add space as needed but if you run out of extents on tables....tough luck!
Why Tough luck? Sure, if a table or index reaches max extents your system will freeze or go down, or certain transactions will have errors. .....
Authorization Objects
Object /SDF/E2E /SDF/TRACE BV_SR_TCOD C_DML E_WDPLJRNL F_GMGT_RLT I_VV_IC K_PRPS_SET MAN_PM_KPI PPF_ADMIN P_EFI SASAP_ADIM S_ADMI_FCD S_ARCHIVE S_ASAPIAAT S_ASAP_RF S_ASAP_TF S_BDC_MONI S_BPE_CONF S_BRAN_ADM S_BTCH_ADM S_BTCH_EXT S_BTCH_JOB S_BTCH_NAM S_CCMS_CMC S_CCM_RECV S_CLNT_IMP S_CPIC S_CTS_ADMI S_CTS_LANG S_C_FUNCT S_DATASET S_DB2_ADM S_DB2_COMM S_DBCON S_DDSTCAUT S_ENQUE S_ESH_ADM
Class BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A
Description Authorization for end-to-end diagnostic Authorization for end-to-end trace Sales Returns - Authorization Check at Transaction Level MDF Object Type Authorization Object for Operations Log Grants Management: BP Roles Authorization Info Container CO-CCA: PSP Element Groups Manufacturing: Add Plant Manager KPI Authorization for Parallel Processing Authorisation object efiling Administrator: Implementation Assistant System Authorizations Archiving Maintain Topic Attributes Implementation Assistant: Roadmap (Type and Flavor) Separate Roadmap Type and Flavor Batch Input Authorizations Configuration Inbound Processing for Integration Processes Industry management Background Processing: Background Administrator External Scheduler Background Processing: Operations on Background Jobs Background Processing: Background User Name CCMS Monitoring Console Authorizations for Transferring Central System Repos. Data Data Import for Client Copy CPIC Calls from ABAP Programs Administration Functions in Change and Transport System Language Transport Administration Functions C calls in ABAP programs Authorization for file access DB2/390: Database Administration DB2 OS/390 commands: in Database Performance Monitor (ST04) Database Multiconnect Structure Changes in Support Package Systems Enqueue: Display and Delete Lock Entries Administration Enterprise Search Appliance
S_EWA_ADM S_FIELDSEL S_FP_CHK S_FRA_AREA S_FRA_CLRO S_FRA_CORO S_FRA_SP S_FRA_SPS S_FRA_SPTY S_GUI S_IWB_ADM S_J2EEROLE S_LANG_ADM S_LAS_ADM S_LCRDB S_LDAP S_LDAPMAP S_LOG_COM S_OLE_CALL S_OSS1_CTL S_OTR_ACTV S_OTR_LANG S_PACKSTRU S_PATH S_PTCH_ADM S_QIO_MONI S_RZL_ADM S_SAA_ADMI S_SAA_ROLE S_SCR S_SCRP_ACT S_SCRP_FRM S_SCRP_GRA S_SCRP_GRB S_SCRP_STY S_SCRP_TXT S_SDCC S_SDCC_ADD S_SHM_MON S_SKOM_SRV S_SPO_ACT S_SPO_DEV S_SPO_PAGE S_SRT_ADM S_SRT_CA S_SRT_LPR S_SWC S_SWF_GMP S_SWITCH S_TABU_CLI S_TABU_DIS S_TABU_LIN S_TMS_ACT
BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A
Administration EarlyWatch Alert Central Field Selection Form Processing: Authorization for Form Update Framework Registry: Area Framework Registry: Class Role Framework Registry: Component Role Framework Registry: Service Provider Framework Registry: Element Type Framework Registry: SP Type Authorization for GUI activities Knowledge Warehouse: Administration J2EE Security Roles from VMC Servlets Language Administration System Measurement Authorization Maintenance Authorization for LCR Database Authorization to Access LDAP Directory Authorization to Maintain Directory Mapping Authorization to Execute Logical Operating System Commands OLE calls from ABAP programs Authorization for OSS logon OTR Activities Authorization to Change Objects: Language-Dependent Internal SAP Use: Package Structure File system access via ABAP/4 Administrating Component-Specific Patches (Configuration) Queue Management Authorizations CCMS: System Administration System Administration Assistant: Execution System Administration Assistant: Application View Authorization for SAP GUI Scripting SAPscript: Activities SAPscript: Layout set SAPscript: Graphic SAPscript: Graphics (BDS buffer) SAPscript: Style SAPscript: Standard text Data Interface for the Service Assistant Berechtigung fr /bdl/sdcc im AddOn-Namensraum Shared Objects: Monitor SAPcomm: Server Authorization Spool: Actions Spool: Device authorizations Spool: Restriction on Maximum Number of Pages Administration/Configuration of SOAP Runtime Central Administration of SOAP Runtime Authorization Object for Logical Port Maintenance Authorization for Changing Software Components Workflow Administrator Good Morning Page Switch Settings in Switch Framework Cross-Client Table Maintenance Table Maintenance (via standard tools such as SM30) Authorization for Organizational Unit TemSe: Actions on TemSe objects
S_TOOLS_EX S_TREX_ADM S_UDDI_REG S_USERCERT S_USER_ADM S_USER_AGR S_USER_AUT S_USER_GRP S_USER_OBJ S_USER_PRO S_USER_SAS S_USER_SYS S_USER_TCD S_USER_VAL S_VMCADMIN S_VMC_TRAN S_WF_PRCTP S_WORKFLOW S_WSSP_ADM S_X500_CON S_XMB_ACT S_XMB_ADM S_XMB_AUTH S_XMB_DSP S_XMB_MONI S_XMI_LOG S_XMI_PROD W_CM_CDT1 W_CM_CDT2
BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A BC_A
Tools Performance Monitor Administration of TREX Register in UDDI Registries Certificate Logon: Certificate Request and Assignment Administration Functions for User/Authorization Administratn Authorizations: Role Check User Master Maintenance: Authorizations User Master Maintenance: User Groups Globally Deactivate Authorization Objects in a Client User Master Maintenance: Authorization Profile User Master Maintenance: System-Specific Assignments User Master Maintenance: System for Central User Maintenance Authorizations: Transactions in Roles Authorizations: Field Values in Roles Authorizations for VMC Administrators Transport of Java Development Objects Workflow: Authorizations for Process Types Workflow: Authorizations for Processes Administer Web Services Security Profile Authorization for X500 directory access Obsolete as of XI 2.0. Use S_XMB_AUTH Integration Engine: Administrator Integration Engine: Activities for Individual Areas Obsolete: Do not use. Use S_XMB_MONI instead Authorization Object for XI Message Monitoring Internal Access Authorization for XMI Log Authorization for External Management Interfaces (XMI) CDT Maintenance ISR Authorization for Article Hiearchy Maintenance
Object PAW_LOCID PAW_PRINT S_CARRID S_COOL S_COV_ADM S_DEVELOP S_DOKU_AUT S_ENH_CRE S_FLBOOK S_FOBU_MTH S_IWB S_IWB_ATT S_IWB_ATTR S_KW_MODEL S_PROGRAM S_QUERY S_SHM_ADM S_TERM_AUL S_TERM_AUT
Class BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C BC_C
Description PAW - Location PAW - Authorization object to print Certificates Authorization Object for Airlines Central Authorization for Enterprise Services Coverage Analyzer: Administration ABAP Workbench SE61 Documentation Maintenance Authorization Authorization Check for Code-Based Enhancement Options Authorization Object for Flight Bookings (Demo) Formula Builder Methods Knowledge Warehouse Authorizations for Attribute Values Authorizations for Attribute Values Administration of KW Document Models ABAP: Program Flow Checks SAP Query Authorization ABAP Shared Objects: Management Authorization for SAPterm for Individual Languages Maintenance of Glossary and Terminology Objects
Translation Performance Monitor authorization object Translation environment authorization object Transport Organizer
Object
Class
Description Authorizations in Audit Processing FOX Explosion Framework ALE Distribution Packet ALE Distribution Unit: Customizing Business Address Services: Communication Addresses Business Address Services: Address Type 1 (Org. Addresses) Business Address Services: Address Type 2 (Private Addrs.) Business Address Services:Addr.Type 3(Work Center Addresses) ALV Standard Layout Applications log Implementation Assistant Implementation Assistant: Attribute Maintenance Accelerators Implementation Assistant - Documentation Implementation Assistant BC Set Authorization Object BC-SRV-KPR-BDS: Authorizations for Accessing Documents BC-SRV-KPR-BDS: Authorizations for Document Set Public holiday and factory calendar maintenance CheckMan_f Authorization Object Authorization to Maintain Exchange Rates Form Processing: Authorization for ICF Service Hierarchy maintenance authorization check WFEDI: S_IDOCADM - Debugging Functions WFEDI: S_IDOCCTRL - General Access to IDoc Functions WFEDI: S_IDOCDEFT - Access to IDoc Development IDoc Metadata: Load and Display IDoc Metadata in XI WFEDI: S_IDOCMONI - Access to IDoc Monitoring WFEDI: S_IDOCPART - Access to Partner Profile (IDoc) WFEDI: S_IDOCPORT - Access to Port Description (IDoc) WFEDI: S_IDOCREPA - Access Repair Programs KW Framework: Authorization Check Number Range Maintenance SAPoffice: Authorization for an Activity with Documents SAPoffice: Authorization to Create Shared Folders SAPoffice: Office User Attribute Authorization Object for Sending Authorization Object for Send Request Overview SAPoffice: Transaction Code Authorizations Change documents Deadline Service: Authorizations for Deadlines Client Comparison and Copy: Data Export with RFC Time Streams Test Workbench structure maintenance Time zones UWL: power user for uwl service
AUDIT_AUTH BC_Z B_FOX BC_Z B_UPS BC_Z B_UPS_CUS BC_Z S_ADDRCOMM BC_Z S_ADDRESS1 BC_Z S_ADDRESS2 BC_Z S_ADDRESS3 BC_Z S_ALV_LAYO BC_Z S_APPL_LOG BC_Z S_ASAPIA BC_Z S_ASAPIAA BC_Z S_ASAPIAD BC_Z S_ASAP_IA BC_Z S_BCSETS BC_Z S_BDS_D BC_Z S_BDS_DS BC_Z S_CALENDAR BC_Z S_CHKM__FA BC_Z S_EXCHRATE BC_Z S_FP_ICF BC_Z S_HIERARCH BC_Z S_IDOCADM BC_Z S_IDOCCTRL BC_Z S_IDOCDEFT BC_Z S_IDOCMETA BC_Z S_IDOCMONI BC_Z S_IDOCPART BC_Z S_IDOCPORT BC_Z S_IDOCREPA BC_Z S_KWF BC_Z S_NUMBER BC_Z S_OC_DOC BC_Z S_OC_FOLCR BC_Z S_OC_ROLE BC_Z S_OC_SEND BC_Z S_OC_SOSG BC_Z S_OC_TCD BC_Z S_SCD0 BC_Z S_SWF_SLS BC_Z S_TABU_RFC BC_Z S_TSTRID BC_Z S_TWB BC_Z S_TZONE BC_Z S_UWL_SERV BC_Z
S_WDR_P13N BC_Z S_WFAR_KPR BC_Z S_WFAR_LOG BC_Z S_WFAR_LOP BC_Z S_WFAR_OBJ BC_Z S_WFAR_PRI BC_Z S_WFAR_RED BC_Z S_WFMODCMPBC_Z S_WFMODOBJ BC_Z S_WFMODTMP BC_Z S_WFMODWKFBC_Z S_WF_GPENG BC_Z S_WF_LVIEW BC_Z S_WF_SUBST BC_Z S_WF_WI BC_Z
Administration Personalization in WD4A Components SAP ArchiveLink: Authorization Object for Document Search Authorizations for ArchiveLink Logging Authorization in Logging Print Lists in ArchiveLink ArchiveLink: Authorizations for access to documents SAP ArchiveLink: Authorization to Access Print Lists ArchiveLink: Authorization for Redlining Workflow Modeler component: activity/content access right Workflow Modeler : Access right to UI areas (tab...) Workflow Modeler template: activity/content access right Workflow Modeler: activities for user workflow Workflow Guided Procedure Engine Access Workflow: Handling of Integrated Inbox View Workflow: Substitute Rule Workflow: Work Item Handling
Open the text file do a replace all of PADISABLED = "" to PADISABLED = "X" Then import the same file. or Another way is to go through each output device in SPAD and click on 'Lock Printer in SAP System' which is in the DeviceAttributes tab
In the field "Host spool access method" set to "P: Device Pool". Click the tabstrips 'DevicePool' Click the options "Send to all devices in pool". Type in the list of the SAP printers device you want the report to go to in this pool under the section 'Pool Device List'. Now, when the users send a print to the new device for e.g. ZXXX, it will print to all the spool device you have specify. The above step is done using SAP 4.6c
Right click on HP LaserJet 5100 ... Properties.. General Tab --> Printing Preferences --> Advanced --> Paper Size --> Change it to 14x11 or A3 and hplaserjet 5100 --> Properties --> Advanced Tab Printing Defaults --> Advanced --> Paper Size -> change it to 14x11 or A3 hplaserjet 5100 --> Properties --> Device Settings tab -> Autoselect -> A3 or 14x11... PrakashP Our ABAPer already changed some attributes(ex. font name & size) in print control of SPAD followed by SAP Notes 21738. Like this -> # THSAPWIN Z_65_255 # SAPWIN indicatior makes it possible to send via berkeley protocol \e%SAPWIN% # change WinCharSet to 222 (Thai) \eW222; # set orientation(LANDSCAPE) #\ePL # set font name \eFAngsana New; # set font size(5.5ponits)->8p->5.5 \eS220 # set vertical spacing(8.7LPI) #\el3.0; # set horizontal spacing(24.0CPI)->20->18 (255/11) ->23 #\ec5.0; # set top/left margin(1.0cm=568.5) #\eMT567; #\eML567; However, it take moderately time to change font size and test report printing for A3 format. Thank you for your recommend. Bankly I follow by your instruction. It's work well. Note It doesn't need to setup these config at all.
Tab "Output Attributes" Paper tray = "Paper tray 3" Tab "Tray Info" Tray 3 = "DINA3" Key points of this solution, If the SAP spool server and the Microsoft Windows spool system are not on the same host, you must create a remote PC connection to the printer and force paper size to be A3 (Prakash's instruction) By the way, I also adjust HP Laserjet 5100 from "EXEC" to "A3" in Tray 3 physically too. After that I can print ABAP List in A3 Format successfully.
First you have to add a printer using Windows -> Start -> Settings -> Printers -> Generic / Text Only -> Port : Print to File Next create a new device type e.g. ZPDF -> Select device type ZPDF1 Options for HostSpoolAccMethod -> Host spool access method : F : Printing on Frontend Computer Host Printer : __DEFAULT or Generic / Text Only Save your entries. When you print to the device type ZPDF, choose Generic / Text Only for the Frontend Computer if it is not the default type. A user prompt Print to File will appear to let you specify the Output File Name.
OSS
Apply OSS Notes On My SAP R/3 System
How to apply OSS notes to my R/3 system? In order to fix one of the problem in R/3 system, SAP will asked you to download an OSS notes which is a ".car" file. To work with a CAR File do the following at OS Level: Get into OS as <sapsid>adm Copy the .CAR file to a Temporary Directory. Uncompress the file with SAPCAR
Copy the the data file generated in the data transport directory ( ej: = /usr/Sap/trans/data). Copy the the cofile file generated in the cofiles transport directory ( = ej: /usr/Sap/trans/cofiles). Run transaction STMS Upload the support package with SPAM transaction and the support package will show "New support packages". ********** Examples of CAR command :1) UNIX only: Log on as user <sapsid>adm. cd /usr/sap/trans CAR -xvf tmp/<ARCHIVE_NAME>.CAR -V 2) Windows NT only: Log on as user <SAPSID>ADM. cd \USR\SAP\TRANS CAR -xvf TMP\<ARCHIVE_NAME>.CAR This Will create two(2) FILES After you run SPAM you MUST run STMS and check the transport queues ********** As per 315963 note you can direct made the changes in the program or you can apply the support pack. a) If you want to apply correction then first you need to register the object in SAP, so that you will get the Access key and then you can make the changes. b) If you want to import the support pack then you need to down load from SAP market-place. and this is in CAR file. and then you need extract the same using CAR utility. ex: CAR -xvf abc.car or you can directly apply the patch from SAPGUI, login to 000 client and then you can load the patch from Presentation server. Also check what is your current basis patch level?
For example if you want to apply patch 07 and you are having 05 then you need to apply 06 and then apply 07. ********** Things to take note of:It would definitely be better to apply the latest spam/saint spam manager, tp, R3trans and possibly a new kernel patch. This is not a simple task to complete on the fly. By applying SAP support packs, you may run into problems with SPDD and SPAU adjustments. Also include the fact that the support packages may break one of your transactions. You may want to test this in your sandbox environment, if you have one, before tackling it. In most situation when you apply support packages, it can takes about 3 weeks to fully test the support packages before you can apply them to the production system. Do test your "golden" transactions to make sure that they are not broken. If you are not familiar with SPDD and/or SPAU adjustments than do not attempt to load support packages. You may be better off just to modify the SAP object in question via OSS note.
Follow this step to obtain the Program Access key: Menu Path: System -> Services -> SAP Service (Transaction code OSS1) Login in with your OSS ID and Password Click the Registration button Click Register Object Double click R/3 Value Contract Fill in the Object Registration for Installation: For e.g. PGMID/Object/Name: R3TR FUGR MIGO SAP release: 46C Finished, click the Register button Select the Key number and use the Copy and Paste short key to copy the Access key You are now able to modify the SAP standard program. Finished the modification, do remember to transport it to the production system after all the necessary testing.
If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code. If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied. You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.
Transaction Codes
Changing the Title of SAP Transaction
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.
Yes - SM37 - select - kill If you have a long running Job, how do you analyse? Use transaction SE30. How to uncar car/sar files in a single shot? on Unix: $ for i in *.SAR; do SAPCAR -xvf $i; done When we should use Transactional RFC ? A "transactional RFC" means, that either both parties agree that the data was correctly transfered - or not. There is no "half data transfer". What is the use of Trusted system. I know that there is no need of UID and PWD to communicate with partner system. In what situation it is good to go for Trusted system ? E. g. if you have an R/3 system and a BW system and don't want to maintain passwords. Same goes for CRM and a lot of other systems/applications. Let me know if my understanding below is correct: 1) By default the RFC destination is synchronous 2) Asynchronous RFC is used incase if the system initiated the RFC call no need to wait for the response before it proceeds to something else. Yes - that's right. But keep in mind, that it's not only a technical issue whether to switch to asynchronous. The application must also be able to handle that correctly. Which table contains the details related to Q defined in SPAM? Is there a way to revert back the Q defined? If yes, How? There is a "delete" button when you define the queue. If you already started the import it's no more possible since the system will become inconsistent. What is a developer key? and how to generate a developer key? The developer key is a combination of you installation number, your license key (that you get from http://service.sap.com/licensekey) and the user name. You need this for each person that will make changes (Dictionary or programs) in the system. What is XI3.0 ? EXPLAIN XI = Exchange Infrastructure - Part of Netweaver 2004. SAP Exchange Infrastructure (SAP XI) is SAP's enterprise application integration (EAI) software, a component of the NetWeaver product group used to facilitate the exchange of information among a company's internal software and systems and those of external parties. Like other NetWeaver
components, SAP XI is compatible with software products of other companies. SAP calls XI an integration broker because it mediates between entities with varying requirements in terms of connectivity, format, and protocols. According to SAP, XI reduces integration costs by providing a common repository for interfaces. The central component of SAP XI is the SAP Integration Server, which facilitates interaction between diverse operating systems and applications across internal and external networked computer systems. How to see when were the optimizer stats last time run? We are using win2k, oracle 9, sapr346c. Assumed DB=Oracle Select any table lets take MARA here but you should do the same for MSEG and few others to see whether the dates match or not.Run the following command on the command prompt:select last_analyzed from dba_tables where table_name like '%MARA%'; This gives you a straight answer .Else you can always fish around in DB14 for seeing when the optimzer stats were updated.
- Allows the distribution of resources and system components - Provides interfaces for decentralized system parts and external products. An R/3 instance is a group of R/3 services that are started and stopped as a unit (by an R/3 dispatcher) and have a common instance profile. The name of an R/3 instance is composed of letters standing for the relevant services, and an instance number which is unique for each computer. The services may be D, V, E, B, M, G, or S, which respectively stand for dialogue, update, enqueue, background, message, gateway, and spool services. Tips by : Suresh Babu I would like to know the version or name of SAP that is implemented in real time? This is a very generic question and really depends on what you are implementing (modules). The history of the "R/3" is 3.0D Basis 300 3.0E Basis 300 3.0F Basis 300 3.1H Basis 310 3.1I Basis 310 4.0B Basis 400 4.5B Basis 450 4.6C Basis 460 4.71 Basis 6.20 4.72 Basis 6.20 5.00 Basis 6.40 (ECC 5.0 - Enterprise Core components) 6.00 Basis 7.00 (ECC 6.0) - actually in RampUp All of those have increased business functionality and interfaces to other systems (CRM, BW etc.) What is mysap? It's a term for all the systems that in a contract (e. g. a MySAP business suite consist of ERP2005, CRM2005, SRM2005). What is the systems configuration required to implement SAP.. i.e for production,development and QAS servers the hard disk space, RAM, Processor This also depends on what your are implementing, how many users will work on the system, how many records in what area are created etc. We need a BIG database system and an even bigger application server for ~ 900 users and 12 languages. What is ASAP?
It's an old term for an implementation strategy. Blueprint -> prototype -> goLive (if you want to say it in one sentence). How should I set priority for Printing say like user, teamlead, project manager? There's nothing like "priority" settings for spool processes. Just define more (profile parameter rdisp/wp_no_spool) processes so people don't need to wait. Using Tc SGEN I have generated 74% job and later I have terminated the job. I wish to start generating from where it stopped I have refreshed but to no chance nothing was done. How should I further proceed so as to complete the remaining job.. Start SGEN again and select the same you have selected before. It will popup and ask if you want to start from scratch or generate the just the remaining.
AS: Is just a dialog instance. CI: Is Dialog instance + Database Instance. What is Transport domain and Domain controller? TD: is the collection of transport controller, trans directory and all other systems in the group. TC: A system which will have trans directory, and in which the total landscape is designed and maintained. in stms you can see all these. *-- Suneel What are SNOTES ? How to apply them in SAP ? The name of the transaction is SNOTE. A "note" in general is a hint, documentation, error/bug description and may contain code corrections, that are applied with the transaction SNOTE. What is OSS ? OSS is the old name of the nowadays "sapnet" which contains everything you need to run SAP a program, patches, installation/upgrade documentation etc. What are different modules used like EP, XI, CRM ,BW, etc? Those are not different modules but different products. EP = Enterprise Portal XI = Exchange Infrastructure CRM = Customer Relationship Management BW = Business Warehouse (that is the old term), it's now call BI (Business Intelligence) What is the correct use of SPAM, SAINT, SPAD and SPDD transactions. When should we use each? SPAM is for installing support packages, SAINT is used to install new addons. SPAD is for creating printers (I assume you meant SPAU) and SPDD is for adjusting modification to dictionary objects. Is it possible to update Support Release packages from OS level? No - you can import them but the full process will require additional steps the tools "tp" and "R3trans" are not aware of. The way is to use SPAM - but SPAM has the possibility to schedule those imports in the background. After doing any Support Package update in SPAM, are there any further steps to carry out for this update to take effect?
Referenced Links: http://sap-img.com SAP (Systems Applications Products in Data Processing) B.A.S.I.S. (Business Application Systems Integrated Solutions) ABAP (Advanced Business Application Programming Language)