Complaint replication issue - BDOC State: ERP Adapter call/No Upload to ERP

Question

Hi,
When creating the complaint as an individual document it replicates to the ECC system without fail. But once I create it as a followup of an interaction record it does not replicate.
It is probably because even the interaction record (ZINR) creates BDOC upon save (which is not required, I dont know how to stop BDOC creation from an interaction record). SMW01 results show that ZINR also has the same BDOC errors: ERP Adapter called and No Upload into ERP.
Can anyone explain how to overcome this either by stopping BDOC creation from ZINR or replicating complaint regardless if ZINR was replicated or not.

Answer 1

Hi jacob,
Intially it is doing well which is a Initial Load. Then Comes to Delta Loads. So try to handle everything in the Middleware Mapping Function Modules in R3AC1.
Try to create a ZFunction Module in the Respective Object in R3AC1 and if you go into the Details of that particular Object you will see a Tab Control with different tabs, Among them Select the CRM to R/3 Mapping Function Function Modules  or R/3 to CRM Mapping Function Modules depends on your requirement and add a ZFunction Module there and break the Code.
So Every time the BDOC is created it will stop there when you try to process the Inbound or Outbound Queue in the Debugging mode. You can do this in SMQ1 and SMQ2 and DB click on the entry of your queue and Click on LUW Debugging. So that it will stop at the Z Function added in R3AC1.
So here you will find an entry if it is a Initial Load the structure fielf Initial Load will be 'X' if it s Delta load structure field with Delata Loads = 'X' or 'D' (Not sure) but there will be a indication for Initial and Delta Loads for sure.
Hope this helps