SRM System upgrade from SRM 5.0 to SRM 7.01

[Former Member]

Hello SRM Gurus,

I am working on a upgrade project from SRM 5.0 to SRM 7.01 ( EHP 1). Its a classic scenario and basically a Technical Upgrade.

I would like to know from people who have done  upgrade earlier of the same from SRM 5.0 to SRM 7.01.

Functional Perspective - 1. What additional configurations will be required in SRM 7.01 apart from basic configurations which would be more or less same as those of SRM 5.0.

2. What steps would be required for Enterprise Portal / POWL integration with SRM 7.01.

3. What steps required for PI integration.

Technical Perspective -

1. Which Badis , Function module , Programs are obselete now in SRM 7.01 .

2. Do we require some technical adjustments for Enterprise Portal , PI integration.

3. Since BRF is new workflow in SRM 7.01 , so how do we shift from existing application workflow to Process workflow ( BRF ) . Whetther is it mandatory to adopt BRF ? or can we still work with traditional application workflow because there are some z developments done for this.

Please let me know the above details and also if i have missed some important points.

Thanks,

Ashish

[Former Member]

Some more pointers to focus when upgrading from version 5.5 to 7.0:

Most imp configuration would be for Backend systems.

Change in Roles for Portal and backend in addition to many configurations including UWL,Iview properties etc.

Not much configuration change on PI side except for new functinality.

From technical point,you need to have a very good resource for Portal configuration as Portal is now mandatory with SRM 7.01 if you are not using NWBC.

Also regarding workflows,PCW are much more flexible and reliable as compared to ACW.So it would be worth switching to PCW with the upgrade.Workflow configuraion and development is another key area where expertise will help reduce the development timeline convertign old Application controlled workflows to Process controlled workflows.

[former_member64271]

Hello Ashish,

Adding some more information you requested:

What steps would be required for Enterprise Portal / POWL integration with SRM 7.01?

You might find this link useful: http://wiki.sdn.sap.com/wiki/display/EP/Portal+7.0+and+SRM+6.0+Integration(Part+II)

Also, refer to SRM Installation/Configuration guides found on SAP Marketplace.

Which Badis , Function module , Programs are obselete now in SRM 7.01 ?

New & Obsolete BADI’s are as follows:

New in SRM 7.0

Input Values for Temporary Contact Person Creation

BADIs for Process-Controlled Workflow (BRF)

Process Customer Fields

Digital Signature - Define Customer-Specific Document Preview

Obsolete in SRM 7.0

Change Display in Shopping Cart (ITS Technology)

Deactivate Cross-Catalog Search (ITS Technology)

Display of Input Helps, and Favorites (ITS Technology)

Restrict the Display in Input Helps (ITS Technology)

Internal Temporary Storage of Favorites for Input/Search Helps

Final Saving of Favorites for Input Helps and Search Helps

Determine Screen Variants (ITS Technology)

Field Control in Purchasing Document (ITS Technology)

Do we require some technical adjustments for Enterprise Portal , PI integration?

According to the Upgrade guide, if you will be upgrading to SRM 7.1, you require:

• PI: SAP enhancement package 2 for SAP NetWeaver 7.0
• PI Content for the following components:
  • SRM Server 7.01
  • BI Content 7.0.5
  • SRM-MDM Catalog 7.01
• SAP enhancement package 2 for SAP NetWeaver Portal 7.0.
• Import into SAP NetWeaver Portal: Business Package for SAP SRM 7.0 EHP1

Hope this information was useful.

[Former Member]

HI Ashish,

You can consider the below points.

1. You might need to run BP_TD_SWITCH report in SRM after the upgrade to SRM 7.0. After upgrade, it is likely that the business partners become inconsistent. You can check in BUT000 for the business partners, whether the validity start date and validity end date are set to default date. If not, the above report will take care of this issue.

2. If the attachment transfer from SC to PR/PO stops working, you can make the changes in the BAdI BBP_CREATE_BE_RQ_NEW / BBP_CREATE_BE_PO_NEW depending upon whether you create PR or PO. The following parameters need to be set in the BAdI.

BE_DOC_TYPE = SRM

BE_STORAGE_CAT = DMS_C1_ST

TRANSFER_ACTIVE = X

3. If you are using punch out catalogues, it is likely that some of them might not work after the upgrade. It needs to be properly tested. SAP suggests the punch out vendors should be on OCI 4.0 for SRM 7.0. You need to contact the vendor for the same.

In some cases, the items don't get transferred from punch out catalogue to the SC. You can make the changes in the call structure by inserting the inbound and outbound OCI parameters and setting them to X. These two parameters should be inserted before HOOK_URL parameter.

If any issue in IE 8, please refer note 1511147.

In some of the cases, you need to do a http watch trace to know the exact cause of the issue.

4. Application controlled workflow can still be used in SRM 7.0.

Thanks & Regards,

Aswini