Upgrade steps Details for 9.2.0.8 to 11.2.0.3 Database

Support,
We have one requirement from our client like "Upgrade the Database from 9.2.0.8 to 11.2.0.3". They are asking only the DB upgrade except Application.
Our Current Database is running in Solaris OS and DB is an 9.2.0.8 and Application is an 11.5.10.2.
I am going to follow the below documents for the Database Upgrade process using DBUA for First Iteration,
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0.3) (Doc ID 1585577.1)
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) (Doc ID 881505.1)
In the above documents they mentioned the steps related to the 11g new home installation and upgrade process but before starting the process what are all the things i have to check it in my current Database and Applications.
Because i have clear idea on what we have to do in the new Oracle Home 11g and the Upgrade process but still have some confusion on the Pre-Upgrade Steps in current database.
Kindly suggest me what are the details i have to collect and check in my Current Database or provide any proper Oracle documents for the Database Pre-Upgrade Process.
Thanks in advance,
Vijay.

Vijay,
We would suggest you advice your customer to upgrade to 11.2.0.4 instead on 11.2.0.3
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) (Doc ID 881505.1)
https://blogs.oracle.com/stevenChan/entry/11_2_0_4_database
Preparing to Upgrade Oracle Database can be found at http://docs.oracle.com/cd/E11882_01/server.112/e23633/toc.htm
You would also need to refer to:
How To Get The Proper Environment Set To Run Adbldxml.pl When Upgrading To 11g/11gR2? (Doc ID 1310854.1)
11i: ad_parallel_compile: Ora-01031: Insufficient Privileges in adadmin / re-create grants and synonyms for APPS schema after upgrade from 10gR2 to 11gR2 (Doc ID 1148264.1)
Note: Please note that we have a dedicated forum for EBS questions -- https://forums.oracle.com/community/developer/english/e-business_suite
Thanks,
Hussein

Similar Messages

Upgradation steps for FSG Reports from 11.5.10 to 12i and probable issues.

Hey i have one issue,
we are planning to upgrade FSG from 11.5.10 to 12i
i need steps to upgarde and what are probable issue while upgardation of FSG Reports.
If you have any link or document where we can see this its most welcome.
Many Thanks
Swapnil

Hi Swapnil ,
All upgrade steps (also for FSG if available) should be listed in the following manual:
Oracle® Applications
Upgrade Guide: Release 11i to Release 12
Release 12
Part No. B31566-01
Thanks,
KAR

Step by step procedure for Upgrade to ECC6.0

Hi,
I gained a lot from this forum . Can someone please mail me at
[email protected]
step by step procedure for upgrade .
Will award full points for helpful documents..
With regards,
Mrinal

SAP defined a roadmap for upgrade.
1) Project Preparation
Analyze the actual situation
Define the objectives
Create the project plan
Carry out organizational preparation for example identify the project team
2)Upgrade Blueprint
The system and components affected
The mapped business processes
The requirements regarding business data
3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
5)Production Cutover and Support
The production solution upgrade
Startup of the solutions in the new release
Post processing activities
Solving typical problems during the initial operation phase.
SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
STEPS IN TECHNICAL UPGRADE
     Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
     Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
     After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
     Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
     Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
The main Category of Objects that needs to be Upgraded is
     Includes
     Function Groups / Function Modules
     Programs / Reports
     OSS Notes
     SAP Repository Objects
     SAP Data Dictionary Objects
     Domains, Data Elements
     Tables, Structures and Views
     Module Pools, Sub Routine pools
     BDC Programs
     Print Programs
     SAP Scripts, Screens
     User Exits
Also refer to the links -
http://service.sap.com
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
Hope this helps you.

Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 537, state 3, severity 16

Hello,
I've encountered issue during installation of SP1 to SQL Server 2012. After upgrade I'm getting this error in Event Log:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 537, state 3, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline.
If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script
upgrade steps run to completion.
Can someone point me direction how I can fix it? This is a production server and currently only way to make it working is to use T902 flag in SQL Server startup params. I've found some suggestions to check Data path if it exists but it does so this is not
the issue here. Any ideas?
I've found also here
http://www.sqlservercentral.com/Forums/Topic1377073-1550-1.aspx#bm1378279
suggestions for similar issue with SQL Server 2008 which that I should do:
Via ssms:
From msdb:
Delete:
dc_admin role
Dc_operator role
Dc_proxy role
UlitityCMRReader role
UtilityIMRReader role
UtilityIMRWriter role
but for not I didn't tried it yet. This is standalone SQL Server instance.
Any help really appreciated.
Regards

Script returns the same error.
System databases:
1   1   760   -1   10   1048578   0   1   master       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
2   0   12768   -1   10   1048642   0   1   mastlog       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
1   1   1024   -1   10   1048578   0   2   tempdev       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\tempdb.mdf
2   0   64   -1   10   1048642   0   2   templog       C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\templog.ldf
1   1   288   -1   128   2   0   3   modeldev   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\model.mdf
2   0   4464   -1   10   1048642   0   3   modellog   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\modellog.ldf
1   1   28936   -1   10   1048578   0   4   MSDBData   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf
2   0   3352   268435456   10   1048642   0   4   MSDBLog   C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf
are all in place where path shows.
Before sending my message I've searched update script for "FROM master.sys.master_files" and I found script which you are showing me. I've made some digging and when I runned:
       SELECT physical_name
       FROM master.sys.master_files
       WHERE (name = N'master')
it returned also path to one my customers database name which has filename set correctly but it's Logical DB name is master and mastlog. I'm running shared hosting company and I allow my customers to restore their DBs from .bak files but I have no idea why
this customers logical name is set to master and mastlog. Probably when I change this names update script will work as it should. On the other hand in my opinion there should be some kind of fail safe mechanism for situations like this one.
EDIT: After changing logical name for DB and log for mentioned DB your script runned fine so probably now when I remove T902 flag and restart my SQL Server update will run correctly. Big thanks for resolving this issue.

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,

How to extract OHC_C21 detail step required FOR THIS

how to extract OHC_C21 detail step required FOR THIS

Hi Deba,
Check the following URL
http://help.sap.com/saphelp_nw70/helpdata/en/ba/a3463c9c9ffc3ae10000000a114084/frameset.htm
Regards,
Tom

Category 3 Upgrade Steps for Rel 11i

Upgrading Oracle Applications Rel 11i manual page 4-2 lists three upgrade steps for Oracle Common Modules.
Step 1: Delete all AK data for Production 16 Global Demo databases (conditionally required)
Step 2: Check for invalid AK data in non-Global Demo databases (condionally required)
Step 3: Fix invalid data in non-Global Demo databases (conditionally required)
My Questions:
1. What is AK data?
2. What is the difference between a Global Demo database and a non-Global Demo database?
3. Does the AutoUpgrade utility migrate the data from the Global Demo and non-Global Demo databases to the Vision database?
null

I do not have any experience with standbys, but pl see if these MOS Docs can help
How To Upgrade A Primary Database And A Physical Standby To Oracle10gR2 (10.2)          (Doc ID 407040.1)
Oracle11g Data Guard: Database Rolling Upgrade Shell Script          (Doc ID 949322.1)
Applying Patch Sets / Interim Patches with Physical Standby Database in Place          (Doc ID 187242.1)
Is it possible to use different RDBMS-releases on primary/standby within a Dataguard Configuration?          (Doc ID 1294585.1)
HTH
Srini

SCM5 - SCM7 Upgrade Error during LiveCache upgrade Step C4

We are in the process of upgrading our SCM5 system to SCM7 release level. During livecache upgrade step C4 to load transaction data, we are getting error CONNE_IMPORT_WRONG_COMP_TYPE. The dump says that "when importing the object 'OT_ORDERS", the component no. 5 in the dataset has a different type from the corresponding component of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL". The data type is "P" in the dataset, but "C in the program".
Our source livecache version is 7.6.03.12 and target livecache version we are upgrading to is 7.7.04.29. We used BS 7 SR1 liveCache 7.7.04 DVD from service marketplace. We did not use the update DVD since the guide mentioned that customers on SCM5.1 or higher need to run livecache upgrade from update DVD.
All steps in A, B have already been completed.
More details from the ST22 dump -
Error analysis | | An exception occurred that is explained in detail below. | | The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was | | not caught in | | procedure "GET_DB" "(METHOD)", nor was it propagated by a RAISING clause. | | Since the caller of the procedure could not have anticipated that the | | exception would occur, the current program is terminated. | | The reason for the exception is: | | When importing the object "OT_ORDERS", the component no. 5 in the | | dataset has a different type from the corresponding component | | of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL". | | | | The data type is "P" in the dataset, but "C" in the program. Information on where terminated | | Termination occurred in the ABAP program "/SAPAPO/SAPLOM_UPGR_PARALLEL" - in | | "GET_DB". | | The main program was "SAPMSSY1 ". | | | | In the source code you have the termination point in line 3222 | | of the (Include) program "/SAPAPO/OM_UPG_CLASS_IMPCLUT". | | The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR" | | occurred in | | procedure "GET_DB" "(METHOD)", but it was neither handled locally nor declared | | in the RAISING clause of its signature. | | | | The procedure is in program "/SAPAPO/SAPLOM_UPGR_PARALLEL "; its source code | | begins in line | | 3221 of the (Include program "/SAPAPO/OM_UPG_CLASS_IMPCLUT ".
We are running AIX5.3 and Oracle 10.2.0.2.0.
Any help here will be greatly appreciated.

This is exactly the same with OSS 305147 2010. It will be answered in BC-DB-LCA area.

Post Upgrade Step "Adjust custom development"

Hello all:
Based on your BI 3.x to 7.0 upgrade experience, I wanted some insight on the post upgrade step "Adjust custom development per note 857904". Can you please share how you handled this, any details of activities done here...any tips?
Thanks,
Pravin

Hi Pravin,
Hope this helps you -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881 - you can use this checklist for 2004s too!
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0d7c290-0201-0010-bbaa-d8f8af341796
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a1a0eb43-0b01-0010-23aa-908cc4eaabcd
Bye...

MW R12 - key upgrade steps clarification

OS: RHEL4 x86
DB: 11.2.0.3
EBS Upgrade: 11.5.10.2 -> R12.1.1
MW: 2.20
<-> Process Step: Upg to Rel 12.1.1
<---> Product Family: Perform the Upgrade
<-----> Task: Apply Preinstall Patches
<------->Step 1-Check for critical pre-upgrade patches for Financials
I am on my 2nd upgrade. With the first upgrade I had lots of problems with this step since it refers to an MOS note that has lots of information and refers to other MOS notes and it isn't clear what steps in those notes is duplicated within the MW steps.
The first time I did some things in the wrong order since there was no clear direction between the MW steps and all of the notes.
Is there anything that can help clarify how to correctly proceed through this task and the next task, Perform the Upgrade, which are so critical?
Thanks!

It would be really nice to have the exact steps spelled out in detail since this is too crucial to have it be vague and not well understood.
Here's how the MW explains it.
- Process Step: Upg to Rel 12.1.1
--- Product Family: Perform the Upgrade
1) Apply pre-install patches
----- Task: Apply Preinstall Patches
-------- Step 1-Check for critical pre-upgrade patches for Financials (Required)
I think that I understand this section except that I don't know whether patch 7303029 should be applied in this step or not.
2) Apply DBA CUP and related patches
----- Task: Perform the Upgrade
-------- Step 9: Apply DBA CUP and related patches
This is basic and understood.
3) Step 9.1:Apply patch 7303029
Here's what the MW says for the "setup" section:
"This step will download patch 7303029. It will also verify that the u67780700.drv driver is in the correct location and ready to be merged."
Here's what it says for the "execute" section:
cd $AU_TOP/patch/115/driver
admrgpch -d . -preinstall -master u6678700.drv
Neither of these steps actually applies patch 7303029 in pre-install mode but I am under the impression that this needed to be done at some point.
So, please provide the exact steps needed to get this done correctly.
Thanks

Step-by-step approach for "manual" Oracle Database Migration

Hi All,
I'm looking for a step-by-step approach for "manual" Oracle Database Migration. Basically, the minutes followed in a real-time production DB implementation.
I assume the steps may vary for different setups. However any scenario-based docs will be of great help!

The
Oracle Upgrade Guide
that comes with your download as far as I know is very detailed.

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

Can't update credit card details for recurring pay...

I'm trying to update my grandma's Skype credit card details to the new credit card details (same numbers just new expiry date) for her recurring payments on Skype. I follow all the prompts but the final step requires Mastercard to verify the card with an online bank account which she doesn't have and has no intention of getting which means there is no way to update her credit card details for the recurring payments. How do we solve this problem? Thanks

Hi JW2230
It looks like the payment details are being rejected. Please check this with your card issuer before trying to update them again. The phone number for Australia is 1800 614 863.
Thanks
Bev

Step-by-Step Guide for connecting CRM with SAP R/3 system Server

Hi Experts,
For my ongoing project , I am in the need of connecting the CRM server with
SD server.
Can u share any Step- By Step guide for doing that.
I know that the RFC connection has to be established between the system.
Logical system must be create and all such stuffs.
It is definitly helpful, If u can help me out.
I would to thank, appreciate and reward for your help
Best Regards,
Maniprabu

Hi Mani,
Follow the following steps :
1. Create RFC destination for both the systems on CRM and R/3 in SM59.
2. Create the logical systems and assign clients to logical system in SALE transaction both on CRM and R/3.
3. Create a user in the R/3 table CRMCONSUM with the name CRM.
4. Maintain the Middlware Parameter tables on CRM : Table SMOFPARSFA:
   Create an entry for following parameter entry:
   Key - R3A_COMMON
   Para name - CRM_DEFAULT_DESTINATION
   Value - R/3 logical system
5. Maintain the parameter tables on R/3 system : CRMRFCPAR, CRMPAROLTP
    CRMRFCPAR :
    Create new entry with following data:
    User - CRM
    Object name - *
    RFC Destination - RFC destination for CRM
    Load types - All Load Types
    In Queue flag - X
    Send XML No XML
    CRMPAROLTP :
    Create the following parameter entry:
    Para name - CRM_DEFAULT_DESTINATION
    User - CRM
    Value - Name of the CRM logical system
6. Create Sites and attach subscriptions in Admin Console : Tcode SMOEAC
    Create a Site as CRM and another as R/3. Attach the required subscriptions to the R/3 site.
7. Register the queues in SMQR and SMQS transactions.
PS : For detailed steps refer the Middlware Base Customizings(CR500 and CR100)
<b>Reward points if it helps.</b>

Upgrade steps Details for 9.2.0.8 to 11.2.0.3 Database

Similar Messages

Maybe you are looking for