What is ECC? Where to find the installation steps of ECC 5/6.0 with SQL as database and on windows platform with the steps including Solution Manager installation?
http://service.sap.com/instguides
ECC means Enterprise Central Component.
There are all the relevant installation guides. You NEED SAPNet access because without a registered and licensed SolMan installation number you will not be able to generate the SolMan key for the ECC 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 systemsbecause it has notes, patches etc.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now….I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ……
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in ‘old’ system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to ‘new’ system.
(This results in the entries being populated in transport table AQTDB in ‘new’ system).
Step 3. Run RSAQR3TR in ‘new’ system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled ‘dataset with imports’.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn’t find the queries, so ran RSAQR3TR one more time, this time specifying ‘Copy Standard Area -> Global Area’.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
SAP Message : TP_CANNOT_CONNECT_SYSTEM
Using spam, trying to import SPAM UPDATE, I get the above message together with TP_INTERFACE_FAILURE.
1. tp works fine when I am doing transports (tp import devk90000 qas client=400 u1 or addtobuffer).
2. niping -t SELFTEST works fine
I worked through notes 44946 and 96907, but could not resolve the issue.
The support packages have been uploaded from the DEV box into the QAS queue. The DEV and QAS boxes are in the same centre on the network, by fibre. I am working on QAS.
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.
It seems like a lot maybe, but it only takes a couple of minutes to perform.
SAP Learning 