Beruflich Dokumente
Kultur Dokumente
Support Package 04
Release Notes
Release 2007
Release Notes 31.01.2008
Copyright
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product
specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
This document is for informational purposes only. Its content is subject to change without
notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES,
EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR
PURPOSE.
Coding samples
Any software coding and/or code lines / strings ("Code") included in this documentation are
only examples and are not intended to be used in a productive system environment. The
Code is only intended better explain and visualize the syntax and phrasing rules of certain
coding. SAP does not warrant the correctness and completeness of the Code given herein,
and SAP shall not be liable for errors or damages caused by the usage of the Code, except if
such damages were caused by SAP intentionally or grossly negligent.
Internet hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are
intended to serve as a hint where to find supplementary documentation. SAP does not
warrant the availability and correctness of such supplementary documentation or the ability to
serve for a particular purpose. SAP shall not be liable for any damages caused by the use of
such documentation unless such damages have been caused by SAP's gross negligence or
willful misconduct.
Accessibility
The information contained in the SAP Library documentation represents SAP's current view of
accessibility criteria as of the date of publication; it is in no way intended to be a binding
guideline on how to ensure accessibility of software products. SAP specifically disclaims any
liability with respect to this document and no contractual obligations or commitments are
formed either directly or indirectly by this document. This document is for internal use only
and may not be circulated or distributed outside your organization without SAP's prior written
authorization.
The architecture, implementation, and use of the function have been simplified. The thought
behind the redesign is to:
The completion and approval processes have been merged into a single process, also
known as combined completion and approval process.
The process related to shopping carts has been redesigned. Shopping carts must now
be completed before the approval process is started.
Process levels and process level steps help you set up completion and approval
processes effectively, regardless of the number of approvals (n-step approval).
The Business Rule Framework (BRF) provides an easy-to-use interface for defining
triggering events and level validation for workflow-based processes.
Business Add-In Determine Agents (/SAPSRM/BD_WF_AGENTS) helps you assign
the relevant user to each level.
The SRM Inbox has been replaced with the Universal Worklist, an Enterprise Portal
technology.
A more sophisticated approach to decision-making based on decision sets has been
implemented: the new approval template has been designed as a line item approval
workflow to address both header (one decision set) and line item approval (multiple
decision sets).
For performance reasons, the Java applet-based graphical approval preview has been
replaced with a preview in tabular form.
Some features available in mySAP Supplier Relationship Management 5.0 have been
removed:
You are not allowed to copy workflow templates or to delegate BOR objects (that is,
add customer-specific methods) anymore.
You cannot change documents any time.
You cannot change approver during the approval phase.
Changing a shopping cart document now depends on the approval level, not on user
attributes.
Effects on Customizing
To use the new workflow function, you must make customizing settings in the Implementation
Guide under SRM Server -> Cross-Application Basic Settings -> SAP Business Workflow
(new). This section contains the activities you have to perform to set up workflows based on
the new concept:
Basis Workflow Settings
SRM Workflow Settings
BRF Settings
Define business rules that are processed when an event is triggered.
Workflow Settings
Activate the event linkage of the new workflow and configure process levels
within the completion and approval process.
Effects on Customizing
To change the output format, you must perform the following activities in the Implementation
Guide under SRM Server -> Cross-Application Basic Settings -> Set Output Actions and
Output Format:
Define Actions for Document Output
Condition-Dependent Document Output
The existing documentation has been updated to reflect the technical changes.
When creating a shopping cart, you can use the search help to help you select the required
account assignment. The system always displays the default account assignment for the
particular account assignment category, even when you change the account assignment
category.
Effects on Customizing
You define G/L accounts in the Implementation Guide (IMG) under Supplier Relationship
Management -> SRM Server -> Cross-Application Basic Settings -> Account Assignment ->
Define G/L Account for Product Category and Account Assignment Category.
Items belonging to the same released authorized purchasing organization, but different
locations, can be grouped together into one backend contract. This grouping logic can only be
used if the customer creates a GOA with a 1:1:1 relationship among an item, a released
authorized purchasing organization, and a location.
You activate or deactivate the grouping of backend contracts out of a GOA in customizing.
Effects on Customizing
To use the Grouping Backend Contracts out of a GOA function, you must make customizing
settings in the Implementation Guide (IMG) activity Supplier Relationship Management ->
SRM Server -> Cross-Application Basic Settings -> Activate Grouping Logic for Locations in
GOA.
Previously, the current date was always shown as the delivery date. Now, you can alter the
date to meet your specific needs. For example, you can set the current date plus x days as
the default value.
Effects on Customizing
The following BAdI is relevant:
SRM Server -> Business Add-Ins (BAdIs) -> Default Values for Delivery Date and Selection
Criteria
Effects on Customizing
To have the checkbox Bidder can change quantities selected by default, you must make the
following settings in the Implementation Guide (IMG) activity Supplier Relationship
Management -> SRM Server -> Cross-Application Basic Settings -> Define Transaction
Types. Select the RFx entry and double-click on Transaction Types in the tree on the left
hand side of the screen. Double-click on the RFx entry. Under Process Control, select Bidder
can change quantities.
The indication to bid or not to bid is not binding for bidders. They can bid in an RFx although
they indicated not to have the intent to bid, and the other way around. They can also change
their choices in the bid intent buttons.
If the checkbox "Allow multiple responses per company" has not been selected in
customizing, all bidder contacts from the same company edit a single intend to bid indication.
For contact persons already invited to the RFx, the bid intent button replaces the register
button.
See also
Release Note "Multiple Responses per Company".
Effects on Customizing
To have the checkbox Allow multiple responses per company selected by default, you must
make the following settings in the Implementation Guide (IMG) activity Supplier Relationship
Management -> SRM Server -> Cross-Application Basic Settings -> Define Transaction
Types. Select the RFx entry and double-click on Transaction Types in the tree on the left
hand side of the screen. Double-click on the RFx entry. Under Process Control, select Allow
multiple responses per company.
See also
Release Note "Intend to bid indication".
If an RFx response modification exists, this is indicated in the item details. As a purchaser,
you can access the details of the RFx response modification directly from the response
comparison. You cannot accept or reject RFx responses including RFx response modificatios
in the response comparison. Neither can you accept or reject quotations in which the bidder
has created a new item.
An alternative item is an item in which the bidder bids on the original item, but he also
proposes another item which in general conforms to the purchaser's original specifications.
The bidder is therefore responding to the original line item, and is proposing a second,
comparable line item that could replace the original line item. If the RFx response is accepted,
the purchaser selects either the original line item, or one of the alternatives.
A substitute item is an item in which a supplier offers to deliver goods or services other than
the goods or services a purchaser has requested, because he cannot deliver the goods or
services originally requested. If the RFx response is accepted, the purchaser selects one of
the substitutes.
A supplement item is an item in which a supplier offers to deliver goods or services in addition
to the goods or services a purchaser has requested. If the RFx response is accepted, the
purchaser selects none, one or several supplements in addition to the original item.
Awarded alternative, substitute and supplement items are transferred to follow-on documents.
The information for the creation of a temporary contact person is partially derived from
business partner master data (language, country, telephone, and so on). Fields that cannot
be filled with business partner information are filled with default values (title, first name, last
name, and so on). You can overrule these default values by activating the BAdI mentioned
below.
After the supplier has been transferred to SRM via OPI and the contact person has been
created, the latter receives an e-mail with the link to the RFx and with a temporary user ID. In
addition, the temporary contact person receives a second e-mail with the password.
Effects on Customizing
To create a temporary contact person, you must activate the temporary contact person
creation in the Implementation Guide (IMG) activity Supplier Relationship Management ->
SRM Server -> RFx -> Activate Temporary Contact Person Creation.
< Implementation Guide (IMG) activity Supplier Relationship Management -> SRM Server ->
Business Add-Ins(BADIs)-> Input Values for Temporary Contact Person Creation >
Implement and activate the Business Add-In to customize the default values for the creation
of a temporary contact person.
Standard Setting:
FILL_CONTACTPERSON
Effects on Customizing
To enable versioning of RFx responses, you must make the following settings in the
Implementation Guide (IMG) activity Supplier Relationship Management -> SRM Server ->
Cross-Application Basic Settings -> Switch On Version Control for Purchasing Documents.
You have to set the indicator for the RFx Response.
Effects on Customizing
To use Dutch Auctions, you must make customizing settings in the Implementation Guide
(IMG) activity Supplier Relationship Management -> Supplier Self-Services -> Cross-
Application Basic Settings -> Settings for Documents -> Define Transaction Types.
Effects on Customizing
To use the new SRM Workflow Framework, you must make settings in the Implementation Guide
(IMG) under SRM Server -> Cross-Application Basic Settings -> SAP Business Workflow
(New) -> SRM Workflow Settings.
The technical infrastructure changes are valid as of SAP SRM 2007; the corresponding
screens have been redesigned and Customizing has been enhanced.
Effects on Customizing
Depending on the underlying technology (either the Internet Transaction Server or the
Enterprise Portal), you must perform the following IMG activities to complete the integration
with SAP Records Management:
o SRM Server -> Integration with Other mySAP Components -> Integration with
SAP Records Management -> Activate Integration with SAP Records
Management
o SRM Server -> Integration with Other mySAP Components -> Integration with
SAP Records Management -> Define Paths for Link to Records Management
System
o SRM Server -> Integration with Other mySAP Components -> Integration with
SAP Records Management -> Create Shortcuts for SRM - RM Integration
o SRM Server -> Integration with Other mySAP Components -> Integration with
SAP Records Management -> Define Transfer Conditions for Records
Management
Enterprise Portal
o SRM Server -> Technical Basic Settings -> Maintain Portal Information
o SRM Server -> Integration with Other mySAP Components -> Integration with
SAP Records Management -> Activate Integration with SAP Records
Management
o SRM Server -> Integration with Other mySAP Components -> Integration with
SAP Records Management -> Define Transfer Conditions for Records Management
Effects on Customizing
You must perform the IMG activity Activate Digital Signature under SRM Server -> Cross-
Application Basic Settings -> Digital Signatures.
you can select items to work on. The number of business objects per operation queue
is displayed so that you can assess your workload at a glance.
Universal Worklist (UWL)
The UWL is a list in the work center used for receiving, rejecting, approving, forwarding,
and processing workflow work items, alerts, and notifications. It provides quick access
to your critical work items within the context of the work center and allows you to
navigate directly to where the task can be completed.
Effects on Customizing
For information on Customizing, see the Business Package configuration documentation in
SAP Solution Manager.
Effects on Customizing
The following Implementation Guide (IMG) activities are relevant:
SRM Server -> Cross-Application Basic Settings -> SAP Business Workflow (New) -> SRM
Workflow Settings -> BRF Settings -> Define Expressions
For each alert, an e-mail is sent either to the person who started the background processing
or to the shopping cart creator. If you want to deactivate e-mail notification, see SAP Note
896296.
Effects on Customizing
You can make customizing settings in the Implementation Guide (IMG) activity SAP Web
Application Server -> Application Server -> Basis Services -> Generic Business Tools -> Alert
Management -> Define Alert Categories.
You can define an expiry time for your alert messages. Choose SRM Alerts under All
Classifications and choose Alert Category SRM_SOCO. Under Properties, you can enter a
new expiry time in minutes. The default expiry time is 20,160 minutes, which is two weeks.
You can modify the Message Title of the alert message under Long and Short Text. You can
also modify the description under Properties. The message title and description are defined
for the language in which you are logged on to the system. You should maintain this
information for all relevant languages.
Under Long Text (E-Mail, Fax) you can supplement the alert message long text.
See also
For more information, see release note Background Processing in Sourcing Cockpit.
Effects on Customizing
To use the reviewer function, you must make Customizing settings in the Implementation
Guide (IMG) activity Supplier Relationship Management -> SRM Server -> Cross Application
Basic Settings -> SAP Business Workflow (New) -> SRM Workflow Settings -> Workflow
Settings -> Define Process Levels.
Supplier Relationship Management -> SRM Server -> Business Add-Ins (BAdIs) ->
SAP Business Workflow (New) -> Define Agents
In the case of an information message or warning message, you are asked if you want to
update the exchange rate threshold in the purchasing contract.
In the case of an error message, you must update the exchange rate threshold in the
purchasing contract before the purchasing contract can be saved or released, or before the
purchase order can be posted.
See also
On SAP Help Portal (http://help.sap.com), see SAP Supplier Relationship Management ->
Functions -> Contract Management -> Purchasing Contracts.
When you display a purchasing contract or global outline agreement (GOA) in contract
management, and choose Tracking, you can now also see:
The Supplier Survey Cockpit enables you to create questionnaires using the SAP Web
Survey tool accessible from SAP NetWeaver Portal. Furthermore, you can assign
questionnaires to surveys, send them out to the survey participants and monitor the
responses.
Once a survey is closed, the survey data is transferred to SAP NetWeaver Business
Intelligence (SAP BI) for reporting purposes. In SAP BI, you can use a dedicated InfoCube
and DataStore Object to evaluate the data. An indicator tells you, whether participants have
made free text comments to your questions. You can read these free text comments in the
Supplier Survey Cockpit.
In the Supplier Survey Cockpit you can manage a database which stores information about
which survey participants are potentially eligible to rate which suppliers (Who Rates Whom
database). In this way, you gradually build up an expert database for your surveys.
Effects on Customizing
The following Implementation Guide (IMG) activities are relevant:
Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings ->
Number Ranges -> SRM Server Number Ranges -> Define Number Ranges for Survey
Package
Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings ->
Number Ranges -> SRM Server Number Ranges -> Define Number Ranges for Survey
Supplier Relationship Management -> SRM Server -> Supplier Evaluation -> Evaluation
Category
Supplier Relationship Management -> SRM Server -> Supplier Evaluation -> Evaluation Area
Effects on Customizing
The following Customizing activities are relevant:
SRM Server -> Cross-Application Basic Settings -> SAP Business Workflow (New) ->
SRM Workflow Settings -> Workflow Settings -> Activate New Approval Process
Overview
SRM Server -> Cross-Application Basic Settings -> SAP Business Workflow (New) ->
SRM Workflow Settings -> Workflow Settings -> Define Process Levels
The following IMG activities were added to the section SRM Server -> Technical Basic
Settings:
The following IMG activities were added to the section SRM Server -> Master Data -> Create
Users:
The following IMG activities were added to the section SRM Server -> Technical Basic
Settings -> Settings for Supplier Synchronization:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Number Ranges -> SRM Server Number Ranges:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Event and Event Schema for Alert Management:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new):
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> Basis Workflow Settings:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> SRM Workflow Settings -> BRF Settings:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> SRM Workflow Settings -> Workflow
Settings:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Extensions and Field Control (Personalization) -> Configure Customer
Fields
The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Field Control
The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Define and Assign Actions
The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Control for Actions
The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Table Extensions
The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Table Extensions ->
Control Table Extensions and Their Fields and Actions
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Integration with Other SAP Components -> Integration with SAP Records
Management:
The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Digital Signatures:
The following IMG activities were added to the section SRM Server -> Country-Specific
Functions:
The following IMG activities were added to the section SRM Server -> RFx
The following IMG activities were added to the section SRM Server -> Supplier Evaluation:
The following IMG activities were added to the section SRM Server -> Procurement Card:
The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> SRM Workflow Settings -> Workflow
Settings:
The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings -> Set Output Actions and Output Format:
The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings -> Account Assignment:
Define G/L Account for Product Category and Account Assignment Category (SP00)
Process Questions
To access all of the BAdIs available and their documentation, go to the Implementation Guide
(IMG) for Supplier Relationship Management, and choose SRM Server -> Business Add-Ins
(BAdIs).
Shopping Carts and Requirement Items -> Shopping Cart Monitor: Object Adaptation
(SP02)
Shopping Carts and Requirement Items -> Shopping Cart Monitor: UI Content
Adaptation (SP02)
SAP Business Workflow (New) -> Define Deadlines for Events (SP01)
SAP Business Workflow (New) -> Determine Shopping Cart Value for Purchasing
Budget Workflow (SP01)
SAP Business Workflow (New)--> Adjust Search Help for Ad Hoc Agent (SP01)
SAP Business Workflow (New) -> Adjust Search Help for Reviewer (SP03)
SAP Business Workflow (New) -> Customer Enhancement of Offline Approval (SP03)
Customer Fields -> Configure Customer Fields -> Fill Display Fields on Header Level
(SP03)
Customer Fields -> Configure Customer Fields -> Fill Display Fields on Item Level
(SP03)
Interface Configuration -> Input Helps and Search Helps -> Display of Input Helps,
Search Helps, and Favorites
Interface Configuration -> Input Helps and Search Helps -> Restrict the Display in
Input Helps and Search Helps
Interface Configuration -> Input Helps and Search Helps -> Internal Temporary
Storage of Favorites for Input/Search Help
Interface Configuration -> Input Helps and Search Helps -> Final Saving of Favorites
for Input Helps and Search Helps