RFC_CVI_EI_INBOUND_MAIN not Updating field IT_BP_ADDRESS_TELENO~STD_RECIP

[gary_king2]

When using the remote Function call 'RFC_CVI_EI_INBOUND_MAIN' to update Business partner/Customer/Sales details in HANA we seem to hit a problem when trying to update the field STD_RECIP (Indicator: Telephone is SMS-Enabled). This field is essential to us as it indicates whether the phone has SMS capability and can receive SMS type messages. We have debugged the code and can see that it does not take any notice of this field.

I can see no mention of this issue having been raised by any customer, and I can not believe that we are the first to experience this issue.

Everything else works fine with this RFC, which is being called via DS.

[former_member337273]

Hola! Estoy utilizando la BAPI RFC_CVI_EI_INBOUND_MAIN, pero no logro insertar/actualizar datos comerciales como organización de venta, canal y sector (KNVV).

Tienes algún tip o dir.test donde funcione esto?

[gary_king2]

I have just been informed that RFC_CVI_EI_INBOUND_MAIN has been made obsolete!. I am informed by Note 2650140 that this object was never released for general use, which is very odd, because this object is used by the DS object as part of the Rapid deployment/Best Practice solution for loading BP's/Customers/Suppliers.

So, Note 2417298 identifies the alternative solution, but what it does not mention is whether the DS object provided as

part of the Rapid deployment/Best Practice solution has been updated accordingly.

Also, the main reason for raising an incident with SAP was because the telephone SMS flag in the Business area is not being updated, and highly suspect that the same is true for the new solution (Class/method), because I already know that if the 'Post code' is not supplied for the Business partner it will still create the BP, without a warning, but it will show a message when you attempt to edit/use the BP, as it's mandatory. This same issue also happens in the new solution as well as the old, and that's why I suspect this issue I have with the SMS flag will still exist when using the new method.

I am waiting to hear from SAP as to whether their DS object has been updated to use the new suggested method as identified in note 2417298, but if anyone knows ahead of this reply then I would like to hear from you. 😉