SRM Upgrade from SRM 4.0

Does anyone have any good incite on upgrading from SRM 4.0 to SRM 5.0 possibly(6.0)? We are preparing to upgrade to ECC 6.0 and I want to know for:
1 - Is an SRM upgrade absolutely required if we are currently on 4.0?
2 - What are the possible benefits/pitfalls of the upgrade in both SRM 5.0 and 6.0?
Your wisdom is greatly appreciated!
Points will be rightfully rewarded!
Charles

Hi,
See the foll links:
SRM 6.0 update
https://websmp101.sap-ag.de/~sapidb/011000358700006330942006D
Since SRM 6.0 is quite new, and will be officially released after some time, you need to read the release notes in order to find the exact differences in terms of enhancements from the above link.
Refer to this OSS Note as well.
Note 995220 - SRM 6.0 SP Stack 00 (12/2006): Release Information Note
You can check next link:
https://websmp110.sap-ag.de/srm
Re: Additional advantages of having SRM in EBP 5.0 compared to EBP 2.0
In EBP 5.0, you have more flexibility in case of the WF's.e.g. in the SC Approval WF's ,you can have the n-step dynamic header level as well as the Item level approval Workflow in addition to the Standard 1 step,2 step and no approval Workflows
BR,
Disha.
<b>Pls reward points for helpful answers.</b>

Similar Messages

Custom fields in webdynpro SRM 7.0 while upgrade from SRM 5.0

Hi Experts,
We are upgrading from SRM 5.0 to 7.0. We created 2 custom fields using configure field control in Meta data handling (SPRO) and enabled them for visibility. When we tried to see these two custom fields, they didnt appear in the web dynpro component.
Web dynpro details are below.
Webdynpro: /SAPSRM/WDC_UI_DO_ACC
Window : IV_L_FPC_CA_DETAILS
view : V_DO_ACCOUNT_DETAIL
Field : zzXXXX
We have to manipulate the data of those fields.
Since we couldn't see those fields, unable access the data. Could you pls suggest what was the solution you found for your issue.
Thanks
Dhivya

Hi,
Please check the Meta configuration on which set key you configured.
you have to configure the fields as show in the below link for accounting.You have to use set key as 31 for accounting.
http://wiki.sdn.sap.com/wiki/display/SRM/CustomerAccountFieldsatDefaultsettingsonShoppingCart
Regards
Devi prasad

Dependencies for an upgrade from SRM 4.0 to SRM 7.0

We have a Client situation - upgrade from SRM 4.0 to SRM 7.0 - they have SAP EP 6.2 and 4.7E backend system.
Now, the questions are -
1. Is it mandatory to upgrade to SAP EP 7.01 (Netweaver 2004s) or will SRM 7.0 work with SAP EP 6.2?
2. It appears SRM 7.0 will work with SAP 4.7E, however, will self-service procurement, sourcing cockpit functionality work okay and integrate with SAP 4.7E without any issues?
An early response is highly appreciated.
SNR

Hi SNR
For your first question please refer to the following link as well as the SRM 7.0 release notes:
https://wiki.sdn.sap.com/wiki/display/SRM/SRMRelatedComponentsperSP+Stack
If you check the EP 6.2 is no longer supported by SRM 5 releases onwards
Based on this information, the SRM 7.0 should not work with EP 6.2
For your Second Question:
It seems to be no restrictions in use Backend 4.7E. You can define it in the SPRO as backend destination / sys type(BBP_BACKEND_DEST table SYS_TYPE = R/3_4.70)
As additional information please kindly refer to the SRM 7.0 Instalation Guides. It can be found in the Service Marketplace
service.sap.com/srm-inst
-> SRM 7.0
There you will find a lot information about installation / upgrade from prior SRM releases
I hope this information helps!
Alvaro

Workflow not working in SRM upgrade from 4.0 to 5.0

Hello,
We are upgrading SRM 4.0 To SRM 5.0 CS with backend as ECC6. i am having following problem with workflows,
the workflows active on SRM 4.0 is,
WS 14000133 Approval Shopping Cart n-Level (BADI)
For same workflow and starting condition this workflow is not getting triggered for same user ( attribute & authorization wise on SRM 4.0 & SRM 5.0). Can you please tell me how to deal with this problem.
Second problem is with Bid
WS 79000010 Workflow Without Approval for Bid
is active on srm5.0 but still when the purchaser accepts the bid. the bid (Quotation) asks for approval with no approvers in the list.
where as there is no work flow active for Bid but still the bid asks for approval where in two approvers are fixed for the same.
So please help me to solve these problem on SRM 5.0 if possible with brief steps to go ahead.
Regards,
Vivek B.

Hi,
For issue 1. Please check the start condition in the SWB_PROCUREMENT transaction.
For issue 2. Check the document status in BBP_PD. Find the Workflow-item ID. Display the Workflow-item ID in SWI1 transaction. Please double check the approval tasks are general task.
Regards,
Masa

Help needed in SRM upgrade to SRM server 5.0

Experts,
My client is on EBP 2.0 and going for an upgrade to SRM Server 5.0 and working on classic scenario and keeping the backend as 4.6C for this phase of the project. Please share any experiences on how to go about the upgrade, any questionaries, methodologies also I would like to know the major differences between EBP 2.0 and SRM 5.0.
Thanks in Advance,
Surya

HI Surya
Pls go through following sites
http://service.sap.com/instguides (install and upgrade guides)
http://service.sap.com/ibc-srm (config guides - upto SRM 4.0)
http://service.sap.com/srm (general info)
The installation guides and Config guides will give you perfect steps to follow for installation and configuration.
regards,
Nimish Sheth

Pictures not appearing in after upgrade to SRM-MDM Catalog 3.0 SP7 Patch4

Hello,
Due to some issues in Advanced search we performed the service pack upgrade from SRM-MDM Catalog 3.0 SP5 (with MDM 7.1.03.72) to SRM-MDM Catalog 3.0 SP7 Patch4 ( MDM 7.1.04.146). With this new SP, the Pictures are not appearing anymore under the Hyperlink section anwhere in Catalog browser( Compare, Context view, Item details). With earlier SP pictures were appearing perfectly.
We have done like this:( refer earlier thread - Re: SRM MDM Catalog 3.0 Image display) thanks Sudhanshu, Jitesh and Mandeep for suggesting that solution!
Using the hyperlink field
type : rendered
MIME type : image type i.e. .jpg
URL : web URL
We had gone for this option because we dont want to store impages in MDM, and this worked perfoectly until new SP upgrade.
Any clues?
Thanks
Pravin

Hi Bala,
Nothing appears under the Hyperlink section in Catalog browser, though a valid link exists in Data Manager under Hyperlink as type-Rendered, MIME type as JPG and a valid URL.
I have searched Service Market place for this fix of this issue and found that SAP has improved the technology ( from Object Cache to Blob Cache) to display pictures/hyperlinks from SRM-MDM Catalog 3.0 SP06 and MDM 7.1SP04 onwards. We were on SRM-MDM Catalog 3.0 SP05 and MDM 7.1 SP03 before Dev upgrade.
Here are the notes for reference of others who get into same issue.
Note 1450593 - Implementation of BlobCache
This note states "MDM7.1 SP04 offers new image caching functionality called Blob Cache. The old functionality of Object Cache is replaced with the Blocb Cache mechanism in Catalog 3.0 SP06 P1"
Note 1505796 - Images not showing in SRM-MDM catalog (error in BlobCache)
This note talks about the issue in MDM API with Blob Cache. The Fix has been provided in SRM-MDM Catalog SP08 Patch 01.
But upgrade is not something that happens on the drop of a hat, we dont want to do another upgrade, I would like to know if there is a workaround.
Thanks
Pravin

Q & A for blueprint upgrade to SRM server 5.0

All,
As we are going for upgrade from EBP 2.0 to SRM 5.0 and we have go for blue printing. If any body is having Questionare contains technical and general business questions in this scenario please post such a questions from Q&A db. The client is working on classic scenario. If anyone went for such an upgrade, please provide me some inputs in this regard.
Thank you,
Manyam

HI manyam
following post may be usefuls
G/L account field to be disabled for SC screen
Help needed in SRM upgrade to SRM server 5.0
Hope this provides valuable information.
Regards,
Nimish Sheth
Do reward points for helpful answers.

Migrating from SRM 7.0 Classic to ECS - Seeking some clarifications

Hello Friends,
We are now planning to upgrade from SRM 5.0 to SRM 7.0 and then migrated to Classic to ECS. We have the below challenging points which I need clarification,
1) How do we go about the Taxation and Pricing Part, If we migrate from Classic to ECS
2) Presently we have R/3 contracts in place and the same is linked to MDM catalogue and now the client wants the contracts to
    be in SRM. In that case how do we go about the strategy.
3) Asset Procurement: Now all WBS element are converting into assets by running the Z-Program in between PR and PO in R/3
   system. But when we migrate to ECS PO gets created in SRM, so how do we go about the asset procurement in ECS scenario.
4) Confirmation and Invoice transferring to R/3 through Idoc distribution Model. Going forward in SRM 7.0 the same will continue or
    do we go with SOA. Please confirm.
Further to this can you please let me know, what are all the major challenges for upgrading the system to SRM 7.0 and migration from Classic to ECS.
I would appreciate for you quick response. Points will be awarded for appropriate answers.
Thanks and Regards,
Ram.

Ramesh,
Few inputs for this project
1. You need to clearly seperate out the upgrate (5.0 to 7.0) and Migration (Classic to ECS) in your project planning to derisk the project i.e. you should have seperate testing cycle time/ efforts for upgrade and then on migration so that functional/ teachnical team working out in the project can clearly identifies issues between upgrade and migration seperately and work on them.
2. You have to work with business to make a decision on conversion of old classic PO's (incomplete GR/IR still required) and PO in process (SC created under approval in SRM). I strongly suggest you should not involve into conversion and keep it out of this project.
3. SRM do have option to take care of your tax configuration. BTW most of the company use external software to calculate tax amount.
4. You need to build workflow for PO in SRM since now PO will be created in SRM.
5. You need to create smartform / output determination in SRM for the PO. Please note SAP has provided some consulting notes if you continue to handle document transmission in backend with ECS.
6. Yes a distribution model needs to be setup for confirmation and Invoice if you are not doing it now in classic scenario.
Asset procurement solution you mentioned looks specific to your Org business needs, you need to explore to fit into new environment.
All the best
Thanks, Sachin
Edited by: sachindubey on Apr 10, 2010 12:13 PM

Migration from SRM 5.0 Classic to SRM 7.0 ECS Pricing & Taxation Strategy

Hello All,
We are Upgrading from SRM 5.0 Classic to SRM 7.0 Extended Classic Scenario now. In SRM 5.0 Classic scenario pricing and taxation taken care by R/3 system. Now as part of ECS migration taxation and pricing to be moved from R/3 to SRM as leading PO created in SRM system.
What are the best practises to migrate the Pricing and Taxation into SRM system. Please provide some pointers on this.
Thanks and Regards,
Ramesh

Hello All,
We are Upgrading from SRM 5.0 Classic to SRM 7.0 Extended Classic Scenario now. In SRM 5.0 Classic scenario pricing and taxation taken care by R/3 system. Now as part of ECS migration taxation and pricing to be moved from R/3 to SRM as leading PO created in SRM system.
What are the best practises to migrate the Pricing and Taxation into SRM system. Please provide some pointers on this.
Thanks and Regards,
Ramesh

Migration of Transaction Data from SRM 4.0 to SRM 7.0

Hi
We are upgrading from SRM 4.0 to SRM7.0.
In our old release, many Shopping Cart woul be in the status of Approved, Awaiting Approval and Held. When the same data is migrated to the SRM 7.0 Productive system, how should we take care of the same. We would continue to use the Old Workflow (Application controlled) in SRM 7.0. However we have made changes to the Workflow steps in the new system.
Alo while moving to the new SRM 7.0 Production system, how should we manage the Transactonal Data migration overall.
The client has not agreed to close the Open SC, PO or the confirmations.
Any inputs relating to the Transactional data approach would be highly appreciated.
Regards
Raj

Hi Masa
All said and done we have lot of issues with regard to the data migration. The issues are as below:
1. The POWL doesn't reflect the old data at all in the Upgraded system. I was expecting the "Check Status" functionality to be integrated with POWL so that all the existing Shopping Cart and Purchaser Orders could be seen and the follow on actions could be taken.
2. I am not able to do a generic search on "Advanced Search". For example if I try to Search on the old Shopping Carts, until and unless I give the specific Shopping Cart number, the Search doesn't yield any output.
3. Since POWL doesn't reflect the exisitng Shopping Cart we are not able to proceed ahead with them to create the Follow On documents like Confirmation.
4. The Work Flow in the new system remains Application Controlled only. However we have added few extra steps. The existing "Awaiting Approval" Shopping Carts is not picking up the workflow correctly in the new system.
Any ideas about the same?
Regards
Raj

Need to understand impact on workflows during upgrade from EBP 3.0 to SRM 5

Hello experts,
Greetings to all and a Happy New Year!!
I am new to the workflow concept, though i have a fair idea of EBP.
We are using EBP 3.0, classic scenario. Very soon, we would be upgrading from EBP 3.0 to SRM 5.0. I have a few questions which i need to knw before I take up the upgrade part:
1) The impact on the worflows like Shopping cart approval, purchase contract approval etc when we upgrade from EBP 3.5 to SRM 5.0...
2) Does EBP have their own release strategies or are the release strategies defined in R/3 and applied to the shopping cart when it is ordered in EBP? As in classic scenario, POs are created in R/3, then how does the appoval process happen?
3) What are the necessary things, if any, that I should make sure of before upgrading?
4) Does all workflows also get upgraded or is there any tool to upgrade the workflow?
I am not clear with the approval concept in EBP. I know there are workflows that get triggered when a shopping cart is ordered but the approval process in this workflow is something which i want to understand. Please forward me a document, if possible, or a link will also do.
Please let me know the necessary details.
Thanks in advance.
Regards,
Ayush

Hi Ayush,
Most workflows will be the same, but if you have modifications on these workflows' then i'd suggest reverting back to the standards for the upgrade.
Im not quite sure what you mean about the release strategy. What can be done though, is creating Purchase Requisitions in the R/3 and pass them to the SRM system. From here PO's can be created and the approval process will take place in accordance with your workflow rules in tcode: swb_cond.
Before upgrading, try to have the system as clean as possible. When i say clean, i mean make sure that users are consistent, SC's, PO's etc arent left hanging. Try to avoid carrying documents over to the new system. I'd suggest archiving anything you can too.
I don't have any documents to give you but the basic process and transactions are as follows:
SWB_COND: Your workflow start conditions. Which WF's are on/off (defined by green/red light)
SWI6: This will let you examine a document and its relevant WF by its object id. (SC No, PO No etc..
SWUD: Allows for Consistency checks on your workflow and will find any inconsistencies which are occuring. (Use Test Environment and WF Tech Name i.e 14500015)
SWDD: The workflow builder, will let you build, activate, create new version and modify the worklows in your system.
Approval itself is simply the chain of approval which a workflow is defined to follow. You need your managers to approve/reject and the conditions for which Managers should be called for approval. Its works from Possible Approvers for workitems and Excluded Approvers for workitems.
Understanding the WF log is the most essential thing of all. The understanding of BADI is quite important too.
Hope this info helps you. Check help.sap.com cause everything is documented there too!
Cheers
Will

Upgrade from EBP 4.0 to SRM 5.0

Hi y'all,
We are thinking about upgrading from our current EBP 4.0 to SRM 5.0. We are only using EBP for the self-service procurement scenario - with a classic integration towards two different R/3 4.6C systems. We have no internal catalogs and it is very much a standard set-up
Has anyone had some <b>experiences to share?</b>
Will it be a "large" or a "small" upgrade?
Are there any watchouts or learnings?
Many thanks in advance
Thyge

hello Thyge,
you are running on EBP 4.0, i.e. SRM 3.0: Extension of mainstream maintenance was extended from end of June 2006 to end of December 2006, at no extra fee.
Requisite 4.0 will be supported to end of December 2006 (refer to SAP Note 485884 for detailed information on Requisite).
That means that, excpet if you go in a custom support contract with SAP, your system will not be supported at end of 2006.
So you must "be prepared" and do this upgrade in 2006 !!!
If you don't use new features, have only 20 users, and a nearly standard SRM, you upgrade efforts will be really light:
- technical upgrade (attention: new Oracle version required) Unicode version ?
- nearly no custom dev alignement
- light re-training
The main workload would be the migration from Requisite to SAP CCM 2.0 (if you choose this option), depending on your actual content management strategy.
I think a 3 months upgrade project will be the correct duration for you.
Rgds
Christophe

SRM Server 5.5 SP stack Upgrade from 14 to 17 ( 15 16 & 17)

Dear Experts,
We are on SRM 5.0, Server 5.5 Extended Classic Scenario
We recently upgraded from SP 14 and now added 15, 16 and 17.
While testing the plan driven scenario, for PR with material master we are getting the follwoing error:
BBP_BC_EXTREQ_INB , BBP_EXTREQ_TRANS , Product ID is longer than the Customizing setting
Please advice for resolution.
Regards,
Anil Rajpal
Edited by: Anil anil on May 5, 2011 1:18 PM

Study this SAP note for more understanding the issue with technical resource.. the give note is just clue and may not be a solution...since already you have higher version with updated sp(s)
Are you geting this error for all the material transfer ? or some material only fails?
Hope you must debug the queue on product length.
Note 532286 - Error "Product ID longer than allowed in Customizing
during SPAU analysis - did you ignore this ?
but you must see this piece of code is overwritten by any other code
Symptom
During the transfer of external requirements from a planning system, the outbound queue can remaining hanging with the following error:
Product ID is longer than allowed in Customizing.
Other terms
SRM, Supplier Relationship Management, Ecommerce, E-Commerce, BBP EBP, Enterprise Buyer professional edition, E-Buyer, E-Procurement, SAP Business-to-Business Procurement, external requirement, PM, Plant Maintenance, Content Integrator
Reason and Prerequisites
First check whether Note 530920 was implemented in your system.
If the error still occurs nevertheless, the following situation might have occurred:
1. The product ID was transferred with a length of 18 characters to the EBP System
2. A product with this product ID exists in the EBP System, and therefore the product ID was converted into the internal 40-character format (with leading zeros) in the EBP System.
3. Afterwards the attempt is made to determine the product GUID. However, this failed since there are several products with the same product ID in your system and the external demand came from a system from which you have not replicated the product master.
4. Since no product GUID was found, the product is considered as an external product and the system checks whether the product ID matches the settings in Customizing. During this process, the error occurs that the 18-character product ID is not used from the back end system, but instead the product ID converted to the 40-character format in step 2. If you have set a maximum length smaller than 40 for the product ID in Customizing, it results in the above-mentioned error message
Solution
Implement the attached program correction.
but i did not face this issue during our service pack upgrades...

Upgrade SRM from SRM 3.5 to SRM 5.0 - BW Influence

Hello,
We were working with BW above SRM 3.5 and built a lot of Business logic, DSO and Infocubes using the extractors: 0BBP_TD_PO_1, 0BBP_TD_CONF_1. We are now upgrade our SRM system to SRM 5.0 and found out that all the data sources had changed. Is there standard migration for the DSO 0bbp_po and 0bbp_con ? Do we need to build everything from the beginning?
Thanks,
Amir

EBP 3.5 to SRM 5.0 upgrade
Go through the thread, i hope this would help you.

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

SRM Upgrade from SRM 4.0

Similar Messages

Maybe you are looking for