on 07-06-2017 2:57 PM
We are having a Cloud for Customer tenant which is integrated with a S/4 HANA 1610 system. We would like to prevent replication of prospects (and their relationships) from C4C to S/4 HANA. We have implemented BADI CheckBusinessObjectInstanceProcessIntegrationRelevance to filter out prospects from being replicated to S/4 HANA. Once a prospect is changed into a customer the account is becoming relevant for replication to S/4 HANA. So, this works fine. We do have an issue with the replication of the relationships of this customer:
The relationships (with contacts and other customers) of this customer are not triggered for replication to S/4 HANA after the prospect have been promoted to a customer.
How can we trigger these relationships for replication to S/4 HANA after the prospect has been changed into a customer?
Hi Saurabh,
We're using BADI CheckBusinessObjectInstanceProcessIntegrationRelevance. That's not the issue or question!
The issue was that business partner relationship messages we're not filtered out with this BADI. We have solved that issue now as well with the same BADI.
However we noticed a new issue here. When deleting a relationship between a customer and a prospect still messages are being triggered to S/4 HANA. In S/4 HANA the message will run in error, because the respective prospect doesn't exist in S/4. Does anyone have an idea how to filter out the messages for deletion of a relationship between a prospect and a customer?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please use Enhancement Implementation "CheckBusinessObjectInstanceProcessIntegrationRelevance" for disrupting the replication of prospect from C4C to S4.
Please see this blog for more details;
Thanks
Saurabh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.