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