Skip to Content
avatar image
Former Member

what is local purchase group in SRM

Hi,

I keep reading this word local purchase group in SRM books . what I do not understand is what does it reffers to.....is it a group in org plan where in function there is no purchase group assigned or reffered to backend system.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 13, 2014 at 11:23 AM

    Purchase groups are picked up based on the settings maintained in Responsibility tab of the Purchase group in PPOMA_BBP.

    1.By maintaining Object ID(ID of the user dept node), this Purchase group is responsible to all users belonging to that node.If you do not maintain Product category under Product responsibility then that Purchase group is responsible for all product categories user is selected.

    If you want to maintain an equation that a purchase group is responsible to only certain product categories then maintain those in Responsible product categories section. This will be helpful in certain scenarios like multiple purchase groups are responsible to the same user group and each Purch group looks after only certain product categories.

    A purchasing Group should be assigned to the Pur Org in the hierarchy .

    Functionality wise :

    The Purchasing group and Purchasing Org. determination goes this way:

        First the tree hierarchy from the user position is taken.

        From the hierarchy, the Purchasing Org, Purchasing Group and Company is filtered.

        Find the Purchasing Groups which are responsible for the selected /filtered Purchasing Org and Company.

        Out of these Purchasing Groups find out which has Product categories for the specified backend system.

    Next the purchasing groups responsible for the backend sys/ local logical system  is checked. It may results in many purchasing groups and purchasing organization.

    The system will always assign the first purchasing org. from the list.  This determination is happening in FM BBP_OM_DETERMINE_RESP_PGRP and FM BBP_OM_FIND_SC. This is the standard way of determining default purchasing group and purchasing organization.

    The standard determination can be overwritten by the BADI BBP_PGRP_FIND.

    Difference between SRM and MM pur grp :

    In r/3 Purchase group is not assined to Purchase Group but in SRM Purchase group must be assigned to Purchase organisation.The Shoping card picked the purchase group from org structure in SRM (PPOMA_BBP).

    Depending on what technical scenarios you implement, you may have some Local Purchasing Groups who are responsible for processing Local Purchase Orders. In this case you will need to assign users with a Purchaser role to these Purchasing Groups. These Purchasers will be assigned to the Local Purchase Orders created, dependingon their Organizational and Product Category responsibilities. These Purchaserswill be responsible for processing the Local Purchase Orders and Requirements that are incomplete.So, you can see that in Classic Scenario it is an error to define Local Purchasing Group, and it is no sense to speak about creating PO using local purchasing groups in classic scenario


    Settings :

    -  If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.

    -- If the backend system is an SAP 4.6B or higher, you need to map the purchasing group in SRM to the backend purchase group

    -- Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.

    ---- If a local pur. group and pur. Org. are used, then a valid backend pur. group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.

    Links;

    http://wiki.scn.sap.com/wiki/display/SRM/Purchasing+Group+and+Purchasing+Organization+determination


    pastedImage_4.png (89.5 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Also you have mentioned that in classic scenario we must have backend purchase group assigned


      but then below sentence contradicts the above statement.in standalone case there is no backend system then it means the below statement should be valid for classic / extended case or decoupled so to say


      a local pur. group and pur. Org. are used, then a valid backend pur. group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.