sap srm ins
DESCRIPTION
sap srm insalltion with eh2TRANSCRIPT
SAPTECHNO
Extra LargeLargeNormal CONTACT ACCUEIL
Rechercher
Vous êtes ici : Home SAP Top Notes Note 1582094
Note 1582094 - EHP2 for SAP SRM 7.0 SP stacks - Release & Information Note
Header
Version / Date 22 / 2013-03-18
Priority Correction with high priority
Category Release planning information
Primary ComponentXX-SER-REL Releaseinformation ERP
Secondary Components
Summary
Symptom
This Release- & Information Note (RIN) contains information and references to notes for applying Support Package Stacks (SPS) of SAP SRM 7.0 Enhancement Package 2
Note: This note is subject to change. Listed below are a few general points to keep in mind:
GENERAL INFORMATION
Read this note completely BEFORE applying SP Stacks of SAP Enhancement Package 2 of SAP SRM 7.0 and follow the instructions given below.
Ensure that you check the note for changes on a regular basis. All changes made after release of the stack are documented in section "Changes made after Release of SP Stack <xx>" at the end of this note.
Ensure that you install new Support Package Stacks regularly to prevent problems that have already been corrected, from recurring in your SAP solution. For more
Recherche...
Summary
information about SAP's Release Strategy, see SAP Service Marketplace at service.sap.com/releasestrategy.
Before you begin, you should have a clear picture of the components you use in your system landscape. Only instructions and notes for components that you use are relevant for you.
In addition to the notes mentioned in this note, you should also take into account the list of side effects known for Support Packages, which is created especially for your situation (SP queue). You can request for this list on SAP Service Marketplace at service.sap.com/notes.
While this SAP Release- & Information Note (RIN), in general, refers to other SAP Notes of very high priority and critical for successful implementation and operation of the SP Stack, the list of side effects includes notes of different priorities, which are related to the range of Support Packages you will apply with your selected SP queue.
Single patches can be found on SAP Service Marketplace atservice.sap.com/patches.
You will find general information about SP Stacks underservice.sap.com/sp-stacks.
Be informed that all corrective SPs, including SP Stacks, released after April 2, 2007, are available exclusively through the Maintenance Optimizer in SAP Solution Manager. For more information about the Maintenance Optimizer, see SAP Service Marketplace atservice.sap.com/solman-mopz.
TECHNICAL INFORMATION
SAP strongly recommends using SAP Solution Manager to identify & implement the required SPs. The Solution Manager - Maintenance Optimizer provides you with the option to automatically calculate the recommended SP levels and add them to your download basket. It provides you with a combined import queue that includes the
Summary
Enhancement Package SPs as well as the required SRM 7.0 SP Stack components.
Before you begin the upgrade process, identify the SP levels of the components you use in your system landscape.
Technical Usages - You can select the Technical Usages on the SP stack download page in the Maintenance Optimizer.
SPAM Update - We strongly recommend that you apply the latest version of the Support Package Manager before you apply any other Support Packages.
SPAM Updates are available on the download page for the SP Stack or on SAP Service Marketplace at service.sap.com/patches -> Support Packages and Patches -> SAP Support Packages in Detail -> ABAP Support Package Manager -> Download the Support Package Manager for your release. For additional information, see the initial screen of transaction SPAM, choose the 'i' icon (online documentation: help -> application help).
When you import components using the Support Package Manager, ensure that no system activities occur in parallel and no background jobs are running.
To update Java components, use JSPM and the related SP-Stack stack.xml file. For more information, refer to SAP Note 884537.
Single patches can be found on SAP Service Marketplace atservice.sap.com/patches.
Installation an Upgrade Information
For known upgrade issues from previous releases, see SAP Note 1448239
You can find information about browser support in SAP
Summary
Note 1574357.
For the installation of Java Components ensure to use the correct Kernel DVD. For more details see SAP Note 1642797.
Before you begin to implement new functionality provided in EhP2 for SAP SRM 7.0, read SAP Note 1621788.
If the component CPRXRPM 450_700 or CPRXRPM 500_702 is present in your system you need to apply SAP Note 1660342 as a prerequisite before the upgrade.
For more information about the usage of SAP SRM on one client in SAP ERP 6.0, see SAP Note 963000.
Important Consideration
Please ensure to update your system at least to Support Package Stack 04 (SP stack for General Availability). This is applicable for both, installation and upgrade.
SAP Business Suite 7 Innovations 2011 (including EhP6 for SAP ERP 6.0, EhP2 for SAP CRM 7.0, EHP2 for SAP SCM 7.0 and EhP2 for SAP SRM 7.0) based on SAP NetWeaver 7.0 including Enhancement Package 3 is the last SAP Business Suite release with dual-stack support, for more information (including information about a dual stack split tool), see SAP Note 1655335. Please note that as of SAP Business Suite 7 (including EhP4 for SAP ERP 6.0, SAP CRM 7.0, SAP SRM 7.0 and SAP SCM 7.0), you can no longer install Dual Stack Application Systems (ABAP+Java) see SAP Note 855534.
If you have an Add-On installed on top of your existing SAP SRM installation, please read SAP Note 1598140.
The most recent versions of SAP SRM Master Guide and Upgrade Master Guide are available on SAP Service Marketplace atservice.sap.com/instguides -> SAP Business Suite Applications - SAP SRM -> SAP SRM Server 7.02.
Summary
Other terms
SAP SRM, SRM, Supplier Relationship Management, EBP, SAP Enterprise Buyer, SUS, Supplier Self-Services, Auctioning, Direct Procurement, Indirect Procurement, Self-Service Procurement, Plan-Driven Procurement, Service Procurement, Supplier Enablement, Strategic Sourcing, Sourcing, Contract Management, Bidding Engine, Catalog, Catalog Content Management, eProcurement, SRM 7.0 ,SRM 7.02
Solution
SUPPORT PACKAGE STACK 06 (02/2013)
Installation Requirements: Enhancement Package 2 for SAP SRM 7.0 SP Stack 06 is based on:
SAP SRM 7.0 SP Stack 13.
Enhancement Package 3 of SAP NetWeaver 7.0 Support Package Stack 06 (02/2013).For more information about SAP NetWeaver, see the stack guide on SAP Service Marketplace at service.sap.com/maintenanceNW70 -> EHP3 SPS4
SP Equivalence LevelsThe SP equivalence levels for SAP SRM 7.0 EhP2 SP06 are listed below. This means that the correction levels are equivalent and also determines your upgrade path to any Enhancement Package:
SRM 7.0 EhP2 SPS06 --- SRM 7.0 EhP1 SPS09 --- SRM 7. 0 SPS13 ---SRM 5.0 SPS21 --- SRM 4.0 SPS18
SAP NetWeaver SP Stack Levels
In September 2011 SAP introduced the so called 'Minimum SP Stack Level' in order to simplify the maintenance process in bigger system landscapes. Based on SAP's version interoperability paradigm, decoupled software updates in system landscapes can now also be offered for SP stack implementations. Details about version interoperability and the supported software update strategies are described
Summary
here:http://wiki.sdn.sap.com/wiki/display/SLGB/Version+Interoperability+Strategy
Based on the Landscape Pattern (HUB or SIDECAR) defined in SMSY for the JAVA system, the Maintenance Optimizer will determine the corresponding SAP NetWeaver SP Stack. Please refer also to SAP Note1620472.
You do not need to apply a new SP Stack on the technical instance defined as HUB in case your JAVA instance is greater or equal the defined Minimum SP Stack Level outlined below:
SAP NetWeaver 7.0 SP Stack 18 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 03 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 03 (03/2010) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.03 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.03
SAP NetWeaver 7.30 SP Stack 02 (03/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
If your JAVA instance is below the defined Minimum SP Stack Level, you need to apply the following Recommended SAP NetWeaver SP Stacks for instances in the cases outlined below:
SAP NetWeaver 7.0 SP Stack 27 (08/2012) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 13 (02/2013) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 12 (09/2012) - If you are running your JAVA instance on SAP NetWeaver 7.02
Summary
SAP NetWeaver 7.03 SP Stack 06 (02/2013) - If you are running your JAVA instance on SAP NetWeaver 7.03
SAP NetWeaver 7.30 SP Stack 08 (10/2012) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 06 (01/2013) - If you are running your JAVA instance on SAP NetWeaver 7.31
For more information about the NW SP Stacks, see SAP Service Marketplace at service.sap.com/maintenanceNW70.
Important Consideration
SAP MDM CATALOG MGMT. 7.02 SPS06 is based on Core SAP MDM 7.1 SPS 09. For more information on SAP MDM CATALOG MGMT. 7.02 SP 06 please refer SAP Note 1548532.
Notes to be applied as part of this stack according to processes:
SAP Note Number Description
Issue with note implementation after patching process
1817684 To correct the function group inconsistency in
Service Procurement
1818934 SRVMAPKEY generated for CCM and Purchase orders
Self-Service Procurement (Classic)
1823170 Simplified shopping cart displayed in
Self-Service Procurement (Extd. Classic)
1777860 PDO layer error when DELETE the PO
Summary
1468452 Expression 0B_PO_ISCHANGEVERS is not filled.
Strategic Sourcing with RFx
1799599 Some PO header business partners disappear after check
Bid Decoupling
1794721 Questions are not visible to bidder in RFx view.
Note:
Customers utilizing Simplified Shopping Cart feature, please implement notes1823170andopening the shopping cart document in the simplified shopping cart mode.
Changes made after the release of Enhancement Package 2 for SAP SRM 7.0 SP Stack 06
1661038 FAQ:Purchase Requisition in External Sourcing
***********************************************************************
SUPPORT PACKAGE STACK 05 (11/2012)
Installation Requirements: Enhancement Package 2 for SAP SRM 7.0 SP Stack 05 is based on:
SAP SRM 7.0 SP Stack 13.
Enhancement Package 3 of SAP NetWeaver 7.0 Support Package Stack 05 (10/2012).For more information about SAP NetWeaver, see the stack guide on SAP Service Marketplace at service.sap.com/maintenanceNW70 -> EHP3 SPS4
SP Equivalence LevelsThe SP equivalence levels for SAP SRM 7.0 EhP2 SP05 are listed below. This means that the correction levels are equivalent and also determines your upgrade path to any Enhancement Package:
SRM 7.0 EhP2 SPS05 --- SRM 7.0 EhP1 SPS09 --- SRM 7. 0 SPS13 ---SRM 5.0 SPS21 --- SRM 4.0 SPS18
SAP NetWeaver SP Stack Levels
Summary
In September 2011 SAP introduced the so called 'Minimum SP Stack Level' in order to simplify the maintenance process in bigger system landscapes. Based on SAP's version interoperability paradigm, decoupled software updates in system landscapes can now also be offered for SP stack implementations. Details about version interoperability and the supported software update strategies are described here:http://wiki.sdn.sap.com/wiki/display/SLGB/Version+Interoperability+Strategy
Based on the Landscape Pattern (HUB or SIDECAR) defined in SMSY for the JAVA system, the Maintenance Optimizer will determine the corresponding SAP NetWeaver SP Stack. Please refer also to SAP Note1620472.
You do not need to apply a new SP Stack on the technical instance defined as HUB in case your JAVA instance is greater or equal the defined Minimum SP Stack Level outlined below:
SAP NetWeaver 7.0 SP Stack 18 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 03 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 03 (03/2010) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.03 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.03
SAP NetWeaver 7.30 SP Stack 02 (03/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
If your JAVA instance is below the defined Minimum SP Stack Level, you need to apply the following Recommended SAP NetWeaver SP Stacks for instances in the cases outlined below:
Summary
SAP NetWeaver 7.0 SP Stack 27 (08/2012) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 12 (08/2012) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 12 (09/2012) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.03 SP Stack 05 (10/2012) - If you are running your JAVA instance on SAP NetWeaver 7.03
SAP NetWeaver 7.30 SP Stack 08 (10/2012) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 05 (10/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
For more information about the NW SP Stacks, see SAP Service Marketplace at service.sap.com/maintenanceNW70.
Important Consideration
SAP MDM CATALOG MGMT. 7.02 SPS05 is based on Core SAP MDM 7.1 SPS 09. For more information on SAP MDM CATALOG MGMT. 7.02 SP 05 please refer SAP Note 1548532.
Notes to be applied as part of this stack according to processes:
SAP Note Number Description
Catalog Content Management (SRM-MDM)
1781826 Catalog product in CCTR results in error
Self-Service Procurement (Classic)
1791665 Auction creation from SOCO has wrong item
Summary
Self-Service Procurement (Extd. Classic)
1784487 Dump while clicking on Propose Source of
1711478 Page not found or not available
Strategic Sourcing with RFx
1630248 SP30:Field descriptions of Errorstack gets lost
1789958 Abortion: DYNPRO_SEND_IN_BACKGROUND
1790246 Item level acceptance not possible in RFx Response & Awards
Changes made after the release of Enhancement Package 2 for SAP SRM 7.0 SP Stack 05
1573047 CPPR: Error 'Please maintain Service or Limits'
1761712 Enable contract upload for replicated master agreement
1764355 1764355:Service lines not trasferred from catalog
1769491 Unable to Submit Response in Offline Bidding with Questions
1773362 Dump in RFX while navigating from NA tab to item tab
1774091 POR and ASN flags are editable even if invoice exists in PO
1776744 Corrections for unified rendering up to SAP_BASIS 731/05 III
1777290 Unable to display the PR in CPPR
1800381 Notification mail ends up with error 'Incorrectly Processed'
1804939 Issue with Substitute Item in Bidder login
***********************************************************************
SUPPORT PACKAGE STACK 04 (08/2012)
Installation Requirements: Enhancement Package 2 for SAP SRM 7.0 SP Stack 04 is based on:
SAP SRM 7.0 SP Stack 12.
Enhancement Package 3 of SAP NetWeaver 7.0 Support Package Stack 04 (06/2012).For more information about SAP NetWeaver, see the stack guide on SAP Service Marketplace at service.sap.com/maintenanceNW70 -> EHP3 SPS4
Summary
SP Equivalence LevelsThe SP equivalence levels for SAP SRM 7.0 EhP2 SP04 are listed below. This means that the correction levels are equivalent and also determines your upgrade path to any Enhancement Package:
SRM 7.0 EhP2 SPS04 --- SRM 7.0 EhP1 SPS08 --- SRM 7. 0 SPS12 ---SRM 5.0 SPS20 --- SRM 4.0 SPS17
SAP NetWeaver SP Stack Levels
In September 2011 SAP introduced the so called 'Minimum SP Stack Level' in order to simplify the maintenance process in bigger system landscapes. Based on SAP's version interoperability paradigm, decoupled software updates in system landscapes can now also be offered for SP stack implementations. Details about version interoperability and the supported software update strategies are described here:http://wiki.sdn.sap.com/wiki/display/SLGB/Version+Interoperability+Strategy
Based on the Landscape Pattern (HUB or SIDECAR) defined in SMSY for the JAVA system, the Maintenance Optimizer will determine the corresponding SAP NetWeaver SP Stack. Please refer also to SAP Note1620472.
You do not need to apply a new SP Stack on the technical instance defined as HUB in case your JAVA instance is greater or equal the defined Minimum SP Stack Level outlined below:
SAP NetWeaver 7.0 SP Stack 18 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 03 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 03 (03/2010) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.03 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.03
Summary
SAP NetWeaver 7.30 SP Stack 02 (03/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
If your JAVA instance is below the defined Minimum SP Stack Level, you need to apply the following Recommended SAP NetWeaver SP Stacks for instances in the cases outlined below:
SAP NetWeaver 7.0 SP Stack 26 (02/2012) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 11 (03/2012) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 11 (03/2012) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.03 SP Stack 04 (06/2012) - If you are running your JAVA instance on SAP NetWeaver 7.03
SAP NetWeaver 7.30 SP Stack 07 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 04 (06/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
For more information about the NW SP Stacks, see SAP Service Marketplace at service.sap.com/maintenanceNW70.
Important Consideration
SAP MDM CATALOG MGMT. 7.02 SPS04 is based on Core SAP MDM 7.1 SPS 08. For more information on SAP MDM CATALOG MGMT. 7.02 SP 04 please refer SAP Note 1548532.
Notes to be applied as part of this stack according to processes:
Summary
SAP Note Number
Description
Installation/upgrade
1713393 Error in TREXADMIN on TREX 7.00
Catalog Content Management
1548532 SRM-MDM Catalog 7.02 Repository information
1748289 Problem with uploading Sustainability record to catalog
Self-Service Procurement
1712530 Corrections for unified rendering up to SAP_BASIS 731/04 I
1747975 Deleting PO throws unwanted Popups
1748334 Contract Price is not picked by item from Propose SoS
1749643 Error in Add item from Shopping Cart in local PO
1755249 History: SC related RFx Response doc is not getting udpated
Service Procurement
1746653 Best Bid Value field calculates Contingency item value also
Strategic Sourcing
1745887 Infoline missing in follow documnet
1747616 Extended classic PO creation fails with supplement items
1731823 Partner differences wrongly determined
1629859 PurchaseRequestERPSourcingRequest_Out:PR changes not updated
1747769 Condition: Not able to change the scales
1714594 Rfx response modification checkbox is getting unchecked
1748147 Issue with Auction Responses when auction created from rfx.
1748168 Create PO_Xml fails in ERP to FEH
1748315 Not able to award response due to improper item ordering
1746737 Issue in change version ofresponse in Bid-Decoupled scenario
Summary
1746345 ESA: No link maintained between backend PO and shopping cart
1749130 Issues with SOCO reject status for service item
1732790 PO confirmation with quotation reference do no update SC
1749601 Response_Contract_XML fail in ERP
1749233 ME33K: Service item price is zero for SRM GOA
1749682 ESA: Short dump in PO incoming confirmation for services
1749585 Purchase Requisition reappears in SOCO after RFx close
1744887 Info Record conditions not updated by SRM Central Contract
1728308 Not able to copy an RFx which has MM-SRV Structure
1749562 Creation Date and time missing in Rfx response and Rfx
1750345 Able to delete a Response after submitting it
1748103 Update of Info Rec. cond. for multiple items not working
1751563 It is possible to seach a Closed Rfx in Supplier System
1621788 SAP SRM 7.0 EHP2 : Important info about scenarios
1751254 Delivery date rolls down in supplier system for hier_srm
1754897 Rfx Bids not copied to Auction History,On convert to Auction
1694596 Target Value behaviour in sourcing scenario
1712226 Important Information about Strategic Sourcing Scenario
1753241 PO confirmation XML fails in SRM for PO created from Rfx
1753996 No ERP Sourcing confirmation triggered when adding new items
1754186 Backend contract from accepted RFX response not created
1754661 Deleted Rfx Response attachment visible in the SRM System
1754763 Returned Bid information is not shown in the RFX tracking
1754951 Edit of Quote in Awaiting approval in Bid-Decoupled Scenario
1754887 Product id copied from base item to expressive item
***********************************************************************
SUPPORT PACKAGE STACK 02 (03/2012)
Installation Requirements: Enhancement Package 2 for SAP SRM 7.0 SP Stack 02 is based on:
SAP SRM 7.0 SP Stack 11.
Enhancement Package 3 of SAP NetWeaver 7.0 Support
Summary
Package Stack 02 (03/2012).For more information about SAP NetWeaver, see the stack guide on SAP Service Marketplace at service.sap.com/maintenanceNW70 -> EHP3 SPS2
SP Equivalence LevelsThe SP equivalence levels for SAP SRM 7.0 EhP2 SP02 are listed below. This means that the correction levels are equivalent and also determines your upgrade path to any Enhancement Package:
SRM 7.0 EhP2 SPS02 --- SRM 7.0 EhP1 SPS07 --- SRM 7. 0 SPS11 ---SRM 5.0 SPS19 --- SRM 4.0 SPS17
SAP NetWeaver SP Stack Levels
In September 2011 SAP introduced the so called 'Minimum SP Stack Level' in order to simplify the maintenance process in bigger system landscapes. Based on SAP's version interoperability paradigm, decoupled software updates in system landscapes can now also be offered for SP stack implementations. Details about version interoperability and the supported software update strategies are described here:http://wiki.sdn.sap.com/wiki/display/SLGB/Version+Interoperability+Strategy
Based on the Landscape Pattern (HUB or SIDECAR) defined in SMSY for the JAVA system, the Maintenance Optimizer will determine the corresponding SAP NetWeaver SP Stack. Please refer also to SAP Note1620472.
You do not need to apply a new SP Stack on the technical instance defined as HUB in case your JAVA instance is greater or equal the defined Minimum SP Stack Level outlined below:
SAP NetWeaver 7.0 SP Stack 18 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 03 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.01
Summary
SAP NetWeaver 7.02 SP Stack 03 (03/2010) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.30 SP Stack 02 (03/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
If your JAVA instance is below the defined Minimum SP Stack Level, you need to apply the following Recommended SAP NetWeaver SP Stacks for instances in the cases outlined below:
SAP NetWeaver 7.0 SP Stack 26 (02/2012) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 11 (03/2012) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 10 (12/2011) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.30 SP Stack 05 (11/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
SAP NetWeaver 7.31 SP Stack 03 (04/2012) - If you are running your JAVA instance on SAP NetWeaver 7.31
For more information about the NW SP Stacks, see SAP Service Marketplace at service.sap.com/maintenanceNW70.
Restriction for Installation and Upgrade
Because of an error in the TREX Client of SAP AS ABAP 7.31 (used by SAP Business Suite 7 Innovations 2011) comparing to SAP AS ABAP 7.02 the Version Interoperability for TREX 7.0 is violated - it is either required to upgrade the TREX to 7.10 before updating the Business Suite System or wait until a correction for the error is provided.
Summary
Important Consideration
SAP MDM CATALOG MGMT. 7.02 SPS02 is based on Core SAP MDM 7.1 SPS 08. For more information on SAP MDM CATALOG MGMT. 7.01 SP 02 please refer SAP Note 1548532.
Notes to be applied as part of this stack according to processes:
SAP Note Number
Description
General
1674472 Adhoc approver disappears for saved purchasing
Business Warehouse
1636155 730SP6:Error 'RSTRAN 510' while activating Transformation
Catalog Content Management
1681129 Conditions not copied during PR creation from MDM
1681236 Error in ordering SC having service items from Catalog
1673698 Catalog Item Price is Editable
1570580 BAPI Call for Catalog items referencing CCTR leads to error
Contract Management
1677424 PurchasingContractERPRequest_I: Error message VK098
1677038 Dump when editing a rejected document
Self-Service Procurement
1687645 Error in Invoice display for Managers Login
1638075 Iview for invoicing party is not assigned to manager role
804249 SURVEY: Short dump when you send a questionnaire
1676082 Not possible to execute BBP_GET_STATUS_2 when days is blank
1673946 Multiple issues in RFx creation from Shopping Cart
1691568 Professional Shopping Cart dispayed from ESS role
Service Procurement
1681175 Bidder cannot change Expressive Items in Returned
1692823 On entering wrong payment term Excel upload throws error
1693727 No errors in contract when pressing Check button
1692485 Excel Upload: Product data could not be interpreted
Strategic Sourcing
1679161 Release rejected bid is not editable in case of auctions
Summary
1681696 Changed version quote with expressive item not replicated
1673698 Catalog Item Price is Editable
1570580 BAPI Call for Catalog items referencing CCTR leads to error
1676014 CPPR: Submit not possible without submission deadline date
1692315 Auction Incorrect bidder details
1692265 Issues while replication change version of Response
1691740 Publish button not enabled for Release rejected RFX
1683533 Reinitialization of Approval Process
1681794 DO Layer error when changing a saved purchasing
1678433 Restart behaviour in completion steps
1667331 Approver preview in recall process
1690581 Target value visible when follow on doc is "PO or
1672674 Advanced Bid Comparision Various Issues
1694941 Convert-to-auction button will be enabled after price opening
1694101 Issues with auction replication in response outside firewall
1694412 Unnecessary warning pop-up on permissions table in tendering
1693892 Saved technical bid visible to the Technical evaluator
1695004 Return option in Quotes created in Auction process
1695332 Issues in total value calculation for items in Response
1690215 RFx Response Awarding issues
1693212 Unwanted warning messages during RFx response
***********************************************************************
SUPPORT PACKAGE STACK 01 (11/2011)
As a special case, Support Package Stack 01 has to be applied with theinstallation of Enhancement Package 2 for SAP SRM 7.0.
Installation Requirements:
Enhancement Package 2 for SAP SRM 7. 0 SP Stack 01 is based on EhP3 for SAP NetWeaver SP Stack 01 (11/2011). For more information about SAP NetWeaver, see the stack guide on SAP Service Marketplace atservice.sap.com/maintenanceNW70 -> EHP3 SPS1
SP Equivalence LevelsThe SP equivalence levels for SAP SRM 7.0 EhP2 SP01 are listed below. This means that the correction levels are equivalent and also determines your upgrade path to any
Summary
Enhancement Package:
SRM 7.0 EhP2 SPS01 --- SRM 7.0 EhP1 SPS05 --- SRM 7. 0 SPS11 ---SRM 5.0 SPS19 --- SRM 4.0 SPS17
SAP NetWeaver SP Stack Levels
In September 2011 SAP introduced the so called 'Minimum SP Stack Level' in order to simplify the maintenance process in bigger system landscapes. Based on SAP's version interoperability paradigm, decoupled software updates in system landscapes can now also be offered for SP stack implementations. Details about version interoperability and the supported software update strategies are described here:http://wiki.sdn.sap.com/wiki/display/SLGB/Version+Interoperability+Strategy
Based on the Landscape Pattern (HUB or SIDECAR) defined in SMSY for the JAVA system, the Maintenance Optimizer will determine the corresponding SAP NetWeaver SP Stack. Please refer also to SAP Note1620472.
You do not need to apply a new SP Stack on the technical instance defined as HUB in case your JAVA instance is greater or equal the defined Minimum SP Stack Level outlined below:
SAP NetWeaver 7.0 SP Stack 18 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 03 (01/2009) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 03 (03/2010) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.30 SP Stack 02 (03/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
If your JAVA instance is below the defined Minimum SP Stack Level, you need to apply the following Recommended SAP NetWeaver SP Stacks for instances in
Summary
the cases outlined below:
SAP NetWeaver 7.0 SP Stack 25 (08/2011) - If you are running your JAVA instance on SAP NetWeaver 7.0
SAP NetWeaver 7.01 SP Stack 10 (08/2011) - If you are running your JAVA instance on SAP NetWeaver 7.01
SAP NetWeaver 7.02 SP Stack 09 (09/2011) - If you are running your JAVA instance on SAP NetWeaver 7.02
SAP NetWeaver 7.30 SP Stack 04 (09/2011) - If you are running your JAVA instance on SAP NetWeaver 7.30
For more information about the NW SP Stacks, see SAP Service Marketplace at service.sap.com/maintenanceNW70.
Restriction for Installation and Upgrade
Because of an error in the TREX Client of SAP AS ABAP 7.31 (used by SAP Business Suite 7 Innovations 2011) comparing to SAP AS ABAP 7.02 the Version Interoperability for TREX 7.0 is violated - it is either required to upgrade the TREX to 7.10 before updating the Business Suite System or wait until a correction for the error is provided.
Important Consideration
SAP MDM CATALOG MGMT. 7.02 SPS01 is based on Core SAP MDM 7.1 SPS 07. For more information on SAP MDM CATALOG MGMT. 7.01 SP 01 please refer SAP Note 1548532.
Notes to be applied as part of this stack according to processes:
SAP Note Number
Affected Releases
Software Component Release From Release To Release
Summary
SRM_SERVER 702 702 702
Related Notes
1649406Release Restriction Note for SRM 7.0 Enhancement Package 2
1621887 SRM PPS 702 Brazil Localization
1621788SAP SRM 7.0 EHP2 : Important info about scenarios
1598140SAP Enhancement Package 2 for SAP SRM 7.0:Compatible Add-ons
1580107Solution Manager Content for SAP EHP2 for SAP SRM 7.0
1574357 Main Browser Note for BS7i2011
1548532SRM-MDM Catalog 7.02 Repository information
1523939SAP SRM 7.0 EhPxx: PPS-Important info on New Functionality
Powered by Joomla!. Valid XHTML and CSS.