Transports and UpgradeMeaning behind those unconditional tp command modeanyone tell me what's the meaning behind all those unconditional mode U1 or U126 or U148 or anything?tp import transportrequest clientxxx U1tp import transportrequest clientxxx U126tp import transportrequest clientxxx U148The 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. Transport guide Tips for Different SAP Objects You may be wondering if you can transport certain SAP objects, and if possible, how? Here are tips for different objects: 1 LSMW There are 2 ways for transporting LSMW data from a system to another. 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 = R3TRObj = TABUObject name = Name of your tableDouble-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 QueriesQueries, 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 = R3TRObj = TEXTObject name = TEXT,,ST,Example : R3TR / TEXT / TEXT,YMM_MEDRUCK_MAIN_16_EC,ST,FYou 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. The latter part BASIS will take care. Transport Request within same Server Different Clients I have 3 clients under one SID (dev 130,140,150). And we have more than 400+ transport requests in client 130. How can we transport these requests to other clients of 140 & 150. If I want to use tcode SCC1, that can be done only one tran. request at one time. Do I need to write a script within unix? SAP 4.6COracle 9.2AIX 5.2Try STMS.Click on the "import overview"Double click on your target systemClick "refresh"Click on "import all request" or ctrl+F9Specify the target client Execute the transportDone...But this will import all request.....thousands of them...You can use Extended Transport Control.Extended Transport Control is another way to set up the Transport Route so that the route is system and CLIENT specific. 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. Find transports imported into system by search criteriaTo find transports imported in a particlar system log into it,1. Use transaction se16A D V E R T I S E M E N T2. Table name is E0703. Table contents4. Enter your search criteria, by Name, Date, Time, etc.Good to use if you suspect a problem in your system and want to trace back transports that went in that possibly could have caused the fault.Transporting a Request From OSTo import a transport request from OS .# cd /usr/sap/trans# tp addtobuffer pf= # tp import pf= Find Your SAP Transport Request Number Even If You Forgot If you happend to be one of those who forgot the transport request number of your abap program.You can easily find it via the Versions Management.Steps :-Transaction SE38Filled in your ABAP program name.Then click Utilities -> Versions -> Version ManagementSAP system will display this sample list :- Versions: Report source ZPROGRAMVersion Cat Fla SAP Rel. Arch Request Date Time AuthorVersion(s) in the development database:X activ X 46X 01.08.9999 15:21:56 SAPVersion(s) in the version database:X 00002 46X ABCD123456 01.08.9999 15:52:43 SAPX 00001 S X 46X 00.00.0000 00:00:00 Comparing SAP Objects You can compare the IMG setting between two systems using OY19.Comparison can be made for individual application components or all the application components.How To Do the TMS Configuration?We have two systems with version ECC 5.0A D V E R T I S E M E N TThe SID is XY1 - Development & Quality XY6 - ProductionNow 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 0002. Goto SE06.3. Click Post installation activities4. Goto STMS5. It will ask for Domain controller name.6. Enter DOMAIN_ as domain controller name and enter the description. 7. Click Save buttonSteps to add the other system with Domain controller----------------------------------------------------1. Login to system with sap* in client 0002. Goto SE063. Click Post installation activities4. Goto STMS5. It will ask for Domain controller name.6. Enter System ID of the Domain controller7. Enter DOMAIN_ as domain controller name and enter the description. 8. Click Save button 9. Login to Domain controller system 10. Approve the added system. Post Installation Steps For ECC 5.0 What are the post installation steps after I have installed the Central Instance and Database instance?Initial Consistency CheckSM281. Logon to the newly refreshed SAP system and run transaction SM282. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.Edit Batch Jobs1. Set the fields as followsJob name: RDDIMPDP*User name: *Job Status: Released and Ready checked off, all others uncheckedFr: 01/01/0001To: 12/31/9999Or after event: *2. Press to execute the query3. Highlight the first job in the list and press the + to change the job.4. Examine the Exec Target field.a. If the box is empty, press to exitb. If the box is not empty, then clear out the contents so the field is blank and press + to save5. Repeat Steps 3 and 4 *for* each additonal job listed.Workbench Organizer Reconfiguration1. Logon on to client 000 of the newly refreshed system with DDIC.SE061. Select the Database Copy or migration option2. Press the Post-installation Processing button.3. When prompted Do you want to re-install the CTS?, press the Yes button4. When prompted *for* the Source System of Database Copy?, make sure that the of the production system is selected. Press the checkmark button to continue.5. When prompted Change originals from PRD to QUA?, press the Yes button6. When prompted Delete TMS Configuration?, press the Yes button7. When prompted Delete old TMS configuration?, press the Yes button8. When prompted Delete Old Versions of transport routes?, press the No buttonTMS Configuration1. Logon on to client 000 of the newly refreshed system.STMS1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed2. The information on *this* screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description *for* the system and press +S to save. Otherwise, press the Other configuration button and manually configure.3. From the Overview menu, select Transport Routes4. From the Configuration menu, select Adjust with Controller5. Press the Yes button when prompted *if* you want copy the transport routes from the controller.Import Printers1. Logon on to the production client of the newly refreshed system. STMS2. Press to go to the *import* Overview.3. Double click on the of the newly refresh system4. From the Extras menu select Other Requests, then Add.5. In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press to save.6. Select the transport that was just added to the queue and press + to start the import.7. In the Target client box, enter the productive client of the newly created system. Press to save.8. Press the button to start the transport.Client ConfigurationSCC41. From the Table view menu, select Display -> Change2. When warned that the table is cross-client, press the checkmark button.3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)4. Define client as follows:Client role: TestChanges and transports *for* client-specific object: Changes without automatic recordingClient-independent object changes: Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowed5. Press +S to save.6. Repeat steps 4 through 6 *for* any additional clientsSet System Change OptionSE061. Press the System Change Option button.2. Set the global setting to Modifiable3. From the Edit menu, select Software Components Modifiable4. From the Edit menu, select Namespaces Modifiable5. Press +S to save.Import UsersSTMS1. Press to go to the Import overview2. Double click on the of the newly refreshed system.3. Press to refresh the list of transports4. Locate the transport in the list containing the user exports done before the start of the refresh.If the transport is NOT in the list, then from the Extras menu, select Other requests then Add. Enter the transport number and press . Then press the Yes button to add the transport.5. Highlight the transport and press the Import request icon .6. At the client *import* screen, enter the target client and then press the Import button7. Press to confirm that the *import* will proceedSCC71. Run the Post Client Import Processing2. The transport number should be the same as that of the transport started in STMS3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.4. Press +S to save.SM371. Set the fields as followsJob name: CLIENTIMPORT*User name: *Job Status: All options checkedFr: 01/01/0001To: 12/31/9999Or after event: *2. Highlight the job that was created by SCC7 and press + to modify the job.3. Press the Step button.4. Select the RSCLXCOP line and press ++ to modify that step.5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).6. Press +S to save the changes7. Press to go back to the main job screen.8. Press the Start condition button.9. Press the Immediate button.10. Press +S to save the changes11. Press +S again to save all the changes to the job.12. Job will start immediately once saved. Press to refresh the list of jobs13. Continue to press every once in a *while* to update the status of the job. Do not *continue* until the job is completed sucessfully.SCC41. From the Table view menu, select Display -> Change2. When warned that the table is cross-client, press the checkmark button.3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)4. Set the Protection to Protection level 15. Press +S to save.6. Repeat steps 3 through 5 *for* any additional clientsDeleting Source System ProfilesRZ101. From the Utilities menu, select Import Profiles then Of Active Servers. (Note: All application servers of the target system must be started)2. If the Display Profile Check Log screen is displayed, press to leave *this* screen.3. Select the Profile field and press to bring up a list of profiles.4. From the list select one of the profiles associated with the source production system.5. From the Profile menu, select Delete, then All versions, then of a profile.6. When prompted, press the Yes button to delete all version of the profile7. When prompted to delete the file at the operating system level, press the No button.8. Repeat steps 3 through 7 *for* all additional profiles associated with the source systemReconfigure Operation ModesRZ041. From the Operation Mode menu, select Timetable2. Select Normal Operation and press the Change button.3. Highlight 00:00 in the left hand column and press the Delete Assignment button4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.5. Once all the assignments are deleted, press +S to save.6. If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.7. Press to go back to the main RZ04 screen.8. Right click on one of the listed Operation modes and select Delete9. Press the Yes button to confirm the deletion.10. Repeat steps 8 through 9 *for* any additional operation modes11. Press to create a *new* operation mode.12. Enter a name and *short* description *for* the operation mode13. Press +S to save.14. Press to create a *new* Instance15. From the Settings menu, select Based on current settings, then New Instances, then Set16. Press to go back to the main RZ04 screen.17. Press the Yes button to save18. From the Operation Mode menu, select Timetable19. Select Normal Operation and press the Change button.20. Highlight the 00:00 at the top and press 21. Highlight the 00:00 at the bottom and press 22. Press the Assign button.23. Press to select the operation mode created above.24. Press +S to save.Delete Update FailuresSM131. Set the fields as followsClient: *User: *From data: 01/01/0001From time: 00:00:002. Press to display the list of outstanding update requests3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing to select all records, then selecting the Update Records menu, then Delete.4. Press the Continue button to confirm the deletion.Delete Batch Input SessionsSM351. From the Edit menu, select Select All2. Press + to delete all the batch input sessions.3. Press the checkmark button to confirm4. Press the Yes button to start the delete.Reorganize SpoolSPAD1. From the Administration menu select Clean-up Spool2. Check all check boxes and enter 0 *for* minimum age3. Press the Execute button4. Once complete, press twice to get back to the main SPAD screen5. From the Administration menu select Check Consistency6. Press the Delete All button.SP121. From the TemSe database menu, select Consistency check2. When the check is complete, press the Delete All button. Delete Invalid Background Control ObjectsSM611. Press to *switch* in to change mode2. Press the Cleanup List button.Restrict Outgoing Email and FaxesSCOT1. Double click on the green Fax entry2. From the Supported Address Types area, press the Set button that is beside Fax3. In the Address area, ADJUST AS NECESSARY4. Double click on the green SMTP entry5. From the Supported Address Types area, press the Set button that is beside Internet6. In the Address area, ADJUST AS NECESSARYAdjust RFC connections.SM591. Expand the TCP/IP connections section2. Double click on the first entry listed3. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system. Make changes as necessary.4. Press the Test Connection button to test the connection5. Press Press +S and then to save and *return* to the list of RFCs.6. Repeat steps 1 through 5 *for* each additional RFC connectionConvert Logical SystemsUnder no circumstances perform *this* procedure on a Production systemBDLS1. When warned to read the documentation, press the checkmark button.2. In the Old logical system name box, press .3. Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)4. In the New logical system name, enter what that logical system name should be called on *this* newly refreshed system (i.e.WIITRN400) Note: Ignore Error/Warning about duplicate system by clicking on the check mark.5. De-select the Test Run and Existence check on *new* names in tables options6. From the Program menu, select Execute in background7. Press the checkmark button when asked to select a spool device8. Press the Immediate button when asked *for* the schedule9. Press +S to save10. Use SM37 to monitor the job11. When job is complete, repeat steps 2 through 10 *for* any additional logical system names that need to be changed.Adjust Logical Systems namesSALE1. Expand Sending and Receiving Systems, then Logical Systems2. Click on the execute icon beside Define Logical System3. Press the checkmark button to confirm that the change is cross client4. Allow Certains Settings to be modifiable(Refer to Note 356483 *for* more Details)SM541. Enter V_T001B in the Table/View box.2. Select the Generated Objects option.3. Press the Create/Change button.4. Enter any access keys *if* requested5. Change the Recording routine to no, or user, recording routine.6. Press +S to save7. Press *if* warned that you are changing a function group that doesn't belong to you.8. You are prompted *for* transport. Create a *new* local transport.9. Repeat steps 1 through 8 *for* the following objects. You can specify the same transport you created above.V_T001B_GLV_T093B_01V_T093B_02BSI Configuration (R3 HR Systems only)SM591. Expand TCP/IP Connections2. Highlight BSI70-US-TAX and press the Change button3. Change the program field to \\\sapmnt\\SYS\EXE\RUN\TF60SERVER.EXE4. Double check the target host and gateway point to the correct server5. Press +S to save6. Press the Test connection button to test. If the connect is not successful, take the necessary steps to resolve the issue.SE381. In the Program field, enter RPUBTCU02. Press to execute3. Select option BSI version 7.04. Press to execute5. BSI should *return* tax calculations. If there are errors, take the necessary steps to resolve.Reconfigure DB13 scheduleDB131. Using the print out created before the refresh, recreate the DB13 calendar.Client ConfigurationSCC41. From the Table view menu, select Display -> Change2. When warned that the table is cross-client, press the checkmark button.3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)4. Define clients as follows depending on client roleDevelopmentClient role: CustomizingChanges and transports *for* client-specific object: Automatic recording of changesClient-independent object changes: Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowedQuality AssuranceClient role: TestChanges and transports *for* client-specific object: No changes allowedClient-independent object changes: No Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowedTrainingClient role: EducationChanges and transports *for* client-specific object: No changes allowedClient-independent object changes: No Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowedSandboxClient role: TestChanges and transports *for* client-specific object: Changes without automatic recordingClient-independent object changes: Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowed5. Press +S to save.6. Repeat steps 4 through 6 *for* any additional clientsSet System Change OptionSkip *this* section of the system is a Development or Sandbox System.SE061. Press the System Change Option button.2. Set the global setting to Not Modifiable3. Press +S to save.Release Background JobsCurrently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled). Where To Find Deleted Transport Request Logs Is there any way to find out deleted transport requests logs?If you have deleted from SAP level. Then you need to check at the OS level in /usr/sap/trans/log directory else you can check for the SLOG and ALOG folder also. If total request has been deleted then you can also do the transport manually at OS level.orIf 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 /log. The logs are named in the format: ., where step ID is a single alphabet denoting a particular transport action. Transport Tables between ClientsUse report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system. A D V E R T I S E M E N TStart RSCLCCOP from the target client which the users and authorizations should be copied.Do not use this report if the target client contains some users and authorizations you want to preserve. Copying table entries from client 000I need to copy table entries from client 000. I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries. The simplest way is to go into the table through SM31 Then in your top row of buttons there should be one called 'utilities' from here select 'adjust', Then select the client that you want to compare/copy from (you need to have an RFC destination set up). This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories: ML Differences, logon client entry MR Differences, comparison client entry L Entry only exists in logon client R Entry only exists in comparison client Identical entries (M) Differences only in hidden fields You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table. That should do the job. SAP Tablespace sizes in large databases -----Original Message----- Robert and others following the thread,First a little background on extents in our production system. We created the instance about 4 months prior to going live. As man of you know, getting down time during the last few months is nearly 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.-----Reply Message----- 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 17extents. 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 hard-and 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? Users Profiles and PasswordDifferent methods to Lock or unlock SAP usersA D V E R T I S E M E N TI 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 usersor Execute program EWULKUSR in SE38or 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.orProbably 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 = and BNAME != ; You can replace != with if you want. To run this from an OS command line, you would type: Unix/Oracle 8---> sqlplus internal @ NT/Oracle 8.0---> plus80 internal @ NT/Oracle 8.1---> sqlplus internal @s Unix/Oracle 9:--> sqlplus /nolog @ NT/Oracle 9-----> sqlplus /nolog @ In UNIX you can cron the script to schedule it. In NT you can schedule it as a task.orThis 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. This is considered as DoS (Denial of Service). Changing the default password for sap* user You are trying to change the password for sap* user, however when you go into su01 and enter sap* as the user name, the following message is displayed, user sap* does not exist.You can delete the SAP* user using ABAP code :-Delete from usr02 where bname = 'SAP*' and mandt = '***';Where '***' means your client no.Then login to your client using password SAP* and password PASSHowever, if you delete it, then it will automatically created once again with password PASSThe userid, SAP*, is delivered with SAP and is available in clients 000 and 001 after the initial installation. In these 2 clients, the default password is 07061992 (which is, by the way, the initial date when R/3 came into being...). It is given the SAP_ALL user profile and is assigned to the Super user group. When I say it is "delivered" with SAP, I mean that the userid resides in the SAP database; there are actually rows in the user tables used to define userids.If you delete the userid, SAP*, from the database, SAP has this userid defined in its kernel (the SAP executable code that sits at the operating system level, i.e., disp+work). When this situation exists, the password defined in the SAP code for SAP* is PASS. This is necessary when you are performing client copies for example, as the user information is copied at the end of the process. You can sign into the client you are creating while a client copy is processing using SAP* with password PASS (but you should have a good reason to do this - don't change anything while it's running).Anyway, if the SAP* userid is missing, you can sign in to the client you want and simply define it using transaction SU01 and, as I stated above, assign it to the SUPER user group and give it the SAP_ALL profile. You define its initial password at this point. If you've forgotten its password and don't have a userid with sufficient authorization to create/change/delete userid, then you can use the SQL statements to delete it from the database and then you can use SAP* with PASS to sign back into the client you want to define it in and recreate it.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) Mass Maintenance of Users Profiles Goto transaction code SU10Select your SAP User by Address data or Authorization data.With the users you want to change selected, click :-User -> Change -> ProfilesFilled in the Profiles and click save.How can I create multiple User Id at RandomWe usually created Id though SU01, it only one by one.Can I create multiple user id having same profile at once.Yes you can, use tcode SCAT. First, make sure your client setting (SCC4) is enabled with ' X eCATT and CATT allowed'. Just in case your Production disabled this.- Then, you need to create a simulation (test case) of creating new user id by calling tcode SU01 later. - Test case must start with Z, example ZCREATE_NEW_USER. Create this case, put title and choose component as BC (basis components). - Save and choose Local if you dont want to transport it or choose a dev. class (example ZDEV) if you want to transport it later.- Go back and click Change button. Then key -in Object as example SU01, and choose Record button on top. When it prompts to enter Transaction code, key in SU01 (if for roles, key-in PFCG) and begin recording. As usual in SU01 create 1 user id, dept field, password, roles, group and so on. - Make sure you press Enter on each field because we want to capture the value/object and SCAT is a bit stupid if you become familiar later....but still useful...indeed. - You will see a clock on the bottom which means the recording process is on going. Once done, click Back button and press End button to end the recording.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. Hoping this will help you. I have done (Sap 4.6C) this to create thousands of user ids and also thousands of roles/profiles (pfcg). I heard with Sap 4.7, the SCAT has so many extra features.....Correct me if i'm wrong elsewhere.....just shared my experience.