srm overview - part i v1.0

7/21/2019 SRM Overview - Part I V1.0

1/106

IBM Global Business Services

2007 IBM Corporation

SRM Overview

SRM Overview Mar-2011


2/106



Objectives

Upon Completing the course the participant will be able to:

Know the basic structure of SRM

Master data maintenance

Creation of SC and PO

A little bit on workflows

Plan Driven procurement

Know how of Contract Management

2 Mar-2011SRM Overview


3/106



Course Outline

Module 1. SRM Architecture Overview

Module 2. SAP Procurement Portfolio Overview

Module 3. Self-Service Procurement

Module 4. Service Procurement

Module 5. Direct/Plan-Driven Procurement

Module 6. Catalog Content Management

Module 7. Central Sourcing Hub

Module 8. RFx/Auctioning

Module 9. Supplier Collaboration

Module 10. Contract Management



4/106



Module 1: SRM Architecture



5/106



Lesson Overview

This lesson will provide an overview of the different software components that

make up the SAP SRM solution.


6/106



Lesson Objective

After completing this lesson, you will be able to:

Explain the SAP Business Suite

Describe the main features of SAP Supplier Relationship Management

Describe the SRM Application and Technology Components


7/106



Business Scenario

You company will be implementing SAP Supplier Relationship Management

(SAP SRM) and you have been assigned to the project team. As a project team

member, you need to become familiar with the different software components that

make up this solution and their integration points.


8/106



Business Suite 7

No more stovepipes : Flexible end-to-end processes

Deploy as you go : Stepwise projects and installation

No more upgrades : Enhance Pack = Innovation Packages

Dynamic : Re-usable enterprise services

Industry focused : Delivers integrated industry solutions Extensible : Easy expansion beyond ERP



9/106



Companies Require Process Excellence to Meet BusinessRequirements New Reality

Driving a need to Develop loyalty and trust in

Business

Improve execution speed, reduce

complexity, optimize assets

Take action through insight

Requiring Business To: Ensure Global

Process Excellence

Improve Efficiency and

Reduce Costs

Making Better Decisions toCapture Opportunities


10/106



SAP Business Suite 7

Process excellence

Introducing value scenarios

Consolidated industry

capabilities

Reduce cost

Delivering best-run Now

packages

Extending enhancement

packages

Capture opportunities

Creating better insight

Enabling faster flexibility


11/106



SAP Business Suite 7 contd

As part of SAP Business Suite, SAP SRM provides a single, consolidated view ofthe procure-to- pay process including purchasing data from the SAP ERP

application, which can be viewed as a single display via a personalized

dashboard


12/106



Harmonization of Procure-To-Pay within the SAPBusiness Suite

Procurement processes in your enterprise, from the creation of a purchaserequisition 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: Extend sourcing to MM customers and enhance

services via catalogs Central Contract Management: Central contracts repository in both SRM

and ERP

Strategic Sourcing with RFx: Making use of SRM RFx from ERP



13/106



Harmonization of Roles Across SRM and ERP


Traditional Approach With New SAP BusinessSuite

ERP Role SRM Role One Role

ERP SRM ERP SRM

Harmonization of Procure-To-Pay within the SAPBusiness Suite contd


14/106



Harmonized UI via NetWeaver Portal



15/106



Release Strategy for SRM One Client



16/106



Business Suite 7.0: SRM Landscape



17/106



SRM Architecture Overview



18/106



SRM 5.0 was using ITS User Interface technology. SRM 7.0 uses NetWeaver Dynpro User Interface Technology along with the NetWeaver

Enterprise Portal.

For SRM 7.0, the Enterprise Portal is mandatory component.

Internet Pricing Configurator (IPC) 7.0 is part of the component AP 7.0

RFC-> Remote function Call

Data exchange via the application gateway using ABAP Web Dynpro Applications orBusiness Server Pages (BSP) technology

Data exchange via Java applet Live Auction Cockpit WPS (also via application gateway)

The following SAP SRM scenarios, where the Web front-end is based on ABAP WebDynpro technology, work on Data Exchange via the Application Gateway for

Applications with Web Frontends principle:

Self-Service Procurement, Plan-Driven Procurement, Service Procurement, CatalogContent Management, Spend Analysis, Strategic Sourcing with Bidding Engine butwithout LAC WPS & Contract Management

SRM Architecture Overview contd


19/106



SAP NetWeaver Process Integration (PI)

It comprises core components for modeling, designing, automating, and integrating the

processes of one or more application systems.SAP Process Integration requires a dedicated SAP Web Application Server.

This means that running applications in other clients of the same Web AS is not supported.

SAP GUI

The latest release of the SAP GUI software (such as SAP GUI 6.20) can be used with allthe previous SAP component releases.

SAP R/3 Plug-In

The SAP R/3 Plug-In is an interface for exchanging data between one or several SAP R/3systems and other SAP components. All SAP-industry-specific components based on SAPR/3 4.7 and higher SAP R/3 releases require an SAP R/3 Plug-In.

SAP NetWeaver Application Server (JAVA)Application Server (AS) is the application platform of SAP NetWeaver and, consequently, ofthe SAP Business Suite. It provides the technological foundation for all other SAP softwareunits. Since AS comprises the ABAP Engine, Java Engine or both, it can provide a runtimeenvironment for both ABAP and Java applications.

SRM Architecture Overview contd

IBM Gl b l B i S i


20/106



Software Component Matrix

Software Instance Self ServiceProcurement

StrategicSourcing

ServiceProcurement

Analytics(Spend Analysis

& Supplier

Evaluation)

Contract Mgnt

SAP SRM Server M M M O M

SAP NetWeaverBI and BI Content

O O O M O

SAP NetWeaver

EP and EP Content

M M M M M

SAP NetWeaver &

Adobe DocumentServices

M M M N.A. M

SAP NetWeaver PI & XI

Content

M M M N.A. M

SAP NetWeaver

TREX

O O O O O

IBM Gl b l B i S i


21/106



Software Instance Self Service

Procurement

Strategic

Sourcing

Service

Procurement

Analytics Contract

Mgnt

SAP ERP M M M O O

SAP SRM-MDM

Catalog

M O O O O

Legend: O = Optional (Business or Technology enhancement for this scenario)

M = Mandetory (minimum requirement for the deployment variants of this scenario)

N.A.Not applicable to this scenario

Software Component Matrix contd

IBM Gl b l B i S i


22/106



SRM Scenarios


IBM Gl b l B i S i


23/106



Course Overview

There are three basic SRM business and deployment scenarios depending on thekind of business you are in and what process is currently being used.



24/106



Course Objectives

After completing this course, you will be able to:

Explain the different SRM Deployment scenarios

Explain the SRM Business scenarios

Describe the roles utilized in different business scenarios



25/106



Business Example

You need to identify the Deployment and Business scenarios of SRM that willbest meet your company.s requirements.



26/106



Classic

The Classic Integrationscenario supportsend users inretrieving desiredgoods and servicesfrom predefinedcatalogs

The back-endsoftware is theleading applicationfor the PO documentand subsequentdocuments

Goods receipt orinvoice creation cantake place in SAPSRM


Back-end Software

AccountingMaterials

Management

Create

PReq

Create

Purchase

Order

Create

Invoice

CreateGoods

Receipt

Consultinginformation

AccountsPayable

SAP SRM

Create

ShoppingCart

Create

Purchase

Order

CreateInvoice

CreateGoods

Receipt

SAP SRM

Server



27/106



Extended Classic

The extended classic integration scenariosupports the end-to-end procurement cycle

in SAP SRM; a copy of the necessary

documents is stored in the back-end

software

SAP SRM is the leading application for

the PO document and subsequentdocuments

A copy is the maintained in the back-end

software

Changes can only be made to the PO in

SRM. The changes are then replicated to

the copy in the backend

Users of the back-end software have full

visibility; even without touching SAP SRM

Goods receipt or invoice creation can take

place in SAP SRM or the back-end


Back-end Software

AccountingMaterials

Management

Create

PReq

Create

Purchase

Order

Create

Invoice

Create

Goods

Receipt

Consulting

information

Accounts

Payable

SAP SRM

Create

Shopping

Cart

Create

Purchase

Order

Create

Invoice

Create

Goods

Receipt

SAP SRM

Server

Replication

of PO



28/106



Standalone

The stand-alone integration scenariosupports back-end softwareintegration that is require only tokeep the underlying financialsystems synchronized

SAP SRM is the leading application

for the PO document andsubsequent documents

All tasks and activities take placewithin SAP SRM

Purchasing invoices are posted tothe underlying accounts payablesystem


Back-end Software

AccountingMaterials

Management

Create

PReq

Create

Purchase

Order

Create

Invoice

Create

Goods

Receipt

Consulting

information

Accounts

Payable

SAP SRM

Create

Shopping

Cart

Create

Purchase

Order

Create

Invoice

Create

Goods

Receipt

SAP SRM

Server



29/106


2011 IBM Corporation29 Mar-2011SRM Overview

Classic Extended Classic Standalone

Shopping Cart SAP SRM SAP SRM SAP SRM

Approval SAP SRM SAP SRM SAP SRM

Purchase Order Backend system SAP SRM

(leading system)

and backend

system

SAP SRM

Goods Receipt Backend

system (can be

pre-entered in

SAP SRM)

Backend

system (can be

pre-entered in

SAP SRM)

SAP SRM (no

accounting posting

made in backend

system)

Invoice Backend

system (can be

pre-entered in

SAP SRM)

Backend

system (can be

pre-entered in

SAP SRM)

SAP SRM

(accounting

information sent to

backend system)



30/106



Various Business Scenarios




31/106



SRM Roles




32/106



User Mapping

User mapping is used for Single Sign-On (SSO) to back-end systems. Usermapping maps a portal user ID to the user ID of the back-end system.



33/106



Module 2: SAP Procurement Portfolio

Overview




34/106



Lesson Overview

SAP offers a variety of solutions to support the Source to Pay process. This lessonwill introduce you to these different solutions.



35/106


Lesson Objective

After completing this lesson, you will be able to:

Describe the features and integration aspects of SAP E-Sourcing.

Understand the master data maintenance



36/106


Business Example

As a member of the Source to Pay team, you need to understand the otherSAP solutions that can build on your core Supplier Relationship Management

functionality. You want to evaluate the features and benefits of SAP E-Sourcing,

Contract Lifecycle Management and Spend Analytics.



37/106


SAP Procurement Excellence:

Bridges the gap between strategic and operational to create greater time to value,

increased compliance and sustainable savings.


SAP Procurement Portfolio



38/106


SAP Procurement End to End Coverage




39/106


Key Focus Areas



40/106


SAP Spend Analytics

SAP Spend Analytics is SAP.s next-generation end-to-end spend analysis solution.It is an analytical application that helps companies gain a comprehensive view

of their spend data. It aggregates data from heterogeneous sources, supports da

cleansing and classification activities and provides a rich reporting and analysis

environment that offers both out-of-the-box and ad hoc analysis capabilities for

analyzing all spend data.



41/106


SAP e-Sourcing

The SAP E-Sourcing application is Web-based software that helps you maximizesavings by automating and streamlining the strategic sourcing process across allof your supplier expenditures.

SAP E-Sourcing enables you to perform processes such as reporting,collaborative project management, online bidding, contract negotiation, and

contract management.

You can deploy SAP E-Sourcing according to your needs. For example, to get upand running quickly, the application can be hosted by SAP. Or, you can choose todeploy SAP E-Sourcing on your own infrastructure.

Suppliers can be given access to E-Sourcing to participate in processes such as

RFx, Auctions and Contract reviews.




42/106


SAP e-Sourcing contd.

SRM E-SourcingFor Legal clause libraries and document

management functionality in contracts you

need to use Document Builder which as of

SRM 5.0 is not a standard delivered

solution with SRM

The E-Sourcing contracts have an advantage

over the SRM contracts primarily due to the

legal clause libraries and document

management functionality that does not exist

in SRM

No projects exists in SRM The Sourcing Projects can be used to enforcestandard procedures throughout the sourcing

process. The Projects in E-Sourcing are

completely independent of Projects in the ERP

system.

Supports Self service procurement Does not Support Self service procurement

It is integrated to SAP ECC using RFCs It is integrated with the SAP ECC system to

support master data and process integration.

This integration is made possible via PI.



43/106





44/106



The workbench is the default view for all users within E-Sourcing. The workbenchprovides channels of information to help users manage activity within the

application. These include:

Event calendars and To Do lists

Activity / Management reports Search functionality

Shared files

Alerts

Discussions

Training materials

Technical support information

Links to internal and external websites



45/106


SAP Contract Lifecycle Management

The SAP Contract Lifecycle Management (SAP CLM) application supportsyour companys entire contract management process. The application

supports all contract types and can integrate with back-end systems in

support of contract compliance.

SAP Contract Lifecycle Management (CLM) contains all of the features andfunctionality of the Contract Management module within SAP E-Sourcing. Themain difference is that CLM can be used for the creating of Enterprise-widecontracts, such as Sales contracts.

CLM also includes the following features from E-Sourcing:

Projects

Business Partner Management (Supplier Management)

System Libraries (Clauses, Sections and Templates.)



46/106


Master Data Maintenance



47/106



Course Overview:

Understanding the Material /Product Master maintenance

What is a business partner and how are they used

The basic organization structure of the company

Course Objective:

You should be ale to create and use the master data in your SRM system

objectively



48/106


Business Example

Your company needs to utilize the vendors and materials that already exist in its

ERP system within SAP SRM. Therefore, you need to explore the options for

creating and utilizing this master data in SAP SRM. You also need to understand

the role of the Organization Plan in SRM.



49/106



Business Partners:

An internal or external business partner is created in SRM for every person,organization, or group of people that could be involved in a businesstransaction.

InternalRequisitioner, Purchasing company, location, ship-to address,strategic buyer. They are normally attached to the organization structure

ExternalWith role vendor or bidder. They are attached to the contactperson.




50/106


Master Data Maintenance contd

Business Partnerscontd

Addresses: All addresses and address types are saved with the businesspartner. Vendors can be given permission to change their own addresses

Address Type Description

Ordering : The purchase order goes to this address

Ship-from : The goods are sent from this address

Invoicing party : The invoice is sent from this address

Ship-to : Goods are delivered here

Invoice recipient : The invoicing party sends the invoice here Goods recipient : Internal address of the receiving party



51/106



Vendors

Through Backend

BBPGETVD

BBPUPDVD

BBP_VENDOR_SYNC

The vendors themselves are assigned to vendor groups; transactionPPOMV_BBP

Vendor Hierarchies : Vendor Hierarchies can be employed for reporting

purposes (mergers and acquisitions)

Terms of payment and Quality Management systems are only transferred ifthey have first been replicated. To do this, use the following reports:BBP_UPLOAD_PAYMENT_TERMS and BBP_UPLOAD_QM_SYSTEMS.



52/106



Vendor Master in SRM : PPOMV_BBP



53/106


Product Replication:

For Product categories: COMM_HIERARCHY

For direct materials: COMMPR01




54/106


Organization Structure


Root Node

Company CodeCompany CodeCompany Code

Departments Departments Departments

Local

Purchasing

Organization

Backend

Purchasing

Organization

Purchasing

Group

Purchasing

Group

Purchasing

Group

Purchasing

Group



55/106


Organization Structure

Purchasing Organization and Groups in the organization structure can be defined

as follows:



56/106




57/106




58/106


Attributes

Attributes are predefined values that are maintained for the various Org Units.

Company Codes

Plants

Storage Locations

Account Assignment Categories

Cost Centers

Catalogs

Purchasing Document Type

Attributes maintained at the Root Node in the Organization Plan are usuallyinherited by the nodes below it.

Changes or additions to inherited attributes at the lower nodes is also possible.

The attributes are utilized by users creating shopping carts. It may be possible fora user to have multiple values for a give attribute. For example, a user may morethan one account assignment category to choose from when creating a shoppingcart, such as Cost Center, Asset and WBS Element. In this case they could setone of these as their default and choose from the other options as needed.




59/106




60/106



61/106



62/106


Module 3: Self-Service Procurement




63/106


Self Service Procurement:Shopping Carts

Self Service Procurement:

Confirmations

Self Service Procurement:Invoices



64/106




65/106


Self Service ProcurementShopping Carts

Lesson Overview

One of the main goal of SAP SRM implementation is to facilitate the process of

requesting goods and services for the employee

This is achieved by providing a user-friendly Web interface for shopping wherethe user can add items from the catalogues and also by other means like free text

carts, old shopping carts and templates etc.

This lesson details about the process of an employee ordering their own items



66/106


Self Service ProcurementShopping Carts contd

Lesson Objectives

To describe the different ways to create shopping cart in SAP SRM

To explain the purpose of using catalogues in SAP SRM

To describe the approval workflows for shopping carts



67/106



Self Service Procurement empowers the employees of the organization to createand manage their own requirements by creating shopping carts

It helps procurement departments to concentrate on more strategic

purchasing activities

Helps to abolish manual paper-based process which are error prone

Helps to reduce the transaction costs which are extremely high as compared

to the values of goods and services

Ensures compliance and reduces process costs by decentralizing the

purchasing process while maintaining central control with SAP Business

Workflow



68/106



Self Service Procurement in SAP SRM provides the following:

A purchasing platform that complements a typical ERP based procure-to-pay

process and adds integrated, catalogue based requisitioning to the process

An easy to use procurement environment, empowering every employee in theenterprise to search for and buy items. It also ensures that transactions done

comply with the corporate purchasing policies and internal controls

It helps in decentralization of the process which enables to reduce overhead

and allows purchasing professionals to focus on managing relationshipsinstead of transaction

Role based tasks and workflows that free purchasing professionals to spend

more time on high-value sourcing and procurement tasks



69/106



End users can create their own requisitions without intervention of the purchasing department

Key Features:

Wizard approach for occasional users

Support of direct and indirect business scenarios

Generation of a requisition, reservation or purchase order and even on behalf of other users

Team Purchasing concept

Availability check and assignment of source of supply

Specification of preferred vendor

Contracts and budget checks

Procurement cards

Old shopping carts and Public templates

Attachments and customer fields Ship-to address at item level

Cost Assignment to cost center, assets, orders and projects

Automatic lead time adjustment of delivery date

Distribute account assignment



70/106



Create a Shopping Cart: The employee initiates the shopping process by creating a shopping cart

Employees can fill their shopping cart with goods / services

They can search for a suitable product in the catalogue or can describe the

requirement

They can hold the requirement or can place the order immediately

Catalogues in SAP SRM can be of following types:

Internally hosted catalogues: Purchasing control over the content that is

delivered by the supplier

Internal catalogs: Publishing of stock materials

External supplier catalogs: Its also know as Punch-out catalogs which is

accessed by the internet and managed by the supplier



71/106



Navigation Areas:

The shopping cart has navigational designs to accommodate the needs of the causaluser, the frequent user and the purchaser user

The three interfaces are called wizard, simplified form and extended form

These screens are designed to be used by different category of users based upon thelevel of experience and needs

Below mentioned are the different shopping cart transactions:

Shopping Cart (Wizard): This template is for causal users with step by step instructions.It helps employees find, select and add goods or services to their shopping carts quicklyand easily

Shopping Cart (Professional): This template is used for more experienced users likepurchasers / purchasing assistants. This will have less steps as compared to the wizard

Shopping Cart on behalf of other users: This template helps the purchasers /purchasing assistants to buy goods on behalf of other users

Shopping Cart Templates: It helps to process recurring procurement transactionsefficiently



72/106



Wizard:

The wizard navigational screen is intended for the occasional user who

doesnt spend much time ordering and doesnt get repetitive practice to

become familiar with the screens

It consists of three steps viz: Select goods / service, shopping cart, complete

and order

Users can see only one view at a time and therefore they can easily identify

what stage of the purchasing process they have reached



73/106



Step 1: Select Goods / Services

In this step, users can select products through four methods:

Search catalogs

Reference existing templates

Directly enter an internal product number

Describe requirement



74/106



Step 2: Shopping Cart

Step 2 displays the information

on the screen in concise

format:

The system only displaysthe information that is

actually required for the

purchasing process

You can modify the

information, delete / add

line items, check shopping

cart data forcorrectnessetc.



75/106



Step 3: Complete and Order: Step 3 gives the user the below choices:

Order

Save

Giving meaningful name to the shopping cart

See the approval wokflow

Check the validity of the information



76/106



Step 4: Confirmation:

Step 4 is the final step:

It displays a success message along with the shopping cart number

Print Preview

Shop again

Close



77/106



Purchaser / purchasing assistant template:

The purchaser navigational screen is intended for the purchaser user

It consists of a vertical layered, single screen

This screen format allows the user to see all the steps in the shopping cart

process and quickly jump between area

This screen possesses additional functionality that doesnt exist in the wizard



78/106



The Professional Shopping Cart:



79/106



Additional features in shopping cart:

Account assignment: Cost center / asset / project / order / sales order /network. Also provision for cost distribution (Percentage, quantity or value)

Documents and Attachments: Vendor Text / Internal Note / Attachments

Ship-To Address

Availability: For stock materials only

Source of supply

Approval preview

Procurement cards: Only for local purchase order in standalone scenario

Budget display



80/106



Shopping Cart Status and Processing:

Employees can check the status of the individual items in their shopping carts



81/106



The following statuses exist:

Saved Held / Incomplete

Awaiting Approval Subject to an approval procedure

In Your Inbox View Items

Rejected

Contains Error

My Personal Template: Belongs to a template

Public Template (created centrally): Belongs to a public template

My Favourites (single item): Belongs to your favourite

Open for Confirmation Open for Invoice



82/106



Follow-on documents:

When shopping cart items are completely approved, it gets converted to one

of the below mentioned follow-on documents.

Purchase requisition

Purchase order

Reservation

Goods receipt / Service entry sheets

Invoices



83/106



Changes and Deleting

Changes: Employees can change the shopping cart under the following

conditions:

Follow-on documents are not yet created Shopping cart kept on hold

Shopping cart awaiting approval

Shopping cart has not been accepted

Deleting: Employees can delete the shopping cart if they no longer need the

items they have requested provided the shopping cart has no follow-on

documents created



84/106



Catalog Scenarios

One of the main benefits of an e-procurement solution is the facility to use

catalogs. Catalogs provide a product listing along with extended product

information, including link to manufacturer and supplier data.



85/106



The following catalog scenarios are supported:

External catalogs: Maintained by the vendor and hosted at the vendor site

Multi-supplier catalogs: Managed by a third-party content aggregator / a

marketplace

Catalogs hosted by the customer (Intranet): Managed by the customer itself.

This needs a catalog management tool e.g. SRM-MDM

Internal catalogs: Allows employees to request items from their own stock



86/106



Workflow:

A flexible approval workflow enables organizations to manage the requisitioning ofgoods and services in full compliance with purchasing policies

SAP SRM provides two frameworks for approval workflows:

Application-controlled (Used in SAP SRM 5.0 and earlier versions)

Process-controlled (Introduced in SAP SRM 2007)



87/106



Process Controlled Workflow:

Process Controlled Workflows are approval workflows based on SAP

Business Workflow, in which the modelled or configured process, and not the

application itself, controls the process flow.

A unified workflow template is used, and a process is evaluated by way ofprocess schema containing a set of distinct process levels.

The Business Rule Framework (BRF) can be applied to control further the

process flow.

Process controlled workflows model and carry out approval processes for

purchasing documents, such as shopping carts.

Approval process typically run on several process levels.

Throughout these process levels, a document can require different kinds of

checks and can involve agents with different roles.



88/106



Application Controlled Workflow:

Application Controlled Workflows are approval workflows based on SAP

Business Workflow, in which the application itself is in control over the SAP

Business Workflow templates.

Multiple workflow templates can be used using different start conditions.

Standard Application-Controlled Workflows in SRM include either two levels of

approval, one level of approval or no approval based upon the value of the

shopping cart

In addition to this, Value limit workflow, Value limit n-step workflow, Multi-step

approval workflow, Shopping cart completion workflow, User budget workflow

etc. are also there.

Approval process typically run on several process levels.

Throughout these process levels, a document can require different kinds of

checks and can involve agents with different roles.



89/106



Check Status:

Check status functionality of SAP SRM allows monitoring the status and

workflow of shopping carts and follow-on documents.

Key Features are: Checking the approval status

Changing and editing the shopping carts

Extensive search

Link to follow-on documents

Express confirmation and invoice



90/106


Self Service Procurement: Confirmations



91/106


Self Service ProcurementConfirmations contd

Lesson Overview

This lesson provides an overview of confirmations in SAP Supplier

Relationship Management


Self Service Procurement Confirmations contd


92/106


Lesson Objectives

To outline the different scenarios for confirmations in SAP SRM

To define the roles and their functions for processing confirmations



S f S C f


93/106



Business Example:

This function is used in SAP SRM to confirm the delivery of goods, and enter services rendered and

hours worked.

Confirmation Scenarios:

Goods receipt, Service entry and Time entry are handled by one confirmation scenario

These are replaced by a single document: the confirmation

Confirmations can refer either to purchase orders created in SAP SRM, or to purchase orders

created outside SAP SRM in the back-end system.


S lf S i P t C fi ti td


94/106



Two ways for employees or central goods recipients to save their confirmations:

Confirm Posts a document that has been processed completely.

Save It saves the confirmation as incomplete which can be completed at a later date.

Confirmations can be entered for purchase orders created in local or in backend

systems:

Local purchase orders create local confirmations

Backend purchase orders produce backend goods receipts

You can search for purchase orders that contain items yet to be confirmed or

confirmations that already have been created




95/106



Return Delivery from Confirmations:

Return deliveries can be generated from confirmations

Reasons for the return delivery of goods can be entered

Confirmation Functions: Other functions become available after the confirmation is saved as mentioned below:

DisplayA list of confirmations is displayed

ChangeConfirmations can be changed that are in the status Held.

DeleteConfirmations can be deleted if the status is held, awaiting approval or saved




96/106



Roles in Confirmations:




97/106



There are several groups of users who can process confirmations:

Employees: Employees can confirm the receipt of goods or services they ordered,

modify the account assignment, add items, change confirmations before they are

approved and display confirmations. Confirmations entered by vendors or central

recipients are approved by the requestor

Vendors: Vendors can confirm the delivery of their goods. Service providers can enterservices that they performed

Central Recipients: Central recipients enter confirmations for groups of users. E.g.

Administrators who record all of the receipts for their departments

Internal Dispatchers: Internal dispatchers work at the receiving point. They distribute

the products to the recipients using their room number, or notify the actual receivers by

e-mail that their goods have arrived.



98/106


Self Service Procurement: Invoices


S lf S i P t I i


99/106


Self Service ProcurementInvoices

Lesson Overview

Invoices from vendors can be recorded in SAP SRM to complete the

procurement process


Self Ser ice Proc rement In oices contd


100/106


Self Service ProcurementInvoices contd

Lesson Objectives

To outline the different scenarios for invoices in SAP SRM

To define the roles and their functions for processing invoices


Self Service Procurement Invoices contd


101/106



Invoice scenarios:

In SAP SRM, there are several functions for invoices or credit memos

The documents are created in the local or back-end system, depending on the location of the

previous documents such as purchase orders and confirmations

The approval process may be required based on business requirements

After the invoice is posted and approved or the credit memo is posted, the payment information is

transferred to corresponding back-end systems that contain the components Financial Accounting(FI) and Controlling (CO)




102/106



Invoice for Back-End Purchase Orders:

Invoices can be entered for back-end purchase orders.

The data from the purchase order history is read automatically from the backend

system.

The invoice and the accounting document are posted in the backend system.




103/106



Invoice for Local Purchase Orders:

Invoices can be entered for local purchase orders.

The data from the purchase order history is read automatically from the local SRMsystem.

The quantities ordered and received display in the browser for invoice entry

Only the accounting documents are posted in the backend system

Invoice without Purchase Order Reference:

Invoices can be entered for which no purchase orders or confirmations exist in thesystem.

For these types of invoices, data is entered normally from the vendor invoice that havebeen received by means of fax / paper form.

The invoice remains in SRM system and the accounting information is posted in thebackend system.




104/106



Roles in Invoices:




105/106



Invoice entry is controlled by employees, vendors or accountants depending upon

the business scenarios:

Employee:

Enter invoices and credit memos with or without reference to their purchase orders

Display, delete or reverse their invoices

Approve invoices enter by vendors or accountants

Vendors:

Vendors can enter invoices and credit memos with or without reference to their purchase orders


Send invoice documents in XML format or choose to print, fax or e-mail as the output form

Accountants:

Enter invoices and credit memos centrally with or without reference to purchase orders from

multiple employees


Send invoice documents in XML format or choose to print, fax or e-mail as the output form



106/106

Questions