Sie sind auf Seite 1von 55

SAP SRM 2007

Support Package 04
Release Notes

Release 2007
Release Notes 31.01.2008

Copyright

© Copyright 2007 SAP AG. All rights reserved.

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.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft


Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,
OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC
are trademarks or registered trademarks of IBM Corporation.

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.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

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.

SAP SRM 2007 2


Release Notes 31.01.2008

SAP - Important Disclaimers

SAP Library document classification: PUBLIC

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.

SAP SRM 2007 3


Release Notes 31.01.2008

Release Notes Support Package 00................................................................................... 6


User Interface (New) ...................................................................................................... 6
Workflow Redesign (Changed) ....................................................................................... 7
SAP Interactive Forms by Adobe (Changed)................................................................... 9
Transferring External Requirements with Attachments (New)........................................ 10
Account Assignment (Enhanced).................................................................................. 11
Grouping Backend Contracts out of a GOA (New) ........................................................ 12
Configuration of Delivery Date in Shopping Cart and Confirmation (New)...................... 13
Withdraw RFx Response (New).................................................................................... 14
Calculate Value of RFx Response (New) ...................................................................... 15
Full Quantity Bidding (New) .......................................................................................... 16
Intend to Bid Indication (New)....................................................................................... 17
Allow Multiple Responses per Company (New)............................................................. 18
Questions and Answers Function (New) ....................................................................... 19
Response Comparison (Changed)................................................................................ 20
RFx Response Modifications (New) .............................................................................. 21
Creation of a Temporary Contact Person after OPI Transfer (New)............................... 22
Versioning of RFx Responses (New) ............................................................................ 23
Dutch Auction (New)..................................................................................................... 24
Release Notes Support Package 01................................................................................. 25
User Interface (New) .................................................................................................... 25
Currency on Item Level for Global Outline Agreements (GOA)...................................... 26
Operational Contract Enhancements ............................................................................ 27
Replacement of Free Text Item with Catalog Item (New)............................................... 28
SRM Workflow Framework (Enhanced) ........................................................................ 29
Invoice Management System (Enhanced)..................................................................... 30
Payment Terms at Item Level for Contracts: PO Enhancement (New)........................... 31
Integration with SAP Records Management.................................................................. 32
Digital Signatures (New) ............................................................................................... 33
Release Notes Support Package 02................................................................................. 34
User Interface (New) .................................................................................................... 34
SRM Workflow Framework (Enhanced) ........................................................................ 36
Display of Contract Hierarchy Discounts in Purchase Order (New)................................ 37
Revision Levels (New).................................................................................................. 38
Currency on Item Level for RFx (New) .......................................................................... 39
Procurement Card (Enhanced) ..................................................................................... 40
Background Processing in Sourcing Cockpit (New)....................................................... 41
Alerting in Sourcing Cockpit (New)................................................................................ 42
Release Notes Support Package 03................................................................................. 43

SAP SRM 2007 4


Release Notes 31.01.2008

SRM Worfklow Framework (Enhanced) ........................................................................ 43


Exchange Rate Thresholds (New) ................................................................................ 45
Change Documents and Version Management for Conditions (New) ............................ 46
Supplier Survey Cockpit (New) ..................................................................................... 47
Release Notes Support Package 04................................................................................. 48
SRM Workflow Framework (Enhanced) ........................................................................ 48
IMG Structure for Supplier Relationship Management (Changed) ................................. 49
Business Add-Ins (Changed) ........................................................................................ 54

SAP SRM 2007 5


Release Notes 31.01.2008

Release Notes Support Package 00


User Interface (New)
See updated version in SP02 section.

SAP SRM 2007 6


Release Notes 31.01.2008

Workflow Redesign (Changed)


Use
As of SAP SRM 2007, a new workflow function is available.

The architecture, implementation, and use of the function have been simplified. The thought
behind the redesign is to:

Rationalize workflow-based processes and provide more visibility by offering one


workflow instead of a whole set of workflows.
Remove complex coding and discontinue little-used features.
Support complex business objects.
Standardize approval processes.
Provide an easy-to-use tool to better support your completion and approval processes.
Simplify implementation and maintenance.
The following features are supported:
The existing workflow templates have been replaced with a single, non-modifiable template: Main
SRM Approval Process Template (WS 40000014). This template contains the sub-workflow
templates Approval Sub-Workflow (WS 40000016) and Completion Sub-Workflow (WS
40000017).

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.

SAP SRM 2007 7


Release Notes 31.01.2008

Other features are currently not supported:


Spending limit approval
Alert-based workflows and notifications for shopping carts
Reviewers for internal or technical revisions

Effects on Existing Data


Run report SRM Workflow Conversion (/SAPSRM/PR_WF_MIGRATION_CFG) after the
process level configuration (as described in the IMG step Define Process Levels) to make all
running workflows compatible with the new architecture.

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.

SAP SRM 2007 8


Release Notes 31.01.2008

SAP Interactive Forms by Adobe (Changed)


Use
As of SAP SRM 2007, you can use SAP Interactive Forms by Adobe as an alternative to
Smart Forms for your business documents.

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.

SAP SRM 2007 9


Release Notes 31.01.2008

Transferring External Requirements with Attachments (New)


Use
As of SAP SRM 2007, external requirements including attachments can be transferred from
external systems, such as SAP ERP or non-SAP systems, to the SRM system. The
attachments are added to the corresponding shopping cart items.

SAP SRM 2007 10


Release Notes 31.01.2008

Account Assignment (Enhanced)


Use
From SAP SRM 2007, you can enter more than one G/L account per product category and
account assignment category in Customizing. You set one G/L account as default account
assignment.

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.

SAP SRM 2007 11


Release Notes 31.01.2008

Grouping Backend Contracts out of a GOA (New)


Use
As of SAP SRM 2007, you can create one single contract in the backend system out of a
global outline agreement (GOA) with multiple items referring to multiple locations of one
backend system.

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.

Changes to the User Interface


If the grouping logic for locations is activated in customizing, the following changes to the user
interface come into effect:
The header distribution screen is disabled while creating the GOA.
The released organized purchase organization, location, document type, and target
values are maintained at item level on the item distribution screen.
The header distribution screen is filled with the values maintained at item level. The
target values of all items resulting in one backend contract, are accumulated, and
displayed, on the header distribution screen.

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.

SAP SRM 2007 12


Release Notes 31.01.2008

Configuration of Delivery Date in Shopping Cart and


Confirmation (New)
Use
As of SAP SRM 2007, you can influence the values of the fields Delivery Date in the shopping
cart and Delivery/Performance Date in the confirmation with the help of a Business Add-In
(BAdI).

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

SAP SRM 2007 13


Release Notes 31.01.2008

Withdraw RFx Response (New)


Use
As of SAP SRM 2007, the bidder has the option to withdraw his RFx response prior to the
submission deadline if the response has not yet been accepted or rejected by the purchaser.
He can reactivate a withdrawn RFx response prior to the submission deadline. Withdrawn
RFx responses cannot be awarded or rejected. The purchaser can perform the same
functions if he acts on behalf of the bidder.

SAP SRM 2007 14


Release Notes 31.01.2008

Calculate Value of RFx Response (New)


Use
As of SAP SRM 2007, you can easily view the value per line item of an RFx response. With
simple prices, the system automatically calculates and displays the total value. With complex
prices, the bidder and the purchaser have the option to manually trigger a price calculation to
display the total value per line item of an RFx response.

SAP SRM 2007 15


Release Notes 31.01.2008

Full Quantity Bidding (New)


Use
As of SAP SRM 2007, as a purchaser, you can set an indicator on the basic data tab of the
RFx called Bidder can change quantities. The bidders must bid on the full quantity then. This
is particularly useful when you want to order from one supplier only, or when you do not
expect many bidders to take part in the RFx.

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.

SAP SRM 2007 16


Release Notes 31.01.2008

Intend to Bid Indication (New)


Use
As of SAP SRM 2007, the bidder in SAP Bidding Engine can indicate his willingness to
participate in a bidding event at an early stage of the bidding process, that is, after receiving
the RFx. He can choose between yes, tentative, or no in the bid intent buttons. As a
purchaser, you can see if a bidder has accepted or declined his participation on the
Bidder/Responses tab of the RFx detail. There is also a counter for the different responses.
You can sort bidders according to their intentions to bid.

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.

As a purchaser, you can also perform this function on behalf of a bidder.

See also
Release Note "Multiple Responses per Company".

SAP SRM 2007 17


Release Notes 31.01.2008

Allow Multiple Responses per Company (New)


Use
As of SAP SRM 2007, you can set an indicator called Allow multiple responses per company
on the basic data tab of the RFx. When the indicator is set, the system behaves as in former
releases: Different contacts within one company can compete with each other editing different
RFx responses. The new functionality can be used when the indicator is not set: Contacts of
one and the same company handle one and the same RFx response then, and the intent to
bid indication is at the company level. Still, all invited contacts of a company get automatic e-
mails.

Effects on Existing Data


Existing data needs to be migrated. Otherwise, after upgrade to SAP SRM 2007, old RFx's
will be considered as NOT allowing multiple RFx 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".

SAP SRM 2007 18


Release Notes 31.01.2008

Questions and Answers Function (New)


Use
As of SAP SRM 2007, you can use questions and answers (Q&A) functionality within SAP
Bidding Engine. Bidders and the purchaser can create Q&A messages after the RFx has
been published up until the RFx moves into a status where no further activities are possible
(closed or transaction complete status). The bidder can see his own messages and those of
the purchaser only; he can see no messages from other bidders. The purchaser can write
messages to one bidder or broadcast them to all bidders. In the upper part of every screen,
there is a link to the Q&A answers panel. This allows the panel to be seen by the purchaser
and bidder, irrespective of the tab they are processing in the RFx/RFx response.

All Q&A messages are stored with the RFx.

SAP SRM 2007 19


Release Notes 31.01.2008

Response Comparison (Changed)


Use
As of SAP SRM 2007, as a purchaser you can accept or reject RFx responses in the
response comparison of an RFx. You can accept or reject on line item level, or accept or
reject the whole RFx response. You can also save your choices in the response comparison
by clicking on Save. By clicking on Hold, on the other hand, your choices are saved, too, but
bids are not actually accepted or rejected.

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.

SAP SRM 2007 20


Release Notes 31.01.2008

RFx Response Modifications (New)


Use
As of SAP SRM 2007, as a purchaser you can allow or prevent bidders to apply modifications
in their responses to your RFx. RFx response modifications can be of three different types:
alternative, substitute, or supplement items.

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.

SAP SRM 2007 21


Release Notes 31.01.2008

Creation of a Temporary Contact Person after OPI Transfer


(New)
Use
As of SAP SRM 2007, you can directly invite a supplier that has been transferred to SRM via
OPI to participate in an RFx. This is possible due to the fact that a temporary contact person
can be created in SRM when the supplier is transferred via OPI. You activate or deactivate
the creation of temporary contact persons in customizing. The temporary contact person has
the role mySAP SRM Bidder and is included in the bidder list.

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.

The following BAdIs are relevant:

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

In the standard system, the Business Add-In is not active.

The BAdI provides the following method:

FILL_CONTACTPERSON

SAP SRM 2007 22


Release Notes 31.01.2008

Versioning of RFx Responses (New)


Use
As of SAP SRM 2007, RFx responses are versioned so that you can easily track changes the
bidders have made to their responses. The version number is displayed on the bidder/bid tab
of the RFx. Bidder and purchaser can compare two different versions of an RFx response in
the version history view.

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.

SAP SRM 2007 23


Release Notes 31.01.2008

Dutch Auction (New)


Use
As of SAP SRM 2007, you can create and process Dutch Auctions within SAP Live Auction
Cockpit. A Dutch Auction is a type of reverse (buy-side) auction with one buyer and multiple
suppliers, whereby the auctioneer raises the price from a low starting point until a bidder
agrees to sell at that price. The purchaser enters a start price, a time increment and a price
increment. Bidding begins at the start price. If no supplier is willing to sell at the starting price,
the price automatically goes up by the price increment, after the time increment has passed.

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.

SAP SRM 2007 24


Release Notes 31.01.2008

Release Notes Support Package 01


User Interface (New)
See updated version in SP02 section.

SAP SRM 2007 25


Release Notes 31.01.2008

Currency on Item Level for Global Outline Agreements (GOA)


Use
As of SAP SRM 2007, you can define the currency for each item within a Global Outline
Agreement (GOA) and not simply at the header level. Most businesses have different
currencies for one supplier in the single backend systems.
A Global Outline Agreement is a business document that acts as an umbrella agreement,
negotiated by a purchasing organization for an entire corporate group. In most cases, the
negotiated conditions are valid for more than one associated purchasing organization or
location. For that reason, the Global Outline Agreement as such remains as a bracket within
the SRM system, whereas the single items are distributed to several backend systems for
execution.
After execution in the backend systems, the released value is transferred back to the Global
Outline Agreement to collect all values from all backend systems into one document.
This enhanced functionality is valid for the following SRM roles:
Purchaser: SRM user with authorization to create and maintain business objects in
SRM.
Supplier: Business partner from whom materials or services can be procured.
Bidder: A contact of a business partner, who can participate in bid invitations and Live
Auctions in SRM.

SAP SRM 2007 26


Release Notes 31.01.2008

Operational Contract Enhancements


Use
As of SAP SRM 2007 SP01, you can:
Enter additional contract information in the Shopping Cart
The following additional contract information is displayed in the Source of Supply tab of
the Create SC process:
Contract line description
Supplier part number
Prioritization in the Supplier List
Enter payment terms (for example, currency) at the item level
The payment term information is available on the line item level.
The payment terms are forwarded automatically to the Purchase Order and Invoice
document and incorporated into the Invoice.
The payment terms that are maintained in the contract purchase order or invoice
overrule the settings maintained for the supplier as a business partner in the system.
Receive alerts at the contract level
The thresholds to trigger the alerts for expired contracts and overspend can be
customized at the system level as a default, using the table BBPD_THRESH_CHK.
The contract creator can adjust the alert threshold for a single contract. It is possible to
have multiple alert thresholds for a single contract.
Distribute contract items to a catalog
The checkbox Distribute Contract to Catalog has been moved to the line item level. As
a result, the user can select a single line item to be pushed to the catalog staging area.

SAP SRM 2007 27


Release Notes 31.01.2008

Replacement of Free Text Item with Catalog Item (New)


As of SAP SRM 2007 SP01, you can replace free text items with catalog items in Sourcing.
Replacing such items means that product data like supplier, product number, price, and so on
is then immediately available. There is also a function to undo the replacement.

SAP SRM 2007 28


Release Notes 31.01.2008

SRM Workflow Framework (Enhanced)


Use
As of SAP SRM 2007 SP01, the new SRM workflow framework is available for the following
business objects:
Shopping cart
Purchase order
Contract
RFQ
Quote
The archiving objects of the business objects listed above have been enhanced to enable the
system to archive the approval history. Data related to the new workflow concept, such as
process levels or decision sets, can now be archived.
The following functions have been migrated to the new SRM workflow framework:
Spending limit approval
Alerts and notifications
Approval process for change versions of business objects

Effects on Existing Data


To migrate your running workflows to the new architecture, follow the instructions given in the
Implementation Guide under SRM Server -> Cross-Application Basic Settings -> SAP
Business Workflow (New) -> SRM Workflow Settings -> Workflow Settings -> Convert
Workflows.

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.

SAP SRM 2007 29


Release Notes 31.01.2008

Invoice Management System (Enhanced)


Use
As of SAP SRM 2007, you can display additional information in the Invoice Monitor, a tool
within the Invoice Management System that displays erroneous invoices. This additional data
facilitates work for the invoicing clerk. The following data is displayed:
The person working on the respective exception
How long this person has been responsible for the exception
The invoices that have already been posted (via the Advanced Search)
All available discount levels, for example discount level 1, 3 days: 3%; discount level 2,
20 days: net cash, and so on.

SAP SRM 2007 30


Release Notes 31.01.2008

Payment Terms at Item Level for Contracts: PO Enhancement


(New)
Use
As of SAP SRM 2007 SP01, payment terms are available not only on header level but also
on item level in Global Outline Agreements (GOA) and local contracts.
However, neither the Purchase Orders in the backend system, nor the Purchase Orders in
mySAP SRM have the payment terms at the item level; only at the header level.
Therefore, if you search for a Source of Supply, the PO is now enabled such that the payment
terms are taken into account in this search. When searching for a matching contract, you can
enter payment terms as a search option. If you do so, the system only displays the contract
positions that have the specified payment term for the position. If you leave the payment
terms search field blank, the system displays all contracts with matching items without
considering the payment terms.
If the Purchase Order (PO) header has no payment terms, the search for sources of supply
considers the payment terms at the item level of the contract. If the system finds payment
terms at the item level, this value is transferred to the Purchase Order line Item. If no payment
terms are maintained on the item level of a contract, the source of supply transfers the values
of the contract header to the Purchase Order header.
If the Purchase Order header contains payment terms, the search for sources of supply is
carried out as follows:
If the PO header payment terms match the contract item payment terms, the system
displays the payment terms in the Sources of Supply overview
If the PO header payment terms differ from contract item payment terms, the system
displays the payment terms in the Sources of Supply overview and displays a message
when the contract is assigned as the Source of Supply
If the PO header payment terms match the contract header payment terms, the system
displays the payment terms in the Sources of Supply overview
If the PO header payment terms differ from the contract header payment terms, the
system displays the payment terms in the Sources of Supply overview and displays a
message when the contract is assigned as the Source of Supply.
When creating backend contracts out of a Global Outline Agreement (GOA), different
payment terms on item level of the GOA are considered as split criteria. Header level
payment terms of backend contracts are populated with item level payment terms of the GOA
if existing - if not, they are populated with header level payment terms of the GOA. If you have
activated grouping logic for backend contracts, only line items with identical payment terms
can be grouped together.

Effects on Existing Data


The payment terms are forwarded to the Purchase Order document and subsequently
considered in the Invoice. These payment terms overrule the settings that are made in the
business partner maintenance for the supplier.

SAP SRM 2007 31


Release Notes 31.01.2008

Integration with SAP Records Management


Use
The integration of SAP SRM 2007 with SAP Records Management enables you to create
records for shopping carts, contracts, RFxs, and purchase orders.

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:

Internet Transaction Server

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

SAP SRM 2007 32


Release Notes 31.01.2008

Digital Signatures (New)


Use
As of SAP SRM 2007, digital signatures have been implemented to allow you to encrypt bid
invitation, contract, and purchase order data in procurement processes.
Digital signatures provide the following capabilities:
Enhanced security
Fraud prevention
Document integrity
Sender identification
More specifically, and from a strictly functional point of view, digital signatures are:
Created on purchase orders sent to vendors
Created on contracts sent to vendors
Received on bids (quotes)

Effects on Customizing
You must perform the IMG activity Activate Digital Signature under SRM Server -> Cross-
Application Basic Settings -> Digital Signatures.

SAP SRM 2007 33


Release Notes 31.01.2008

Release Notes Support Package 02


User Interface (New)
Use
SAP SRM 2007 applies a new user interface (UI) concept, based on a clear separation of
organizing, planning, and monitoring work on the one hand and executing tasks on the other
hand. Organizing, planning, and monitoring take place in the SAP NetWeaver Portal while
tasks are executed in separate application windows.
As of SAP SRM 2007, application screens are gradually converted to Web Dynpro, the new
SAP standard UI technology. With Web Dynpro, navigation within the application is
standardized and therefore provides user experience consistency and ease of use. Moreover,
Web Dynpro screens can be personalized, allowing you to set up your work environment
according to your business needs. For instance, you can change the layout of tables.
With SP00, Web Dynpro screens are available for the Shopping Cart application.
With SP01, Web Dynpro screens are available for the following applications:
Operational contract
Global outline agreement
Contract mass change
Approved supplier list (formerly known as vendor list)
Quota arrangement
Purchase order
Purchase order response
RFx (formerly known as bid invitation)
Live auction
Sourcing cockpit
Advanced document search for all applications mentioned above
With SP02, Web Dynpro screens are available for the following applications:
Confirmation
Invoice
Application monitor
Manage internal and external business partners
The SAP NetWeaver Portal with its control center and work centers is the central point of
access to your work environment. You can set up a control center as your home area, which
lists your tasks from all work centers assigned to you, across the different roles you may
have. Work centers, by contrast, are role-based and allow you to start work in a certain area,
such as purchasing, sourcing, or invoice processing. Both from a control center and from a
work center, you can immediately navigate to where the tasks can be completed, for instance
to a Web Dynpro application.
The following worklists are also provided to help you to organize and monitor your work:
Personal Object Worklist (POWL)
The POWL is a new Web Dynpro application that exists in the work center. It provides
a general overview of your work environment and all related business objects. The
POWL is generated by predefined queries. Own queries can also be defined. The
results of the queries are represented as clearly organized lists of objects, from which

SAP SRM 2007 34


Release Notes 31.01.2008

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.

SAP SRM 2007 35


Release Notes 31.01.2008

SRM Workflow Framework (Enhanced)


Use
As of SAP SRM 2007 SP02, the new SRM workflow framework is available for the following
business objects:
Shopping cart
Purchase order
Contract
RFQ
Quote
Confirmation
Invoice
Stochastic document check is now realized using the Business Rule Framework (BRF). You
can define a BRF expression for stochastic document check and use this expression for
process level configuration. Stochastic document check can now be applied to all business
objects.

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

SAP SRM 2007 36


Release Notes 31.01.2008

Display of Contract Hierarchy Discounts in Purchase Order


(New)
Use
As of SAP SRM 2007, you can display contract hierarchy discounts in a purchase order.
Since SAP SRM 2005, you can
Use contract hierarchies to support and improve your purchasing operations and
Define condition types for discounts, where the scale base is the aggregated release
value of all previous releases. In the case of contract hierarchies, the aggregated
release value then includes all of the contracts within a particular hierarchy.
As of SAP SRM 2007, aggregated release values which are the basis for discount for the
contract level you are using are visible in the purchase order.

SAP SRM 2007 37


Release Notes 31.01.2008

Revision Levels (New)


Use
In discrete production processes, assembly parts are often modified slightly, so that they can
be used in the manufacture of other similar products. In many cases, a company must keep
both the original and modified parts in stock for production purposes. Instead of assigning a
new plant number to the modified part, both parts retain the same number, but are assigned
different revision levels (for example, original part = revision level A, modified part = revision
level B).
As of SAP SRM 2007 SP02, a revision level assigned to a material in SAP ERP is available in
SAP SRM if the user has selected a product with the product type Material and if the
product's master data has been replicated from the SAP ERP back end. This assumes that
the system landscape is homogeneous, that is, the revision level for the product is the same
in all back-end systems. The SAP ERP back end must be SAP ERP 2005 Support Package 9
or higher. As a result, documents in SAP SRM (for example, shopping carts, purchase orders,
contracts, RFx, RFx responses, global outline agreements) can be based on a material and
also the specific revision level.
In SAP SRM, the revision level is displayed at line item level. A purchaser can change the
revision level in SAP SRM. The valid revision levels in the material master record in SAP ERP
are offered for selection in SAP SRM. For documents to be created or replicated in SAP ERP
(for example, purchase orders, global outline agreements), the revision level in SAP SRM
must be valid. If it is not valid, an error message is displayed in the shopping cart and
purchase order in SAP SRM.
In documents maintained by bidders or suppliers (for example, RFx responses) and in live
auctions, the revision level is displayed only; bidders and suppliers cannot enter or change
the revision level, or check for existing values of the revision level in the SAP ERP back end.

SAP SRM 2007 38


Release Notes 31.01.2008

Currency on Item Level for RFx (New)


Use
As of SAP SRM 2007 SP02, as a purchaser, you can enable bidders in an RFx to choose
between different currencies on item level, if one of the following situations is given:
The follow-on document of the RFx is a Global Outline Agreement (GOA)
A GOA is in renewal
A GOA is in negotiation
In these cases, the currency is provided on item level of the RFx and RFx response. This item
currency is the leading currency for all values maintained on the item level, for example target
value, price, and conditions.
If a response has a currency that is different from the header currency, the response
comparison view has an additional line for response currency per item. Header and item net
value in the response comparison are nevertheless calculated in the RFx header currency.

Global outline agreement is the follow-on document of an RFx


If the follow-on document of an RFx is specified to be a contract, you can, as a purchaser,
define whether currency should be allowed on line item level. If this is the case, only GOA is
enabled as follow-on document. In this case, the invited bidders are able to select a currency
on item level in the RFx response. Since there is no preceding GOA, all bidders are allowed
to change the currencies proposed by the purchaser when creating their bids.
Global outline agreement is in renewal
As a purchaser you can renew a GOA that has already been released. In this case, a new
RFx is created as a copy of the GOA. All header and item currencies of the preceding GOA
are transferred to the RFx and its RFx responses.
Only the bidders that you have invited additionally can use currencies different from the one in
the original GOA. The actual supplier in the current GOA is not allowed to change the
currency in his bid.
Global outline agreement is in negotiation
As a purchaser, you can negotiate a GOA that has not been released yet. In this case, a new
RFx is created as a copy of the GOA. All header and item currencies of the preceding GOA
are transferred to the RFx and its RFx response.
All suppliers are allowed to change the header or item currency when creating RFx
responses.

SAP SRM 2007 39


Release Notes 31.01.2008

Procurement Card (Enhanced)


Use
As of SAP SRM 2007 SP02, you can also use procurement cards for product categories
enabled for the extended classic scenario. So far, the use of procurement cards has been
limited to the standalone scenario.
Procurement cards are a payment method ideal for making small payments. A bank or card
institute issues a procurement card to a company. The company authorizes selected users to
pay with this card. Users place orders with a supplier, who requests authorization from the
bank. The bank then sends a consolidated statement to the company where the required
approvals are then carried out. The account statement is reconciled with purchasing data.
The company then issues payment to the bank.
You can select Procurement Card as a payment method on the Basic Data tab of the
shopping cart. It is possible to distribute costs, for example split costs across multiple cost
centers. Later in the reconciliation process, you can change the account you have assigned in
the shopping cart.
As of SAP SRM 2007, the procurement card number is encrypted wherever it appears, except
on the screen on which you enter or change procurement card master data.

SAP SRM 2007 40


Release Notes 31.01.2008

Background Processing in Sourcing Cockpit (New)


Use
As of SAP SRM 2007, you can use background processing in the sourcing cockpit to process
the following documents:
Purchase orders
RFx
Contracts
Auctions

Background processing improves the performance of the front-end system.


In the Implementation Guide, you can define the number of shopping cart items above which
sourcing cockpit follow-on documents are processed in the background.
Effects on Customizing
The following Implementation Guide (IMG) activities are relevant. You have to enter a number
for the business transaction category Sourcing Cockpit.
Define Threshold Value for Background Processing

SAP SRM 2007 41


Release Notes 31.01.2008

Alerting in Sourcing Cockpit (New)


Use
As of SAP SRM 2007 SP02 you can use alerting in the sourcing cockpit. Alerting can be
used:
During background processing of documents. If an error occurs during background
processing, an alert is displayed in the universal worklist (UWL). You can access the
shopping cart that caused the problem from this alert message.
After a user has set the status of a shopping cart item to complete with the complete
items pushbutton in the sourcing cockpit. In this case, the user that created the
shopping cart receives an alert in the UWL.

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.

SAP SRM 2007 42


Release Notes 31.01.2008

Release Notes Support Package 03


SRM Worfklow Framework (Enhanced)
Use
As of SAP SRM 2007 SP03, the new workflow framework provides the following features:
Adding reviewers
It is now possible to add reviewers to the approval process. Reviewers can follow the
entire approval process for the document. They can display and create attachments
and notes, and they can insert further reviewers. The following options are available:
The system can add reviewers automatically based on rules that you have
defined using the IMG activity Define Process Levels. The Business Add-In
(BAdI) Define Reviewers (/SAPSRM/BD_WF_REVIEWER_RULE) is provided to
assign documents to groups of agents for review.
Document creators, approvers, and reviewers can add ad hoc reviewers. The
BAdI Adjust Search Help for Reviewer (/SAPSRM/BD_WF_REVIEWER_F4)
allows you to specify who is authorized to add ad hoc reviewers and who can be
added as an ad hoc reviewer.
Offline approval
In approval processes for shopping carts, approvers can now process their work items
offline in an e-mail without logging on to the SRM system. The approval decision is
then sent to the SRM system during the next data synchronization. The BAdI Customer
Enhancement of Offline Approval (BBP_OFFLINE_APP_BADI) allows you to extend
the SRM standard functionality for offline approval of work items.
Multiple account assignment
For items with multiple account assignment, the system can now distribute the
responsibility to approve the item among several approvers depending on the
accounting information. Each of the approvers then gets a work item and must decide
on the item. As soon as one of the approvers rejects the item, the item receives the
status rejected.
To use this function, implement the BAdI Define Agents
(/SAPSRM/BD_WF_RESP_RESOLVER) according to your specific needs.
Approval history for old workflows
It is now possible to display the approval history of workflows that have been started
using the old workflow technology.

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.

The following BAdIs are relevant:


Supplier Relationship Management -> SRM Server -> Business Add-Ins (BAdIs) ->
SAP Business Workflow (New) -> Define Reviewers
Supplier Relationship Management -> SRM Server -> Business Add-Ins (BAdIs) ->
SAP Business Workflow (New) -> Adjust Search Help for Reviewer
Supplier Relationship Management -> SRM Server -> Business Add-Ins (BAdIs) ->
SAP Business Workflow (New) -> Customer Enhancement of Offline Approval

SAP SRM 2007 43


Release Notes 31.01.2008

Supplier Relationship Management -> SRM Server -> Business Add-Ins (BAdIs) ->
SAP Business Workflow (New) -> Define Agents

SAP SRM 2007 44


Release Notes 31.01.2008

Exchange Rate Thresholds (New)


Use
As of SAP SRM 2007 SP03, when you create a purchasing contract, you can reduce the risk
of exchange rate fluctuations by entering:
Currencies in which a purchase order is likely to be created, and
Lower and upper exchange rate threshold
When you save or release the purchasing contract, or when you create a purchase order from
this contract, an information message, warning message, or error message is displayed if the
exchange rate is not between the lower and upper exchange rate threshold. When you create
a purchase order from this contract, an information message, warning message, or error
message is also displayed if the purchase order currency was not maintained in the contract.

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.

Effects on System Administration


System administrators can define the message type (information, warning, or error) in
Customizing for Supplier Relationship Management -> SRM Server -> Cross-Application
Basic Settings -> Message Control -> Influence Message Control. In the standard system,
the message type is set to warning.

See also
On SAP Help Portal (http://help.sap.com), see SAP Supplier Relationship Management ->
Functions -> Contract Management -> Purchasing Contracts.

SAP SRM 2007 45


Release Notes 31.01.2008

Change Documents and Version Management for Conditions


(New)
Use
As of SAP SRM 2007 SP03, change documents are available for conditions. Change
documents are already available for all other fields in contract management. As a result, an
audit trail (change history) is available for all fields in contract management.

When you display a purchasing contract or global outline agreement (GOA) in contract
management, and choose Tracking, you can now also see:

Which conditions were changed at header level or item level


Old value and new value for the conditions
By whom the conditions were changed
When the conditions were changed
You can also select versions of a purchasing contract or GOA, and compare changes to
conditions at header level and item level between these versions. (This requires version
control to be switched on in Customizing for Supplier Relationship Management -> SRM
Server -> Cross-Application Basic Settings -> Switch On Version Control for Purchasing
Documents).

SAP SRM 2007 46


Release Notes 31.01.2008

Supplier Survey Cockpit (New)


Use
As of SAP SRM 2007, you can use the Supplier Survey Cockpit to administrate surveys about
your suppliers' performance. It enables you to perform ad-hoc surveys. This new feature
supplements the event-driven surveys offered in the SAP SRM business scenario Supplier
Evaluation up to now, where the user is asked to fill out a questionnaire after saving an
invoice or a confirmation.

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.

Monitoring is supported by a survey and questionnaire status management function, as well


as survey statistics. The statistics display the number of days until the survey deadline, the
number of submitted questionnaires, the number of answers received and the percentage of
reviewed answers. You can group surveys that belong together content-wise, so that you
easily find related survey data.

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

SAP SRM 2007 47


Release Notes 31.01.2008

Release Notes Support Package 04


SRM Workflow Framework (Enhanced)
As of SAP SRM 2007 SP04, the new approval process framework provides the following
features:
Business Configuration Sets (BC Sets) for workflow precustomizing
You can now use BC Sets to activate predefined Customizing for certain standard
approval processes. BC Sets are available for processes without approval and for
processes with one-step manager approval.
For more information, see SAP Solution Manager under Configuration -> SAP SRM
2007 -> Basic Settings for SAP SRM -> Cross-Application Settings -> SAP Business
Workflow (New) -> Business Configuration Sets for SAP SRM.
New approval process overview
The new approval process overview provides more detailed information about your
approval processes. For example, you can now see all work items that have been
created for a process level, and you can see how the responsible agents are
determined.
You can activate the new approval process overview in Customizing for Supplier
Relationship Management under SRM Server -> Cross-Application Basic Settings ->
SAP Business Workflow (New) -> SRM Workflow Settings -> Workflow Settings ->
Activate New Approval Process Overview.
Changing rejected documents
It is now possible to change a document even after all of its items have been rejected in
the final approval process level. In this case, the requester of a shopping cart, for
example, receives a work item after the final approval process level has been
processed and can then change the document.
To be able to use this function, you must have configured the system so that a work
item is sent to the requester at the process end. You can do so in Customizing for
Supplier Relationship Management under SRM Server -> Cross-Application Basic
Settings -> SAP Business Workflow (New) -> SRM Workflow Settings -> Workflow
Settings -> Define Process Levels.
As an alternative, during shopping cart creation, the requester can set the Work Item to
Requester at Process End indicator.

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

SAP SRM 2007 48


Release Notes 31.01.2008

IMG Structure for Supplier Relationship Management


(Changed)
Use
In SAP SRM 2007, there have been several changes to the structure of the Implementation
Guide for Supplier Relationship Management.

New IMG activities


The following IMG activities were added to the section SRM Server:

Activate Industry Business Solutions, Scenarios, and Country Versions (SP02)

The following IMG activities were added to the section SRM Server -> Technical Basic
Settings:

Maintain Portal Information (SP00)

The following IMG activities were added to the section SRM Server -> Master Data -> Create
Users:

Activate UME SPML Connector (SP03)

The following IMG activities were added to the section SRM Server -> Technical Basic
Settings -> Settings for Supplier Synchronization:

Notes on Supplier Replication (SP01)

Create Supplier Groups (SP01)

Change Supplier Groups (SP01)

Display Supplier Groups (SP01)

Information on Automatic Download from Marketplace (SP01)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings:

Activate grouping logic for locations in GOA (SP00)

Threshold Value for Background Processing (SP00)

Adjust Layout of POWL (SP03)

Enter Alert Threshold Data for Contracts (SP03)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Number Ranges -> SRM Server Number Ranges:

Define Number Ranges for Survey Packages (SP03)

Define Number Ranges for Surveys (SP03)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Event and Event Schema for Alert Management:

Define Recipient of Notifications (SP02)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new):

SAP SRM 2007 49


Release Notes 31.01.2008

Notes on New Workflow Functionality (SP00)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> Basis Workflow Settings:

Maintain Prefix Numbers (SP00)

Maintain Standard Settings for SAP Business Workflow (SP00)

Set Active Plan Version (SP00)

Copy BRF Objects (SP00)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> SRM Workflow Settings -> BRF Settings:

Note on the Following IMG Activities of the BRF (SP00)

Define Events (SP00)

Define Expressions (SP00)

Define Groups (SP00)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> SRM Workflow Settings -> Workflow
Settings:

Activate Workflow (SP00)

Define Filter Values for BAdI 'Define Agents' (SP00)

Define Filter Values for BAdI 'Define Reviewer' (SP03)

Migrate Workflows to BRF (SP01)

Define Process Levels (SP00)

Convert Workflows (SP01)

Object Visualization (SP02)

Activate New Approval Process Overview (SP04)


The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Extensions and Field Control (Personalization)

Configure Generic Field Display on User Interface (SP03)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Extensions and Field Control (Personalization) -> Configure Customer
Fields

Define Customer Fields on Header Level (SP03)

Define Customer Fields on Item Level (SP03)

Define Customer Display-Only Fields on Header Level (SP03)

Define Customer Display-Only Fields on Item Level (SP03)

The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Field Control

SAP SRM 2007 50


Release Notes 31.01.2008

Display Standard Metadata Tables for Header Fields (SP03)

Configure Control for Fields on Header Level (SP03)

Display Standard Metadata Tables for Item Fields (SP03)

Configure Control for Fields on Item Level (SP03)

Display Standard Metadata Tables for Substructure Fields (SP03)

Configure Control for Fields of Substructures (SP03)

The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Define and Assign Actions

Define Actions (SP03)

Assign Actions (SP03)

The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Control for Actions

Display Standard Metadata Tables for Actions on Header Level (SP03)

Configure Control for Actions on Header Level (SP03)

Display Standard Metadata Tables for Actions on Item Level (SP03)

Configure Control for Actions on Item Level (SP03)

Display Standard Metadata Tables for Actions on Substructure Level (SP03)

Configure Control for Actions on Substructure Level (SP03)

The following IMG activities were added to the section SRM Server-> Cross-Application Basic
Settings -> Extensions and Field Control (Personalization) -> Configure Table Extensions

Define Customer Table Extensions on Header Level (SP03)

Define Customer Table Extensions on Item Level (SP03)

Configure Control of User Interface for Extension Tables (SP03)

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

Set Visibility of Table Extensions (SP03)

Configure Control for Fields of Table Extensions (SP03)

Configure Control for Add and Delete Buttons (SP03)

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:

Notes on SAP Records Management (SP01)

Activate Integration with SAP Records Management (SP00)

Define Paths for Link to Records Management System (SP00)

SAP SRM 2007 51


Release Notes 31.01.2008

Create Shortcuts for SRM-RM Integration (SP00)

Define Transport Conditions for Records Management (SP00)

Define Integration Scenarios (SP01)

The following IMG activities were added to the section SRM Server -> Cross-Application
Basic Settings -> Digital Signatures:

Activate Digital Signature (SP01)

Select Algorithm for Digital Signature (SP01)

Select Hash Algorithm for Digital Signature (SP01)

The following IMG activities were added to the section SRM Server -> Country-Specific
Functions:

Assign Tax Groups to Tax Classifications (Product) (SP00)

Define Tax Tariff Codes (SP00)

The following IMG activities were added to the section SRM Server -> RFx

Activate temporary contact person creation (SP00)

The following IMG activities were added to the section SRM Server -> Supplier Evaluation:

Evaluation Category (SP03)

Evaluation Area (SP03)

The following IMG activities were added to the section SRM Server -> Procurement Card:

Define Product Categories for Procurement Card (SP00)

Enhanced IMG activities


The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings :

Define Transaction Types (SP00)

Switch on Version Control for Purchasing Documents (SP00)

Define Threshold Value for Background Processing (SP02)

The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings -> SAP Business Workflow (new) -> SRM Workflow Settings -> Workflow
Settings:

Define Process Levels (SP03)

The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings -> Set Output Actions and Output Format:

Define Actions for Document Output (SP00)

Condition-Dependent Document Output (SP00)

The following IMG activities were enhanced in the section SRM Server -> Cross-Application
Basic Settings -> Account Assignment:

SAP SRM 2007 52


Release Notes 31.01.2008

Define G/L Account for Product Category and Account Assignment Category (SP00)

The following IMG section has been renamed:

Old: SRM Server -> Bid Invitation -> Dynamic Attributes

Define Data Types for Dynamic Attributes

Assign Dynamic Attributes to Groups

Process Dynamic Attributes

New: SRM Server -> RFx -> Questions

Define Data Types for Questions

Assign Questions to Groups

Process Questions

SAP SRM 2007 53


Release Notes 31.01.2008

Business Add-Ins (Changed)


Use
There are new BAdIs in SAP SRM 2007.

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

The following new BAdIs are available:

Input Values for Temporary Contact Person Creation (SP00)

Default Values for Delivery Date and Selection Criteria (SP00)

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 Processor (SP00)

SAP Business Workflow (New) -> Define Deadlines for Events (SP01)

SAP Business Workflow (New) -> Process Level Configuration (SP01)

SAP Business Workflow (New) -> Manage Process Restarts (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) -> Define Reviewers (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)

Digital Signatures -> Define Customer-Specific Document Preview (SP01)


The following BAdIs are obsolete:

Customer Fields -> Customer Field Control

Customer Fields -> Customer Fields with Standard Table Control

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

SAP SRM 2007 54


Release Notes 31.01.2008

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

Interface Configuration -> Determine Screen Variants

Interface Configuration -> Field Control in Purchasing Document

SAP SRM 2007 55

Das könnte Ihnen auch gefallen