Upgrade SRM on 4.7 to ECC 6.0

Hi Gurus,
I am moving from SRM 5.0 from 4.7 to ECC 6.0
In this updgrade what are the things that need to be checked and
what kind of issues to be looked .
What are the major changes is ECC6.0 from 4.7?
Looking forward to hear from you
Best Regards

Hi
<u>There is so problems as such until you face any or you have faced any in you past SRM uprgrades.
You can integrate SRM 5.5 to R/3 ECC 6.0 versions without any problems.
Refer this link and get the insights from there .</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/3a/7fdf4204892a78e10000000a155106/frameset.htm</b>
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Similar Messages

SRM 7. 0 with ECC 6.0 Enhancement Pack

1) My client just upgraded their R/3 to ECC 6.0, but no Enhancement Pack.
2) They are trying to upgrade from SRM 5.0 to SRM 7.0 in the near futures.
3) During their first SRM phase, their scenario is limited to the following:
a. R/3 RFQs are pushed to SRM via RFC call (custom program)
b. SRM vendor logs in to see the RFQs and creates Quote
c. SRM buyer evaluates the quotes
4) Question: In order to run the above mentioned scenario without issues, is Enhancement Pack 4 a mandatory component for them, or can ECC 6.0 without any EnH support it already? If it's mandatory, which sub-components of the EnH 4 must be activated in order to support the scenario?
5) Question: In their next SRM phase, they are trying to run scenarios like PPS and Doc Builder. In that case, is Enhancement Pack 4 a mandatory component?
6) Last: Is there any SAP official documentation that maybe answers the question that I listed above?
Thanks.

Hello Jay,
Please find the upgrade information:
https://websmp206.sap-ag.de/upgrade-srm
EhP4 is not mandatory for strategic sourcing, data transfer via RFC can be used.
The benefit with EhP4 for your scenario will be new feature of "Collective Processing of purchase requistion" CPPR; where buyer can select the PReq line items on the portal & create RFx directly in the SRM system. All data transfer is via PI in this scenario. Creating a RFQ in ECC is not a good idea, when you can leverage the RFx capabilities of SRM.
New features: Blog:
/people/michael.jud/blog/2008/09/10/srm-70-in-the-business-suite
Official information :
http://service.sap.com/srm click on SRM 7.0 external view
Hope this solves.
Thanks
Ashutosh

Vendor Migration issue for SRM as add-on to ECC

Hello Experts,
I am working on SRM as add-on to ECC.
When I am trying to migrate vendors from ECC to SRM using MDS_LOAD_COCKPIT. Within monitor, all queues are 'green' indicating that data has successfully migrated to SRM.
But when I check vendors in trx- ppomv_bbp, i don't see any vendor being migrated from ECC. Neither the BPs are crated for these vendor masters.
I have configured all necessary configuration- i.e.
1) I have carried out necessary settings in tables-
mdsv_ctrl_opt_a
crmc_but_call_fu
v_tbc001
2) In addition, I have maintained backend Purchase Org in PPOMA_BBP.
3) I have checked RFC connections, definition of logical systems and
it seems to be alright.
Can anybody please guide if I am missing on any config or can point
me in right direction to investigate??
At SRM GUI, I tried making a local vendor using 'BBPMAININT' but end up in a short-dump.
Can you please help?
Thanks and Regards,
Amit

Hi,
if you problem is still existing, following might be possible solution. Try it.
Maintain Table BBP_MARKETP_INFO with corresponding Vendorroot ID (ex. VG50000....) that you already created in the PPOCV_BBP trx.
Hope it helps.
Regards
PM

Connection SEM 4.0 and BW 3.5, after upgrade R/3 4.6C to ECC 6.0

Hello experts,
Currenctly my customer has the following systems:
BW 3.5 with software component SEM 4.0
R/3 4.6C without software component SEM
ECC 6.0 with software component SEM 6.0 (Development system, I cannot connect the BW system to this one!)
Next week my customer is going to upgrade R/3 4.6C to ECC 6.0 (Test system).
I have to investigate if this upgrade does not influence the communication between SEM 4.0 and BW 3.5, if I connect BW 3.5 to ECC 6.0.
According to the blog: /people/karen.comer/blog/2006/12/19/confused-about-business-planning-releases-between-sap-sem-and-sap-netweaver-bi
SAP SEM is an add-On on top of SAP BW / SAP NetWeaver BI.
This blog also states that:
SEM 4.0 should work with BW 3.5
SEM 6.0 should work with Netweaver 2004s (BW 7.0)
Now I have the situation that software component SEM 4.0 is installed in BW 3.5, and SEM 6.0 is integrated in ECC 6.0 because it is part of Netweaver 2004s.
Does anyone know if the upgrade to ECC 6.0 has influence to the connection between BW 3.5 and SEM 4.0??
Tnx for your help!
G.

>
Markus Taxacher wrote:
>Is the only possible way to migrate the BW 3.5 to ERP/ECC 6.0?
> Whats the easiest way for upgrading to 6.0?
>
> Best regards,
> Markus
Hi, you cannot use BW3.5 you must have BI7 (not ECC6!) to install BCS 6 - BCS sits on BI (formerly known as BW).
It doesn't matter what version of source system you have, you can still collect data from ERP 4.6, you don't necessarily need ECC6.

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

SRM "one-client" installation on ECC 6.0 EhP: Own client needed for SRM?

Hello experts,
i've a question concerning the SRM "one-client" installation on ECC 6.0 EhP4 as Add-On.
Is it possible to use SRM and ERP funtionality in a single client e.g. 001?
Or do we have to use different clients on the system like for SUS?
I haven't found any information regarding this topic in SAP ressources. I'm currently using CG "SAP SRM on One Client in
SAP ERP" Release date 2008 (found on marketplace/srm-inst --> srm7.0); SRM - Technical Basis Configuration (BuildingBlock S00/S03). I'm facing problems while going through the following customizing steps:
Assign logical System to Client [both logicall systems are on the same client (001)] ==> error while trying to reference the second logical sys. because client (001) cannot be used again (own presumption: error message differs)
I've seen that some of you have successfully installed and customized this szenario. If someone could provide me any helpful information or guideline how to proceed in general... would be great...
Best regards,
PATRICK

Thanks for your reply. I've checked the offline documentation because i've no access to solman.
There is a document which describes the steps for configuring one-client customizing on marketplace.
Link: [SAP SRM 7.0: SAP SRM on One Client with SAP ERP|https://websmp203.sap-ag.de/~sapidb/011000358700001201562009E]
The problem is that its impossible to cofigure the system like it's described in the document.
Let me explain why...
SRM Addon is installed and customizing is done in client 001 (same client as erp)
overview about defined logical systems:
-ONECLNTERP (for ERP is defined)
-ONECLNTEBP (for SRM is defined)
When I try to assign the logical system to client 001 it works for the first entry
for the second log. system it shows up an error message.
-->I assume because client 001 has been already assigned. I cant use client 001 again.
But One-Client szenario schould be possible in a single client or is SAPs One-Client more like One-System with differnet clients for SRM and ERP on the same machine?
Because of the above mentioned problem I assume that it's impossible to run ERP and SRM in the same Client number.
Am I right? Do I have to use two Clients on One System for proper Customizing?
Or if it's possible to use a single client on one machine for both ERP and SRM how is it possible to assign two log. systems to one client number?
I'm totally confused. Any help would be appreciated - any tips/hints/experiences from someone who has customized One-Client?
BR, Patrick

Issues during technical upgrade from version 4.6C to ECC 6.0

Dear All,
We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
Request to kindly suggest the alternative to carry out the same in ECC 6.0.
Thanks in advance.
Regards,
Dhawal

Hi Akshya,
Please find answers below.
1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
Yes you can.
If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
Yes you can activate it.
3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
After the upgrade and unicode conversion you can install the java stack.
Regards,
Ravi.

Unable to create shopping cart/RFx in the upgraded SRM 7 server

Hi All,
We are upgrading from SRM 3 to SRM 7. We have also installed a fresh SRM 7 server separately. In that standalone sandbox we are able to create SC/RFx etc , but with the similar configuration we are unable to do the same in the upgraded SRM 7 server. I was wondering if we need to do any specific settings in the upgraded server or not. I am getting the following error message :
The following error text was processed in the system SD1 : Initialize trace failed with error 2
The error occurred on the application server sapsrmcs3_SD1_00 and in the work process 0 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Method: INITIALIZE of program /SAPSRM/CL_WF_BRF_TRACE=======CP
Method: INIT_BRF_TRACE of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: CONSTRUCTOR of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: INITIALIZE_BRF_MSG of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of program /SAPSRM/CL_WF_BRF_CONNECTOR===CP
Method: /SAPSRM/IF_WF_LEVEL_VALIDATION~VALIDATE of program /SAPSRM/CL_WF_PROCESS=========CP
Method: CREATE_PROCESS_FORECAST of program /SAPSRM/CL_WF_APV_FACADE======CP
Method: RETRIEVE_PROCESS_INFO_60_RES of program /SAPSRM/CL_WF_APV_FACADE======CP
Method: RETRIEVE_COMP_PROCESS_DATA of program /SAPSRM/CL_WF_APV_FACADE======CP
Method: GET_PROCESS_INFO of program /SAPSRM/CL_WF_APV_FACADE======CP
Please suggest. Looking forward to your valuable comments.
Regards
PuspaSourav Biswas

Hi,
If the server is upgraded one, please set the workflow framework as "Application-Control Workflow".
Transaction: SPRO
SRM -> SRM Server -> Cross-Application Basic Settings -> Business Workflow -> Select Workflow Framework
Regards,
Masa

Can Central Contracts be Distributed from SRM 7.03 PPS to ECC?

Does anyone know if central contracts can be distributed from SRM 7.03 (PPS) to ECC? I have read several forums that this is not supported. I need to know if it is are there limitations?
Thanks.

SAP very unlikely to state anything 'clearly' especially if it could be perceived as a shortcoming in their software! I was involved in an SRM-PPS implementation in 2010 where an SAP consultant managed the procurement piece and we were simply told it didn't accommodate distribution of contracts.
Found this Note :
1354971 - Disable distribution tab and distribution buttons in PPS
See this discussion :
No Contract Distribution with PPS
Good luck.

Error while upgrading SRM portal from 7.01 to 7.02

Hi All,
We are in process of upgrading SRM Java from 7.01 to 7.02. While JSPM was running 250GB of trace files (around 29317 files) have been written under D:\usr\sap\SJ7\JC01\j2ee\cluster\server0 and we are forced to stop JSPM and complete SAP instance.
As soon as we start the instance with minutes 1GB trace files are written. All these files are dev_jrfc_xxxxx.trc.
All these files have single error repeated continuously, kindly let us know how to resolve this issue.
Error file opened at 20110706 102426 Eastern Daylight Time Rel 7.01.3 (2008-10-28) [710.234]
Error thrown [Wed Jul 06
10:26:12,128]:Error in RequestDispatcher.DispatcherWorker.run() java.lang.UnsatisfiedLinkError: nativeSAP_CMLISTEN
            at com.sap.mw.rfc.driver.CpicDriver.nativeSAP_CMLISTEN(Native Method)
            at com.sap.mw.rfc.driver.CpicDriver.SAP_CMLISTEN(CpicDriver.java:1137)
            at com.sap.mw.rfc.driver.RfcTypeRegisterCpic.waitForRequest(RfcTypeRegisterCpic.java:593)
            at com.sap.mw.rfc.api.RfcApi.RfcWaitForCpicRequest(RfcApi.java:1262)
            at com.sap.mw.jco.MiddlewareJRfc.waitForRequest(MiddlewareJRfc.java:641)
            at com.sap.mw.jco.RequestDispatcher$DispatcherWorker.run(RequestDispatcher.java:159)
            at java.lang.Thread.run(Thread.java:534)
Regards,
Siva.

Hi Siva,
it seems to me that you have heavy log archiving on the system. You can switch the log severity of all (or at least most) of the locations to the default. In addition, switch off the archiving of old log files:
In the visual configtool navigate to Server -> Services -> Log Configurator -> Properties tab and set the value of the ArchiveOldLogFiles to "OFF".
Also, using the Visual Administrator -> Services -> Log Configurator -> restore to default all the trace levels.
Regards,
Jonas Cella

Upgrade from 4.6 B to ECC 6.0

Hi Gurus,
Well and I would like to inform to our gurus that currently we are in the Phase of upgrading form 4.6 B to ECC 6.0
I this regarding, can any one of our Guru's guide me regarding the following doubts.
1. How to do Upgrade from 4.6 B to ECC 6.0?
2. If you have any documents in this regard?
3. Do you have any documentation for ECC 6.0?
I request you to kindly forward the information to mail id: [email protected]
Thanks with regards,
Bala

Hi,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Please assign points if it useful.
Regards
Ravinah Boni

Advantages and disadvantages for SRM on one client with ECC

Dear SAP gurus,
We are evaluating the use of SRM on one client with ECC. Is there a paper spesifally discuss the advantage and disadvantages of having this deployment option?
Best regards,
John

Hi
check this link
SRM Server as an Add on to ERP 2005
Advantages
1) one backend for SRM and ECC6.0
Disadvantage
1.Sourcing scenario cannot be implemented.
2.It does not support multiple backend system.
Regards
G.Ganesh Kumar

Using MOPZ to upgrade SRM from 5.0 to 7.0

Hello to the group,
We are lookinig to upgrade SRM from 5.0 to 7.0 and were looking to MOPZ to calculate all the needed packages. However, when we run MOPZ for SRM we are not seeing the selection that allows us to select upgrades/enhancement packages (all we see is 'maintenance'). Is this normal? Has anyone been able to use MOPZ for this upgrade process?
Note that we have verified our settings in SMSY against SAP's recommendations for using the Maintenance Optimizer.
Thanks in advance for any help.
J. Haynes

Hello there,
Please check the Support Package level of the Solution Manager system. It should be at least on SP22.
In https://websmp107.sap-ag.de/solman-mopz it says that upgrade with an EHP install is supported for SRM, so it should offer the upgrade.
Please check the order of activation of these BC sets:
SOLMAN40_MOPZ_TTYP_SLMO_000
SOLMAN40_MOPZ_001
SOLMAN40_MOPZ_SP18
If they are activated in the above order, then it is OK. If not, or if any of them is not activated, them activate them in this order.
Best regards,
Miguel Ariñ

Gurus: Recommend Upgrade SRM 3.0 to SRM 7.0 (2 step upgrade) or reimplement

SAP Gurus: Quick information needed - really appreciate a quick answer/any material - Is it recommended to Upgrade SRM 3.0 to SRM 7.0 (2 step upgrade) or do a re-implementation on SRM 7.0 ?

Hi,
I always recommed 1 step upgrade. What are reasons you do not take 1 step upgrade?
Recommended Order:
1 step upgrade
2 step upgrade
New implementation
Regards,
Masa

SRM upgrade also required in case of ECC upgrade?

Hi Experts,
We are planning to upgrade ECC systems from ECC6.0 (SPS8) to EHP6 and our SRM system is on SRM 5.00 version.
Do we also need to upgrade our SRM system also in order to avoid any compatibility issue?
I checked in PAM and upgrade guides for ECC & SRM but could find any statement on this.
Please help.
Thanks,
Ankur

Hi,
The release 5.00 is compatible with ECC 6 EHP6,
although you could find restrictions in the full usage of the features
of this release, you can find more information in the notes below:
852235 Release Restrictions for SAP ERP 6.0
863532 Release Restrictions mySAP SRM 2005
963000 Usage and release of SRM as AddOn to ECC in ERP 6.0
1684511 SRM<->ERP coupling: Table maintenance for BBP_BACKEND_DEST
I strongly recommend you reading carefully the upgrade guides available
at Service Marketplace for ERP 6.0 EHP6:
http://service.sap.com/erp-inst
Please visit the below link upgrade dependency analyzer.
http://service.sap.com/uda
Regards,
Aidan

Upgrade SRM on 4.7 to ECC 6.0

Similar Messages

Maybe you are looking for