Post Install Steps for EP7.0

Hello Guru's.
I am looking for a listing of needed Post Install Steps for EP7.0. I have the installation guide for NW2004's SR1 ABAP+JAVA on AIX: Oracle and the NW2004s Master Guide. Is there any thing else I should have? I am not doing the actual install, just the post steps.
Thanks,
Chris

Hi,
Start with this: http://help.sap.com/saphelp_nw2004s/helpdata/en/a9/76bd3b57743b09e10000000a11402f/frameset.htm
Marc.

Similar Messages

ABAP & Java Preview install done. Need Post install steps for XI.

Hi
Please excuse for the most basic question.
From the trial downloads, I've installed the
ABAP and Java and would like to know the
post-install steps for activating and configuring
the Exchange Infrastructure component and
subsequent configuration
I've installed on the local host along with the
Microsoft Loopback Adapter. What should be
the connection parameters for the Visual
Administrator?
Any help is appreciated. Thank U.
Rajendra.

Hi Rajender
I think no question is difficult or basic .The severity depends on whether you know it or not,in other terms your comfort level.
Coming back to your post:Go through the below link
https://websmp103.sap-ag.de/~sapidb/011000358700001697502004E.PDF
Re: XI INSTALLATION and POSTINSTALLATION
If you need the XI configuration guide then visit:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dcc97
Any issues feel free to ask
Reward with suitable points:

Post Install steps for htmldb 1.6.1

I am done with a new installation on RHL
- 10g DB install on ORACLE_HOME1
- Standalone 9.0.4 Http Server for the CCD on ORACLE_HOME2
- Install of HTMLDB 1.6.0 and later patch of 1.6.1 error free
I am following the post installation steps for configuring the DAD and I am unable to find the file "wdbsrv.app". I am on page 22 of the HTMLDB installation guide (B14498_02.pdf)
How do I configure the DAD and up my htmldb.
thanks
-/srinath

I am still having issues .....
I get INVALID LOGIN CREDENTIALS - logging as ADMIN/HTMLDB in the /pls/htmldb/htmldb_admin page
I unknowingly unlocked and changed the passwords of HTMLDB_PUBLIC_USER and other users
to "htmldb", but IMO that should'nt matter because I used "htmldb" as the password during
the initial install too. So....
the access log has this:
172.16.4.57 - HTMLDB_PUBLIC_USER [01/Apr/2005:13:13:33 -0800] "POST /pls/htmldb/wwv_flow.accept HTTP/1.1" 302 165
172.16.4.57 - HTMLDB_PUBLIC_USER [01/Apr/2005:13:13:33 -0800]
"GET /pls/htmldb/f?p=4550:10:1949690027032632943&notification_msg=Invalid%20Login%20Credentials/344577F9B4C4782C9D0F6CCC888077AB/ HTTP/1.1" 200 6688
172.16.4.57 - HTMLDB_PUBLIC_USER [01/Apr/2005:13:13:42 -0800] "POST /pls/htmldb/wwv_flow.accept HTTP/1.1" 302 165
172.16.4.57 - HTMLDB_PUBLIC_USER [01/Apr/2005:13:13:42 -0800]
"GET /pls/htmldb/f?p=4550:10:1949690027032632943&notification_msg=Invalid%20Login%20Credentials/344577F9B4C4782C9D0F6CCC888077AB/ HTTP/1.1" 200 6688
my dad looks likes this:
<Location /pls/htmldb>
SetHandler pls_handler
Order deny,allow
Allow from all
AllowOverride None
PlsqlDatabaseUsername HTMLDB_PUBLIC_USER
PlsqlDatabasePassword htmldb
PlsqlDatabaseConnectString biz1:1521:e5dwhdb1 SIDFormat
PlsqlDefaultPage htmldb
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDocumentPath docs
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlAuthenticationMode Basic
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
</Location>
I tried this from the FAQ section but get this:
SQL> begin
2 wwv_flow_api.set_security_group_id(p_security_group_id=>10);
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> ed /tmp/z
wwv_flow_api.set_security_group_id(p_security_group_id=>10);
begin
wwv_flow_fnd_user_api.create_fnd_user(
p_user_name => 'myself',
p_email_address => '[email protected]',
p_web_password => 'mypasswd') ;
end;
ERROR at line 1:
ORA-20001: Unauthorized access (wwv_flow_api.set_credentials not set).
ORA-06512: at "FLOWS_010600.WWV_FLOW_FND_USER_API", line 19
ORA-06512: at "FLOWS_010600.WWV_FLOW_FND_USER_API", line 429
ORA-06512: at line 2
===============================
thanks in advance for your insights
-/srinath

Post install steps for 11i on XP

Please advise on post install steps after 11i installtion on XP based OS/
ALso what are the steps/services to be completed before trying to login into Apps
Thx much

as such nothing is required as a POST INSTALL on XP and not even a "Restart" sounds strange but this is how simple it is to install on Windows.
anyways... there r two ways to log on to Apps.. one is as mentioned by using the http://........ stuff where u use /pls/ to run the apps. Sometimes (more often) it doesn;t work well wtih XP and therefore the alternative is to runt he servlet instead.
this is how it is:
http://host.domain.com:8002/dev60cgi/ifcgi60
I am considring that u didn;t change the default port assignments. the above shud prompt u to download n install "jinitiator" which is Oracle's JVM (required). Install it and u shud be able to see the logon screen.
Use "sysadmin/sysadmin" or "operations/welcome" as deafult "username/password" combination.
HTH.
Rajeev.

Post Install steps for opatch 9218789 while upgrd DB from 10g to 11.2.0.1

Hi,
I am little bit confused with patch application steps of opatch 9218789 , while upgrading my db from 10g to 11.2.0.1
I have setup my new 11g ORACLE_HOME , created old nls directory , now applying the opatches mentioned in the doc Interoperability Notes Oracle EBS R12 with Oracle Database 11gR2 (11.2.0.1) [ID 1265232.1].
Now while applying the patch 9218789 as a prerequisite steps it says to drop the objects in MGDSYS schema by running catnomgdidcode.sql. i had run that and applied the opatch.
Now as part of the post installation steps it says to recreate the objects using sqls as below.
Load the following package in CTXSYS schema:
SQL> @?/ctx/admin/dr0ddl.plb
Load the following packages into the database after connecting as SYSDBA:
cd $ORACLE_HOME/rdbms/admin
SQL> exec dbms_metadata_util.load_stylesheets;
SQL> @?/rdbms/admin/catnomtt.sql
SQL> @?/rdbms/admin/catnomta.sql
SQL> @?/rdbms/admin/dbmsmeta.sql
now my question is from which oracle home i have to run these scripts from. 11g or 10g.
Request your help on this.

Hi srini ,
thanks for your reply , but when i run the scripts from 11g home then packages are been created with compilation errors can i ignore those and go head with upgradation.
Thanks.
Puneeth.

Post Install steps for R12.1.1

Hi,
I have successfully installed R12.1.1 in OEL4U5.
are there any steps to be done after installing R12.1.1 like should i need to re-compile packages, forms and reports etc.. if yes, what are the steps?
(or)
do i need to apply any Patches ater installing 12.1.1. if so, what are they?
regards,
Charan.

Hi,
are there any steps to be done after installing R12.1.1 like should i need to re-compile packages, forms and reports etc.. if yes, what are the steps?No steps are required after installing R12 (you do not need to compile any object).
do i need to apply any Patches ater installing 12.1.1. if so, what are they?Login to Metalink, and navigate to "Patches & Updates" tab, click on "Recommended Patches Oracle eBusiness Suite R12" and "Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs".
Regards,
Hussein

PI 7.11 sp5 post install steps - SLD update hangs in IE browser

Hello gurus,
This is my first shot at installing PI ever. We decided to go with PI 7.1 EHP1 and SP5. I think the latest may be SP6.
At any rate, we're doing this on AIX 6.1 and Oracle 10.2.0.4.
I followed the install Guide exactly. Did the sapinst, oracle and patch. Next, I manually updated the KERNEL, IGS , JVM, Then I updated SPAM, SAP_BASIS, then all the other abap components. Then did JSPM and all those components. Everything matches SP5 for PI 7.11
https://websmp204.sap-ag.de/maintenanceNWPI71
SAP_ABA     711     0005     SAPKA71105
SAP_BASIS     711     0005     SAPKB71105
PI_BASIS     711     0005     SAPK-71105INPIBASIS
ST-PI     2008_1_710     0003     SAPKITLRE3
SAP_BW     711     0005     SAPKW71105
ST-A/PI     01M_BCO710     0001     SAPKITAB8F
Now I'm doing the post install steps that are in the instguide. THere are tons of steps, but let me go over the big ones and where I'm having a problem:
READ ALL THESE NOTES:
Note 1309239 - Configuration Wizard: PI NetWeaver initial setup
Note 1286149 - Configuration Wizard: PI Self Test for NetWeaver
Note 1107808 - Collective Note: Configuration Wizard 7.1
Note 1286428 - Configuration Wizard: PI Wizard Templates overview
Note 1115280 - PI CTC: Running SAP NW for PI in a different client
At this point, based on being at PI 7.11 and SP5, I did the client copy. from 000 SAP_UCUS to my new 400 client. Then I did 001 SAP_USER to my new 400 client.
Then I followed the steps to link the java UME from 001 to 400. No problem after restarted SAP, it goes to 400.
Now, the next step as I see it is to run the initial config wizard out of NWA. I did that, no errors.
My problem is when I get to updating the SLD. I started at cimsap 1.5.42 and CRDelta 5.0....
I updated cimsap to the cimsap51509_1-20005942.zip which took me to 1.6.9
Next, I tried to import CRDelta51509_1-20005942.ZIP. I "browse" to find it during the import, but when I click the "IMPORT" button, my browser hangs...
I don't even get to the next page where it would be one more "warning/info" before I could really start the import.
I didn't find anything in the work directory or the cluster/server0/log directory.
I search all through SDN/OSS but could not find anyone who had this problem.
Where did I mess up? Are there other config wizards I should have run before I tried to update the SLD?
--NICK

Hey Caio,
Thanks for the response but it doesn't actually answer my question. But to that point, for a "basic" PI post install, which of the NWA config tasks would you run other than the "initial config" ? And would you run them BEFORE you updated the SLD content (cimsap/CRDelta) ?
NW: PI - AS ABAP (Basic Configuration for Idoc, Proxy): Maintain
PI Adapter Engine in JPR Mode
PI Demo Client
PI Full Qualified Host Name
PI Self Test for NetWeaver
PI SLD Self Registration
Specifically, I did the SAPINST - ABAP/JAVA patches - Client copy - and THEN the initial config wizard (Setup a new local SLD, ). Also, during the initial config, I clicked the box marked "This SLD will be used as a name server for development" and my PI server hostname was already in the box marked "object server name". This config took about 30 minutes. I didn't see any errors or warnings. although I didn't view the log. I did go into Java JEE services and Filter for Services with name "XPI". All were green.
THEN I tried to update the SLD content.
any thoughts appreciated.
NICK

Post upgrade step for EP

HI Friends,
I have upgraded my EP from 6.0 to 7.0 successful with all component. ALos i am getting login screen. SO what are post upgrade step for EP.
Thanks,
Regards,
Sachin

HI ,
System restart
run the SICK verify the installation check
Check developer traces on the operating system. Log on to
Check the installed license and profile configuration (RZ10 and PFCG)
confirm the operation modes
Perform a client copy
Check the status of the SAP Web AS Java and the user SAPJSF
Check the rdisp/j2ee_start profile parameter
Check the current state of SAP Web AS Java using transaction SMICM
SAP Load Generator
Start SAP Load Generator (SGEN)
Regards,

Post Installation Steps for ERP add-on Inventory Manager 4.0

Hi,
I need to confirm what are the post-installation activities we must to perfom for ERP Add-on (Inventory Manager 4.0), besides de BC Activation. I did not find any information regarding the post installation steps for the ERP Add-on of Inventory Manager 4.0 (the installation guide for IM 4.0 on service marketplace does not remark the steps only explain the theorical part of the installation)... And we need to confirm if the steps are the same of Inventory Manager 3.2 Add-on or we must do an additional step?
Best Regards,
MC
Stephen Streeter Manju Venkatesha

Yeah...of course...
I forgot to specify it.
I install the first ERP 2005 SR2 on Oracle 10.2.0.2 and the other have to be installed on the same version of DB.
All installation are not MCOD.
This mean every installation has its own DB with different SID for every installation.
And of course I have at least doubled the space required by installer. Taken from sap notes the required space for ERP 2005 SR2 is about 90 GB.
The total space of mount point is about 500 GB....
Thanks
Dan

SCM 2007 Post Install Steps - Questions

Hello,
I'm installing SCM 2007 and have a questions on a coulpe of the post steps.
1. 5.18 BI-Specific Post-Installation Steps (pg 107 of install guide). Has anyone done these steps and can you explain them to me? It looks like it's wanting me to do a client copy. I already did one of those as part of the post insall steps. Are these steps to be done in the BI system or the SCM system. Thank you.
5.18 BI-Specific Post-Installation Steps
After you have installed the SAP SCM system , you need to perform the following post-installation
steps for BI ABAP.
Procedure
1. Import additional languages (optional).
2. Apply all Support Packages.
3. Create the logical system as follows:
a) Log on to the SAP system and call transaction SPRO.
b) Choose Integration with SAP components Integration via APO Core Interface (CIF) Basic Settings for
Creating the System Landscape Name Logical Systems .
Note
For more information about the conventions for the creation of logical systems see SAP
Notes 155009 and 423184.
4. Maintain a client.
5. Assign the logical system to the new client:
a) Call transaction SPRO.
b) Choose Integration with SAP components Integration via APO Core Interface (CIF) Basic Settings for
Creating the System Landscape Assign Logical Systems to a Client .
Note
If you need more than one client, repeat steps 4 and 5.
6. Log on to one of the new clients with sap/pass.The creation of the user sap can be disabled
with the parameter login/no_automatic_user_sapstar.
7. Install the liveCache according to the documentation Installation Guide SAP liveCache for NetWeaver 7.0,
available on SAP Service Marketplace at http://service.sap.com/install70.
8. Copy client 000 by using transaction SCCL with user profile SAP_CUST.
9. Set parameter login/system_client = <one of the new clients (e.g. productive
client)> in the default profile or in the instance profile. For more information, see SAP Notes
116432 and 116520.
Do not change this profile setting after you executed step 12.
10. Stop and restart the system in order to activate the default profile.
11. Log on to the new client that was set in step 10.
2. 5.21 Activating Services for the Web UI for SAP Supply Network Collaboration (SAP SNC). It tells me to look in Solution Manager to see which services I need to activate. Can someone describe where I find that in Solution Manager or which services I need to activate? Thank you.
5.21 Activating Services for the Web UI for SAP Supply
Network Collaboration (SAP SNC)
To be able to use the web user interface for SAP SNC, you must activate services with transaction
HTTP Service Hierarchy Network (transaction code SICF).
For more information, see the configuration documentation for one of the following SAP SNC
scenarios in SAP Solution Manager under:
n Solutions SAP for Automotive Scenarios Supplier Managed Inventory/Release Processing/Web-Based Supplier
Kanban Solutions
5 Post-Installation
5.22 Post-Installation Steps for SCM Replenishment Workbench for Store (SCMRWBS)
n Solutions SAP for Consumer Products Scenarios Responsive Replenishment
n Solutions SAP for High Tech Scenarios Contract Manufacturing Procurement/Supply Network Inventory/Work
Order Collaboration
Choose the chapter Basic Settings for SAP Supply Network Collaboration Maintaining Settings for Service and
Single Sign-On Activation
I appreciate any assistance - Thank you.
~TJ

HI,
Are you able to install SCM 2007?

Post installation steps for PI 7.0

Hi,
Can anybody send me the Post installation steps for PI 7.0?
Thanks in advance..
~Kumar

Hello,
 
We did PI Installation recently and version is 7.1
 
Steps are as under...
 
 1. Basic PI installation
 2. System checks after basic installation
 a. SM50
 b. SM21
 c. ST22
 d. SM12
 e. SM13
 f. SM37
 3. Unlock the 001 client for cross-client changes temporarily and set system timezone (STZAC)
 4. Change 001 client settings back to no changes allowed.
 5. Create BASIS team member accounts in ABAP Stack and assign SAP_ALL.
 6. Set directory permission for \usr\sap\trans directory on Transport Domain Controller system.
 7. Import profiles (RZ10)
 8. Add the 4 following entries in to the instance profile and restart instance(RZ10)
 a. DIR_TRANS =
hostname.domain.ext\sapmnt\trans
 b. icm/host_name_full = hostname.domain.ext
 c. login/system_client = 100
 d. icm/server_port_0 = PROT=HTTP,PORT=5<sysno>00,TIMEOUT=1800,PROCTTIMEOUT=1800 {SAP Note 1107808}
 9. Configure TMS in transport domain controller{PI DEV} (STMS)
 a. Add virtual system
 b. STMS in newly installed system and configure proper transport domain
 c. In domain controller approve the new system (STMS -> SAP system -> Approve)
 10. Get maintenance certificate and SAP license from service marketplace and apply in to the new system {ABAP and JAVA} (slicense and NWA)
 11. Kernel Update JSPM
 a. JSPM update
 b. Kernel update
 c. BC-FES-IGS update
 12. Support pack installation ABAP
 a. SPAM update
 b. Support packs update
 13. Support pack installation JAVA
 a. Apply support pack stack
 b. Apply support pack patches
 i. After JVM installation Error occurs apply MS windows KB973544 {SAP Note 1367498}
 c. Restart JSPM and continue patch installation
 14. Client copy from client 001 to X00 using profile SAP_ALL
 15. Create logical system and assign it to new client (SALE)
 16. Change UME target in JAVA to client X00.
 a. Enter URL as http://hostname.domain.ext:port/nwa
 b. Management -> Infrastructure -> Destination
 c. Logon data TAB change client to X00
 d. Restart JAVA Instance
 17. Create following users
 a. PIAFUSER, PIRWBUSER, PIISUSER, PIDIRUSER, PIREPUSER and PIAPPLUSER on the target SLD and new system manually and assign role/group SAP_SLD_CONFIGURATOR to them. {SAP Note 1309239}
 b. PISUPER in new system and assign appropriate roles in ABAP and JAVA
 c. SLD_DS_<SID> and SLD_CL_<SID> on target SLD {Use source system master password}
 d. JCoRFC_<SID> in new system
 e. Sapadm user in new system
 18. Assign roles and groups to BASIS team on JAVA Stack
 19. Create PUBLIC logon group (SMLG)
 20. Configure SLD collector job as sapadm (RZ70)
 21. Run Configuration Wizard
 a. Enter URL as http://hostname.domain.ext:port/nwa
 b. Configuration management -> Scenarios -> Configuration Wizard
 c. Select Initial Configuration and click Start.
 22. Create the JCoRFC connection.
 a. Enter URL as http://hostname.domain.ext:port
 b. Web Dynpro -> Content administrator -> Maintain JCo destination
 c. Fill in information for the following 4 entries using client X00 and JCoRFC_<SID> as the user {Make sure you note the distinction between Metadata and Model destinations when you are creating the destination}
 i. WD_ALV_METADATA_DEST
 ii. WD_ALV_MODELDATA_DEST
 iii. WD_MODELDATA_DEST
 iv. WD_RFC_METADATA_DEST
(Use dictionary Meta Data for the Metadata connections, use Application Data for the Model Data connections.)
(Use the master password for EXQ)
 23. Repeat for the remaining 3 JCo RFC destinations.
 24. Run PI Full Qualified Host Name Wizard {SAP Note: 1320707}{Make sure you check the host names for integration server and SLD}
 25. Create RFC destination in to ERP target system (SM59)
 a. Give Name PI_INTEGRATIONSERVER
 b. Connection type H
 c. In Technical settings TAB provide
 i. Target host = hostname.domain.ext
 ii. Path Prefix = /sap/xi/engine/?type=entry
 iii. User information is blank
 26. Setting SXMB_ADM ERP target system
 a. Open Integration engine configuration
 b. Goto -> Change Global Configuration Data
 c. Role of Business system = Application System {This is optional}
 d. Provide RFC destination name in Corresponding Integ. Server = dest://PI_INTEGRATIONSERVER
 27. Schedule Standard Jobs as SAPADM in client X00.
 28. SICF service to activate
 a. /default_host/sap/public/bc/pictograms
 b. /default_host/sap/public/bc/webicons
 c. /default_host/sap/public/bc/its/designs
 d. /default_host/sap/public/bc/workflow
 e. /default_host/sap/bc/ccms
 f. /default_host/sap/bc/webdynpro/sap/CTS_BROWSER
 g. /default_host/sap/bc/webflow
 h. /default_host/sap/bc/workflow
 i. /default_host/sap/bc/workflow_xml
 j. /default_host/sap/bc/xmb
 k. /default_host/sap/bc/ping
 l. /default_host/sap/xi/wsdl_sr
 m. /default_host/sap/xi/wsdl_url
 n. /sap/bc/webdynpro/sap/appl_soap_management
 29. Adjusting JNLP Heap size
 a. Open the Exchange profile through the link u201Cadministrationu201D from the web page of the Process Integration tools.
 b. Under the folder u201CIntegration Builderu201D click on the variable u201Ccom.sap.aii.ib.clientjnlp.j2se.maxheapsizeu201D
 c. Value = 1024
 d. Save the change and restart the J2EE instance of PI so that the new value can take effect.
 30. Create RFC destination for Advanced Adaptor Engine in sender ERP system(SM59)
 a. RFC Destination = AAE_<SID>
 b. Connection type = G
 c. Target Host = Host Name of AAE Server {PI Server}
 d. Service No. u2013 HTTP port number of AAE Server
 e. Path Prefix = /XISOAPAdepter/MessageServlet?ximessage=true
 f. Under Logon & Security use PIAPPLUSER with PI target systemsu2019 master password.
 31. Create RFC destination <SID>_ALE in ERP Source system with user ERQALEUSER {Make sure you have this user created in new installed system}
 32. Install External Driver Configuration in Process Integration 7.1 Using JSPM {SAP NOTE: 1138877}
 
Please let me know if I am missing anything there...
 
Cheers,
 
Yogesh

What are the post instalation steps?

hi,
i am fresher in SAP.anybody plz send me postinstalation steps.
regards,
jana

Hi All,
Rewards if useful.
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 Check
SM28
1. Logon to the newly refreshed SAP system and run transaction SM28
2. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.
Edit Batch Jobs
1. Set the fields as follows
Job name: RDDIMPDP*
User name: *
Job Status: Released and Ready checked off, all others unchecked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2. Press <F8> to execute the query
3. Highlight the first job in the list and press the <CTRL>+<F11> to change the job.
4. Examine the Exec Target field.
a. If the box is empty, press <F3> to exit
b. If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save
5. Repeat Steps 3 and 4 for each additonal job listed.
Workbench Organizer Reconfiguration
1. Logon on to client 000 of the newly refreshed system with DDIC.
SE06
1. Select the Database Copy or migration option
2. Press the Post-installation Processing button.
3. When prompted Do you want to re-install the CTS?, press the Yes button
4. When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected. Press the checkmark button to continue.
5. When prompted Change originals from PRD to QUA?, press the Yes button
6. When prompted Delete TMS Configuration?, press the Yes button
7. When prompted Delete old TMS configuration?, press the Yes button
8. When prompted Delete Old Versions of transport routes?, press the No button
TMS Configuration
1. Logon on to client 000 of the newly refreshed system.
STMS
1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
2. 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 <CTRL>+S to save. Otherwise, press the Other configuration button and manually configure.
3. From the Overview menu, select Transport Routes
4. From the Configuration menu, select Adjust with Controller
5. Press the Yes button when prompted if you want copy the transport routes from the controller.
Import Printers
1. Logon on to the production client of the newly refreshed system.
STMS
2. Press <F5> to go to the import Overview.
3. Double click on the <SID> of the newly refresh system
4. 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 <Enter> to save.
6. Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import.
7. In the Target client box, enter the productive client of the newly created system. Press <Enter> to save.
8. Press the <Yes> button to start the transport.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. 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: Test
Changes and transports for client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press <CTRL>+S to save.
6. Repeat steps 4 through 6 for any additional clients
Set System Change Option
SE06
1. Press the System Change Option button.
2. Set the global setting to Modifiable
3. From the Edit menu, select Software Components Modifiable
4. From the Edit menu, select Namespaces Modifiable
5. Press <CTRL>+S to save.
Import Users
STMS
1. Press <F5> to go to the Import overview
2. Double click on the <SID> of the newly refreshed system.
3. Press <F5> to refresh the list of transports
4. 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 <Enter>. 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 button
7. Press <Enter> to confirm that the import will proceed
SCC7
1. Run the Post Client Import Processing
2. The transport number should be the same as that of the transport started in STMS
3. 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 <CTRL>+S to save.
SM37
1. Set the fields as follows
Job name: CLIENTIMPORT*
User name: *
Job Status: All options checked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2. Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.
3. Press the Step button.
4. Select the RSCLXCOP line and press <CTRL><SHIFT><F7> to modify that step.
5. In the User box, enter the background user for that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6. Press <CTRL>+S to save the changes
7. Press <F3> to go back to the main job screen.
8. Press the Start condition button.
9. Press the Immediate button.
10. Press <CTRL>+S to save the changes
11. Press <CTRL>+S again to save all the changes to the job.
12. Job will start immediately once saved. Press <F8> to refresh the list of jobs
13. Continue to press <F8> every once in a while to update the status of the job. Do not continue until the job is completed sucessfully.
SCC4
1. From the Table view menu, select Display -> Change
2. 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 1
5. Press <CTRL>+S to save.
6. Repeat steps 3 through 5 for any additional clients
Deleting Source System Profiles
RZ10
1. 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 <F3> to leave this screen.
3. Select the Profile field and press <F4> 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 profile
7. 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 system
Reconfigure Operation Modes
RZ04
1. From the Operation Mode menu, select Timetable
2. Select Normal Operation and press the Change button.
3. Highlight 00:00 in the left hand column and press the Delete Assignment button
4. 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 <CTRL>+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 <F3> to go back to the main RZ04 screen.
8. Right click on one of the listed Operation modes and select Delete
9. Press the Yes button to confirm the deletion.
10. Repeat steps 8 through 9 for any additional operation modes
11. Press <F5> to create a new operation mode.
12. Enter a name and short description for the operation mode
13. Press <CTRL>+S to save.
14. Press <F6> to create a new Instance
15. From the Settings menu, select Based on current settings, then New Instances, then Set
16. Press <F3> to go back to the main RZ04 screen.
17. Press the Yes button to save
18. From the Operation Mode menu, select Timetable
19. Select Normal Operation and press the Change button.
20. Highlight the 00:00 at the top and press <F2>
21. Highlight the 00:00 at the bottom and press <F2>
22. Press the Assign button.
23. Press <F4> to select the operation mode created above.
24. Press <CTRL>+S to save.
Delete Update Failures
SM13
1. Set the fields as follows
Client: *
User: *
From data: 01/01/0001
From time: 00:00:00
2. Press <Enter> to display the list of outstanding update requests
3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.
4. Press the Continue button to confirm the deletion.
Delete Batch Input Sessions
SM35
1. From the Edit menu, select Select All
2. Press <Shift>+<F2> to delete all the batch input sessions.
3. Press the checkmark button to confirm
4. Press the Yes button to start the delete.
Reorganize Spool
SPAD
1. From the Administration menu select Clean-up Spool
2. Check all check boxes and enter 0 for minimum age
3. Press the Execute button
4. Once complete, press <F3> twice to get back to the main SPAD screen
5. From the Administration menu select Check Consistency
6. Press the Delete All button.
SP12
1. From the TemSe database menu, select Consistency check
2. When the check is complete, press the Delete All button.
Delete Invalid Background Control Objects
SM61
1. Press <F8> to switch in to change mode
2. Press the Cleanup List button.
Restrict Outgoing Email and Faxes
SCOT
1. Double click on the green Fax entry
2. From the Supported Address Types area, press the Set button that is beside Fax
3. In the Address area, ADJUST AS NECESSARY
4. Double click on the green SMTP entry
5. From the Supported Address Types area, press the Set button that is beside Internet
6. In the Address area, ADJUST AS NECESSARY
Adjust RFC connections.
SM59
1. Expand the TCP/IP connections section
2. Double click on the first entry listed
3. 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 connection
5. Press Press <CTRL>+S and then <F3> to save and return to the list of RFCs.
6. Repeat steps 1 through 5 for each additional RFC connection
Convert Logical Systems
Under no circumstances perform this procedure on a Production system
BDLS
1. When warned to read the documentation, press the checkmark button.
2. In the Old logical system name box, press <F4>.
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 options
6. From the Program menu, select Execute in background
7. Press the checkmark button when asked to select a spool device
8. Press the Immediate button when asked for the schedule
9. Press <Ctrl>+S to save
10. Use SM37 to monitor the job
11. When job is complete, repeat steps 2 through 10 for any additional logical system names that need to be changed.
Adjust Logical Systems names
SALE
1. Expand Sending and Receiving Systems, then Logical Systems
2. Click on the execute icon beside Define Logical System
3. Press the checkmark button to confirm that the change is cross client
4.
Allow Certains Settings to be modifiable
(Refer to Note 356483 for more Details)
SM54
1. 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 requested
5. Change the Recording routine to no, or user, recording routine.
6. Press <Ctrl>+S to save
7. Press <Enter> 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_GL
V_T093B_01
V_T093B_02
BSI Configuration (R3 HR Systems only)
SM59
1. Expand TCP/IP Connections
2. Highlight BSI70-US-TAX and press the Change button
3. Change the program field to
<hostname>\sapmnt\<SID>\SYS\EXE\RUN\TF60SERVER.EXE
4. Double check the target host and gateway point to the correct server
5. Press <CTRL>+S to save
6. Press the Test connection button to test. If the connect is not successful, take the necessary steps to resolve the issue.
SE38
1. In the Program field, enter RPUBTCU0
2. Press <F8> to execute
3. Select option BSI version 7.0
4. Press <F8> to execute
5. BSI should return tax calculations. If there are errors, take the necessary steps to resolve.
Reconfigure DB13 schedule
DB13
1. Using the print out created before the refresh, recreate the DB13 calendar.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. 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 role
Development
Client role: Customizing
Changes and transports for client-specific object: Automatic recording of changes
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Quality Assurance
Client role: Test
Changes and transports for client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Training
Client role: Education
Changes and transports for client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Sandbox
Client role: Test
Changes and transports for client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press <CTRL>+S to save.
6. Repeat steps 4 through 6 for any additional clients
Set System Change Option
Skip this section of the system is a Development or Sandbox System.
SE06
1. Press the System Change Option button.
2. Set the global setting to Not Modifiable
3. Press <CTRL>+S to save.
Release Background Jobs
Currently, all background jobs, except for system standard jobs have been placed on hold (status scheduled).
Rewards if useful.
Regards,
Pherasath

Post Installation steps for Solution Manager 4.0

Hi Experts,
Please can you guide me if there are Post Installation steps for Solution Manager 4.0!If so can you explain me.I have successfully installed the SolMan 4.0.
Thanks & Regards
Sunil

Hi
In installtion guide you can find the information you needed also check
Visit for step by step details of Standard Configuration of Basic Settings
www.service.sap.com/rkt-solman->select solution Manager 7.0>technical Role-->Technolagy
&system administartion just drill out there you can find lot of simulator how to install and
configure solution manager
https://websmp109.sap-ag.de/~sapidb/011000358700000424922008E.sim
https://websmp109.sap-ag.de/~sapidb/011000358700000525622007E.sim
and for Maintenance optimizer setup
https://websmp109.sap-ag.de/~sapidb/011000358700000086852008E.sim
https://websmp109.sap-ag.de/~sapidb/011000358700000086862008E.sim
Let me know if needed more information
Regards
Uday

ECC6.0 Post-instalation steps..

Hi
Any one can provide the post instalation steps in IBM Aix server/UDB DB2(8.x/9.x) environment...It's very helpful for me the current project..
ECC'6.0 - Post Instalation Steps.
NW'2004s(EP,BW,Xi) - Post Instalation steps.
SRM'5.5 - Post Instalation Steps.
My ID: [email protected]
Thanks for your help.
seshu.

Hi,
U can get post installation steps in upgrade manual itself. It is no specific think for AIX.
Thanks

What are the post installation steps for sap 4.7ee

what are the post installation steps for sap 4.7ee

Hi,
Post installation steps are as follows.
1.SICK to be run first to checkt the errors while installation.
2. Install SAP GUI
3. Set up the TMS. Configuration the domain controller through SE06 and then set up the transport system through TMS.
4. Change the default password of SP* and DDIC.
5. Set up the operations mode using RZ04 and SM63.
6. Apply patches through SPAM.
7 Schedule default background jobs through SM36.
8 Import default profiles through RZ10.
9. Schedule backup calender through DB13.
10. Create clients using SSC4
11. Install lisence
12. Schedule SGEN

Post Install Steps for EP7.0

Similar Messages

Maybe you are looking for