Standard Communication Method Stuck as E-mail

[Former Member]

We recently added a new company code to our system. I was trying to push one of our catalog vendors, which was set up with a Standard Communication Method of URL, to the new company code. It would not replicate, so on a hunch I changed the standard communication method to E-mail and the vendor then replicated. I changed the standard communication method back to URL in ECC and tried to use BBPUPDVD to change the communication method back to URL, but it will not replicate the change. The vendor is stuck with a communication method of e-mail in SRM, eventhough it shows URL in ECC. I vaguely remember at some point that the programmers changed something so that only vendors with a communication method of E-mail would be replicated to SRM, but I do not know where this change would have been made. Our catalog vendor is now receiving POs via e-mail instead of via URL (XI). This is causing huge issues. Any suggestions?

[laurent_burtaire]

Hello Leah,

URL transmission medium cannot be used in SRM.

Indeed, communication medium is stored in SRM in SEND_MEDIUM field from BBPM_BUT_FRG0061 and BBP_SENDMEDIUM tables.

Value range for corresponding domain (BBP_METYPE) is limited to PRN, MAI, FAX and XML.

In R/3, communication method is stored in DEFLT_COMM field from ADRC table. Here, AD_COMM is the domain: its value range comes from TSAC table

So, to cover your request, implement BBP_TRANSDATA_PREP BAdI definition for PREPARE_REPLICATION_DATA and PREPARE_UPDATE_DATA methods.

For both, when CT_ADRC-DEFLT_COMM changing parameter is equal to 'URL', put 'XML'.

To be sure all is OK during your tests, check FORM set_send_medium_mode (include LBBP_BUPA_VRF06).

Regards.

Laurent.