Skip to Content

Vendor Organization Structure in SRM


This procedure is for new vendor addition/ extending an existing vendor to a particular Purch. Org.

Vendors in SRM are replicated from ECC R/3 system. Usually a batch job runs in the background that will replicate the vendors from ECC to SRM in periodic routine. Here, in this document I will show you how to manually transfer/replicate a vendor from ECC to SRM.

Standard T. Codes for vendor org structure in SRM:

PPOSV_BBP       : Display Vendor
PPOMV_BBP       : Change Vendor
PPOCV_BBP       : Create Vendor


For a fresh SRM installation the vendor root node is created in transaction PPOCV_BBP. And, if an existing SRM 4.0 system is upgraded to a later release then we need to run report BBP_XPRA_ORGEH_TO_VENDOR_GROUP from SE38 to get the vendor node created under Vendor Org Structure. Once Vendor root is created, we can proceed with the vendor transfer from R/3 to SRM system. Same can be displayed in transaction PPOSV_BBP.

Vendor available.png

In above figure, in right hand side panel window, Vendor Group assignment is the description of the supplier, Code is the supplier number, ID denotes the business partner ID and then comes the validity dates.

Number ranges

For number range definition of vendors, please refer to the following customizing:

1. Cross-Application Components > SAP Business Partner > Business Partner > Basic Settings > Number Ranges and Groupings > Define Number Ranges


Use t-code SNRO and input object ‘BU_PARTNER’. Here you should define an external number range which corresponds to the R/3 numbers.


2. Cross-Application Components > SAP Business Partner > Business Partner> Basic Settings > Number Ranges and Groupings > Define Groupings and Assign Number Ranges


Use t-code BUC2 to check it


For each replication run, you can download the vendors which corresponds to the external number range / grouping which is marked as ‘standard external’.

Creation/Addition of new Supplier in SRM system

New supplier is created in R/3 system and is replicated to SRM via BBPGETVD

Below is the example with step by step procedure for the same-

Create a vendor in ECC system-


Vendor account created successfully-


Now run BBPGETVD in SRM system to get the vendor from ECC to SRM system-


This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start transmission.


Check SLG1 for application log.


Vendor has been transferred successfully from R/3 system to SRM system.


Checking the same in SRM portal –


In this way a new Supplier is integrated to the SRM system manually.

Update Existing Vendor’s Master records

This procedure is for updating data records for any existing vendor or extending a vendor to any purticular Purchasing organization.

T.Code- BBPGETVD – To transfer Vendor from ECC to SRM system. Enter the below required fields-


System represents the backend R/3 system from where vendor data has to be picked. Enter Supplier number and P.Org. To transfer a vendor without ref to any backend Purchasing Org, we need to check without reference to backend purchasing org. box and leave the Purchasing Organization filed blank.

To avoid any duplicity of the vendors check for the address comparison box and proceed.

Object ID is the Vendor Root ID (Refer PPOSA_BBP screenshot)


Select “Only transfer R/3 Numbers” radio button and Click “Start Transfer”. If vendor is not transferred via batch job then it will be transferred instantly else an information pop up will be displayed as shown below-


This, above message, shows that Vendor is already transferred to the SRM system.

Now we need to update the vendor master record using T.Code BBPUPDVD. This will update the vendor backend data from ECC to SRM.

Enter the below mentioned mandatory fields and click start transfer.


This will lead you to another window which will show the total no. of entries given and no. of updates possible. You can display list for your reference. And start update.


Vendor will be updated in SRM system with this.

Now we can check whether it went successfully or not. So for that analyze application log.

Tcode- SLG1 –Give the accurate entry data to populate the required data only.

In case of any update failure, we can find the root cause for vendor update failure here and then it needs to be rectified from ECC front.


Click execute


Messages in red are errors else rest all means it went through successfully.

Log in to portal and specify vendor no. in search criteria.

Vendor available.png

We can find the Purchasing organization details under the Supplier data tab.

Vendor available.png

This shows Supplier has been extended to the SRM system for the required Purchasing organization.

You must be Logged on to comment or reply to a post.