cancel
Showing results for 
Search instead for 
Did you mean: 

DRF - Business Partner replication - disable confirmation message

StefanK
Explorer
0 Kudos
236

Hello experts,

I have a question or an issue with Business Partner distribution. We would like to disable the confirmation message to reduce the message load. I have deactivated the corresponding services on the receiver side.

BUSINESSPARTNERSUITEBULKREPLI1

BUSINESSPARTNERRELATIONSHIPSU1

Now we receive the following error on the receiver side: "Error creating the confirmation message: ABAP.PRX_PROTO_NOT_SUPPORTED Proxy protocol for K"

Is it really necessary to enable the confirmation message? Or do you know a way to disable the message?

Thank you in advance,

Stefan

michael_theis
Advisor
Advisor
0 Kudos

Hi,
If you disable the confirmation message, the system is unable to create key mapping. This creates severe data inconsistencies which will sooner or later cause undesired data replication such as inconsistent master data, duplicates, data loss, etc.
It is not really advisable to disable the confirmation message.
Best regards
Michael

Accepted Solutions (0)

Answers (1)

Answers (1)

michael_theis
Advisor
Advisor

If you disable the confirmation message, the system is unable to create key mapping. This creates severe data inconsistencies which will sooner or later cause undesired data replication such as inconsistent master data, duplicates, data loss, etc.
It is not really advisable to disable the confirmation message.
Best regards
Michael

StefanK
Explorer
0 Kudos
Hello Michael, Thank you for your message. I suspected that the confirmation is important, but I couldn't find any information on it. Especially since all fields within the message are marked as optional. However, we are facing the issue that many messages in srt_moni are in the status "WAIT ON SCHEDULER" and the processing takes a very long time. The idea was to disable the confirmation message and this halving the message load. Do you have any other suggestion for where to start with the configuration of the bgRFC queue to speed up the processing? Best regards, Stefan
michael_theis
Advisor
Advisor
0 Kudos
Which package bulk sizes do you use vs. the number of objects to be replicated? Do you use the Key Mapping Web Service in parallel to the BP Web Service?
StefanK
Explorer
0 Kudos

You are referring to the "MDG_KM_MAINTAIN" key mapping web service in this replication, right? We don't use it in this replication.

The number of business partners is approximately 30,000 per day. This is a change replication.

The PACK_SIZE_BULK is set to 1 because of error handling. We cannot restart the messages in srt_moni; if an error occurs for one business partner, the other business partners within the message are also not processed. It is easier to figure out which business partner has an error and resend it.

StefanK
Explorer
0 Kudos

Hello Michael,

do you have any further suggestions for the configuration?

I have shared your concerns regarding the disabling of the Confirmation Message with the team. I am wondering why inconsistencies might occur when all fields in the Confirmation Message are optional and the change pointers are processed only once each. Is there more information available about this process somewhere? Is there a link or a blog related to this?

Best regards,

Stefan

michael_theis
Advisor
Advisor
0 Kudos
Using a bulk enabled web service for sending single records causes a high number of message. Sending 30.000+ messages individually instead of using a pooled and bulk based replication causes work on the sending and receiving systems. If you have data related errors, this means that your different systems don't share the same customizing. You need to harmonize customizing across systems, or use features such as key and value mapping. Regarding disabling the confirmation, as explained above, your biggest issue will be missing key mapping, and the consequences that arise if you don't have any key mapping in your system(s).