sap srm7.02 ehp2 new functionality

17.01.2013 of 6

SAP Note 1621788 - SAP SRM 7.0 EHP2 : Important info aboutscenarios

Note Language: English Version: 7 Validity: Valid Since 05.11.2012

Summary

SymptomSAP Enhancement Package 2 for SAP SRM 7.0 - Important Information aboutScenarios

Other termsSRM 7.02, Release info, Restrictions, Supplier Relationship Management,Advanced Comparison, Limits, Live Auction on ABAP Server, FAQ, RFx responseoutside firewall

Reason and PrerequisitesThis note provides additional important information to be considered beforedeploying new functionality provided in SAP SRM 7.0 EHP2

Solution

A. Bid and RFx Response Submission Outside Firewall

The following additional information should be considered for the sourcingdeployment variant - Bid and RFx Response Submission Outside Firewall.

The following functions supported in Strategic Sourcing scenario will notbe supported when you use the new sourcing deployment variant - Bid andRFx Response Submission Outside Firewall.

- Chat functionality in RFx and RFx Response

- The purchaser activities like Auction active, pause and extendcan be done only from Live Auction (Java Applet) and not fromthe Auction screen (WebDynpro).

- Weights for prices.

- Location based conditions

- Adding items from MDM Catalog in RFx Response

- Undo accept and Undo reject

- Bidder can access RFX Documents & Auctions in External SupplierSystem System through a POWL Application via Netweaver BusinessClient (NWBC). Bidder will not be able to access the RFx andAuction documents via Portal using the SAP delivered bidderrole for External System and with the existing portal contentfor this role. To configure External Supplier System viaEnterprise Portal relevant iView, Page and workset has to becreated and assigned to the portal role for bidder ( Bidderrole found under the path SAP -> Specialist -> SAP SRM 7.0 ->EHP1-> Supplier Collaboration). To reach the SAP providedEnterprise Portal content follow the path: Portal Content ->

17.01.2013 of 6


Content provided by SAP -> Specialist -> SAP SRM 7.0 ->EhP1 andits subfolders. (This restriction is not valid from SP02)

B. Limits in Bidding Documents

The following additional information should be considered for the limits inbidding functionality.

- Limit items from an RFX response can only be transferred into aPO, but not into a contract.

- Limit items are not supported when RFx is created from SAP ERPCollective Processing of Purchase Requisitions (CPPR)functionality.

- Limit items in RFx are supported only with service hierarchyand at 2nd level of hierarchy only. Only one limit item perhierarchy is supported.

- Output from RFx and RFx response do not show limit items.

- Limit items are not exported/imported to Microsoft Excel whenyou use Export/import feature.

- Offline bidding is not supported with limit items.

C. Sourcing with RFx

The following information should be considered, if you are planning to use'Add items from catalog ' functionality in RFx/RFx response :

- When bidder selects items from MDM catalog in an RFx response,delivery date will be taken as current date. The delivery dateis not visible and cannot be changed.

- Items are not added when bidder tries to add items of productcategories from different logical systems in an RFx response.

- An error message is displayed when purchaser adds items ofproduct categories from different logical systems in an RFx butitems are added. Purchaser can correct the items to ensure thatonly items from one logical system are in a hierarchy.

- Bidder cannot add an item with blank product category in RFxresponse.

The following checks are made in RFx/RFx response to ensure correct dataentry:

- RFx/RFx response shall contain items with product categoriesfrom one logical system only within a hierarchy.

- In MM-SRV hierarchy, only backend ERP product categories areallowed.

17.01.2013 of 6


D. External Requirements from ERP

The following restrictions should be considered, if you are planning to useexternal requirements.

1. Changes to purchase requisition: When a requirement from ERP purchaserequisition is transferred to sourcing application (SOCO) and the sourcingprocess (RFx or Auction) is still in progress i.e. a purchase order or acontract is not yet created, then changes to the requirement are notupdated in Sourcing application. In such a case, the follow on sourcingdocument (RFX/Auction) is unaware of changes to the requirement. This meanschanges to PR cannot be processed until RFx process is completed. If therequired quantity or delivery date is changed in purchase requisition, werecommend to change the RFx/Auction directly before submission deadline.

2. RFx from CPPR : Purchase requisition (PR) is processed in CPPR and a RFxis created with reference to PR. Changes to purchase requisition will notbe reflected in shopping cart in SRM when the RFx status is published ordeleted or transaction completed. RFx also does not get updated withchanges. This means changes to PR cannot be processed until RFx process iscompleted. Recommend to make changes directly in RFx before the submissiondeadline or recommend to create another PR, if the changes are to increasequantity.

The above restriction is not valid, if the RFx status is not published.

E. Central Contracts for Services

The following additional information on price determination for servicespecifications (service lines) in ERP purchase order should be considered.

You create an SAP ERP purchase requisition item with item category 'D'(Service) and assign a central contract as source of supply either directlyor after a sourcing event.You create an SAP ERP purchase order for the above purchase requisitionitem either from SAP SRM or SAP ERP.Note that the purchase order price for the service specifications is takenfrom the preceding SAP ERP purchase requisition and not from the assignedcontract.If you would like to get prices for service specifications to be taken froma central contract, we recommend that you use the 'Service Selection'function, which enables you to adopt services from contracts.

F. Sourcing Application (SOCO)

1. Zero price contracts are not proposed as source-of-supply in sourcingapplication (SOCO).

2. Source of supply(SoS) for services with outlines : When a contract isproposed as a SoS in service procurement scenario, the price of the outlinewill be shown for all items. This is because, price determination forindividual services from the contract is not done in Sourcing application.

3. The source of supply determination is done only at line item level (topoutline) and not done at service lines level. Hence, we do not recommend

17.01.2013 of 6


the source of supply determination for service lines using sourcingapplication. We recommend that you use the 'Service Selection' function inERP, which enables you to adopt services from contracts along with contractprices.

G. Simplified Shopping Cart

The following restriction should be considered in simplified shopping cartprocess.

1. Partial Refresh of POWL for shopping cart documents in simplifiedshopping cart : After ordering a simplified Shopping Cart using the ORDERNOW button (seen on the right side panel), in the POWL you would get anerror "Update not possible as update task not finished; refresh latermanually". In this case, the user needs to manually trigger the POWLrefresh as the automatic partial refresh does not work .

H. Extended Classic Deployment

The following restriction should be considered while creating purchaseorder for services.

100% rebate for services in purchase order is not transferred to ERPsystem. We recommend not to use discounts exceeding 99%.

I. Harmonized roles in NWBC HTML or NWBC Client

The following restriction should be considered before using harmonizedroles in NWBC HTML or NWBC Client. This restriction is not applicable whenyou use Netweaver Enterprise Portal.

2nd level navigation in ERP is not supported when you use harmonized rolesin NWBC HTML or NWBC client.- For example, you search for purchase order in POWL and click on an ERPpurchase order. The purchase order is displayed. Now, if you click on anyof the links in purchase order pointing to another ERP transaction, you mayreceive an error message that "Transaction is not recognized".

J. Live Auction on ABAP Server

Note the following information, if you decide to use Live Auction on ABAPserver:1. You do not need Java server for Live Auction (LAC WPS).2. There is no change in the user interface for end users. Java Applet forbidder and purchaser are still used for live auction.

K. Advance RFx Response comparison

Please note the following behaviour for the advance Rfx response comparisonscreen.1) Rank calculation- Supplement items are not ranked- In case there is a substitute item provided then the corresponding basic

17.01.2013 of 6


item will not be ranked

2) Different color for Rank 1The bidder (or bidder item) with rank 1 will be shown in different color tohighlight the best rank. All other ranks will be shown in the same color asrest of the screen fields.

3) In the pdf that is generated from response comparison, followingrestrictions exist.

- All expressive items are displayed seperately. So if one bidderhas provided an alternate item and another bidder has provideda supplement item for the same basic item, the alternate andsupplement items shall be displayed independently and not inthe same row.

- The field "Deviation from Rfx Response" is displayed as"Deviation from Rfx R". Hence 'Deviation from Rfx R' should beread as 'Deviation from Rfx Response'.

- All numeric fields that do not have a value are shown as 0.This includes rank field for the items not considered forranking, fields for which no data is provided by bidders andthe field "Deviation from Rfx R" if the item is not consideredfor ranking.

- In case the deviation from Rfx Response is 0.00% for allbidders or only one bidder has provided that item, the field"Deviation from Rfx R" is not shown.

Header Data

Release Status: Released for CustomerReleased on: 06.11.2012 15:17:10Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: SRM-EBP-TEC-INS Installation

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SRM_SERVER 702 702 702

Related Notes

17.01.2013 of 6


Number Short Text

1712226 Important Information about Strategic Sourcing Scenario

1670096 FAQ:Tendering scenario is not supported through CPPR

1582094 EHP2 for SAP SRM 7.0 SP stacks - Release & Information Note

1523939 SAP SRM 7.0 EhPxx: PPS-Important info on New Functionality