Post refresh step

Hi
Pardon the reference to E-Business Suite.
One of the post-clone/refresh steps in -Business Suite involves updating a 'profile option value' SiteName.
The value of this reflects the usage of the instance usually like 'FINancial UAT copy of PROD as on ...'
Can you please help me with the steps to update the greeting message in PeopleSoft after a clone/refresh?
Currently my DEV/UAT/PROD every cloned environment has the same greeting message
Thanks a lot for the help
Cyril

cyrilt wrote:
After logging into the front end..
on the top left most we have the Oracle logo (i think it is a image file which can be modified, that is another question which will ask about later)
Just below that is "Personalize Content |Layout'"
To the right of this entire thing comes a message like
"<Username> on <DBNAME> - Production"Don't you realize that's a customization, do you ? I mean this is not a standard output, it has been modified by customer.
i am looking for ways and means of changing the above message
This message does not change after updating the psoptions by logging into the url and following the navigation path:
PeopleTOols -> Utilties -> Administration -> PeopleSoft options
In fact just now i checked a few other instances and found that the message that appears there has no resemblance to what i see in the greeting..
Also i noticed in the demo env there is just a "blank blue" just above the
"Home |WorkList |MultiChannel|Add to Favorites|Sign out"It seems your application have been customized, you should work closer to the in-house developers.
Nicolas.

Similar Messages

SRM - System Refresh (Post Refresh steps)

Hi,
Can anyone tell me the steps to execute after SRM system refresh using file copy method ?
Thanks & Regards,
Jag

I have seen this somewhere in the forum: See if this helps you
BDLS: Convertion of logical system (SRM).
Check entry in table TWPURLSVR.
Check RFC connections (R/3 and SRM)
SPRO, check or set the following points:
Set up Distribution Model and distribute it
Define backend system
Define backend sytem per product category
Setting for vendor synchronization
Numbe ranges
Define object in backend sytem
Define external services (catalogs)
Check WF customizing: SWU3, settings for tasks
SICF: maintain the service BBPSTART, SAPCONNECT
SE38:
Run SIAC_PUBLISH_ALL_INTERNAL
Run BBP_LOCATIONS_GET_ALL
Update vendor BBPUPDVD
Check Middleware if used.
Run BBP_GET_EXRATE.
Schedule jobs (bbp_get_status2, clean_reqreq_up)
Convert attributes with RHOM_ATTRIBUTE_REPLACE
BR
Muthu

Post-refresh steps for a CUA child system

Hi,
I implemented CUA in our non-prod system.
I will copy my DEV system (CUA enabled) to a SBX machine (also CUA enabled).
our CUA Master is installed on our Solution Manager machine.
I searched the web for possible solutions. One of them is:
1.export users from SBX
2. refresh SBX
3. import users back into SBX
4. run SCC7
Any other possible solutions such as forcing data from CUA master to be "implemented" into my refreshed system?
Thanks.

Hi Eric,
Not much aware, hope this might be helpfull.
http://wiki.sdn.sap.com/wiki/display/Security/Bestpractice-HowtoperformaclientcopywhenCUAisactive
http://sapbasisnotes.blogspot.com/2009/05/how-to-perform-client-copy-when-cua-is.html
Cheers
Deepanshu

Automate post refresh process

Hi,
I am doing system refresh from Porduction to QA and my client has a
need to automate most of the biggest post refresh steps like language
suppliment install, BDLS and SGEN.
We are running SAP ECC5/AIX5 and oracle9.
Question is how can we install language suppliment and create a in
batch job after system refresh ? can we create batcj job as a transport
and where should we keep it in target system or a source system ?
The main goal here is to automate these post steps and make the refresh
time shorter.
I appreciate your time.
Thanks
Regards,
Mohammad

Hi,
We can use Group Policy to change the default AutoArchive settings for all users. However, if the AutoArchive setting for separate folders is set to "Do not archive items in this folder", the Group Policy settings won't apply to these separate
folders and there is no way to deploy AutoArchive settings to separate folders.
Since you are in Exchange 2007 environment, we can use Managed Folders instead of AutoArchive to achieve the same goal. See:
https://technet.microsoft.com/en-in/library/bb125163%28v=exchg.80%29.aspx
If you need further assistance regarding Managed Folder, you can post a new question in the Exchange forum:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
Thanks,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Post QA Refresh Steps in an HR Environment

Hello All
I'm hoping to get some additional information on this.
When the UMR is imported in post-refresh activities, this will wipe out the target system's roles/profiles/users and replace with the source system's UMR (the backup).
However with HR Role assignments through OM, will these be restored when RHPROFLO is run on the QA system that's just been refreshed?
I want to ensure that the roles assigned to position through OM in QA are restored after the refresh. My guess is running RHPROFLO and User Comparison after importing the UMR will restore the QA roles/profiles/users.
can anyone confirm?

Hi Nigel,
Welcome to SDN.
RHPROFLO will read the HR master data and create the users in the system in which it is run. However, when you are talking about client copies / refreshes, after the QA refresh and the QA exported UMR is imported back in QA, you will get the QA users retained after PRD data is copied.
Why do you want to run RHPROFL0 in QA? Is'nt the HR master data being masked in QA post refresh?
Thanks
Abhishek

How to add enter-in-insert mode without post-generation steps

Hello,
We'd like to enter one of our pages in insert mode.
We found the trick how to do it, there is one step which is a post JHeadstart generation step (add code to Page Definition). I'd like to know if we can avoid this post-generation step
Here the complete list of steps
(1) Model project, set View Object, Tuning to 'No Rows'
(2) ViewController Project
2.1 JHeadstart settings for the page
- Single-row insert allowed Yes
- Single-row update allowed Yes
- SHow New Rows at Top Yes
2.2 Generate the JHeadstart application
2.3. Go to the Page which you'd like to enter in insert mode and click on 'Go to Page Definition'
Add in the <executable> part the following code
<invokeAction Binds="CreateAanmakenAdminEenheden" id="invokeCreate" Refresh="renderModel"
RefreshCondition="${!adfFacesContext.postback and empty
bindings.exceptionsList}"/>
(see also http://download-uk.oracle.com/docs/html/B25947_01/web_form006.htm for more information)
Make sure that the Binds part has the sam name as the <action id='Create...' which is available in the bottom part of the page definition.
My question is
How can we avoid this last post-generation step, the addition of code to the Page Definition file.
I know you can unclick the 'Generate Page Definition' property in JHeadstart, but that introduces a risk that functionality is not included after changing the page.
Regards Leon
By the way, this is a lot of of work, just for entering a page in directly in insert mode. I think there can be made some improvement in ADF to accomodate this (a lot wanted) functionality.....

Navid,
You need to create custom templates to achieve this. The easiest way to get everything in place, is to first generate the group as insert-only (without search and query).
This will generate the following:
- in the page definition the ControllerClass property will be set to a JSF EL expression, something like #{EmpWizardPageLifecycle}
- in the group beans config file, two beans are generated like this:
<managed-bean>
<managed-bean-name>EmpWizardPageLifecycle</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.lifecycle.JhsPageLifecycle</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>beforePrepareRenderMethods</property-name>
<list-entries>
<value-class>oracle.jheadstart.controller.jsf.bean.InvokeMethodBean</value-class>
<value>#{CreateEmpWizardMethod}</value>
</list-entries>
</managed-property>
<managed-property>
<property-name>validateADFModel</property-name>
<value>false</value>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>CreateEmpWizardMethod</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.bean.InvokeMethodBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>methodBinding</property-name>

<value>bindings.CreateEmpWizard.execute</value>
</managed-property>
<managed-property>
<property-name>executeCondition</property-name>

<value>jsfNavigationOutcome=='StartEmpWizard' or param.StartEmpWizard=='true'</value>
</managed-property>
</managed-bean>
The executeCondition does the trick here: it causes the page to start in insert mode when the navigation outcome is 'StartEmpWizar' or there is a request param named StartEmpWizard with value true.
So, to get this functionality in a normal queryable group, you need to create a custom template for the groupFacesConfig.vm and add the two bean defs as above. And to get the ControllerClass property generated correctly, you can use the advanced group-level property Page Lifecycle class and set this to #{EmpWizardPageLifecycle}.
(and replace EmpWizard with your own group name)
Steven Davelaar,
JHeadstart Team.

Post-refresh activities in BI after R/3 is restored or refreshed

Dear Experts
From what i could recall, post-refresh of R/3 system requires certain steps to be done on the basis / Netweaver layer of BI before the system can be normalised.
I recall that there is a RFC (sm59) user whose password I need to know in order to carry out the BDLS?
Please advise what activities are needed after a R/3 system connected to BI is refreshed or restored with backup.
Is there a guide for this?
Would greatly appreciate your advice.
Best regards
Pascal

Hi,
Check following
Delta Loads:
1. Whenever a refresh happens from the production, the delta pointers are disturbed.
2. You need to re initialize the delta pointer for the DS you mentioned.
3. If it is for the testing purpose of the Delta functionality, you may intialize the delta pointer 1st and then ask for postings of data in the ECC side.
4. Once the postings are done, you would see data in Delta Queue in RSA7 in source system.
5. Now run the Delta InfoPackage so as to fetch this data from the Delta Q of SS to the BW system.
Full Loads
1. If you are expecting a full load (Historical data), you need to first fill the Setup tables (in Background only) in the SS.
2. Once the Setup table fill job is completed in SS, you may execute a Full InfoPackage in order to get this full load.
thanks

What are the security post refresh procedures in general?

Hi,
Can anyone list me out What are the security post refresh procedures in general?
Thanks and Regards,
Damanaidu J

>
Damanaidu jawaharlal wrote:
> Hi,
>
> Can you cite with respect to CUA.
>
> Thanks and Regards,
> Damanaidu J
CUA
====
CUA behaves differently during a system/client copy and this is the approach we took and it was successful. The goal is to take a backup of the source before CUA deletion then restore. Do not delete CUA and just attempt to rebuild it, all the roles will be gone. Backup and restore will be the approach I recommend.
a1. Take a snap shot of your QA user and role assignments before copy.
1. (Basis) First make a backup of the source system. This is important before step 2.
2. After successful backup delete the CUA from the source system.
3. After successful copy to target system, restore backup to source system.
4. Depending how the copy was done, users and passwords should be in the target system but all the role assignments will be gone.
5. Start assigning roles base on your requirements. If you need to restore the old QA settings that is captured in a1.
Perhaps others can add in other steps I might have missed.
Good Luck!

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

ASU-process POST Upgrade Step on SQL database

Hi All,
To check this message in the right format kindly click on reply first then click on quote original icon ("").
I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
IS-OIL Application Test 600                                                 Optional
KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
CGPL: Entries are blank after upgrade                                                Obligatory
Error handling of task group execution                                Optional
Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Convert customizing for warehouse funds ctr scenarios     Optional
Various problems classification commitment items (class type     Obligatory
Unauthorized error messages udring fiscal year change/reassi     Obligatory
RFFMUDX1 migrates incomplete budgeting tables                          Obligatory
Non-7bit-ASCII character used for BCS key figures             Obligatory
Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory
BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory
BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory
Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory
Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
Activating VMC for the Internet Pricing and Configurator     Obligatory
Customer specific BSEG-fields not transferred                  Optional
Conversion of report headers in drilldown-reporting            Optional                                   600
IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
Conversion of CO-Total-Tables                                              Obligatory     46C                      500
Conversion of CO-line-item table COEP                                Obligatory     46C                       600
New General Ledger, problems in CO-documents                 Obligatory                               500
No receivers found in allocations                                          Obligatory     46C                        470
Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
Migration of process parameters in recipe management     Optional     110                        600
FAQ new depreciation calculation                                        Optional                                600
Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
Reloading Table T512W                                                        Optional
Converting Short Texts                                                         Obligatory
Migrating Data                                                                         Optional     4.7
Activating SAP ECC Extensions                                          Optional
I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
Please suggest me, how to proceed and what to do. please guide if i skip this step now and later on I apply latest SP than still I need to do all this.
Regards
Vinay

Hi All,
I also faced a similar issue during upgrade. Some useful findings.
1. Only super user can access this /n/ASU/START
2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
4. Execute all the checks /n/ASU/UPGRADE
5. This surely can be skipped, but not advisable.
regards,
Amit

Upgrade step ASU-process post upgrade step

Hi All,
To check this message in the right format kindly click on reply first then click on quote original icon ("").
I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
IS-OIL Application Test 600                                                 Optional
KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
CGPL: Entries are blank after upgrade                                                Obligatory
Error handling of task group execution                                Optional
Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Convert customizing for warehouse funds ctr scenarios     Optional
Various problems classification commitment items (class type     Obligatory
Unauthorized error messages udring fiscal year change/reassi     Obligatory
RFFMUDX1 migrates incomplete budgeting tables                          Obligatory
Non-7bit-ASCII character used for BCS key figures             Obligatory
Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory
BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory
BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory
Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory
Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
Activating VMC for the Internet Pricing and Configurator     Obligatory
Customer specific BSEG-fields not transferred                  Optional
Conversion of report headers in drilldown-reporting            Optional                                   600
IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
Conversion of CO-Total-Tables                                              Obligatory     46C                      500
Conversion of CO-line-item table COEP                                Obligatory     46C                       600
New General Ledger, problems in CO-documents                 Obligatory                               500
No receivers found in allocations                                          Obligatory     46C                        470
Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
Migration of process parameters in recipe management     Optional     110                        600
FAQ new depreciation calculation                                        Optional                                600
Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
Reloading Table T512W                                                        Optional
Converting Short Texts                                                         Obligatory
Migrating Data                                                                         Optional     4.7
Activating SAP ECC Extensions                                          Optional
I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
Please suggest me, how to proceed and what to do. please guide if i skip this step now and later on I apply latest SP than still I need to do all this.
Regards
Vinay
Edited by: Vinay Paul on Sep 11, 2009 10:11 PM

Hi All,
I also faced a similar issue during upgrade. Some useful findings.
1. Only super user can access this /n/ASU/START
2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
4. Execute all the checks /n/ASU/UPGRADE
5. This surely can be skipped, but not advisable.
regards,
Amit

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

Error on Oracle 11gR2 RAC database Post upgrade step

[Upgrade the Oracle Clusterware Configuration|http://docs.oracle.com/cd/E11882_01/server.112/e23633/afterup.htm] Problem Description:
O.S Version: HP-UX B.11.31 U ia64
It is upgrading of Oracle RAC 2 node database from 11.1.0.7.0 to 11.2.0.3.0
I receive following error while perfoming the post upgrade step
indba1 racdb> srvctl upgrade database -d racdb -o /app/oracle/product/11.2.0.3/db
PRCD-1231 : Failed to upgrade configuration of database racdb to version 11.2.0.3.0 in new Oracle home /app/oracle/product/11.2.0.3/db
PRKC-1136 : Unable to find version for database with name racdb
Actually I am performing the step "Upgrade the Oracle Clusterware Configuration" whill getting the error.
When I tried on below;
indba1 racdbp> srvctl upgrade database -d racdb -o /app/oracle/product/11.2.0.3/db
PRCD-1231 : Failed to upgrade configuration of database racdb to version 11.2.0.3.0 in new Oracle home /app/oracle/product/11.2.0.3/db
PRKC-1136 : Unable to find version for database with name racdb

Output from Oracle 11.1.0.7 Home:
oracle@indba1:/app/oracle/product/11g/db_1 $ srvctl config database -d racdb
PRKR-1001 : cluster database racdb does not exist
PRKO-2005 : Application error: Failure in getting Cluster Database Configuration for: racdb
Output from Oracle 11.2.0.3 Home:
oracle@usfsdba1:/app/oracle/product/11.2.0.3/db $ srvctl config database -d racdb
PRKR-1001 : cluster database racdb does not exist
PRKO-2005 : Application error: Failure in getting Cluster Database Configuration for: racdb

Upgrading Oracle Text - Post upgrade step 10.2 to 11.2

I already upgraded my 10.2.0.4 database to 11.2.0.1 and have to do post upgrade steps. In step 39 of Manual guideline (837570.1) is not clear for me. If some one can explain further would be appriciated. When i check my source ORACLE_HOME/ctx/admin/ctxf102.txt or ctxf102.sql
Step 39
Upgrading Oracle Text
Copy the following files from the previous Oracle home to the new Oracle home:
* Stemming user-dictionary files
* User-modified KOREAN_MORPH_LEXER dictionary files
* USER_FILTER executables
To obtain a list of the above files, use:
$ORACLE_HOME/ctx/admin/ctxf<version>.txt
$ORACLE_HOME/ctx/admin/ctxf<version>.sql
where version is 920,101,102
For instance, if upgrading from 10.2.0
*1. For dictionary files check*
*$ORACLE_HOME/ctx/admin/ctxf102.txt*
*2. Execute the script as database user SYS,SYSTEM, or CTXSYS*
*$ORACLE_HOME/ctx/admin/ctxf102.sql*
If your Oracle Text index uses KOREAN_LEXER which was deprecated in Oracle 9i and desupported in Oracle 10g Release 2, see below Note for further information on manual migration from KOREAN_LEXER to KOREAN_MORPH_LEXER.
Note 300172.1 Obsolescence of KOREAN_LEXER Lexer Type

Hi Srini
Thank you very much. now i got it.
Oracle asked me to identify the CTXCAT indexes with KOREAN_LEXER execute the following query as user CTXSYS: if nothing return then i can skip this step.
SELECT idx_name
FROM ctxsys.ctx_indexes
WHERE idx_type = 'CTXCAT'
AND idx_name IN
(SELECT ixo_index_name
FROM ctxsys.ctx_index_objects
WHERE ixo_class = 'LEXER'
AND ixo_object = 'KOREAN_MORPH_LEXER ');
SELECT isl_index_owner,isl_index_name,isl_language
FROM CTXSYS.ctx_index_sub_lexers
WHERE isl_object = 'KOREAN_MORPH_LEXER';

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 refresh step

Similar Messages

Maybe you are looking for