SAP SRM Interview Questions

Dear readers, these SAP SRM Interview Questions have been designed specially to get you acquainted with the nature of questions you may encounter during your interview for the subject of SAP SRM. As per my experience good interviewers hardly plan to ask any particular question during your interview, normally questions start with some basic concept of the subject and later they continue based on further discussion and what you answer −

SAP Supplier Relationship Management SRM is SAP product that facilitates the procurement of goods via a web based platform. Organizations can procure all type of products like direct and indirect material, services and this can be integrated with SAP ERP modules and other non-SAP back end systems for accounting and planning.

SAP SRM allows you to optimize your procurement process to work effectively with suppliers to get long term benefits and also to perform forecasting, procurement cycle and to work with partners. You can reduce the time span and costing of procurement cycle using innovative methods to manage business processes with key suppliers.

SAP Supplier Relationship Management supports the full procurement cycle i.e. starting from source and purchase to pay through complete procurement process with suppliers and effectively managing supplier to build long term relationship.

Catalog Management

Suppliers can easily manage catalog data and can be easily integrated with business processes like accounting, finance and planning.

Procure to Pay Optimization

Using SAP SRP product, you can streamline procure to pay life cycle and improve communication with supplier and cost management.

Self Service Procurement

End users can search products using multiple product catalog and helps them to find and purchase product that are compliant with purchase and procurement policy of the company.

Reporting Functionality

Using SAP Supplier Relationship management, you can create reports related to procurement activities, compliance and contract management, and managing costing in procurement process.

Contract Management

You can manage contracts using centralize secure repository that helps to reduce compliance violations and allows end users to follow business processes during self-service procurement.

Bidding Engine

In SAP SRM portal, you can easily perform search for different products and suppliers. Search criteria is easy to use.

You can also restrict the number of entries in search.

Workflows are used to perform easy approvals of PO’s allows organization to perform goods requisition easy and simple.

SAP SRM: Software Components

There are various application and technology components that are part of SAP Supplier Relationship management product. Application components include component that are required to create RFx and submit bids, for financial management, BI needs, Enterprise portal for application interaction and other various components to perform different functions.

Technology component consists of NetWeaver Process Integration to integrate with SAP and non-SAP external systems, SAP GUI for configuration, and R/3 plugin for master data.

Let’s see each of the component under application and technology in detail −

SAP Supplier Relationship Management Server

SAP SRM server includes SAP SRM server and SAP Bidding engine. SAP SRM is based on SAP NetWeaver application server and is available for different platforms and database. You can check all the releases of SAP SRM on SAP Market place under PAM.

SAP SRM Bidding engine

SAP Bidding engine can be used to create and process requests for bids, bidders can submit bids and other functions in RFx.

Bidding engine defines the rules for bidding and bidders can use it to submit bids in the system.

SAP NetWeaver BI

In SAP SRM spend analysis, BI is primary used and requires Application server ABAP on the same system. It may also require Java Application server and SAP Enterprise portal.

SAP NetWeaver Enterprise Portal

This is used as entry point for users to manage applications and information related to Supplier Relationship management. It provides role based and secure access to applications and services.

Online Transaction Processing System

Various systems can be used for back end transaction processing to manage material and financial queries. SAP ERP system can be used and data exchange occurs between SAP SRM and SAP ERP system.

You can also install SAP SRM as standalone without a backend system.

In a standalone deployment model, all the procurement processing is performed in SAP SRM system and back end accounting system is used for invoice financial processing.

In a Standalone scenario, purchase order management, shopping cart and goods receipt and invoices are processed in SRM system.

When there is no operational backend system for material management and there exists only financial accounting systems in landscape.

When you want to move all procurement activities in SAP SRM system and hence allow companies to decrease the work load on the backend procurement system by transferring buyers which are interested to procure from selected options.

It is recommended for customers who want to maintain only minimal product data and only rely on supplier catalogs.

In a classing deployment model, you process the shopping cart in SAP SRM and supporting documents are processed in backend ERP system.

You can perform goods receipt or invoices in any of the system.

In extended classic deployment model, procurement process takes place in SAP SRM system and PO is generated in SRM system and a read only copy is created in back end ERP system.

You can perform goods receipt or invoices in any of the system as in case of classic scenario.

For those customers who has a strong backend procurement system and where buyers do not want to use multiple systems for their operations.

Consider a customer who wants to use the standalone model for certain indirect materials and routine services, the classic scenario for stock materials to utilize inventory and planning capabilities of backend materials management system, the extended classic scenario to perform effective supplier management to provide response for PO’s.

In SAP SRM, contract is defined as a negotiation between a supplier and an organization for supply of goods and material or delivery of services within defined terms and conditions in a specific time period. These contracts are placed at central secure location to resolve the lack of visibility into contract across the different groups.

This allows you to manage different local contracts with different terms and conditions for the similar type of goods.

Central contract management allows buyers form different part of company from different locations to take advantage of negotiated terms and conditions. The terms and conditions are transitioned into a central contract and to be distributed to local purchasing group to perform procurement process for the company.

To upload the central contracts and to schedule agreements from SAP ERP system to SAP SRM system, you can use program BBP_CONTRACT_INITIAL_UPLOAD. As per your configuration these contracts are loaded and scheduled from ERP to SAP SRM system.

To perform contract search you can use TREX search engine. This search engine is provided with SAP SRM but you have to install it and run program to create indexing for all the available contracts. You should run program BBP_TREX_INDEX_ADMIN that creates a new indexes for existing documents and helps you to perform indexing for all new or changed documents when a contract is saved.

LAC web presentation server is a J2ee based software application. This provides user with an option of real time bidding, real time monitoring and reverse auction options.

Apart from these technology component also includes SAP Process Integrator for integrating processes from different systems, SAP GUI for configuration and R/e plug in for data exchange between one or more R/3 systems and other components.

You can upload contracts in SAP ERP system by going to SAP ERP Central Component → Logistics → Materials Management → Purchasing → Outline Purchase agreements with vendors → Contract → Central Contract → SRM Central Contract


You can see different tabs- header tab, overview tab and distribution tab in a Contract. In overview tab go to fill the item details and general header data. You can fill the below details in a contract −

Target Quantity and value

In this field, you need to enter the target quantity and target value. This defines the quantity which shows the number of units to be purchased from a supplier in a time period.

Release Value

It is defined as accumulated value of all POs against the central contract.

Basic Contract

Now if you define a contract as basic contract, it only contains header data and conditions and you can’t put line items and cannot be distributed to a catalog.

Item Category

Under item category, you can define following options −


When you define item category as normal, it must contain a product category.

Product category

Under product category, you need to define a target value and a product category item always refer to all connected catalogs.

When a contract is expired or released status and you select close contract, the status of contract is set to complete and this is irreversible status.

You can search the completed contracts and use them as template for creating new contracts.

In Negotiation

When a contract is selected for renew and is in saved state, the status of contract is set as in negotiation.

In Renewal

This is set when you select a contract for renew is in released state.

A bid invitation is defined as a request from a buyer to a supplier to submit a quotation for goods or services as per mentioned criteria. Bid invitation is also known as request for quotation RFx.

A request for quotation RFx is an invitation sent to supplier by an organization’s purchase department to submit RFx response for the supply of certain goods under specified terms and condition. RFx document contains information like vendor name, vendor's address, goods quantities and delivery dates for the material. You can create RFx with reference to a purchase requisition and all the information is copied from the purchase requisition. When RFx is created without any reference, you can enter the details manually in RFx document.

Public Bid Invitations

These bid invitations are available to all bidders via a web portal. Bidders can access the url available on web portal to login to SAP bidding engine and there they can enter the bids. If you want some specific bidders to send the bid, you can directly email them the bid invitation.

Restricted Bid invitations

In restricted bid invitations, hyperlink to login to SAP bidding engine is sent to some specific set of bidders via email. Bidders can login to Bidding engine and enter the bid.

You can search for suppliers/bidders from the supplier directories and extend the bid invitation to these bidders in case of public invitation.

A Quotation is defined as a response to RFx where a bidder confirms the goods selling and services to buyers/purchasers as per specific criteria. As part of bid invitation process when the email is triggered, supplier gets the information on the request for quotation. Suppliers start bidding as per the bid invitation and when they submit the bid in SAP Bidding engine, final price is shown. Suppliers can bid till the end date is reached and once bids are closed, purchases can perform a price comparison to get the best supplier and to award the bid, and purchase order can be raised for the best supplier.

When number of bidders are less or purchase feels that there is not a best bid. He can always convert RFx to live auction.

To create a live auction, purchasers can use SAP Bidding engine and auction takes place in Live Auction cockpit. Purchasers can create live auction −

  • Using an Auction template
  • By copying an auction
  • In SRM portal from the Sourcing application

When you convert RFx to an auction, RFx is set to the status Completed and there are no changes that you can make to RFx.

Yes, Procurement functions are seamlessly integrated between SAP ERP and SRM. There are various business functions that allow a fully integrated, end-to-end procurement management solution to improve both compliance and procurement management process as per business requirement. It helps in closing the gap in ERP sourcing functionality using SRM capabilities and provides a common UI for designing integrated procurement processes.

Number ranges must be established for EBP shopping carts as well as any potential purchasing document so that unique numbers can be generated in the backend R/3 system from EBP. The EBP system needs a number range established that automatically takes the next available number and assigns it to the document which will be created in R/3.configuration must also be established in R/3 to correlate with the ranges in EBP so that conflict never arise when purchasing document.

To set attributes that define the users` shopping experience. Examples of such attributes are company code, plant and cost centers that the user can order against, etc.

Business Partner includes stake holders like customer, supplier, etc.

Partner Function includes invoicing party, supplying party, etc.

Customer Shopping Cart

Professional Shopping Cart

Simple shopping Cart

In a standalone scenario, shopping cart and other processing is done in SRM system and only final invoice is sent to backend system for financial accounting.

Professional Shopping Cart Form

In this shopping cart, most of the fields are used by professional buyers and employees. In header section, you have details of shopping cart- cart number, name, status, created date and who has created the shopping cart.

Simple Shopping Cart Form

Like the above shopping cart, you can use a simplified shopping cart form with less number of fields. This is suitable for users who has no experience and limited authorization.

It only depends on the catalogs and no other options are there for purchasing.

To replicate Purchase Organization, Purchase group, material master, vendor master from backend. You can create PO in SRM and replicate PO in the R/3.

It is used for managing supplier performance, implementing technologies, processes, policies, and procedures to support the purchasing process.

This is recommended for purchases with less experience to perform purchasing.

Key steps in Shopping cart −

  • Selecting Goods/Services
  • Shopping Cart
  • Complete and Order
  • Confirmation

Supplier self-service is one of the component in SRM that shortens the procurement life cycle time and reduce the costing of procurement process. In SUS, suppliers are provided with access to purchaser’s procurement system and they are able to provide fast response.

Following are the business process in SAP SRM −

  • Procure to pay - we can integrate catalog based requisition and gain the benefits of e-procurement.

  • Catalog management - manages catalog data as master data that is deeply integrated.

  • Centralize sourcing - gain visibility into the demand for goods and services.

  • Centralized contract management - consolidates contract information.

  • Supplier collaboration - links supplier to our purchasing processes through the supplier portal

By assigning a company code, you can keep financial and legal parameters and reports remain separate in the system.

Supplier evaluation is one of the key process in mainting and improving long term relationship with the suppliers.

SAP supports two main methodologies for Supplier Evaluation −

Event-driven evaluation, triggered from confirmation, invoice, and advanced supplier list.

Ad-hoc surveys using the Supplier Survey Cockpit

To define Evaluation area, go to SRM Server → Supplier Evaluation → Evaluation Area

Using internal number ranges, bids does not have a link to any R/3 purchasing document, they are completely local to the ERP system.

In supplier evaluation, you can divide each survey as per evaluation category. This refers to the questionnaire and the target group.

Example − Delivery, Quality, etc.

SAP SRM performs SUS, catalog management, Procurement, Supplier Evaluation, Central Contracts, shopping carts and Live Auction Cockpit.

Number ranges is used to define for shopping carts and purchasing document for EBP, to generate unique number in R/3 backend system.

  • Live Auction Cockpit on Java Web Server
  • Live Auction Cockpit on ABAP Web Server
  • Live Auction Cockpit on Java Web Server in supplier self-services
  • Live Auction Cockpit on ABAP Web Server in supplier self-services

What is Next?

Further you can go through your past assignments you have done with the subject and make sure you are able to speak confidently on them. If you are fresher then interviewer does not expect you will answer very complex questions, rather you have to make your basics concepts very strong.

Second it really doesn't matter much if you could not answer few questions but it matters that whatever you answered, you must have answered with confidence. So just feel confident during your interview. We at tutorialspoint wish you best luck to have a good interviewer and all the very best for your future endeavor. Cheers :-)