Update of vendor - BBP_TRANSDATA_PREP

Question

Hi guys,
Got a question about the update of a vendor.
We're using BBP_VENDOR_SYNC in order to sync the vendor data. However, in one case we want to overrule the default communication method. How to do this?
We've implemented BBP_TRANSDATA_PREP. We've customized method PREPARE_UPDATE_DATA in order to update table BBP_SENDMEDIUM. But somehow it's not working as it should be.
We basically check the address number of the vendor. With this number we check if a certain telex number is used. If so we retrieve the partner guid and with this guid we want to update table BBP_SENDMEDIUM to medium FAX.
During debugging I can see that the table is modified to FAX. But when the program has ended the output medium is reset to another output medium.
Any ideas so far what we're missing?
Regards,
Timo

Answer 1

Hi T. Scholten,
Is there any strong reason why the communication method on the vendor master is not set as "FAX" and with the corresponding FAX numbers?  If this can be done, this is standard SAP while synching the Vendor master data from ECC to SRM.
For any business reason if the communication method on the vendor master cannot be set as "FAX", then we have acheived the similar kind of result on the output medium "XML".
We have used the TELEX communication method (which was never being used in ECC for outputs) and wrote a custom program in SRM to pick the changes/create new vendors of the day and updating a custom table in SRM.
Case 01) For example Vendor A has print and is changed to telex would be picked up by the custom program and updates the custom table with the Vendor id and the communication method as "XML".  The custom program continues and updates the table bbpm_but_frg0061 for the SEND_MEDIUM.
Case 02) Any existing TELEX vendor B is changed to Print or any other output mode would also picked by the program and deletes the entry in the custom table.  The standard Vendor replication job should pick up the changes and set back the updated communication method.
The BBP_VENDOR_SYNC job is scheduled as an hourly background job for 23 times a day with a variant A (capturing the changes between the successive runs of the job) and the last job for the same program is scheduled with another variant B as a sweeper job to pick all the vendor changes during the day (just incase of any slipped vendors between the hourly jobs).
Hope this helps.
DV