Provider contract replication to CC is failing

[former_member644754]

Hi,

We have an issue in replicating provider contract from SOM to CC.

Issue is: When provider contract is created in SOM then only contract is replicated to CC but tolling service is not assigned to that provider contract and therefor contract in CC is not having in charges/charge plan.

However, if we copy that contract in SOM and then submit the same, it creates new provider contract in SOM and everything is replicated to CC along with tolling service. Are we missing something in configuration?

Regards,

Anil

[francois_thimon]

Hi Anil,

This is not a common situation, so the first thing you should do is enable the SOAP WS debug traces in the Convergent Charging updater and reproduce the faulty replication.
This will show you exactly the SOAP query sent by SOM and it'll tell you whether it contains all the expected data (in particular the subscription to the tolling service).

If the subscription does not appear in the SOAP query, then the problem will have to be addressed on SOM's side (you'll probably need assistance from a SOM specialist then).
If, on the other hand, the subscription does appear properly appears in the SOAP query, CC is supposed to take it into account. In that case, please confirm whether it doesn't appear in Core tool, or if it is totally absent, even when you save the contract as an XML document (there was a bug in Core tool a while ago, and some contract items created in the future weren't shown in the GUI).

If you need more assistance with this, you should send the trace file of the updater and the contract saved into an XML file, so we can compare it with the SOAP query.
It's best if you open a BCP ticket for this, especially if your files contain sensitive data.

Best regards.

François
SAP Convergent Charging Support

[former_member644754]

Thank you Francois.

We figured out that replication issue is happening because of wrong cross catalog mapping version assignment in SOM. It is not picking up the correct version (which is released) instead picks 0000 every time and because of that charges are not assigned to contract in CC.

Can you please let me why wrong CCM version is picked? Or where can we check in configuration?

Regards,

Anil

[francois_thimon]

Hi Anil,

Based upon your reply, the issue really seems to be on SOM's side.
If the WS traces from the Convergent Charging updater confirm that the data is properly sent to SOM, then you will need to investigate SOM itself.
Can you please make sure this question already has the proper tags to draw a SOM expert's attention, or possibly open a BCP ticket, if necessary?

If you feel something's wrong with Convergent Charging, don't hesitate to let me know, though.

Best regards.

François
SAP Convergent Charging Support

[chandru_sdn80]

Hi francois.thimon,

I am sorry to ask some inappropriate question .

Would you mind sharing some info on "How to enable the SOAP WS debug traces in the Convergent Charging updater and reproduce the faulty replication"?. Or Any thing related to this will be highly appreciated.

Thanks