• No results found

Logging Off

In document Sap-srm Ref Manual (Page 183-188)

This section explains how to begin using the SAP Supplier Relationship Management (SAP SRM) application in the SAP NetWeaver Portal.

3.6.1 User Self-Registration

Through self-registration, a user can log on and work with the SAP Supplier Relationship Management (SAP SRM) application that is running within SAP NetWeaver Portal.

User self-registration provides business users with the capability to create the required portal user, SAP SRM server user, and business partner within a selected organizational unit. The business user has access to an operational user for his or her daily work while the administrator tracks and manages active user accounts.

Activities

On the logon screen, choose Register Now and enter your user details.

3.6.2 Logging On

You access SAP Supplier Relationship Management (SAP SRM) from the SAP NetWeaver Portal that runs in a Web browser. Depending on administrator configurations, one of the following scenarios occurs once you have launched your portal:

Options for Accessing the Portal

Option Description

Portal for Anonymous Users

If your portal supports anonymous users, you see a portal that displays content approved for anonymous users.

User and Password

If your portal does not support anonymous users (default setting), the

portal Welcome screen opens. You can log on to the portal with the user name and password you have received from the administrator.

Single Sign-On (SSO)

If your administrator has properly set up your portal for client authentication, you can log on using a client certificate. If the certificate has not been mapped to your user ID, you need to map it the first time you log on to the portal.

Procedure

Logging Off

To end your portal session, we recommend clicking Log Off, and not simply closing your browser. Closing the browser leaves the portal still working until it times out.

Note

If you are in the portal as an anonymous user, you do not see a Log Off link. In this case, close the browser to end your portal session.

3.7 Technical Scenarios

SAP Supplier Relationship Management (SAP SRM) is a solution that you can implement in a

heterogeneous system environment that includes SAP systems and other Enterprise Resource Planning (ERP) back-end systems. You must have the components Financial Accounting and Controlling in your system environment.

There are different business scenarios that you can apply, depending on your role as a user and the kind of business you wish to conduct using SAP SRM. You can deploy each of these business scenarios using one of three different technical scenarios listed below.

Note

The scenario you choose depends on the system in which your purchasing department wants to work and, consequently, where you want the follow-on documents to be created.

Features

Classic Scenario

The shopping cart is created and approved in the SAP SRM system. The remainder of the procurement process takes place in the back-end ERP system(s), and all other follow-on documents, such as the purchase order, goods receipt or service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have supplier involvement for the operational procurement business scenarios.

Extended Classic Scenario

The shopping cart is created in the SAP SRM system. The purchase order and follow-on documents are also created there and then replicated to the back-end system. The purchase order in the SAP SRM system is the leading purchase order and cannot be changed in the back-end system. Goods receipts and invoices can be pre-entered in the SAP SRM system or entered directly in the back-end system.

With SAP Supplier Self-Services, you have partial supplier involvement for all your operational procurement scenarios. In these scenarios, you have supplier involvement for the purchase order and the purchase order response.

Standalone Scenario

The shopping cart and purchase order are processed directly in the SAP SRM system. You have no materials management functions in your ERP system and, instead, use those in SAP SRM for all

procurement processes. The final invoice is sent to a back-end accounting system. With SAP Supplier Self-Services, you have complete supplier involvement for all your operational procurement scenarios.

Note

You can also run these scenarios in parallel. To do this, choose — on the basis of the product category

— how you want the goods or services to be processed. This suits customers who already have a productive materials management back-end system, but wish to handle the procurement of some supplies locally and others within the back-end system. This makes sense, for example, if you have already defined a communication interface, such as EDI, to a particular supplier.

To do this, you must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server Technical Basic Settings Define

Backend System for Product Category . If you wish to use different rules, you define them using the Business Add-In (BAdI) BBP_DETERMINE_LOGSYS.

The following table gives an overview of the differences between each of these scenarios in terms of where the main processes occur:

Technical Scenarios

Process Classic Extended Classic Standalone

Shopping Cart

SAP SRM System SAP SRM System SAP SRM System

Approval SAP SRM System SAP SRM System SAP SRM System

Purchase Order

Back-end system SAP SRM System (leading system) and back-end

Invoice Back-end system (can be pre-entered in SAP SRM

Settings for the Purchase Order in the Extended Classic Scenario Synchronization with the Back End

3.8 SAP SRM on One Client in SAP ERP

The above deployment option allows SAP ERP customers to run SAP Supplier Relationship Management (SAP SRM) on the same client as their ERP application. The following SAP SRM scenarios are available:

 Service Procurement

 Self-Service Procurement (classic scenario)

 Strategic Sourcing with RFx

 Strategic Sourcing with Live Auction

 Catalog Content Management

 Plan-Driven Procurement with Supplier Integration

Implementation Considerations

For more information, see SAP Solution Manager under <project name> Configuration SAP SRM

<release> One Client Basic Settings for One Client

Constraints

The deployment option SAP SRM on one client in SAP ERP cannot be used for all SAP SRM business scenarios, nor are all functions supported as described in the SAP SRM documentation.

For exact information on what scenarios and functions are supported for SAP SRM on one client in SAP ERP, see SAP Note 963000.

3.9 Harmonization of Procure-To-Pay within the SAP Business Suite

Procurement processes in your enterprise, from the creation of a purchase requisition or shopping cart up to payment, are optimally supported by the procure-to-pay scenarios that integrate functions of SAP Supplier Relationship Management (SAP SRM) and SAP ERP and allow you to leverage the strengths of both systems to optimize your procurement processes.

The following business scenarios specifically benefit from the harmonization:

 Service Procurement

 Operational Contract Management

 Strategic Sourcing with RFx

Prerequisites

You can use the harmonized processes under the following conditions:

 You are using the classic scenario.

 Your back-end system is SAP enhancement package 4 for SAP ERP 6.0 or higher.

 In Customizing for SAP ERP, you have activated the release-specific version of business function Procurement – SRM Integration.

For example, in SAP enhancement package 4 for SAP ERP 6.0, activate business

function Procurement – SRM Integration(LOG_MM_P2PSE_1). In SAP enhancement package 5 for SAP ERP 6.0, activate business functionProcurement – SRM Integration 2 (LOG_MM_P2PSE_2).

You have installed the release-specific version of Business Package for Buyer and Business Package for Common Parts.

For example, if you are using SAP enhancement package 4 for SAP ERP 6.0, you have

installed Business Package for Buyer 1.4 and Business Package for Common Parts 1.4 If you are using SAP enhancement package 5 for SAP ERP 6.0, you have installed Business Package for Buyer

1.5 and Business Package for Common Parts 1.5.

You are using SAP SRM 7.0 or higher, and in Customizing for SAP Supplier Relationship Management you have defined the SAP systems belonging to your SAP Business Suite system landscape under SRM Server Technical Basic Settings Define System Landscape .

 You are using either the SAP NetWeaver Portal or the SAP NetWeaver Business Client as a single point of entry for users working with the harmonized scenarios running in SAP SRM and SAP ERP.

For more information about the SAP NetWeaver Portal and the SAP NetWeaver Business Client, see SAP Help Portal athttp://help.sap.com under SAP NetWeaver SAP NetWeaver <release>

Library SAP Library Getting Started – Using SAP Software Getting Started .

Features

The following functions are fundamental to the integration of procure-to-pay within the SAP Business Suite:

In document Sap-srm Ref Manual (Page 183-188)