Hi Subbareddy2,The error message doesn't come from Convergent Charging.Still, if you need to analyse what happened within Convergent Charging, you can enable the "WS" debug traces in the updater and then reproduce the scenario.This can be done using ...
Hi Anil,We're not really aware of this particular issue, but it strongly seems to be related with the authentication information sent by S/4 to CC.We can't be sure yet, but it might be that S/4 no longer sends all the security SOAP headers required b...
Hi Doris,For more details about the setup on SOM's side, it's best to get advice directly from the SOM experts here.Regarding CC, though: yes, all catalogues are accessible. The only constraint is that the SOAP WS API requires you to define users tha...
Hi Anil,SOM communicates with CC only over the SOAP WS API so, from CC's point of view, you have to configure only web service entry points.To make sure that everything is properly set up on SOM's side, can you please involve a SOM expert?In the mean...
Hi Anil,For this web service to work, it seems that you need to regenerate the consumer proxy on SOM's side, but this is out of Convergent Charging's scope.If not done yet, can you please open a support ticket on the SOM component (CRM-S4-SOM), or tr...
