Provider Contract distribution to CC - SOAP error

[anilm1]

Dear Experts

We've recently upgraded our S4H and CC systems 2023 and sicne then we are struggling to identify the cause of the below issue.

When a subscription order/contract is created in SOM, It is successfully distributed to FICA provider contract but getting failed to distribute to CC. When checking in the fulfilment status, the ODI step " Subscription Contract activation" is in waiting status.

When check the Monitor provider contract replication, I see following issue.

I've checked the webservice configurations for "CO_ISX_CC_CTR_PROV_SERVICES" and it is properly configured.

I wonder what and where is this issue is cominf from.

Please advide and share your suggesions.

@francois_thimon 

Thanks in advance

Anil

[thomas_glaser]

Hi Anil,
I just want to add the S/4 part. If there are changes in authentication on CC side, you must delete the existing logical port and create it again with the correct authentication method in transaction SOAMANAGER.

Best regards,
Thomas

[anilm1]

Hi Thomas, I've tried multiple times deleting the logical port and configured but the issue still persists. When i check the Admin+ logs, giving warning message #000462

[francois_thimon]

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 by CC.

To verify that, can you please refer to the log file of the CC updater?
CC has many log messages for this kind of issues, and reports them with the "WARNING" level (so, directly in the LOG file, not in the TRC file).
So, first, can you please make sure you enable at least the WARNING level in the CC updater, reproduce the issue, and see if you find anything relevant then?

If this is not enough, we suggest to enable the WS tracing domain, and the DEBUG severity (for the CC updater, again).
Then, you'll find additional details, in the updater's TRC file.

To make sure you don't publish any sensitive info here, it's probably best to submit the resulting logs/traces in a customer ticket, but feel free to let us know if we can help further.

Best regards.

François
SAP Convergent Charging Support

[Subbareddy2]

Hi Anil,

I am facing the same issue, while pc transferring i am getting the authorization issue, is it your issue fixed, or any solution for this type for issues.

Thanks

Subbareddy