Solution for SAP* can't login into Newly Created Client and client copy

Login into 000 client and hit RZ10 transcation and select Instance profile and click Change and set new parameter login/no_automatic_user_sapstar   and value 0
now save and activate. and then stop and start Central Instance from SAP Console.
then try to logoin SAP* with default password and try to do client copy.

if everything goes fine this is the result screen for client copy

ECC6.0 installation error

When I installing ECC 6.0, it through me an error  code 103 at the 19 phase (Import ABAP), guys this error is really piss me off, and I tried Goggling for help, even though it can’t fix it but help me to think more in depth on this error and finally I found the problem is at lack Physical /Virtual memory. Then I just clear it by using Disk Cleanup and then I press retry button to continue the installation process and it goes smooth and finally installation of ECC6.0 is successfully installed.

Task for Security Experts

On Role Management:

Create a single Role with T-codes :
                                             SU01(only display permission)
                                             SU10 (with full authorization)

Result must be :

When user hits SU01 , he can access display option only, and rest will be in disable mode.
When the same user  hits SU10 the user must have full access like (create,delete,display,change,..)

okay friends try it and let see how many of  you are really good in Role Management

 <<<  AltheBest  >>>   

SAP-RECOMMENDED SYSTEM MONITORING TASKS

Frequency	Task	Transaction Code or UNIX Command
Daily	SAP: CCMS System Monitoring (General Monitoring Functions)	(See Note)
	SAP: Checking the System Log	SM21
	SAP: Output Devices in the SAP Spool System	SPAD
	SAP: Checking Spool Output Requests for Errors	SP01
	SAP: Checking Work Process Status	SM51
	SAP: Checking for ABAP Short Dumps	ST22
	SAP: Checking for Update Errors	SM13
	SAP: Checking Lock Entries	SM12
	SAP: Checking Batch Input Sessions	SM35
	SAP: Checking Background Jobs	SM37
	Oracle: Backing Up and Checking the Database	DB13
	Oracle: Backing Up and Checking Offline Redo Log Files	DB13
	Oracle: Monitoring Database Growth	DB02
	Oracle: Checking the Alert File	ST04
	Oracle: Monitoring the Archive Log Directory	DB12
	Oracle: Evaluating Results of the DB System Check	DB16B
	Oracle: Checking and Creating CBO Statistics	DB13
	HP-UX: Monitoring File Systems	ST06
	HP-UX: Checking the Operating System Log	(See HP-UX documents)
	HP-UX: Checking Swap Space	ST06
Weekly	SAP: TEMSE Check	SP12
	Oracle: Searching for Missing Indexes	DB02
	Oracle: Database Verification�Checking Physical Structure	sapdba
	HP-UX: File System Backup	tar
Monthly	SAP: Changing Administrator Passwords	SU01
	Oracle: Analyzing the Entire Database	analyze.cmd
	Oracle: Changing the Database Administrator Password	svrmgr30
Unscheduled/occasional	SAP: Checking the Transport Management System (TMS)	STMS
	SAP: Deleting Old User Master Records	SU01
	SAP: Changing Administrator Passwords	SU01
	SAP: Checking User Activities	SM04
	SAP: Scheduling Jobs	SM36
	Oracle: Extending the Database (Adding Data Files)	sapdba

TMS for single system landscape

Go 000, User : DDIC  and hit >STMS --> here it will ask for domain controller -- give self domain ---> Domain controller has been assigned .

Now again goto STMS--> System overview-->SAP SYSTEM -->Create ->Virtual system--- give name V<SID>
till this point your domain controller is created and virtual system is created .Next our aim is to setup STMS

again goto STMS-->transport routes--> change --> configuration-->statndard configuration ---> select second option (development and productino System ) because here your dev system will your own system and virtual system would be production system .

---> pop up will come ---> give DEV - SID and Productino SID--- it willl automatically create the route .

Save this and exit.


This is the way We can set single system landscape.

TMS Configuration Steps

Development system is always domain controller

2. Logon to Client :000

User: DDIC.

Pwd: ******

3. Put a T-code (se06) in the command field.

4. Click standard installation and click post installation (yes)

5. Put a T-code (STMS) in the command field and give a description then save it.

6. Click System overview push botten, click extras option from the menu and click Distribute and activate configuration. (Yes)

7. Back to the stms main screen and click Transport routes from the push botten.

8. Click Configuration button from the Menu.

9. Click Distribute and activate from the configuration menu.

10. Now your sap system is activate in domain controller.

11. Now logon to QAS system.

12. Client: 000

User: DDIC

Pwd: ****

13. Put a T-code (se06). In the command field.

14. Click standard installation and click post installation (yes)

15. Put a T-code (STMS) in the command field.

16. Click other Configuration push butten in the bottom of appear screen.

17. Give information about development system. Example: tisdev, 00

18. Then save it. Ok

19. Now QAS is waiting for include domain controller.

20. Logon to Development system.

21. Click system overview push butten.

22. Click sap system from the menu.

23. Select the QAS systems.

24. Click Approve butten from the sap system menu.

25. Now QAS is member system of domain Controller.  (Development system).

26. Suppose if you want configuring Production also, following the same step in the QAS.


Source from : http://www.saptechies.com/stms-configuration-and-transport-route-configuration/

ABAP and BASIS patch update error screen shots