cancel
Showing results for 
Search instead for 
Did you mean: 

SRM 5.0 - Non-replication of Blocked Vendors from R/3 to EBP

Former Member
0 Kudos

Hi Team,

We are using SAP SRM 5.0 for e-procurement.

Issue:

The R/3 vendor is transferred to SRM for creation of bidder ID for e-procurement. Presently there is no check/warning message in the system while transferring blocked vendor from R/3 to SRM using BBPGETVD.

The blocked vendor while bidding using e-procurement portal gets a warning message that the 'User is blocked or archived'. With this warning message, the panic situation arises and the bidder gets confused while bidding.

Solution:

BADI BBP_TRANSDATA_PREP was implemented. The Error message u2018Vendor is blockedu2019 was given in case of block vendor of SAP R/3 not getting replicated in SAP SRM. This did not work as the message appearing during BBPGETVD was actually the original Message of Message class BBP_BUPA Message No: 030

Original: u201CAll backend descriptions are already assigned in the systemu201D

It was changed to: u201CVendor is already transferred or blockedu201D.

This was tested and was working fine as the Vendor replication was being done individually and not in lots.

The unblocked ones were getting replicated. The blocked ones and the ones that had already got replicated were throwing up the warning message: u201CVendor is already transferred or blockedu201D.

About 5-8 Vendors both blocked and unblocked behaved as was desired. On further testing it was found that the blocked Vendors instead of throwing up the message were moving on to the next screen/stage for transferring of Vendors. On checking it was found that certain Vendors (Blocked) are appearing in an internal table and as such the required warning message is not appearing.

We are unable to comprehend where from are these Blocked Vendors appearing in the internal table?

Alternatively do kindly suggest if there are any other solutions for this issue by way of configuration change or some other method.

Thanks.

Best regards,

Vijay

Accepted Solutions (0)

Answers (1)

Answers (1)

mani_sreedharala
Active Participant
0 Kudos

Hello Vijay,

Make use of the EEWB transaction for the BO vendor replication. You have an abiltiy to set your own attributes on which/what kind of data you want to replicate into SRM from ECC.

All the best.

Regards,

Mani