Skip to Content
author's profile photo Former Member
Former Member

general SRM questions

Hello All,

I have the following questions. Some help will be appreciated.

1. For PDP with EHP4 with PI/XI do we still need to create entry channels for local Purchasing Org and Employee Org with RFC User???

Also on entry channel can we create just one entry channel for all company codes or have to create separate entry channels for each company code? what is best practice.

2. For Vendor Org structure, do we need to maintain a root Vendor Group and need to maintain sub Vendor Groups for each company code,

before running BBPGETVD for the first time? what is best practise.

Thanks in advance.

Sachin

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Dec 11, 2014 at 02:21 AM

    HI Sachin ,

    Yes Entry channel is needed even in PI when you implement the PDP scenario .

    Entry channel is required for processing the external requirements in SRM System. This Entry channel is created in the Organization Structure anywhere under the root org unit. This Org unit inherits the attributes from the higher level organizational units.

    When a Requisition is pushed by ERP System into SRM System, RFC User which processes this data in SRM is used as Shopping Cart Creator. SRM User is complete only and only if the user has a SU01 id and is integrated in the organizational structure. Due to this reason this RFC user need to be integrated into the org structure under the Organization for Entry Channel.

    As Purchasing Group is used to derive the product responsibility and organizational responsibility while application documents are processed in SRM. Create a local purchasing group in the organization structure and assign the above Entry Channel Organizational Unit in the organizational responsibilities and respective product category(Material group in ERP) in the product responsibilities of this purchasing group

    Vendor group are represented in PPOMV_BBP, where vendor groups (VGs) are entered as organizational objects (including the vendors that belong to the groups).

     The highest level org unit shows the Root for External Vendors which generally represent the Vendor Groups from one source system.

     Next level shows the Vendor Group under that top node

     Under Vendor Group, individual vendors are maintained. Whenever Vendors are created or replicated from R/3, those vendors will get assigned to the vendor group mentioned here.

     Attributes can be maintained at the top level , which get inherited in the Vendor Groups and individual Vendors below in the Vendor Org Model

    It is not necessary to have one VG per vendor, as it used to be in the case for organizational units. System groups the vendors with identical attributes into vendor groups. Positions under the vendor org units will no longer be required.

    If I may explain in simple terms Vendor group can be similar to Org unit in the org structure basically used for grouping . Refer link below

    For vendor group :

    http://help.sap.com/saphelp_srm70/helpdata/en/45/34deb4b02c6bf1e10000000a1553f6/content.htm

    http://help.sap.com/saphelp_srm70/helpdata/en/45/34ddeeb02c6bf1e10000000a1553f6/content.htm?frameset=/en/45/34deb4b02c6bf1e10000000a1553f6/frameset.htm&current_toc=/en/2c/827e41d81d1909e10000000a155106/plain.htm&node_id=135&show_children=false

    Hope it helped.

    Regards

    Vinita

    Add a comment
    10|10000 characters needed characters exceeded

    • You do not maintain in BBPGETVD the company code value anywhere.. while transferring from R/3

      each vendor would have its own company code associated with it .

      You can create vendor groups in SRM using the feature vendor List in SRM. When you create a vendor list you can assign these group of vendors to a product category, contract etc this is the use of the vendor group .. then when they are clubbed together you can assign similar attributes like company code etc to them by transaction PPOMV_BBP .

      There is generally single vendor root organization to which all the vendors are assigned, which you can see in PPOSV_BBP. Within this root org there are vendor groups, corresponding table is HRP1001. Within this table SOBID is vendor number which is linked to vendor group with (fields RSIGN/RELAT) relationship.

      There are some other tables which will show all the other vendor data ...

      BBPM_BUT_FRG0060 and BBPM_BUT_FRG0061 you can make use of the report BBP_CHECK_FRG0060_FRG0061 as well to check if any inconsistency ..

      While replicating the vendor, we always mention vendor root organization. Vendor group is internal grouping and is not referred for vendor determination.

      For PDP always one entry channel is defined and based on the pur grp you can specify the logic as to how to want to determine the pur grp

      It is standard behavior in SRM, PDP scenario, when external requirements are brought into SRM.

      you have to depend on the following BADI to assign the correct P.Org and the P.group.

      BBP_DOC_CHANGE_BADI

      In the BADI , make use of the RFC FM "BAPI_REQUISITION_GETDETAIL" to fetch the details of the PR and assign the P.org and group in the SC>

      Refer links below :

      OSS Note 787426 - Mapping back-end purchasing group to SRM purchasing group

      http://scn.sap.com/thread/1694291

      Hope that clarifies..

      Regards

      Vinita

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.