Skip to Content
avatar image
Former Member

Basic flow in SRM

Hi Experts,

Any one please give me the basic flow or Contents in SRM .



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Feb 13, 2007 at 04:53 AM

    Hi Dan,

    The Basic flow of content is like

    Shopping Cart-> PO->Confirmation->Invoice.

    SRM consists of the following Business Scenarios:

    · Self-Service Procurement

    · Service Procurement

    · Plan-Driven Procurement

    · Spend Analysis

    · Strategic Sourcing

    · Catalog Content Management

    · Contract Management

    For details you can see link

    There is another link which provide lots of PPT on SRM processes.|


    Please reward point if this helps.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Dany,

      The flow you are asking:

      Shopping Cart-> PO->Confirmation->Invoice

      will fit in the business scenario : <b>Self service procurement</b>

      This is i would say most desired business scenario for which SRM is used

      as it takes off the load of regular purchasing from operational purchasers

      and they can focus more on strategic decisions.

      With the approval workflows in place the pur docs i.e. SC & PO can be

      submitted to managers for approval and after approval auto POs can be

      created sent to vendors.

      <b>Some inputs on other business scenarios which SRM covers:</b>

      <b>Service Procurement</b>- This would be similar to previous SSP with special

      provision for services like start date,end date, overtime rates, service

      agents, SEA etc. Add on software comp SUS can be used in this scenario for

      direct communication with suppliers.

      <b>Plan-Driven Procurement</b> - has two subpart PM and SI

      the <b>PM</b> scenario is used for working on requirements from external systems

      like PM,PS,MM MRP etc.Here the requirements from these external systems are

      transferred in EBP and startegic purchaser work on those, add vendor , create


      IN <b>SI</b> scenario mostly oriented towards regular procurement. here again

      SUS is required. PO/SA are sent to SUS business partners i.e. vendors

      they can confirm PO, send ASN, and send Invoices against PO

      <b>Spend Analysis</b>- This scenario is for intelligent reporting to be integrated.

      with SRM. Here BW integration with SRM & ECC(if req) is must.

      <b>Strategic Sourcing</b>- This scenario offers 3 subfunctionalities

      1. <b>Supplier self registration</b>- with a sepertae client for ROS you can

      allow suppliers for self registartion.

      2. <b>Bidding</b>- Strat purchaser can float Bid invitation(RFQ),get Bid(quotation)

      in responce from suppliers which can be summitted for approval, and finally

      pur doc PO/contract created

      3. <b>LAC</b>- On line cockpit for strat.purchaser where they can do online

      bidding with many other facilities.

      <b>Catalog Content Management</b>- here you can upload internal/supplier content

      in diff format viz. CSV,XML,BME Catt and can call these catalogs in

      EBP for shopping. You can even shop directly from Supplier websites

      with open catalog interface.

      <b>Contract Management</b>- scenario for working with contract with suppliers

      The sofware components involved with SRM

      SRM server- Central component of SRM A must for SRM

      SUS- component for supplier self services

      CCM- required for maintaing and searching catalogs

      LAC - required for online Bidding/live auction

      BI- business information warehouse reqd. for reporting

      IPC- required to maintain pricing conditions in SRM

      XI- reqd for EBP to talk with external sys

      EP - Common UI for SAP non SAP applications

      SOLMAN - Implementing and problem solving tools

      PI- plug ins with ECC

      NW- netweaver platform where SRM would be installed

      ECC - most common backend of SRM



      <b>Reward if helps</b>