Dear SCN Member,
In order to fully benefit from what SCN has to offer, please register at:
Thank you,
The SCN team
We are improving!
The SCN wiki will not be available for new content submission starting September 11th 6PM CET until September 14th 6PM CET. Please plan your SCN wiki tasks accordingly.
Skip to end of metadata
Go to start of metadata


Welcome to the Sourcing Cockpit WIKI page. Here you will find all general information relating to the sourcing cockpit, for example how the standard system works and what behavior to expect. I will also update this page with any new information, new issues, FAQ's, important notes and KBA's.


Here I will document how the Sourcing Cockpit works as per standard behavior. I have documented the document flow with regard to the sourcing cockpit, what comes into sourcing and what documents can be generated from sourcing. I have detailed the meaning of the source_rel_ind entry, what sources of supply can be assigned and also what BADIs can influence the sourcing behavior.


The Sourcing Cockpit

  • Here the professional purchaser can the best possible source of supply for a requirement
  • Requirements can come form an external system (external requirement) or created in the SRM via shopping cart.
  • SRM is the central purchasing system with a single access point (Sourcing Cockpit or Assign Sources of Supply) to all sourcing relevant information and tools.

The Process Flow of the Sourcing Cockpit

Directly below is the process flow of documents coming in and going out of the sourcing cockpit.


How does my requirement get to the Sourcing Cockpit ?

You will find all the related information on SAP SCN Wiki Sourcing Determination about requirement availability in Sourcing Cockpit.

Sourcing in four steps

STEP 1 - Select Requisition
STEP 2 - Assign Sources of Supply
STEP 3 - Review Drafts
STEP 4 - Summary Screen

Related Content

Related Documents

We have created a number of useful and important KBAs for the sourcing area. These range from explanation of standard behaviors, to common issues and steps on how to overcome these, and also how to documents which contain important configuration settings for certain functionalities. You will find the collected information on SCN Wiki page Knowledge Based Articles for Sourcing.




  1. Very nice Lisa. Please write on REDISTRIBUTION Workload too when you get time.


  2. i dont have system now to check this behavior in ECS mode .

    for ex. INCOMPLETE HELD PO - If the BUYER deletes this incomplete PO , will sc item venture to Cockpit? Have you ever tested this?

    I do aware good PO deletion takes to cockpit if PO has been set to delete and configure for sourcing.


  3. Guest

    Please include Note 1319462 - Sourcing Indicator set after the creation of a contract

  4. Hello Lisa,


    Nice info just to update , if we get an issue related to SC which is stucked beacuse it has got created with Source REL IND status as P( it has Source of supply ) or other than X & Y  and SC is not searchable in SOCO.

    We have to use FM-BBP_PDIGP_DB_DIRECT_UPDATE to update SC for Sourcing indicator as X manually with item level GUID for SC.


    1. Dear Kaustubh,

      Thank you for your comment. If the SOURCE_REL_IND is in not expected status, we need to find a route cause. In case of "P" the transfer is stocked as you can

      se above the indicator entries :


      In Transfer when using SOA transfer

      With FM-BBP_PDIGP_DB_DIRECT_UPDATE you can not directly change SOURCE_REL_IND, because the FM does not contains a commit, and the change will not write to the database. You need  write a Z report with FM-BBP_PDIGP_DB_DIRECT_UPDATE call. Please note that FM-BBP_PDIGP_DB_DIRECT_UPDATE is a not released FM. (see note 109533).

      1. Hello Laszlo,

        Hello Laszlo, Thanks for update , But my issue is SC is in Approved status with Sourcing indicator in it as P. how to resolve this issue ?