SAPTECHNO

Extra LargeLargeNormal CONTACT ACCUEIL Rechercher

Recherche...

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 Priority Category Primary Component 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.

22 / 2013-03-18 Correction with high priority Release planning information XX-SER-REL Releaseinformation ERP

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 information about SAP's Release Strategy, see SAP Service Marketplace

Summary 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 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.

Summary

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 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

Summary 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. 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 Levels The 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

Summary 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:

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

Issue with note implementation after patching process 1817684 Service Procurement 1818934

Description

To correct the function group inconsistency in

SCWN

SRVMAPKEY generated for CCM and Purchase

orders

Self-Service Procurement (Classic) 1823170 Self-Service Procurement (Extd. Classic) 1777860 1468452 Strategic Sourcing with RFx 1799599 Some PO header business partners disappear after check PDO layer error when DELETE the PO Expression 0B_PO_ISCHANGEVERS is not filled. Simplified shopping cart displayed in professional

Bid Decoupling 1794721 Note: Questions are not visible to bidder in RFx view.

Summary
Customers utilizing Simplified Shopping Cart feature, please implement notes1823170and 1691568 for any issues faced while opening 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 Levels The 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 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.

Summary 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 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

Summary 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

Catalog Content Management (SRM-MDM) 1781826

Description

Catalog product in CCTR results in error

079(BBP_CTR)

Self-Service Procurement (Classic) 1791665 Self-Service Procurement (Extd. Classic) 1784487 1711478 Strategic Sourcing with RFx 1630248 1789958 1790246 SP30:Field descriptions of Errorstack gets Abortion: DYNPRO_SEND_IN_BACKGROUND Item level acceptance not possible in RFx Response & Awards lost Dump while clicking on Propose Source of Page not found or not available Supply Auction creation from SOCO has wrong item numbering

Changes made after the release of Enhancement Package 2 for SAP SRM 7.0 SP Stack 05

1573047 1761712 1764355 1769491 1773362 1774091 1776744 1777290

CPPR: Error 'Please maintain Service or Enable contract upload for replicated master 1764355:Service lines not trasferred from Unable to Submit Response in Offline Bidding Dump in RFX while navigating from NA tab to POR and ASN flags are editable even if invoice Corrections for unified rendering up to Unable to display the PR in CPPR

Limits' agreement catalog with Questions item tab exists in PO SAP_BASIS 731/05 III

Summary
1800381 1804939 Notification mail ends up with error Issue with Substitute Item in Bidder login 'Incorrectly Processed'

*********************************************************************** 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 SP Equivalence Levels The 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

Summary

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 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

Summary Note 1548532.

Notes to be applied as part of this stack according to processes:

SAP Note Number

Installation/upgrade 1713393

Description

Error in TREXADMIN on TREX 7.00

Catalog Content Management 1548532 1748289 SRM-MDM Catalog 7.02 Repository information Problem with uploading Sustainability record to catalog

Self-Service Procurement 1712530 1747975 1748334 1749643 1755249 Corrections for unified rendering up to SAP_BASIS Deleting PO throws unwanted Popups Contract Price is not picked by item from Propose SoS Error in Add item from Shopping Cart in local PO History: SC related RFx Response doc is not getting udpated 731/04 I

Service Procurement 1746653 Best Bid Value field calculates Contingency item value also

Strategic Sourcing 1745887 1747616 1731823 1629859 1747769 1714594 1748147 1748168 1748315 1746737 1746345 1749130 1732790 1749601 1749233 1749682 Infoline missing in follow documnet Extended classic PO creation fails with supplement items Partner differences wrongly determined PurchaseRequestERPSourcingRequest_Out:PR changes not updated Condition: Not able to change the scales Rfx response modification checkbox is getting unchecked Issue with Auction Responses when auction created from rfx. Create PO_Xml fails in ERP to FEH Not able to award response due to improper item ordering Issue in change version ofresponse in Bid-Decoupled scenario ESA: No link maintained between backend PO and shopping cart Issues with SOCO reject status for service item PO confirmation with quotation reference do no update SC Response_Contract_XML fail in ERP ME33K: Service item price is zero for SRM GOA ESA: Short dump in PO incoming confirmation for services

Summary
1749585 1744887 1728308 1749562 1750345 1748103 1751563 1621788 1751254 1754897 1694596 1712226 1753241 1753996 1754186 1754661 1754763 1754951 1754887 Purchase Requisition reappears in SOCO after RFx close Info Record conditions not updated by SRM Central Contract Not able to copy an RFx which has MM-SRV Structure Creation Date and time missing in Rfx response and Rfx Able to delete a Response after submitting it Update of Info Rec. cond. for multiple items not working It is possible to seach a Closed Rfx in Supplier System SAP SRM 7.0 EHP2 : Important info about scenarios Delivery date rolls down in supplier system for hier_srm Rfx Bids not copied to Auction History,On convert to Auction Target Value behaviour in sourcing scenario Important Information about Strategic Sourcing Scenario PO confirmation XML fails in SRM for PO created from Rfx No ERP Sourcing confirmation triggered when adding new items Backend contract from accepted RFX response not created Deleted Rfx Response attachment visible in the SRM System Returned Bid information is not shown in the RFX tracking Edit of Quote in Awaiting approval in Bid-Decoupled Scenario 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 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 Levels The 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

Summary

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 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

Summary

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. 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

General 1674472

Description

Adhoc approver disappears for saved purchasing

Business Warehouse 1636155 730SP6:Error 'RSTRAN 510' while activating Transformation

Catalog Content Management 1681129 1681236 1673698 1570580 Conditions not copied during PR creation from MDM Error in ordering SC having service items from Catalog Catalog Item Price is Editable BAPI Call for Catalog items referencing CCTR leads to error

Contract Management 1677424 1677038 PurchasingContractERPRequest_I: Error message VK098 Dump when editing a rejected document

Summary
Self-Service Procurement 1687645 1638075 804249 1676082 1673946 1691568 Error in Invoice display for Managers Login Iview for invoicing party is not assigned to manager role SURVEY: Short dump when you send a questionnaire Not possible to execute BBP_GET_STATUS_2 when days is blank Multiple issues in RFx creation from Shopping Cart Professional Shopping Cart dispayed from ESS role

Service Procurement 1681175 1692823 1693727 1692485 Bidder cannot change Expressive Items in Returned On entering wrong payment term Excel upload throws error No errors in contract when pressing Check button Excel Upload: Product data could not be interpreted

Strategic Sourcing 1679161 1681696 1673698 1570580 1676014 1692315 1692265 1691740 1683533 1681794 1678433 1667331 1690581 1672674 1694941 1694101 1694412 1693892 1695004 1695332 1690215 1693212 Release rejected bid is not editable in case of auctions Changed version quote with expressive item not replicated Catalog Item Price is Editable BAPI Call for Catalog items referencing CCTR leads to error CPPR: Submit not possible without submission deadline date Auction Incorrect bidder details Issues while replication change version of Response Publish button not enabled for Release rejected RFX Reinitialization of Approval Process DO Layer error when changing a saved purchasing Restart behaviour in completion steps Approver preview in recall process Target value visible when follow on doc is "PO or Advanced Bid Comparision Various Issues Convert-to-auction button will be enabled after price opening Issues with auction replication in response outside firewall Unnecessary warning pop-up on permissions table in tendering Saved technical bid visible to the Technical evaluator Return option in Quotes created in Auction process Issues in total value calculation for items in Response RFx Response Awarding issues Unwanted warning messages during RFx response

Summary *********************************************************************** SUPPORT PACKAGE STACK 01 (11/2011) As a special case, Support Package Stack 01 has to be applied with the installation 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 Levels The 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 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

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 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 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

Summary Affected Releases Software Component Release From Release To Release And subsequent SRM_SERVER 702 702 702

Related Notes 1649406 1621887 1621788 1598140 1580107 1574357 1548532 1523939 Release Restriction Note for SRM 7.0 Enhancement Package 2 SRM PPS 702 Brazil Localization SAP SRM 7.0 EHP2 : Important info about scenarios SAP Enhancement Package 2 for SAP SRM 7.0:Compatible Add-ons Solution Manager Content for SAP EHP2 for SAP SRM 7.0 Main Browser Note for BS7i2011 SRM-MDM Catalog 7.02 Repository information SAP SRM 7.0 EhPxx: PPS-Important info on New Functionality

Powered by Joomla!. Valid XHTML and CSS.